Add reset controller property and bindings header for the
Actions Semi S900 SoC DTS.
Signed-off-by: Manivannan Sadhasivam
---
arch/arm64/boot/dts/actions/s900.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm64/boot/dts/actions/s900.dtsi
Add reset controller property and bindings header for the
Actions Semi S900 SoC DTS.
Signed-off-by: Manivannan Sadhasivam
---
arch/arm64/boot/dts/actions/s900.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm64/boot/dts/actions/s900.dtsi
Add device tree binding constants for Actions Semi S700 SoC Reset
Management Unit (RMU).
Signed-off-by: Manivannan Sadhasivam
Reviewed-by: Rob Herring
---
.../dt-bindings/reset/actions,s700-reset.h| 34 +++
1 file changed, 34 insertions(+)
create mode 100644
Add Reset Management Unit (RMU) support for Actions Semi Owl SoCs.
Signed-off-by: Manivannan Sadhasivam
---
drivers/clk/actions/Kconfig | 1 +
drivers/clk/actions/Makefile | 1 +
drivers/clk/actions/owl-common.h | 2 +
drivers/clk/actions/owl-reset.c | 66
Add reset controller property and bindings header for the
Actions Semi S700 SoC DTS.
Signed-off-by: Manivannan Sadhasivam
---
arch/arm64/boot/dts/actions/s700.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm64/boot/dts/actions/s700.dtsi
Add Reset Management Unit (RMU) support for Actions Semi Owl SoCs.
Signed-off-by: Manivannan Sadhasivam
---
drivers/clk/actions/Kconfig | 1 +
drivers/clk/actions/Makefile | 1 +
drivers/clk/actions/owl-common.h | 2 +
drivers/clk/actions/owl-reset.c | 66
Add reset controller property and bindings header for the
Actions Semi S700 SoC DTS.
Signed-off-by: Manivannan Sadhasivam
---
arch/arm64/boot/dts/actions/s700.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm64/boot/dts/actions/s700.dtsi
Add device tree binding constants for Actions Semi S700 SoC Reset
Management Unit (RMU).
Signed-off-by: Manivannan Sadhasivam
Reviewed-by: Rob Herring
---
.../dt-bindings/reset/actions,s700-reset.h| 34 +++
1 file changed, 34 insertions(+)
create mode 100644
Add device tree binding constants for Actions Semi S900 SoC Reset
Management Unit (RMU).
Signed-off-by: Manivannan Sadhasivam
Reviewed-by: Rob Herring
---
.../dt-bindings/reset/actions,s900-reset.h| 65 +++
1 file changed, 65 insertions(+)
create mode 100644
Add device tree binding constants for Actions Semi S900 SoC Reset
Management Unit (RMU).
Signed-off-by: Manivannan Sadhasivam
Reviewed-by: Rob Herring
---
.../dt-bindings/reset/actions,s900-reset.h| 65 +++
1 file changed, 65 insertions(+)
create mode 100644
Add Reset Controller bindings to clock bindings for Actions Semi Owl
SoCs, S700 and S900.
Signed-off-by: Manivannan Sadhasivam
Reviewed-by: Rob Herring
---
Documentation/devicetree/bindings/clock/actions,owl-cmu.txt | 2 ++
1 file changed, 2 insertions(+)
diff --git
In order to support the reset controller, regmap info needs to
be cached in the private clock descriptor, owl_clk_desc. Hence,
save that and also make the clock descriptor struct non const.
Signed-off-by: Manivannan Sadhasivam
---
drivers/clk/actions/owl-common.c | 3 ++-
Add Reset Controller bindings to clock bindings for Actions Semi Owl
SoCs, S700 and S900.
Signed-off-by: Manivannan Sadhasivam
Reviewed-by: Rob Herring
---
Documentation/devicetree/bindings/clock/actions,owl-cmu.txt | 2 ++
1 file changed, 2 insertions(+)
diff --git
In order to support the reset controller, regmap info needs to
be cached in the private clock descriptor, owl_clk_desc. Hence,
save that and also make the clock descriptor struct non const.
Signed-off-by: Manivannan Sadhasivam
---
drivers/clk/actions/owl-common.c | 3 ++-
This patchset adds Reset Controller (RMU) support for Actions Semi
Owl SoCs, S900 and S700. For the Owl SoCs, RMU has been integrated into
the clock subsystem in hardware. Hence, in software we integrate RMU
support into common clock driver inorder to maintain compatibility. The
syscon approach is
This patchset adds Reset Controller (RMU) support for Actions Semi
Owl SoCs, S900 and S700. For the Owl SoCs, RMU has been integrated into
the clock subsystem in hardware. Hence, in software we integrate RMU
support into common clock driver inorder to maintain compatibility. The
syscon approach is
Looks good. Thanks! I reviewed the series.
Reviewed-by: Dan Carpenter
regards,
dan carpenter
Looks good. Thanks! I reviewed the series.
Reviewed-by: Dan Carpenter
regards,
dan carpenter
Current behaviour of ASoC core w.r.t to component removal is that it
unregisters dependent sound card totally. There is no support to
rebind the card if the component comes back.
Typical use case is DSP restart or kernel modules itself.
With this patch, core now maintains list of cards that are
Current behaviour of ASoC core w.r.t to component removal is that it
unregisters dependent sound card totally. There is no support to
rebind the card if the component comes back.
Typical use case is DSP restart or kernel modules itself.
With this patch, core now maintains list of cards that are
On 10.08.2018 10:49, Cornelia Huck wrote:
> On Thu, 9 Aug 2018 12:06:56 -0400
> Tony Krowiak wrote:
>
>> On 08/09/2018 05:17 AM, Harald Freudenberger wrote:
>>> On 09.08.2018 11:06, Cornelia Huck wrote:
On Wed, 8 Aug 2018 10:44:14 -0400
Tony Krowiak wrote:
> From: Harald
Hi Andrew,
On Fri, Aug 10, 2018 at 2:17 AM Andrey Smirnov wrote:
>
> Add HID quirk driver for Xbox One S controller over bluetooth.
>
> This driver only adds support for rumble. Standard controller
> functionality is exposed by default HID driver.
>
> Cc: Dmitry Torokhov
> Cc: Jiri Kosina
>
On 10.08.2018 10:49, Cornelia Huck wrote:
> On Thu, 9 Aug 2018 12:06:56 -0400
> Tony Krowiak wrote:
>
>> On 08/09/2018 05:17 AM, Harald Freudenberger wrote:
>>> On 09.08.2018 11:06, Cornelia Huck wrote:
On Wed, 8 Aug 2018 10:44:14 -0400
Tony Krowiak wrote:
> From: Harald
Hi Andrew,
On Fri, Aug 10, 2018 at 2:17 AM Andrey Smirnov wrote:
>
> Add HID quirk driver for Xbox One S controller over bluetooth.
>
> This driver only adds support for rumble. Standard controller
> functionality is exposed by default HID driver.
>
> Cc: Dmitry Torokhov
> Cc: Jiri Kosina
>
On Mon, 6 Aug 2018 at 12:53, Valentin Schneider
wrote:
>
> Hi,
>
> On 06/08/18 11:20, Vincent Guittot wrote:
> > Hi Valentin,
> >
> > On Tue, 31 Jul 2018 at 14:33, Valentin Schneider
> > wrote:
> >>
> >> Hi,
> >>
> >> On 31/07/18 13:17, Vincent Guittot wrote:
> >> [...]
>
> This can
On Mon, 6 Aug 2018 at 12:53, Valentin Schneider
wrote:
>
> Hi,
>
> On 06/08/18 11:20, Vincent Guittot wrote:
> > Hi Valentin,
> >
> > On Tue, 31 Jul 2018 at 14:33, Valentin Schneider
> > wrote:
> >>
> >> Hi,
> >>
> >> On 31/07/18 13:17, Vincent Guittot wrote:
> >> [...]
>
> This can
Uwe Kleine-König writes:
> On Thu, Aug 09, 2018 at 02:06:43PM +0200, Esben Haabendal wrote:
>> Uwe Kleine-König writes:
>>
>> > On Mon, Jul 09, 2018 at 11:43:03AM +0200, Esben Haabendal wrote:
>> >> From: Esben Haabendal
>> >>
>> >> Always update the stopped state when busy status have been
Uwe Kleine-König writes:
> On Thu, Aug 09, 2018 at 02:06:43PM +0200, Esben Haabendal wrote:
>> Uwe Kleine-König writes:
>>
>> > On Mon, Jul 09, 2018 at 11:43:03AM +0200, Esben Haabendal wrote:
>> >> From: Esben Haabendal
>> >>
>> >> Always update the stopped state when busy status have been
On Wed, Aug 08, 2018 at 04:23:22PM -0500, Bjorn Helgaas wrote:
> On Wed, Aug 08, 2018 at 11:53:18PM +0800, joeyli wrote:
> > Hi Bjorn,
> >
> > First, thanks for your review!
> >
> > On Mon, Aug 06, 2018 at 04:48:07PM -0500, Bjorn Helgaas wrote:
> > > On Tue, Jul 24, 2018 at 07:01:44PM +0800,
On Wed, Aug 08, 2018 at 04:23:22PM -0500, Bjorn Helgaas wrote:
> On Wed, Aug 08, 2018 at 11:53:18PM +0800, joeyli wrote:
> > Hi Bjorn,
> >
> > First, thanks for your review!
> >
> > On Mon, Aug 06, 2018 at 04:48:07PM -0500, Bjorn Helgaas wrote:
> > > On Tue, Jul 24, 2018 at 07:01:44PM +0800,
On Wed, Aug 08, 2018 at 11:55:48AM -0400, Steven Rostedt wrote:
> Having libtraceevent turn into a proper library has long been asked for.
> I never had time to do it before. Luckily, Tzvetomir was able to spend
> the time to start the preparation. The first thing that needs to be done
> is to
On Wed, Aug 08, 2018 at 11:55:48AM -0400, Steven Rostedt wrote:
> Having libtraceevent turn into a proper library has long been asked for.
> I never had time to do it before. Luckily, Tzvetomir was able to spend
> the time to start the preparation. The first thing that needs to be done
> is to
On Fri, Aug 10, 2018 at 09:57:18AM +0200, Rafael J . Wysocki wrote:
> From: Rafael J. Wysocki
> Subject: [PATCH] cpuidle: menu: Handle stopped tick more aggressively
>
> Commit 87c9fe6ee495 (cpuidle: menu: Avoid selecting shallow states
> with stopped tick) missed the case when the target
On Fri, Aug 10, 2018 at 09:57:18AM +0200, Rafael J . Wysocki wrote:
> From: Rafael J. Wysocki
> Subject: [PATCH] cpuidle: menu: Handle stopped tick more aggressively
>
> Commit 87c9fe6ee495 (cpuidle: menu: Avoid selecting shallow states
> with stopped tick) missed the case when the target
On Wed, 8 Aug 2018 10:44:27 -0400
Tony Krowiak wrote:
> From: Tony Krowiak
>
> Let's call PAPQ(ZAPQ) to zeroize a queue:
>
> * For each queue configured for a mediated matrix device
> when it is released.
>
> Zeroizing a queue resets the queue, clears all pending
> messages for the queue
On Wed, 8 Aug 2018 10:44:27 -0400
Tony Krowiak wrote:
> From: Tony Krowiak
>
> Let's call PAPQ(ZAPQ) to zeroize a queue:
>
> * For each queue configured for a mediated matrix device
> when it is released.
>
> Zeroizing a queue resets the queue, clears all pending
> messages for the queue
From: Bartosz Golaszewski
On non-OF systems spi->controlled_data may be NULL. This causes a NULL
pointer derefence on dm365-evm.
Signed-off-by: Bartosz Golaszewski
---
drivers/spi/spi-davinci.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/spi/spi-davinci.c
From: Bartosz Golaszewski
On non-OF systems spi->controlled_data may be NULL. This causes a NULL
pointer derefence on dm365-evm.
Signed-off-by: Bartosz Golaszewski
---
drivers/spi/spi-davinci.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/spi/spi-davinci.c
On Friday 10 Aug 2018 at 10:41:56 (+0200), Rafael J. Wysocki wrote:
> On Friday, August 10, 2018 10:15:39 AM CEST Quentin Perret wrote:
> > On Thursday 09 Aug 2018 at 23:52:29 (+0200), Rafael J. Wysocki wrote:
> > > I'm a bit concerned that the code here appears to be designed around the
> > >
On Friday 10 Aug 2018 at 10:41:56 (+0200), Rafael J. Wysocki wrote:
> On Friday, August 10, 2018 10:15:39 AM CEST Quentin Perret wrote:
> > On Thursday 09 Aug 2018 at 23:52:29 (+0200), Rafael J. Wysocki wrote:
> > > I'm a bit concerned that the code here appears to be designed around the
> > >
On Fri, Aug 10, 2018 at 04:49:06PM +0800, Leo Yan wrote:
> On Fri, Aug 10, 2018 at 09:22:10AM +0200, Rafael J. Wysocki wrote:
> > On Fri, Aug 10, 2018 at 9:13 AM, wrote:
> > > On Thu, Aug 09, 2018 at 10:47:17PM +0200, Rafael J. Wysocki wrote:
> > >> On Thu, Aug 9, 2018 at 7:20 PM, Leo Yan
On Fri, Aug 10, 2018 at 04:49:06PM +0800, Leo Yan wrote:
> On Fri, Aug 10, 2018 at 09:22:10AM +0200, Rafael J. Wysocki wrote:
> > On Fri, Aug 10, 2018 at 9:13 AM, wrote:
> > > On Thu, Aug 09, 2018 at 10:47:17PM +0200, Rafael J. Wysocki wrote:
> > >> On Thu, Aug 9, 2018 at 7:20 PM, Leo Yan
Changes in v6:
Patch 1:
- nothing changed.
Patch 2, 3:
- added reviewed-by's which were lost when new versions were added.
Patch 4:
- fixed kbuild warning by adding a buffer overflow check in
adxl372_buffer_postenable().
Patch 5, 6:
- nothing changed
Changes in v6:
Patch 1:
- nothing changed.
Patch 2, 3:
- added reviewed-by's which were lost when new versions were added.
Patch 4:
- fixed kbuild warning by adding a buffer overflow check in
adxl372_buffer_postenable().
Patch 5, 6:
- nothing changed
On Thu, 9 Aug 2018 18:27:16 +0200
Pierre Morel wrote:
> On 09/08/2018 13:06, Cornelia Huck wrote:
> > On Wed, 8 Aug 2018 10:44:19 -0400
> > Tony Krowiak wrote:
> >
> >> diff --git a/drivers/s390/crypto/vfio_ap_drv.c
> >> b/drivers/s390/crypto/vfio_ap_drv.c
> >> index d7e39ad..6a827f3 100644
On Thu, 9 Aug 2018 18:27:16 +0200
Pierre Morel wrote:
> On 09/08/2018 13:06, Cornelia Huck wrote:
> > On Wed, 8 Aug 2018 10:44:19 -0400
> > Tony Krowiak wrote:
> >
> >> diff --git a/drivers/s390/crypto/vfio_ap_drv.c
> >> b/drivers/s390/crypto/vfio_ap_drv.c
> >> index d7e39ad..6a827f3 100644
On Thu, 9 Aug 2018 12:06:56 -0400
Tony Krowiak wrote:
> On 08/09/2018 05:17 AM, Harald Freudenberger wrote:
> > On 09.08.2018 11:06, Cornelia Huck wrote:
> >> On Wed, 8 Aug 2018 10:44:14 -0400
> >> Tony Krowiak wrote:
> >>
> >>> From: Harald Freudenberger
> >>>
> >>> Move all the inline
On Thu, 9 Aug 2018 12:06:56 -0400
Tony Krowiak wrote:
> On 08/09/2018 05:17 AM, Harald Freudenberger wrote:
> > On 09.08.2018 11:06, Cornelia Huck wrote:
> >> On Wed, 8 Aug 2018 10:44:14 -0400
> >> Tony Krowiak wrote:
> >>
> >>> From: Harald Freudenberger
> >>>
> >>> Move all the inline
This patch adds the option for the user to select the sampling frequency.
Also, the user can read the available frequencies and read the currently
set frequency via the read_raw function. The frequency can be set via the
write_raw function.
When the frequency is set, the bandwidth is also checked
This patch adds the option for the user to select the sampling frequency.
Also, the user can read the available frequencies and read the currently
set frequency via the read_raw function. The frequency can be set via the
write_raw function.
When the frequency is set, the bandwidth is also checked
From: Crestez Dan Leonard
The regmap API usually assumes that bulk read operations will read a
range of registers but some I2C/SPI devices have certain registers for
which a such a read operation will return data from an internal FIFO
instead. Add an explicit API to support bulk read without
This patch adds the option for the user to select the filter bandwidth. The
user can also read the available bandwidths which are always adjusted to be
at most half of the sampling frequency. Furthermore, the currently selected
bandwidth can be read via the read_raw function, while the write_raw
From: Crestez Dan Leonard
The regmap API usually assumes that bulk read operations will read a
range of registers but some I2C/SPI devices have certain registers for
which a such a read operation will return data from an internal FIFO
instead. Add an explicit API to support bulk read without
This patch adds the option for the user to select the filter bandwidth. The
user can also read the available bandwidths which are always adjusted to be
at most half of the sampling frequency. Furthermore, the currently selected
bandwidth can be read via the read_raw function, while the write_raw
This patch adds support for the adxl372 FIFO. In order to accomplish this,
triggered buffers were used.
The number of FIFO samples which trigger the watermark interrupt can be
configured by using the buffer watermark. The FIFO format is determined by
configuring the scan elements for each axis.
This patch adds support for the adxl372 FIFO. In order to accomplish this,
triggered buffers were used.
The number of FIFO samples which trigger the watermark interrupt can be
configured by using the buffer watermark. The FIFO format is determined by
configuring the scan elements for each axis.
On Fri, Aug 10, 2018 at 09:22:10AM +0200, Rafael J. Wysocki wrote:
> On Fri, Aug 10, 2018 at 9:13 AM, wrote:
> > On Thu, Aug 09, 2018 at 10:47:17PM +0200, Rafael J. Wysocki wrote:
> >> On Thu, Aug 9, 2018 at 7:20 PM, Leo Yan wrote:
>
> [cut]
>
> >> And that will cause the tick to be stopped
On Fri, Aug 10, 2018 at 09:22:10AM +0200, Rafael J. Wysocki wrote:
> On Fri, Aug 10, 2018 at 9:13 AM, wrote:
> > On Thu, Aug 09, 2018 at 10:47:17PM +0200, Rafael J. Wysocki wrote:
> >> On Thu, Aug 9, 2018 at 7:20 PM, Leo Yan wrote:
>
> [cut]
>
> >> And that will cause the tick to be stopped
Add the device tree binding documentation for the ADXL372 3-axis digital
accelerometer.
Signed-off-by: Stefan Popa
Reviewed-by: Rob Herring
---
.../devicetree/bindings/iio/accel/adxl372.txt | 22 ++
MAINTAINERS| 1 +
2 files
Add the device tree binding documentation for the ADXL372 3-axis digital
accelerometer.
Signed-off-by: Stefan Popa
Reviewed-by: Rob Herring
---
.../devicetree/bindings/iio/accel/adxl372.txt | 22 ++
MAINTAINERS| 1 +
2 files
This patch adds basic support for Analog Devices ADXL372 SPI-Bus
Three-Axis Digital Accelerometer.
The device is probed and configured the with some initial default
values. With this basic driver, it is possible to read raw acceleration
data.
Datasheet:
This patch adds basic support for Analog Devices ADXL372 SPI-Bus
Three-Axis Digital Accelerometer.
The device is probed and configured the with some initial default
values. With this basic driver, it is possible to read raw acceleration
data.
Datasheet:
On 08/08/18 at 04:03pm, Mike Galbraith wrote:
> When booting with efi=noruntime, we call efi_runtime_map_copy() while
> loading the kdump kernel, and trip over a NULL efi.memmap.map. Avoid
> that and a useless allocation when the only mapping we can use (1:1)
> is not available.
>
>
On 08/08/18 at 04:03pm, Mike Galbraith wrote:
> When booting with efi=noruntime, we call efi_runtime_map_copy() while
> loading the kdump kernel, and trip over a NULL efi.memmap.map. Avoid
> that and a useless allocation when the only mapping we can use (1:1)
> is not available.
>
>
Hi Quentin,
On Friday, August 10, 2018 10:15:39 AM CEST Quentin Perret wrote:
> Hi Rafael,
>
> On Thursday 09 Aug 2018 at 23:52:29 (+0200), Rafael J. Wysocki wrote:
> > I'm a bit concerned that the code here appears to be designed around the
> > frequency domains concept which seems to be a
Hi Quentin,
On Friday, August 10, 2018 10:15:39 AM CEST Quentin Perret wrote:
> Hi Rafael,
>
> On Thursday 09 Aug 2018 at 23:52:29 (+0200), Rafael J. Wysocki wrote:
> > I'm a bit concerned that the code here appears to be designed around the
> > frequency domains concept which seems to be a
On Thu, Aug 09, 2018 at 09:11:40PM -0700, Guenter Roeck wrote:
> setup_initrd() does not appear to serve a practical purpose other than
> preventing qemu boots with "-initrd" parameter, so let's drop it.
>
> Signed-off-by: Guenter Roeck
Looks good,
Reviewed-by: Christoph Hellwig
On Thu, Aug 09, 2018 at 09:11:40PM -0700, Guenter Roeck wrote:
> setup_initrd() does not appear to serve a practical purpose other than
> preventing qemu boots with "-initrd" parameter, so let's drop it.
>
> Signed-off-by: Guenter Roeck
Looks good,
Reviewed-by: Christoph Hellwig
On Thu, Aug 09, 2018 at 03:19:51PM -0700, Palmer Dabbelt wrote:
> This would be necessary to make non-SMP builds work, but there is
> another error in the implementation of our syscall linkage that actually
> just causes sys_riscv_flush_icache to never build. I've build tested
> this on
On Thu, Aug 09, 2018 at 03:19:51PM -0700, Palmer Dabbelt wrote:
> This would be necessary to make non-SMP builds work, but there is
> another error in the implementation of our syscall linkage that actually
> just causes sys_riscv_flush_icache to never build. I've build tested
> this on
On Fri, Aug 10, 2018 at 06:33:42AM +0800, kernel test robot wrote:
> commit a13c600e15de44ccf03df28d3311ef3cb754ed9b
> Author: Joerg Roedel
> AuthorDate: Wed Aug 8 13:16:40 2018 +0200
> Commit: Thomas Gleixner
> CommitDate: Thu Aug 9 20:42:07 2018 +0200
>
> x86/mm/pti: Move user W+X
On Fri, Aug 10, 2018 at 06:33:42AM +0800, kernel test robot wrote:
> commit a13c600e15de44ccf03df28d3311ef3cb754ed9b
> Author: Joerg Roedel
> AuthorDate: Wed Aug 8 13:16:40 2018 +0200
> Commit: Thomas Gleixner
> CommitDate: Thu Aug 9 20:42:07 2018 +0200
>
> x86/mm/pti: Move user W+X
Dear Friend,
I know that this mail will come to you as a surprise as we have never met
before, but need not to worry as I am contacting you independently of my
investigation and no one is informed of this communication. I need your urgent
assistance in transferring the sum of $11.3million
Dear Friend,
I know that this mail will come to you as a surprise as we have never met
before, but need not to worry as I am contacting you independently of my
investigation and no one is informed of this communication. I need your urgent
assistance in transferring the sum of $11.3million
On 08/10/2018 08:55 AM, Rashmica Gupta wrote:
> On Fri, Aug 10, 2018 at 11:12 AM, Andrew Morton
> wrote:
>>
>> What is the end-user impact of this patch?
>>
>
> Only architectures/setups that allow the user to remove and add memory of
> different sizes or different start addresses from the
On 08/10/2018 08:55 AM, Rashmica Gupta wrote:
> On Fri, Aug 10, 2018 at 11:12 AM, Andrew Morton
> wrote:
>>
>> What is the end-user impact of this patch?
>>
>
> Only architectures/setups that allow the user to remove and add memory of
> different sizes or different start addresses from the
Hi Ravi,
Just to let you know - I hope I've finally bisected all the issues related
to suspend/resume on Samsung Chromebooks with mainline kernel. I did my
tests on Linux next-20180809. The mentioned commit 38ba34a43dbc ("Input:
cros_ec_keyb - mark cros_ec_keyb driver as wake enabled device.")
Hi Ravi,
Just to let you know - I hope I've finally bisected all the issues related
to suspend/resume on Samsung Chromebooks with mainline kernel. I did my
tests on Linux next-20180809. The mentioned commit 38ba34a43dbc ("Input:
cros_ec_keyb - mark cros_ec_keyb driver as wake enabled device.")
On Thu, Aug 9, 2018 at 1:07 AM Jiri Olsa wrote:
>
> On Wed, Aug 08, 2018 at 03:33:20PM -0700, Stephane Eranian wrote:
> > This patch fixes a bug in ordered_event.c:alloc_event().
> > An ordered_event struct was not initialized properly potentially
> > causing crashes later on in free_dup_event()
On Thu, Aug 9, 2018 at 1:07 AM Jiri Olsa wrote:
>
> On Wed, Aug 08, 2018 at 03:33:20PM -0700, Stephane Eranian wrote:
> > This patch fixes a bug in ordered_event.c:alloc_event().
> > An ordered_event struct was not initialized properly potentially
> > causing crashes later on in free_dup_event()
Hi Rafael,
On Thursday 09 Aug 2018 at 23:52:29 (+0200), Rafael J. Wysocki wrote:
> I'm a bit concerned that the code here appears to be designed around the
> frequency domains concept which seems to be a limitation and which probably
> is related to the properties of the current generation of
Hi all,
Changes since 20180809:
The vfs tree lost its build failure but I have still disabled
CONFIG_SAMPLE_STATX.
The ida tree gained a build failure for which I reverted a commit.
Non-merge commits (relative to Linus' tree): 11708
10596 files changed, 498456 insertions(+), 207143
Hi Bart,
On Wednesday 08 August 2018 10:22 PM, Bartosz Golaszewski wrote:
> 2018-08-08 18:44 GMT+02:00 Andrew Lunn :
>> On Wed, Aug 08, 2018 at 06:27:25PM +0200, Bartosz Golaszewski wrote:
>>> 2018-08-08 17:55 GMT+02:00 Wolfram Sang :
On Wed, Aug 08, 2018 at 05:31:22PM +0200, Bartosz
Hi Rafael,
On Thursday 09 Aug 2018 at 23:52:29 (+0200), Rafael J. Wysocki wrote:
> I'm a bit concerned that the code here appears to be designed around the
> frequency domains concept which seems to be a limitation and which probably
> is related to the properties of the current generation of
Hi all,
Changes since 20180809:
The vfs tree lost its build failure but I have still disabled
CONFIG_SAMPLE_STATX.
The ida tree gained a build failure for which I reverted a commit.
Non-merge commits (relative to Linus' tree): 11708
10596 files changed, 498456 insertions(+), 207143
Hi Bart,
On Wednesday 08 August 2018 10:22 PM, Bartosz Golaszewski wrote:
> 2018-08-08 18:44 GMT+02:00 Andrew Lunn :
>> On Wed, Aug 08, 2018 at 06:27:25PM +0200, Bartosz Golaszewski wrote:
>>> 2018-08-08 17:55 GMT+02:00 Wolfram Sang :
On Wed, Aug 08, 2018 at 05:31:22PM +0200, Bartosz
On 8/8/2018 4:33 PM, Geert Uytterhoeven wrote:
Hi Songjun,
On Wed, Aug 8, 2018 at 6:05 AM Wu, Songjun wrote:
On 8/7/2018 3:33 PM, Geert Uytterhoeven wrote:
On Fri, Aug 3, 2018 at 5:04 AM Songjun Wu wrote:
Get serial id from dts.
"#ifdef CONFIG_LANTIQ" preprocessor is used because
On 8/8/2018 4:33 PM, Geert Uytterhoeven wrote:
Hi Songjun,
On Wed, Aug 8, 2018 at 6:05 AM Wu, Songjun wrote:
On 8/7/2018 3:33 PM, Geert Uytterhoeven wrote:
On Fri, Aug 3, 2018 at 5:04 AM Songjun Wu wrote:
Get serial id from dts.
"#ifdef CONFIG_LANTIQ" preprocessor is used because
On 7/24/2018 11:15 PM, Douglas Anderson wrote:
Add both the interface and core clock.
Signed-off-by: Douglas Anderson
(am from https://lore.kernel.org/patchwork/patch/966680/mbox)
---
Changes in v3:
- Removed gcc_parent_names_9 which I had left in (doh!).
Changes in v2:
- Only 19.2, 100,
On 7/24/2018 11:15 PM, Douglas Anderson wrote:
Add both the interface and core clock.
Signed-off-by: Douglas Anderson
(am from https://lore.kernel.org/patchwork/patch/966680/mbox)
---
Changes in v3:
- Removed gcc_parent_names_9 which I had left in (doh!).
Changes in v2:
- Only 19.2, 100,
Note: It is a part time job that won't interrupt your present work or business.
Looking forward to your response.
Best Regards,
Liu Nianzu
HR(Representative Manager)
Beijing Shougang Company Ltd.
No 15,Pingguoyuan Road,Shijingshan District,Beijing
Website: www.sggf.com.cn
On 7/25/2018 9:31 PM, Rob Herring wrote:
On Tue, Jul 24, 2018 at 10:45:12AM -0700, Douglas Anderson wrote:
These clocks will need to be defined in the clock driver and
referenced in device tree files.
Signed-off-by: Douglas Anderson
---
Changes in v3: None
Changes in v2: None
From: Bartosz Golaszewski
We now support nvmem lookups for machine code. Add a lookup for
mac-address.
Signed-off-by: Bartosz Golaszewski
---
arch/arm/mach-davinci/board-da850-evm.c | 16
1 file changed, 16 insertions(+)
diff --git a/arch/arm/mach-davinci/board-da850-evm.c
Note: It is a part time job that won't interrupt your present work or business.
Looking forward to your response.
Best Regards,
Liu Nianzu
HR(Representative Manager)
Beijing Shougang Company Ltd.
No 15,Pingguoyuan Road,Shijingshan District,Beijing
Website: www.sggf.com.cn
On 7/25/2018 9:31 PM, Rob Herring wrote:
On Tue, Jul 24, 2018 at 10:45:12AM -0700, Douglas Anderson wrote:
These clocks will need to be defined in the clock driver and
referenced in device tree files.
Signed-off-by: Douglas Anderson
---
Changes in v3: None
Changes in v2: None
From: Bartosz Golaszewski
We now support nvmem lookups for machine code. Add a lookup for
mac-address.
Signed-off-by: Bartosz Golaszewski
---
arch/arm/mach-davinci/board-da850-evm.c | 16
1 file changed, 16 insertions(+)
diff --git a/arch/arm/mach-davinci/board-da850-evm.c
From: Rafael J. Wysocki
Subject: [PATCH] cpuidle: menu: Handle stopped tick more aggressively
Commit 87c9fe6ee495 (cpuidle: menu: Avoid selecting shallow states
with stopped tick) missed the case when the target residencies of
deep idle states of CPUs are above the tick boundary which may cause
From: Rafael J. Wysocki
Subject: [PATCH] cpuidle: menu: Handle stopped tick more aggressively
Commit 87c9fe6ee495 (cpuidle: menu: Avoid selecting shallow states
with stopped tick) missed the case when the target residencies of
deep idle states of CPUs are above the tick boundary which may cause
On 09/08/18 16:23, Patrick Bellasi wrote:
> On 09-Aug 11:50, Juri Lelli wrote:
> > On 09/08/18 10:14, Patrick Bellasi wrote:
> > > On 07-Aug 14:35, Juri Lelli wrote:
> > > > On 06/08/18 17:39, Patrick Bellasi wrote:
>
> [...]
>
> > > 1) make CAP_SYS_NICE protected the clamp groups, with an
On 09/08/18 16:23, Patrick Bellasi wrote:
> On 09-Aug 11:50, Juri Lelli wrote:
> > On 09/08/18 10:14, Patrick Bellasi wrote:
> > > On 07-Aug 14:35, Juri Lelli wrote:
> > > > On 06/08/18 17:39, Patrick Bellasi wrote:
>
> [...]
>
> > > 1) make CAP_SYS_NICE protected the clamp groups, with an
701 - 800 of 854 matches
Mail list logo