Re: [PATCH v2 3/3] nvme: Enable autonomous power state transitions

On Tue, 2016-08-30 at 14:59 -0700, Andy Lutomirski wrote: > NVME devices can advertise multiple power states.  These states can > be either "operational" (the device is fully functional but possibly > slow) or "non-operational" (the device is asleep until woken up). > Some devices can

Re: [PATCH v2 3/3] nvme: Enable autonomous power state transitions

On Tue, 2016-08-30 at 14:59 -0700, Andy Lutomirski wrote: > NVME devices can advertise multiple power states.  These states can > be either "operational" (the device is fully functional but possibly > slow) or "non-operational" (the device is asleep until woken up). > Some devices can

Re: [v2 PATCH 2/3] clk: rockchip: add dclk_vop_frac ids for vop

Am Freitag, 2. September 2016, 13:58:19 schrieb Chris Zhong: > Hi Heiko > > On 09/02/2016 01:43 PM, Heiko Stübner wrote: > > Am Donnerstag, 1. September 2016, 20:26:24 schrieb Chris Zhong: > >> From: Yakir Yang > >> > >> Export the dclk_vop_frac out, so we can set the

Re: [v2 PATCH 2/3] clk: rockchip: add dclk_vop_frac ids for vop

Am Freitag, 2. September 2016, 13:58:19 schrieb Chris Zhong: > Hi Heiko > > On 09/02/2016 01:43 PM, Heiko Stübner wrote: > > Am Donnerstag, 1. September 2016, 20:26:24 schrieb Chris Zhong: > >> From: Yakir Yang > >> > >> Export the dclk_vop_frac out, so we can set the dclk_vop as the > >> child

[PATCH 2/3] MIPS: OCTEON: add DTS for D-Link DSR-500N

Add DTS for D-Link DSR-500N. Signed-off-by: Aaro Koskinen --- .../mips/boot/dts/cavium-octeon/dlink_dsr-500n.dts | 42 ++ 1 file changed, 42 insertions(+) create mode 100644 arch/mips/boot/dts/cavium-octeon/dlink_dsr-500n.dts diff --git

[PATCH 2/3] MIPS: OCTEON: add DTS for D-Link DSR-500N

Add DTS for D-Link DSR-500N. Signed-off-by: Aaro Koskinen --- .../mips/boot/dts/cavium-octeon/dlink_dsr-500n.dts | 42 ++ 1 file changed, 42 insertions(+) create mode 100644 arch/mips/boot/dts/cavium-octeon/dlink_dsr-500n.dts diff --git

[PATCH 1/3] MIPS: OCTEON: split dlink_dsr-1000n.dts

Split dlink_dsr-1000n.dts to allow reuse with D-Link DSR-500N. Signed-off-by: Aaro Koskinen --- .../boot/dts/cavium-octeon/dlink_dsr-1000n.dts | 45 + .../dts/cavium-octeon/dlink_dsr-500n-1000n.dtsi| 58 ++ 2 files changed, 59

[PATCH 1/3] MIPS: OCTEON: split dlink_dsr-1000n.dts

Split dlink_dsr-1000n.dts to allow reuse with D-Link DSR-500N. Signed-off-by: Aaro Koskinen --- .../boot/dts/cavium-octeon/dlink_dsr-1000n.dts | 45 + .../dts/cavium-octeon/dlink_dsr-500n-1000n.dtsi| 58 ++ 2 files changed, 59 insertions(+), 44

[PATCH 0/3] MIPS: OCTEON: Add support for D-Link DSR-500N router

Hi, D-Link DSR-500N is close to 1000N and with small changes we can support both. A. Aaro Koskinen (3): MIPS: OCTEON: split dlink_dsr-1000n.dts MIPS: OCTEON: add DTS for D-Link DSR-500N MIPS: OCTEON: fix PCI interrupt routing on D-Link DSR-500N

[PATCH 3/3] MIPS: OCTEON: fix PCI interrupt routing on D-Link DSR-500N

Fix PCI interrupt routing on D-Link DSR-500N. Signed-off-by: Aaro Koskinen --- arch/mips/pci/pci-octeon.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/mips/pci/pci-octeon.c b/arch/mips/pci/pci-octeon.c index c258cd4..308d051 100644 ---

[PATCH 0/3] MIPS: OCTEON: Add support for D-Link DSR-500N router

Hi, D-Link DSR-500N is close to 1000N and with small changes we can support both. A. Aaro Koskinen (3): MIPS: OCTEON: split dlink_dsr-1000n.dts MIPS: OCTEON: add DTS for D-Link DSR-500N MIPS: OCTEON: fix PCI interrupt routing on D-Link DSR-500N

[PATCH 3/3] MIPS: OCTEON: fix PCI interrupt routing on D-Link DSR-500N

Fix PCI interrupt routing on D-Link DSR-500N. Signed-off-by: Aaro Koskinen --- arch/mips/pci/pci-octeon.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/mips/pci/pci-octeon.c b/arch/mips/pci/pci-octeon.c index c258cd4..308d051 100644 --- a/arch/mips/pci/pci-octeon.c +++

[PATCH v9 0/5] rk3399 support ddr frequency scaling

rk3399 platform have dfi controller can monitor ddr load, and dcf controller to handle ddr register so we can get the right ddr frequency and make ddr controller happy work(which will implement in bl31). So we do ddr frequency scaling with following flow: kernel

[PATCH v9 4/5] PM / devfreq: rockchip: add devfreq driver for rk3399 dmc

base on dfi result, we do ddr frequency scaling, register dmc driver to devfreq framework, and use simple-ondemand policy. Signed-off-by: Lin Huang Signed-off-by: MyngJoo Ham Reviewed-by: Chanwoo Choi --- Changes in v8: -

[PATCH v9 0/5] rk3399 support ddr frequency scaling

rk3399 platform have dfi controller can monitor ddr load, and dcf controller to handle ddr register so we can get the right ddr frequency and make ddr controller happy work(which will implement in bl31). So we do ddr frequency scaling with following flow: kernel

[PATCH v9 4/5] PM / devfreq: rockchip: add devfreq driver for rk3399 dmc

base on dfi result, we do ddr frequency scaling, register dmc driver to devfreq framework, and use simple-ondemand policy. Signed-off-by: Lin Huang Signed-off-by: MyngJoo Ham Reviewed-by: Chanwoo Choi --- Changes in v8: - None Changes in v8: - do not use ddr_timing node, get ddr timing

[PATCH v9 5/5] drm/rockchip: Add dmc notifier in vop driver

when in ddr frequency scaling process, vop can not do enable or disable operation, since in dcf we check vop clock to see whether vop work. If vop work, dcf do ddr frequency scaling when vop in vblank status, and we need to read vop register to check whether vop go into vblank status. If vop not

[PATCH v9 5/5] drm/rockchip: Add dmc notifier in vop driver

when in ddr frequency scaling process, vop can not do enable or disable operation, since in dcf we check vop clock to see whether vop work. If vop work, dcf do ddr frequency scaling when vop in vblank status, and we need to read vop register to check whether vop go into vblank status. If vop not

[PATCH v9 3/5] Documentation: bindings: add dt documentation for rk3399 dmc

This patch adds the documentation for rockchip rk3399 dmc driver. Signed-off-by: Lin Huang --- Changes in v9: - add ddr timing property to node Changes in v8: - add ddr timing properties Changes in v7: - None Changes in v6: -Add more detail in Documentation Changes in

[PATCH v9 2/5] PM / devfreq: event: support rockchip dfi controller

on rk3399 platform, there is dfi conroller can monitor ddr load, base on this result, we can do ddr freqency scaling. Signed-off-by: Lin Huang Signed-off-by: MyungJoo Ham Acked-by: Chanwoo Choi --- Changes in v9: -None

[PATCH v9 1/5] Documentation: bindings: add dt documentation for dfi controller

This patch adds the documentation for rockchip dfi devfreq-event driver. Signed-off-by: Lin Huang --- Changes in v9: - reorder compatible and reg Changes in v8: - delete a unuse blank line Changes in v7: - None Changes in v6: - None Changes in v5: - None Changes in v4:

[PATCH v9 3/5] Documentation: bindings: add dt documentation for rk3399 dmc

This patch adds the documentation for rockchip rk3399 dmc driver. Signed-off-by: Lin Huang --- Changes in v9: - add ddr timing property to node Changes in v8: - add ddr timing properties Changes in v7: - None Changes in v6: -Add more detail in Documentation Changes in v5: -None Changes in

[PATCH v9 2/5] PM / devfreq: event: support rockchip dfi controller

on rk3399 platform, there is dfi conroller can monitor ddr load, base on this result, we can do ddr freqency scaling. Signed-off-by: Lin Huang Signed-off-by: MyungJoo Ham Acked-by: Chanwoo Choi --- Changes in v9: -None Changes in v8: -None Changes in v7: -access need to *4 to get right DDR

[PATCH v9 1/5] Documentation: bindings: add dt documentation for dfi controller

This patch adds the documentation for rockchip dfi devfreq-event driver. Signed-off-by: Lin Huang --- Changes in v9: - reorder compatible and reg Changes in v8: - delete a unuse blank line Changes in v7: - None Changes in v6: - None Changes in v5: - None Changes in v4: - None Changes in

[PATCH 0/5] rk3399 support ddr frequency scaling

rk3399 platform have dfi controller can monitor ddr load, and dcf controller to handle ddr register so we can get the right ddr frequency and make ddr controller happy work(which will implement in bl31). So we do ddr frequency scaling with following flow: kernel

[PATCH 0/5] rk3399 support ddr frequency scaling

rk3399 platform have dfi controller can monitor ddr load, and dcf controller to handle ddr register so we can get the right ddr frequency and make ddr controller happy work(which will implement in bl31). So we do ddr frequency scaling with following flow: kernel

[PATCH 1/5] Documentation: bindings: add dt documentation for dfi controller

This patch adds the documentation for rockchip dfi devfreq-event driver. Signed-off-by: Lin Huang --- Changes in v8: - delete a unuse blank line Changes in v7: - None Changes in v6: - None Changes in v5: - None Changes in v4: - None Changes in v3: - None Changes in v2:

[PATCH 1/5] Documentation: bindings: add dt documentation for dfi controller

This patch adds the documentation for rockchip dfi devfreq-event driver. Signed-off-by: Lin Huang --- Changes in v8: - delete a unuse blank line Changes in v7: - None Changes in v6: - None Changes in v5: - None Changes in v4: - None Changes in v3: - None Changes in v2: - None Changes in

Re: [v2 PATCH 2/3] clk: rockchip: add dclk_vop_frac ids for vop

Hi Heiko On 09/02/2016 01:43 PM, Heiko Stübner wrote: Am Donnerstag, 1. September 2016, 20:26:24 schrieb Chris Zhong: From: Yakir Yang Export the dclk_vop_frac out, so we can set the dclk_vop as the child of dclk_vop_frac, and then we can start to take use of the

Re: [v2 PATCH 2/3] clk: rockchip: add dclk_vop_frac ids for vop

Hi Heiko On 09/02/2016 01:43 PM, Heiko Stübner wrote: Am Donnerstag, 1. September 2016, 20:26:24 schrieb Chris Zhong: From: Yakir Yang Export the dclk_vop_frac out, so we can set the dclk_vop as the child of dclk_vop_frac, and then we can start to take use of the fractional dividers.

Re: [patch 2/2] i2c: mux: mellanox: add driver

On 2016-08-29 19:36, vad...@mellanox.com wrote: > From: Vadim Pasternak > > This driver allows I2C routing controlled through CPLD select registers on > wide range of Mellanox systems (CPLD Lattice device). > MUX selection is provided by digital and analog HW. Analog part is

Re: [patch 2/2] i2c: mux: mellanox: add driver

On 2016-08-29 19:36, vad...@mellanox.com wrote: > From: Vadim Pasternak > > This driver allows I2C routing controlled through CPLD select registers on > wide range of Mellanox systems (CPLD Lattice device). > MUX selection is provided by digital and analog HW. Analog part is not > under SW

[PATCH] IB/rxe: fix GFP_KERNEL in spinlock context

There is skb_clone(skb, GFP_KERNEL) in spinlock context in rxe_rcv_mcast_pkt(). Found by Linux Driver Verification project (linuxtesting.org). Signed-off-by: Alexey Khoroshilov --- drivers/infiniband/sw/rxe/rxe_recv.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[PATCH] IB/rxe: fix GFP_KERNEL in spinlock context

There is skb_clone(skb, GFP_KERNEL) in spinlock context in rxe_rcv_mcast_pkt(). Found by Linux Driver Verification project (linuxtesting.org). Signed-off-by: Alexey Khoroshilov --- drivers/infiniband/sw/rxe/rxe_recv.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [v2 PATCH 2/3] clk: rockchip: add dclk_vop_frac ids for vop

Am Donnerstag, 1. September 2016, 20:26:24 schrieb Chris Zhong: > From: Yakir Yang > > Export the dclk_vop_frac out, so we can set the dclk_vop as the > child of dclk_vop_frac, and then we can start to take use of > the fractional dividers. > > Signed-off-by: Xing Zheng

Re: [v2 PATCH 2/3] clk: rockchip: add dclk_vop_frac ids for vop

Am Donnerstag, 1. September 2016, 20:26:24 schrieb Chris Zhong: > From: Yakir Yang > > Export the dclk_vop_frac out, so we can set the dclk_vop as the > child of dclk_vop_frac, and then we can start to take use of > the fractional dividers. > > Signed-off-by: Xing Zheng > Signed-off-by: Yakir

Re: [PATCHv2 4/4] staging: android: ion: Add ioctl to query available heaps

On 09/01/2016 11:14 PM, Greg Kroah-Hartman wrote: On Thu, Sep 01, 2016 at 03:40:44PM -0700, Laura Abbott wrote: Ion clients currently lack a good method to determine what heaps are available and what ids they map to. This leads to tight coupling between user and kernel space and headaches. Add

Re: [PATCHv2 4/4] staging: android: ion: Add ioctl to query available heaps

On 09/01/2016 11:14 PM, Greg Kroah-Hartman wrote: On Thu, Sep 01, 2016 at 03:40:44PM -0700, Laura Abbott wrote: Ion clients currently lack a good method to determine what heaps are available and what ids they map to. This leads to tight coupling between user and kernel space and headaches. Add

Re: [RFC PATCH v2 2/3] xpfo: Only put previous userspace pages into the hot cache

On 09/02/2016 04:39 AM, Juerg Haefliger wrote: > Allocating a page to userspace that was previously allocated to the > kernel requires an expensive TLB shootdown. To minimize this, we only > put non-kernel pages into the hot cache to favor their allocation. But kernel allocations do allocate from

Re: [RFC PATCH v2 2/3] xpfo: Only put previous userspace pages into the hot cache

On 09/02/2016 04:39 AM, Juerg Haefliger wrote: > Allocating a page to userspace that was previously allocated to the > kernel requires an expensive TLB shootdown. To minimize this, we only > put non-kernel pages into the hot cache to favor their allocation. But kernel allocations do allocate from

Re: [PATCH -v2 01/10] swap: Change SWAPFILE_CLUSTER to 512

Andrew Morton writes: > On Thu, 01 Sep 2016 16:04:57 -0700 "Huang\, Ying" > wrote: > >> >> } >> >> >> >> -#define SWAPFILE_CLUSTER 256 >> >> +#define SWAPFILE_CLUSTER 512 >> >> #define LATENCY_LIMIT256 >> >> >> > >> > What

Re: [PATCH -v2 01/10] swap: Change SWAPFILE_CLUSTER to 512

Andrew Morton writes: > On Thu, 01 Sep 2016 16:04:57 -0700 "Huang\, Ying" > wrote: > >> >> } >> >> >> >> -#define SWAPFILE_CLUSTER 256 >> >> +#define SWAPFILE_CLUSTER 512 >> >> #define LATENCY_LIMIT256 >> >> >> > >> > What happens to architectures which have different

Re: [Linaro-mm-sig] [PATCHv2 3/4] staging: android: ion: Add an ioctl for ABI checking

On 09/02/2016 02:02 AM, Arnd Bergmann wrote: On Thursday, September 1, 2016 3:40:43 PM CEST Laura Abbott wrote: --- a/drivers/staging/android/ion/ion-ioctl.c +++ b/drivers/staging/android/ion/ion-ioctl.c @@ -22,6 +22,29 @@ #include "ion_priv.h" #include "compat_ion.h" +union ion_ioctl_arg {

Re: [Linaro-mm-sig] [PATCHv2 3/4] staging: android: ion: Add an ioctl for ABI checking

On 09/02/2016 02:02 AM, Arnd Bergmann wrote: On Thursday, September 1, 2016 3:40:43 PM CEST Laura Abbott wrote: --- a/drivers/staging/android/ion/ion-ioctl.c +++ b/drivers/staging/android/ion/ion-ioctl.c @@ -22,6 +22,29 @@ #include "ion_priv.h" #include "compat_ion.h" +union ion_ioctl_arg {

Re: [PATCH] rtc: constify rtc_class_ops structures

On 31/08/2016 at 10:05:25 +0200, Julia Lawall wrote : > Check for rtc_class_ops structures that are only passed to > devm_rtc_device_register, rtc_device_register, > platform_device_register_data, all of which declare the corresponding > parameter as const. Declare rtc_class_ops structures that

Re: [PATCH] rtc: constify rtc_class_ops structures

On 31/08/2016 at 10:05:25 +0200, Julia Lawall wrote : > Check for rtc_class_ops structures that are only passed to > devm_rtc_device_register, rtc_device_register, > platform_device_register_data, all of which declare the corresponding > parameter as const. Declare rtc_class_ops structures that

Re: [PATCH -v2 01/10] swap: Change SWAPFILE_CLUSTER to 512

On Thu, 01 Sep 2016 16:04:57 -0700 "Huang\, Ying" wrote: > >> } > >> > >> -#define SWAPFILE_CLUSTER 256 > >> +#define SWAPFILE_CLUSTER 512 > >> #define LATENCY_LIMIT 256 > >> > > > > What happens to architectures which have different HPAGE_SIZE and/or >

Re: [PATCH -v2 01/10] swap: Change SWAPFILE_CLUSTER to 512

On Thu, 01 Sep 2016 16:04:57 -0700 "Huang\, Ying" wrote: > >> } > >> > >> -#define SWAPFILE_CLUSTER 256 > >> +#define SWAPFILE_CLUSTER 512 > >> #define LATENCY_LIMIT 256 > >> > > > > What happens to architectures which have different HPAGE_SIZE and/or > > PAGE_SIZE? > > For

Re: Memory barrier needed with wake_up_process()?

On Fri, 2 Sep 2016, Paul E. McKenney wrote: > On Fri, Sep 02, 2016 at 02:10:13PM -0400, Alan Stern wrote: > > Paul, Peter, and Ingo: > > > > This must have come up before, but I don't know what was decided. > > > > Isn't it often true that a memory barrier is needed before a call to > >

Re: Memory barrier needed with wake_up_process()?

On Fri, 2 Sep 2016, Paul E. McKenney wrote: > On Fri, Sep 02, 2016 at 02:10:13PM -0400, Alan Stern wrote: > > Paul, Peter, and Ingo: > > > > This must have come up before, but I don't know what was decided. > > > > Isn't it often true that a memory barrier is needed before a call to > >

Re: [PATCH V2 1/5] Documentation: Add support for TI System Control Interface (TI-SCI) protocol

On 09/02/2016 12:07 PM, Nishanth Menon wrote: Rob, On Fri, Sep 2, 2016 at 10:06 AM, Rob Herring wrote: On Tue, Aug 30, 2016 at 08:06:43AM -0500, Nishanth Menon wrote: [...] + +TI-SCI Client Device Node: + + +Client nodes refer to the required TI-SCI

Re: [PATCH V2 1/5] Documentation: Add support for TI System Control Interface (TI-SCI) protocol

On 09/02/2016 12:07 PM, Nishanth Menon wrote: Rob, On Fri, Sep 2, 2016 at 10:06 AM, Rob Herring wrote: On Tue, Aug 30, 2016 at 08:06:43AM -0500, Nishanth Menon wrote: [...] + +TI-SCI Client Device Node: + + +Client nodes refer to the required TI-SCI device using the

Re: [PATCHv2 3/4] staging: android: ion: Add an ioctl for ABI checking

On 09/01/2016 11:10 PM, Greg Kroah-Hartman wrote: On Thu, Sep 01, 2016 at 03:40:43PM -0700, Laura Abbott wrote: The current Ion ioctls lack a good way to tell what ioctls are available. Introduce an ioctl to give an ABI version. This way when the ABI inevitably gets screwed up userspace will

Re: [PATCHv2 3/4] staging: android: ion: Add an ioctl for ABI checking

On 09/01/2016 11:10 PM, Greg Kroah-Hartman wrote: On Thu, Sep 01, 2016 at 03:40:43PM -0700, Laura Abbott wrote: The current Ion ioctls lack a good way to tell what ioctls are available. Introduce an ioctl to give an ABI version. This way when the ABI inevitably gets screwed up userspace will

Re: Memory barrier needed with wake_up_process()?

On Fri, 2 Sep 2016, Peter Zijlstra wrote: > On Fri, Sep 02, 2016 at 02:10:13PM -0400, Alan Stern wrote: > > Paul, Peter, and Ingo: > > > > This must have come up before, but I don't know what was decided. > > > > Isn't it often true that a memory barrier is needed before a call to > >

Re: Memory barrier needed with wake_up_process()?

On Fri, 2 Sep 2016, Peter Zijlstra wrote: > On Fri, Sep 02, 2016 at 02:10:13PM -0400, Alan Stern wrote: > > Paul, Peter, and Ingo: > > > > This must have come up before, but I don't know what was decided. > > > > Isn't it often true that a memory barrier is needed before a call to > >

Re: [PATCH 3/4] dt-binding: remoteproc: venus rproc dt binding document

On Fri 02 Sep 04:52 PDT 2016, Marek Szyprowski wrote: > Hi, > > > On 2016-09-01 16:58, Stanimir Varbanov wrote: > >Hi, > > > >Cc: Marek > > > > ... > > But I presume we have the implementation issue of dma_alloc_coherent() > failing in either case with the 5MB size. I think we need to

Re: [PATCH 3/4] dt-binding: remoteproc: venus rproc dt binding document

On Fri 02 Sep 04:52 PDT 2016, Marek Szyprowski wrote: > Hi, > > > On 2016-09-01 16:58, Stanimir Varbanov wrote: > >Hi, > > > >Cc: Marek > > > > ... > > But I presume we have the implementation issue of dma_alloc_coherent() > failing in either case with the 5MB size. I think we need to

[PATCH v2] rtc-cmos: Reject unsupported alarm values

Some platforms allows to specify the month and day of the month in which an alarm should go off, some others the day of the month and some others just the time. Currently any given value is accepted by the driver and only the supported fields are used to program the hardware. As consequence,

[PATCH v2] rtc-cmos: Reject unsupported alarm values

Some platforms allows to specify the month and day of the month in which an alarm should go off, some others the day of the month and some others just the time. Currently any given value is accepted by the driver and only the supported fields are used to program the hardware. As consequence,

Re: [PATCHv2 2/4] staging: android: ion: Pull out ion ioctls to a separate file

On 09/02/2016 05:44 AM, Greg Kroah-Hartman wrote: On Thu, Sep 01, 2016 at 03:40:42PM -0700, Laura Abbott wrote: The number of Ion ioctls may continue to grow along with necessary validation. Pull it out into a separate file for easier management and review. Signed-off-by: Laura Abbott

Re: [PATCHv2 2/4] staging: android: ion: Pull out ion ioctls to a separate file

On 09/02/2016 05:44 AM, Greg Kroah-Hartman wrote: On Thu, Sep 01, 2016 at 03:40:42PM -0700, Laura Abbott wrote: The number of Ion ioctls may continue to grow along with necessary validation. Pull it out into a separate file for easier management and review. Signed-off-by: Laura Abbott ---

Re: [PATCH v2 1/2] rtc-cmos: Ensure no expired alarm is left enabled after resume

On 01/09/2016 00:58, Gabriele Mazzotta wrote: > Some BIOSes, such as the one of the Dell XPS13 9333, wake the system > when an alarm goes off without informing the OS. If any of the A clarification on this first sentence. I was looking at the ACPI specification [1] and it seems that there are two

Re: [PATCH v2 1/2] rtc-cmos: Ensure no expired alarm is left enabled after resume

On 01/09/2016 00:58, Gabriele Mazzotta wrote: > Some BIOSes, such as the one of the Dell XPS13 9333, wake the system > when an alarm goes off without informing the OS. If any of the A clarification on this first sentence. I was looking at the ACPI specification [1] and it seems that there are two

Re: [PATCH 4/4] tpm_crb: fix incorrect values of cmdReady and goIdle bits

On Fri, Sep 02, 2016 at 10:34:20PM +0300, Jarkko Sakkinen wrote: > CRB_CTRL_CMD_READY and CRB_CTRL_GO_IDLE have incorrect values. > > Signed-off-by: Jarkko Sakkinen Fixes: 30fc8d138e91 ("tpm: TPM 2.0 CRB Interface") Cc: sta...@vger.kernel.org /Jarkko

Re: [PATCH 4/4] tpm_crb: fix incorrect values of cmdReady and goIdle bits

On Fri, Sep 02, 2016 at 10:34:20PM +0300, Jarkko Sakkinen wrote: > CRB_CTRL_CMD_READY and CRB_CTRL_GO_IDLE have incorrect values. > > Signed-off-by: Jarkko Sakkinen Fixes: 30fc8d138e91 ("tpm: TPM 2.0 CRB Interface") Cc: sta...@vger.kernel.org /Jarkko

[tip:x86/urgent] x86/AMD: Apply erratum 665 on machines without a BIOS fix

Commit-ID: d1992996753132e2dafe955cccb2fb0714d3cfc4 Gitweb: http://git.kernel.org/tip/d1992996753132e2dafe955cccb2fb0714d3cfc4 Author: Emanuel Czirai AuthorDate: Fri, 2 Sep 2016 07:35:50 +0200 Committer: Thomas Gleixner CommitDate: Fri, 2

[tip:x86/urgent] x86/AMD: Apply erratum 665 on machines without a BIOS fix

Commit-ID: d1992996753132e2dafe955cccb2fb0714d3cfc4 Gitweb: http://git.kernel.org/tip/d1992996753132e2dafe955cccb2fb0714d3cfc4 Author: Emanuel Czirai AuthorDate: Fri, 2 Sep 2016 07:35:50 +0200 Committer: Thomas Gleixner CommitDate: Fri, 2 Sep 2016 20:42:28 +0200 x86/AMD: Apply erratum

Re: [PATCHv2 1/4] staging: android: ion: Drop heap type masks

On 09/02/2016 06:41 AM, Brian Starkey wrote: Hi Laura, On Thu, Sep 01, 2016 at 03:40:41PM -0700, Laura Abbott wrote: There is no advantage to having heap types be a mask. The ion client has long since dropped the mask. Drop the notion of heap type masks as well. I know this is the same

Re: [PATCHv2 1/4] staging: android: ion: Drop heap type masks

On 09/02/2016 06:41 AM, Brian Starkey wrote: Hi Laura, On Thu, Sep 01, 2016 at 03:40:41PM -0700, Laura Abbott wrote: There is no advantage to having heap types be a mask. The ion client has long since dropped the mask. Drop the notion of heap type masks as well. I know this is the same

[PATCH 4/4] tpm_crb: fix incorrect values of cmdReady and goIdle bits

CRB_CTRL_CMD_READY and CRB_CTRL_GO_IDLE have incorrect values. Signed-off-by: Jarkko Sakkinen --- drivers/char/tpm/tpm_crb.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/char/tpm/tpm_crb.c b/drivers/char/tpm/tpm_crb.c index

[PATCH 2/4] tpm_crb: remove wmb()'s

wmb()'s are not needed as iowrite32() is used. Signed-off-by: Jarkko Sakkinen --- drivers/char/tpm/tpm_crb.c | 3 --- 1 file changed, 3 deletions(-) diff --git a/drivers/char/tpm/tpm_crb.c b/drivers/char/tpm/tpm_crb.c index 1801f38..358c475 100644 ---

[PATCH 2/4] tpm_crb: remove wmb()'s

wmb()'s are not needed as iowrite32() is used. Signed-off-by: Jarkko Sakkinen --- drivers/char/tpm/tpm_crb.c | 3 --- 1 file changed, 3 deletions(-) diff --git a/drivers/char/tpm/tpm_crb.c b/drivers/char/tpm/tpm_crb.c index 1801f38..358c475 100644 --- a/drivers/char/tpm/tpm_crb.c +++

[PATCH 4/4] tpm_crb: fix incorrect values of cmdReady and goIdle bits

CRB_CTRL_CMD_READY and CRB_CTRL_GO_IDLE have incorrect values. Signed-off-by: Jarkko Sakkinen --- drivers/char/tpm/tpm_crb.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/char/tpm/tpm_crb.c b/drivers/char/tpm/tpm_crb.c index c8b0d91..7f602dc 100644 ---

[PATCH 0/4] Small fixes and cleanups for tpm_crb

A set of small fixes and clean ups for tpm_crb. Jarkko Sakkinen (4): tpm_crb: fix crb_req_canceled behavior tpm_crb: remove wmb()'s tpm_crb: refine the naming of constants tpm_crb: fix incorrect values of cmdReady and goIdle bits drivers/char/tpm/tpm_crb.c | 32

[PATCH 3/4] tpm_crb: refine the naming of constants

Renamed CRB protocol specific constants to match the TCG PC Client Platform TPM Profile (PTP) Specification and driver status constants to be explicit that they are driver specific. Signed-off-by: Jarkko Sakkinen --- drivers/char/tpm/tpm_crb.c | 22

[PATCH 3/4] tpm_crb: refine the naming of constants

Renamed CRB protocol specific constants to match the TCG PC Client Platform TPM Profile (PTP) Specification and driver status constants to be explicit that they are driver specific. Signed-off-by: Jarkko Sakkinen --- drivers/char/tpm/tpm_crb.c | 22 +++--- 1 file changed, 11

[PATCH 0/4] Small fixes and cleanups for tpm_crb

A set of small fixes and clean ups for tpm_crb. Jarkko Sakkinen (4): tpm_crb: fix crb_req_canceled behavior tpm_crb: remove wmb()'s tpm_crb: refine the naming of constants tpm_crb: fix incorrect values of cmdReady and goIdle bits drivers/char/tpm/tpm_crb.c | 32

[PATCH 1/4] tpm_crb: fix crb_req_canceled behavior

The req_canceled() callback is used by tpm_transmit() periodically to check whether the request has been canceled while it is receiving a response from the TPM. The TPM_CRB_CTRL_CANCEL register was cleared already in the crb_cancel callback, which has two consequences: * Cancel might not happen.

[PATCH 1/4] tpm_crb: fix crb_req_canceled behavior

The req_canceled() callback is used by tpm_transmit() periodically to check whether the request has been canceled while it is receiving a response from the TPM. The TPM_CRB_CTRL_CANCEL register was cleared already in the crb_cancel callback, which has two consequences: * Cancel might not happen.

Re: [PATCH][RFC v5] timekeeping: Ignore the bogus sleep time if pm_trace is enabled

On Wed, 31 Aug 2016, Rafael J. Wysocki wrote: > On Monday, August 29, 2016 12:40:39 AM Chen Yu wrote: > > + > > + /* > > +* Make rtc-based persistent clock unusable > > +* if pm_trace is enabled, only take effect > > +* for timekeeping_suspend/resume. > > +*/ > > + if

Re: [PATCH][RFC v5] timekeeping: Ignore the bogus sleep time if pm_trace is enabled

On Wed, 31 Aug 2016, Rafael J. Wysocki wrote: > On Monday, August 29, 2016 12:40:39 AM Chen Yu wrote: > > + > > + /* > > +* Make rtc-based persistent clock unusable > > +* if pm_trace is enabled, only take effect > > +* for timekeeping_suspend/resume. > > +*/ > > + if

Re: [PATCH 8/7] net/netfilter/nf_conntrack_core: Remove another memory barrier

On Fri, Sep 02, 2016 at 08:35:55AM +0200, Manfred Spraul wrote: > On 09/01/2016 06:41 PM, Peter Zijlstra wrote: > >On Thu, Sep 01, 2016 at 04:30:39PM +0100, Will Deacon wrote: > >>On Thu, Sep 01, 2016 at 05:27:52PM +0200, Manfred Spraul wrote: > >>>Since spin_unlock_wait() is defined as equivalent

Re: [PATCH 8/7] net/netfilter/nf_conntrack_core: Remove another memory barrier

On Fri, Sep 02, 2016 at 08:35:55AM +0200, Manfred Spraul wrote: > On 09/01/2016 06:41 PM, Peter Zijlstra wrote: > >On Thu, Sep 01, 2016 at 04:30:39PM +0100, Will Deacon wrote: > >>On Thu, Sep 01, 2016 at 05:27:52PM +0200, Manfred Spraul wrote: > >>>Since spin_unlock_wait() is defined as equivalent

Re: Memory barrier needed with wake_up_process()?

On Fri, Sep 02, 2016 at 02:10:13PM -0400, Alan Stern wrote: > Paul, Peter, and Ingo: > > This must have come up before, but I don't know what was decided. > > Isn't it often true that a memory barrier is needed before a call to > wake_up_process()? A typical scenario might look like this: > >

Re: Memory barrier needed with wake_up_process()?

On Fri, Sep 02, 2016 at 02:10:13PM -0400, Alan Stern wrote: > Paul, Peter, and Ingo: > > This must have come up before, but I don't know what was decided. > > Isn't it often true that a memory barrier is needed before a call to > wake_up_process()? A typical scenario might look like this: > >

Re: [PATCH net 0/2] net: thunderx: Fixes for TSO offload issues

From: sunil.kovv...@gmail.com Date: Tue, 30 Aug 2016 11:36:25 +0530 > This patch series fixes couple of issues w.r.t HW TSO offload Series applied, thanks.

Re: [PATCH net 0/2] net: thunderx: Fixes for TSO offload issues

From: sunil.kovv...@gmail.com Date: Tue, 30 Aug 2016 11:36:25 +0530 > This patch series fixes couple of issues w.r.t HW TSO offload Series applied, thanks.

Re: [PATCH v3 6/9] pinctrl: Add IRQ support to STM32 gpios

On Fri, 2 Sep 2016, Alexandre TORGUE wrote: > +static int stm32_gpio_domain_translate(struct irq_domain *d, > +struct irq_fwspec *fwspec, > +unsigned long *hwirq, > +unsigned int *type) > +{

Re: [PATCH v3 6/9] pinctrl: Add IRQ support to STM32 gpios

On Fri, 2 Sep 2016, Alexandre TORGUE wrote: > +static int stm32_gpio_domain_translate(struct irq_domain *d, > +struct irq_fwspec *fwspec, > +unsigned long *hwirq, > +unsigned int *type) > +{

Re: [PATCH v2] iio: adc: ltc2485: add support for Linear Technology LTC2485 ADC

On Mon, Aug 29, 2016 at 05:01:14PM +0100, Jonathan Cameron wrote: > On 25/08/16 06:48, Alison Schofield wrote: > > Adds basic support for the LTC2485 ADC - a delta-sigma analog-to-digital > > converter with an I2C interface that operates in single shot conversion > > mode. > > > > The driver

Re: [PATCH v2] iio: adc: ltc2485: add support for Linear Technology LTC2485 ADC

On Mon, Aug 29, 2016 at 05:01:14PM +0100, Jonathan Cameron wrote: > On 25/08/16 06:48, Alison Schofield wrote: > > Adds basic support for the LTC2485 ADC - a delta-sigma analog-to-digital > > converter with an I2C interface that operates in single shot conversion > > mode. > > > > The driver

Re: [PATCH 4/4] KVM: x86: Hyper-V tsc page setup

On Thu, Sep 01, 2016 at 05:26:15PM +0200, Paolo Bonzini wrote: > Lately tsc page was implemented but filled with empty > values. This patch setup tsc page scale and offset based > on vcpu tsc, tsc_khz and HV_X64_MSR_TIME_REF_COUNT value. > > The valid tsc page drops HV_X64_MSR_TIME_REF_COUNT msr

Re: [PATCH 4/4] KVM: x86: Hyper-V tsc page setup

On Thu, Sep 01, 2016 at 05:26:15PM +0200, Paolo Bonzini wrote: > Lately tsc page was implemented but filled with empty > values. This patch setup tsc page scale and offset based > on vcpu tsc, tsc_khz and HV_X64_MSR_TIME_REF_COUNT value. > > The valid tsc page drops HV_X64_MSR_TIME_REF_COUNT msr

Re: [PATCH 0/7] drm/sun4i: Introduce A33 display driver

Hi Icenowy, On Fri, Sep 02, 2016 at 09:30:05AM +0800, Icenowy Zheng wrote: > > > 01.09.2016, 23:40, "Maxime Ripard" : > > Hi everyone, > > > > This serie introduces the support in the sun4i-drm driver for the A33. > > > > Beside the new IPs and special cases

Re: [PATCH 0/7] drm/sun4i: Introduce A33 display driver

Hi Icenowy, On Fri, Sep 02, 2016 at 09:30:05AM +0800, Icenowy Zheng wrote: > > > 01.09.2016, 23:40, "Maxime Ripard" : > > Hi everyone, > > > > This serie introduces the support in the sun4i-drm driver for the A33. > > > > Beside the new IPs and special cases for the A33 new IPs, there's > >

[PATCH] drm/fsl-dcu: fix endian issue when using clk_register_divider

Since using clk_register_divider to setup the pixel clock, regmap is no longer used. Regmap did take care of DCU using different endianness. Check endianness using the device-tree property "big-endian" to determine the location of DIV_RATIO. Cc: sta...@vger.kernel.org Fixes: 2d701449bce1

[PATCH] drm/fsl-dcu: fix endian issue when using clk_register_divider

Since using clk_register_divider to setup the pixel clock, regmap is no longer used. Regmap did take care of DCU using different endianness. Check endianness using the device-tree property "big-endian" to determine the location of DIV_RATIO. Cc: sta...@vger.kernel.org Fixes: 2d701449bce1

[PATCH] drm/vc4: Allow some more signals to be packed with uniform resets.

The intent was to make sure people don't sneak in a small immediate or something to change the interpretation of the uniform update args, but these signals are just fine. Fixes a validation failure in the current X server on some Render operation. Signed-off-by: Eric Anholt ---

[PATCH] drm/vc4: Allow some more signals to be packed with uniform resets.

The intent was to make sure people don't sneak in a small immediate or something to change the interpretation of the uniform update args, but these signals are just fine. Fixes a validation failure in the current X server on some Render operation. Signed-off-by: Eric Anholt ---

<    1   2   3   4   5   6   7   8   9   10   >