Re: [PATCH v5 7/8] PM / devfreq: rockchip: add devfreq driver for rk3399 dmc

Hi Lin, I add the some comment on below. If you modify them, feel free to add the my reviewed tag on next version: Reviewed-by: Chanwoo Choi On 2016년 08월 10일 12:26, Lin Huang wrote: > base on dfi result, we do ddr frequency scaling, register > dmc driver to devfreq

Re: [PATCH v5 7/8] PM / devfreq: rockchip: add devfreq driver for rk3399 dmc

Hi Lin, I add the some comment on below. If you modify them, feel free to add the my reviewed tag on next version: Reviewed-by: Chanwoo Choi On 2016년 08월 10일 12:26, Lin Huang wrote: > base on dfi result, we do ddr frequency scaling, register > dmc driver to devfreq framework, and use

Re: [RFC][PATCH 3/4] arm64: dts: hikey: Add hikey support for syscon-reboot-mode

On Tue, Aug 9, 2016 at 9:34 PM, Bjorn Andersson wrote: > On Mon 08 Aug 16:03 PDT 2016, John Stultz wrote: > > [..] >> diff --git a/arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts >> b/arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts > [..] >> memory@0 { >>

Re: [RFC][PATCH 3/4] arm64: dts: hikey: Add hikey support for syscon-reboot-mode

On Tue, Aug 9, 2016 at 9:34 PM, Bjorn Andersson wrote: > On Mon 08 Aug 16:03 PDT 2016, John Stultz wrote: > > [..] >> diff --git a/arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts >> b/arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts > [..] >> memory@0 { >> device_type =

Re: [RFC PATCH 2/3] net: macb: Add support for 1588 for Zynq Ultrascale+ MPSoC

Hi Nicolas, Thanks for your reply On Tue, Aug 9, 2016 at 10:26 PM, Punnaiah Choudary Kalluri wrote: > Hi Nicolas, > > 1588 implementation in cadence GEM IP we have in Zynq Ultascale+ MPSoC is > Different to the one in Zynq SOC. > > In earlier version, all

Re: [RFC PATCH 2/3] net: macb: Add support for 1588 for Zynq Ultrascale+ MPSoC

Hi Nicolas, Thanks for your reply On Tue, Aug 9, 2016 at 10:26 PM, Punnaiah Choudary Kalluri wrote: > Hi Nicolas, > > 1588 implementation in cadence GEM IP we have in Zynq Ultascale+ MPSoC is > Different to the one in Zynq SOC. > > In earlier version, all timestamp values will be stored in

Re: [PATCH v5 7/8] PM / devfreq: rockchip: add devfreq driver for rk3399 dmc

Hi Lin, [auto build test WARNING on v4.8-rc1] [also build test WARNING on next-20160809] [cannot apply to rockchip/for-next devfreq/for-rafael linux/master] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci

Re: [PATCH v5 4/8] Documentation: bindings: add dt documentation for dfi controller

Hi Lin, On 2016년 08월 10일 12:26, Lin Huang wrote: > This patch adds the documentation for rockchip dfi devfreq-event driver. > > Signed-off-by: Lin Huang > --- > Changes in v5: > -None > > Changes in v4: > -None > > Changes in v3: > -None > > Changes in v2: > -None > >

Re: [PATCH v5 7/8] PM / devfreq: rockchip: add devfreq driver for rk3399 dmc

Hi Lin, [auto build test WARNING on v4.8-rc1] [also build test WARNING on next-20160809] [cannot apply to rockchip/for-next devfreq/for-rafael linux/master] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci

Re: [PATCH v5 4/8] Documentation: bindings: add dt documentation for dfi controller

Hi Lin, On 2016년 08월 10일 12:26, Lin Huang wrote: > This patch adds the documentation for rockchip dfi devfreq-event driver. > > Signed-off-by: Lin Huang > --- > Changes in v5: > -None > > Changes in v4: > -None > > Changes in v3: > -None > > Changes in v2: > -None > > Changes in v1: >

[PATCH] PM / devfreq: rockchip: fix semicolon.cocci warnings

drivers/devfreq/rk3399_dmc.c:393:2-3: Unneeded semicolon Remove unneeded semicolon. Generated by: scripts/coccinelle/misc/semicolon.cocci CC: Lin Huang Signed-off-by: Fengguang Wu --- rk3399_dmc.c |2 +- 1 file changed, 1 insertion(+), 1

[PATCH] PM / devfreq: rockchip: fix semicolon.cocci warnings

drivers/devfreq/rk3399_dmc.c:393:2-3: Unneeded semicolon Remove unneeded semicolon. Generated by: scripts/coccinelle/misc/semicolon.cocci CC: Lin Huang Signed-off-by: Fengguang Wu --- rk3399_dmc.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- a/drivers/devfreq/rk3399_dmc.c

Re: [PATCH v6 0/2] Block layer support ZAC/ZBC commands

Shaun, On 8/10/16 12:58, Shaun Tancheff wrote: On Tue, Aug 9, 2016 at 3:09 AM, Damien Le Moal wrote: On Aug 9, 2016, at 15:47, Hannes Reinecke wrote: [trim] Since disk type == 0 for everything that isn't HM so I would prefer the sysfs 'zoned' file

Re: [PATCH v6 0/2] Block layer support ZAC/ZBC commands

Shaun, On 8/10/16 12:58, Shaun Tancheff wrote: On Tue, Aug 9, 2016 at 3:09 AM, Damien Le Moal wrote: On Aug 9, 2016, at 15:47, Hannes Reinecke wrote: [trim] Since disk type == 0 for everything that isn't HM so I would prefer the sysfs 'zoned' file just report if the drive is HA or HM.

Re: [PATCH v5 6/8] Documentation: bindings: add dt documentation for rk3399 dmc

Hi Lin, On 2016년 08월 10일 12:26, Lin Huang wrote: > This patch adds the documentation for rockchip rk3399 dmc driver. > > Signed-off-by: Lin Huang > --- > Changes in v5: > -None > > Changes in v4: > -None > > Changes in v3: > -None > > Changes in v2: > -None > > Changes

Re: [PATCH v5 6/8] Documentation: bindings: add dt documentation for rk3399 dmc

Hi Lin, On 2016년 08월 10일 12:26, Lin Huang wrote: > This patch adds the documentation for rockchip rk3399 dmc driver. > > Signed-off-by: Lin Huang > --- > Changes in v5: > -None > > Changes in v4: > -None > > Changes in v3: > -None > > Changes in v2: > -None > > Changes in v1: > -None > >

Re: [PATCH v3] powerpc: Do not make the entire heap executable

Denys Vlasenko writes: > On 32-bit powerps the ELF PLT sections of binaries (built with --bss-plt, > or with a toolchain which defaults to it) look like this: ... > > arch/powerpc/include/asm/page.h| 10 +- > arch/powerpc/include/asm/page_32.h | 2 -- >

Re: [PATCH v3] powerpc: Do not make the entire heap executable

Denys Vlasenko writes: > On 32-bit powerps the ELF PLT sections of binaries (built with --bss-plt, > or with a toolchain which defaults to it) look like this: ... > > arch/powerpc/include/asm/page.h| 10 +- > arch/powerpc/include/asm/page_32.h | 2 -- >

Re: [RFC][PATCH 3/4] arm64: dts: hikey: Add hikey support for syscon-reboot-mode

On Mon 08 Aug 16:03 PDT 2016, John Stultz wrote: [..] > diff --git a/arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts > b/arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts [..] > memory@0 { > device_type = "memory"; > reg = <0x 0x 0x

Re: [RFC][PATCH 3/4] arm64: dts: hikey: Add hikey support for syscon-reboot-mode

On Mon 08 Aug 16:03 PDT 2016, John Stultz wrote: [..] > diff --git a/arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts > b/arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts [..] > memory@0 { > device_type = "memory"; > reg = <0x 0x 0x

Re: Is it ok if ModemManager process is killed AFTER network-interface is brought up and IP-Address assigned?

Ok Greg :) On Tue, Aug 9, 2016 at 1:44 PM, Greg KH wrote: > On Tue, Aug 09, 2016 at 12:48:12PM +0530, Ajay Garg wrote: >> Hi All. >> >> We are using Sierra's USB-to-WWAN driver on Ubuntu-14 for Sierra's >> MC8090 modem, and we have a requirement wherein we need to

Re: Is it ok if ModemManager process is killed AFTER network-interface is brought up and IP-Address assigned?

Ok Greg :) On Tue, Aug 9, 2016 at 1:44 PM, Greg KH wrote: > On Tue, Aug 09, 2016 at 12:48:12PM +0530, Ajay Garg wrote: >> Hi All. >> >> We are using Sierra's USB-to-WWAN driver on Ubuntu-14 for Sierra's >> MC8090 modem, and we have a requirement wherein we need to have access >> to the

Re: [PATCH] cpufreq: powernv: Fix crash in gpstate_timer_handler

Viresh Kumar writes: > On 04-08-16, 20:59, Akshay Adiga wrote: >> 'commit 09ca4c9b5958 ("cpufreq: powernv: Replacing pstate_id with >> frequency table index")' changes calc_global_pstate() to use >> cpufreq_table index instead of pstate_id. >> >> But in

Re: [PATCH] cpufreq: powernv: Fix crash in gpstate_timer_handler

Viresh Kumar writes: > On 04-08-16, 20:59, Akshay Adiga wrote: >> 'commit 09ca4c9b5958 ("cpufreq: powernv: Replacing pstate_id with >> frequency table index")' changes calc_global_pstate() to use >> cpufreq_table index instead of pstate_id. >> >> But in gpstate_timer_handler() pstate_id was

Re: [PATCH 2/2] device-tree: nexus7: Add IMEM syscon and reboot reason support

On Mon 08 Aug 15:34 PDT 2016, John Stultz wrote: > This patch add the IMEM syscon memory region to the DT, > as well as addds support for the magic reboot reason > values that are written to the address for each mode. > This looks good, double checked the addresses and magics. But I think you

Re: [PATCH 2/2] device-tree: nexus7: Add IMEM syscon and reboot reason support

On Mon 08 Aug 15:34 PDT 2016, John Stultz wrote: > This patch add the IMEM syscon memory region to the DT, > as well as addds support for the magic reboot reason > values that are written to the address for each mode. > This looks good, double checked the addresses and magics. But I think you

[PATCH v3 4/5] x86/ioapic: Fix lost IOAPIC resource after hot-removal and hotadd

IOAPIC resource at 0xfecx gets lost from /proc/iomem after hot-removing and then hot-adding the IOAPIC device. After system boot, in /proc/iomem: fec0-fecf : PNP0003:00 fec0-fec003ff : IOAPIC 0 fec01000-fec013ff : IOAPIC 1 fec4-fec403ff : IOAPIC 2 fec8-fec803ff :

[PATCH v3 2/5] x86/ioapic: Support hot-removal of IOAPICs present during boot

IOAPICs present during system boot aren't added to ioapic_list, thus are unable to be hot-removed. Fix it by calling acpi_ioapic_add() during root bus enumeration. Signed-off-by: Rui Wang --- drivers/acpi/pci_root.c | 10 ++ drivers/pci/setup-bus.c | 5 - 2

[PATCH v3 1/5] x86/ioapic: Change prototype of acpi_ioapic_add()

Change the argument of acpi_ioapic_add() to a generic ACPI handle, and move its prototype from drivers/acpi/internal.h to include/linux/acpi.h so that it can be called from outside the pci_root driver. Signed-off-by: Rui Wang --- drivers/acpi/internal.h | 2 --

[PATCH v3 4/5] x86/ioapic: Fix lost IOAPIC resource after hot-removal and hotadd

IOAPIC resource at 0xfecx gets lost from /proc/iomem after hot-removing and then hot-adding the IOAPIC device. After system boot, in /proc/iomem: fec0-fecf : PNP0003:00 fec0-fec003ff : IOAPIC 0 fec01000-fec013ff : IOAPIC 1 fec4-fec403ff : IOAPIC 2 fec8-fec803ff :

[PATCH v3 2/5] x86/ioapic: Support hot-removal of IOAPICs present during boot

IOAPICs present during system boot aren't added to ioapic_list, thus are unable to be hot-removed. Fix it by calling acpi_ioapic_add() during root bus enumeration. Signed-off-by: Rui Wang --- drivers/acpi/pci_root.c | 10 ++ drivers/pci/setup-bus.c | 5 - 2 files changed, 14

[PATCH v3 1/5] x86/ioapic: Change prototype of acpi_ioapic_add()

Change the argument of acpi_ioapic_add() to a generic ACPI handle, and move its prototype from drivers/acpi/internal.h to include/linux/acpi.h so that it can be called from outside the pci_root driver. Signed-off-by: Rui Wang --- drivers/acpi/internal.h | 2 -- drivers/acpi/ioapic.c | 6

[PATCH v3 0/5] Fixing a set of bugs for ioapic hotplug

A set of patches fixing bugs found while testing IOAPIC hotplug. Regards, Rui Changelog: Changes from v2 to v3: * Rebased on top of 4.8-rc1 per Bjorn & Rafael. * Improved the commit message of 0003, w/ clearer explanation. Changes from v1 to v2: * Split the first patch into two as advised by

[PATCH v3 0/5] Fixing a set of bugs for ioapic hotplug

A set of patches fixing bugs found while testing IOAPIC hotplug. Regards, Rui Changelog: Changes from v2 to v3: * Rebased on top of 4.8-rc1 per Bjorn & Rafael. * Improved the commit message of 0003, w/ clearer explanation. Changes from v1 to v2: * Split the first patch into two as advised by

[PATCH v3 3/5] x86/ioapic: Fix setup_res() failing to get resource

acpi_dev_filter_resource_type() returns 0 on success, and 1 on failure. A return value of zero means there's a matching resource, so we should continue within setup_res() to get the resource. Signed-off-by: Rui Wang --- drivers/acpi/ioapic.c | 2 +- 1 file changed, 1

[PATCH v3 5/5] x86/ioapic: Fix ioapic failing to request resource

handle_ioapic_add() uses request_resource() to request ACPI "_CRS" resources. This can fail with the following error message: [ 247.325693] ACPI: \_SB_.IIO1.AID1: failed to insert resource This happens when there are multiple IOAPICs and DSDT groups their "_CRS" resources as the children of a

[PATCH v3 3/5] x86/ioapic: Fix setup_res() failing to get resource

acpi_dev_filter_resource_type() returns 0 on success, and 1 on failure. A return value of zero means there's a matching resource, so we should continue within setup_res() to get the resource. Signed-off-by: Rui Wang --- drivers/acpi/ioapic.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[PATCH v3 5/5] x86/ioapic: Fix ioapic failing to request resource

handle_ioapic_add() uses request_resource() to request ACPI "_CRS" resources. This can fail with the following error message: [ 247.325693] ACPI: \_SB_.IIO1.AID1: failed to insert resource This happens when there are multiple IOAPICs and DSDT groups their "_CRS" resources as the children of a

Re: [PATCH 1/2] device-tree: aqp8064.dtsi: Remove usb phy dr_mode = "host"

On Mon 08 Aug 15:34 PDT 2016, John Stultz wrote: Changes in this file is commonly prefixed "ARM: dts: apq8064:", please follow that. Perhaps: ARM: dts: apq8064: Drop dr_mode property from usb phy > Most 8064 devices have micro-usb ports for phy1, so setting > the dr_mode to host here seems

Re: [PATCH 1/2] device-tree: aqp8064.dtsi: Remove usb phy dr_mode = "host"

On Mon 08 Aug 15:34 PDT 2016, John Stultz wrote: Changes in this file is commonly prefixed "ARM: dts: apq8064:", please follow that. Perhaps: ARM: dts: apq8064: Drop dr_mode property from usb phy > Most 8064 devices have micro-usb ports for phy1, so setting > the dr_mode to host here seems

Re: [PATCH] cpuset: make sure new tasks conform to the current config of the cpuset

On Tue, Aug 09, 2016 at 11:25:01AM +0800, Zefan Li wrote: > A new task inherits cpus_allowed and mems_allowed masks from its parent, > but if someone changes cpuset's config by writing to cpuset.cpus/cpuset.mems > before this new task is inserted into the cgroup's task list, the new task > won't

Re: [PATCH] cpuset: make sure new tasks conform to the current config of the cpuset

On Tue, Aug 09, 2016 at 11:25:01AM +0800, Zefan Li wrote: > A new task inherits cpus_allowed and mems_allowed masks from its parent, > but if someone changes cpuset's config by writing to cpuset.cpus/cpuset.mems > before this new task is inserted into the cgroup's task list, the new task > won't

Re: [PATCH v6 0/2] Block layer support ZAC/ZBC commands

On Tue, Aug 9, 2016 at 3:09 AM, Damien Le Moal wrote: >> On Aug 9, 2016, at 15:47, Hannes Reinecke wrote: [trim] >>> Since disk type == 0 for everything that isn't HM so I would prefer the >>> sysfs 'zoned' file just report if the drive is HA or HM. >>> >>

Re: [PATCH v6 0/2] Block layer support ZAC/ZBC commands

On Tue, Aug 9, 2016 at 3:09 AM, Damien Le Moal wrote: >> On Aug 9, 2016, at 15:47, Hannes Reinecke wrote: [trim] >>> Since disk type == 0 for everything that isn't HM so I would prefer the >>> sysfs 'zoned' file just report if the drive is HA or HM. >>> >> Okay. So let's put in the 'zoned'

Re: [PATCH v2 1/1] blk-mq: fix hang caused by freeze/unfreeze sequence

Hello, On Mon, Aug 08, 2016 at 01:39:08PM +0200, Roman Pen wrote: > Long time ago there was a similar fix proposed by Akinobu Mita[1], > but it seems that time everyone decided to fix this subtle race in > percpu-refcount and Tejun Heo[2] did an attempt (as I can see that > patchset was not

Re: [PATCH v2 1/1] blk-mq: fix hang caused by freeze/unfreeze sequence

Hello, On Mon, Aug 08, 2016 at 01:39:08PM +0200, Roman Pen wrote: > Long time ago there was a similar fix proposed by Akinobu Mita[1], > but it seems that time everyone decided to fix this subtle race in > percpu-refcount and Tejun Heo[2] did an attempt (as I can see that > patchset was not

Re: Potential race condition in drivers/ata/sata_mv.ko

Hello, On Fri, Aug 05, 2016 at 03:43:30PM +0300, Pavel Andrianov wrote: > In drivers/ata/sata_mv.ko function mv_set_main_irq_mask is called several > times. Twice with a spinlock, twice from init function and once without any > protection. The call without protection rises to several handlers

Re: Potential race condition in drivers/ata/sata_mv.ko

Hello, On Fri, Aug 05, 2016 at 03:43:30PM +0300, Pavel Andrianov wrote: > In drivers/ata/sata_mv.ko function mv_set_main_irq_mask is called several > times. Twice with a spinlock, twice from init function and once without any > protection. The call without protection rises to several handlers

Re: [PATCH v5 03/14] arm64/numa: add nid check for memory block

On 2016/8/10 10:12, Hanjun Guo wrote: > On 2016/8/8 17:18, Zhen Lei wrote: >> Use the same tactic to cpu and numa-distance nodes. >> >> Signed-off-by: Zhen Lei >> --- >> arch/arm64/mm/numa.c | 5 + >> 1 file changed, 5 insertions(+) >> >> diff --git

Re: [PATCH v5 03/14] arm64/numa: add nid check for memory block

On 2016/8/10 10:12, Hanjun Guo wrote: > On 2016/8/8 17:18, Zhen Lei wrote: >> Use the same tactic to cpu and numa-distance nodes. >> >> Signed-off-by: Zhen Lei >> --- >> arch/arm64/mm/numa.c | 5 + >> 1 file changed, 5 insertions(+) >> >> diff --git a/arch/arm64/mm/numa.c

Re: [PATCH 1/7] ima: on soft reboot, restore the measurement list

Thiago Jung Bauermann writes: > Am Dienstag, 09 August 2016, 09:01:13 schrieb Mimi Zohar: >> On Tue, 2016-08-09 at 20:59 +1000, Michael Ellerman wrote: >> > Mimi Zohar writes: >> > > diff --git a/security/integrity/ima/ima.h >> > >

Re: [PATCH 1/7] ima: on soft reboot, restore the measurement list

Thiago Jung Bauermann writes: > Am Dienstag, 09 August 2016, 09:01:13 schrieb Mimi Zohar: >> On Tue, 2016-08-09 at 20:59 +1000, Michael Ellerman wrote: >> > Mimi Zohar writes: >> > > diff --git a/security/integrity/ima/ima.h >> > > b/security/integrity/ima/ima.h >> > > index b5728da..84e8d36

Re: [PATCH] w1: fix timeout_us parameter description

Hi On 08/10/2016 06:54 AM, Evgeniy Polyakov wrote: > Hi > > 08.08.2016, 16:52, "Wei Yongjun" : >> Fix 'timeout_us' parameter description. >> >> Signed-off-by: Wei Yongjun >> --- >> drivers/w1/w1.c | 4 ++-- >> 1 file changed, 2 insertions(+), 2

Re: [PATCH] w1: fix timeout_us parameter description

Hi On 08/10/2016 06:54 AM, Evgeniy Polyakov wrote: > Hi > > 08.08.2016, 16:52, "Wei Yongjun" : >> Fix 'timeout_us' parameter description. >> >> Signed-off-by: Wei Yongjun >> --- >> drivers/w1/w1.c | 4 ++-- >> 1 file changed, 2 insertions(+), 2 deletions(-) >> >> diff --git a/drivers/w1/w1.c

Re: [PATCH resend 5/5] libata-scsi: fix MODE SELECT translation for Control mode page

On Fri, Jul 22, 2016 at 02:41:54AM +0800, tom.t...@gmail.com wrote: > From: Tom Yan > > scsi_done() was called repeatedly and apparently because of that, > the kernel would call trace when we touch the Control mode page: > > Call Trace: > [] dump_stack+0x63/0x81 > []

Re: [PATCH resend 5/5] libata-scsi: fix MODE SELECT translation for Control mode page

On Fri, Jul 22, 2016 at 02:41:54AM +0800, tom.t...@gmail.com wrote: > From: Tom Yan > > scsi_done() was called repeatedly and apparently because of that, > the kernel would call trace when we touch the Control mode page: > > Call Trace: > [] dump_stack+0x63/0x81 > [] __warn+0xcb/0xf0 > []

[PATCH] FUSE: add the async option for the flush/release operation

Hi, Miklos: This patch adds the async option for the flush/release operation in FUSE. The async flush/release option allows a FUSE-based application to be terminated without being blocked in the flush/release operation even in the presence of complex external interactions. In addition, the async

[PATCH] FUSE: add the async option for the flush/release operation

Hi, Miklos: This patch adds the async option for the flush/release operation in FUSE. The async flush/release option allows a FUSE-based application to be terminated without being blocked in the flush/release operation even in the presence of complex external interactions. In addition, the async

Re: [PATCH v6 0/2] Block layer support ZAC/ZBC commands

On Tue, Aug 9, 2016 at 1:47 AM, Hannes Reinecke wrote: > On 08/05/2016 10:35 PM, Shaun Tancheff wrote: >> On Tue, Aug 2, 2016 at 8:29 PM, Damien Le Moal >> wrote: On Aug 2, 2016, at 23:35, Hannes Reinecke wrote: On 08/01/2016 07:07

Re: [PATCH v6 0/2] Block layer support ZAC/ZBC commands

On Tue, Aug 9, 2016 at 1:47 AM, Hannes Reinecke wrote: > On 08/05/2016 10:35 PM, Shaun Tancheff wrote: >> On Tue, Aug 2, 2016 at 8:29 PM, Damien Le Moal >> wrote: On Aug 2, 2016, at 23:35, Hannes Reinecke wrote: On 08/01/2016 07:07 PM, Shaun Tancheff wrote: > On Mon, Aug 1, 2016

[PATCH v5 8/8] drm/rockchip: Add dmc notifier in vop driver

when in ddr frequency scaling process, vop can not do enable or disable operation, since dcf will base on vop vblank time to do frequency scaling and need to get vop irq if there have vop enabled. So need register to devfreq notifier, and we can get the dmc status. Also, when there have two vop

[PATCH v5 8/8] drm/rockchip: Add dmc notifier in vop driver

when in ddr frequency scaling process, vop can not do enable or disable operation, since dcf will base on vop vblank time to do frequency scaling and need to get vop irq if there have vop enabled. So need register to devfreq notifier, and we can get the dmc status. Also, when there have two vop

[PATCH v5 0/8] 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 v5 6/8] 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 v5: -None Changes in v4: -None Changes in v3: -None Changes in v2: -None Changes in v1: -None .../devicetree/bindings/devfreq/rk3399_dmc.txt | 35

[PATCH v5 6/8] 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 v5: -None Changes in v4: -None Changes in v3: -None Changes in v2: -None Changes in v1: -None .../devicetree/bindings/devfreq/rk3399_dmc.txt | 35 ++ 1 file

[PATCH v5 0/8] 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 v5 1/8] clk: rockchip: add new clock-type for the ddrclk

On new rockchip platform(rk3399 etc), there have dcf controller to do ddr frequency scaling, and this controller will implement in arm-trust-firmware. We add a special clock-type to handle that. Signed-off-by: Lin Huang --- Changes in v5: - delete unuse mux_flag - use

[PATCH v5 1/8] clk: rockchip: add new clock-type for the ddrclk

On new rockchip platform(rk3399 etc), there have dcf controller to do ddr frequency scaling, and this controller will implement in arm-trust-firmware. We add a special clock-type to handle that. Signed-off-by: Lin Huang --- Changes in v5: - delete unuse mux_flag - use div_flag to distinguish sip

[PATCH v5 2/8] clk: rockchip: rk3399: add SCLK_DDRCLK ID for ddrc

Signed-off-by: Lin Huang --- Changes in v5: -None Changes in v4: -None Changes in v3: -None Changes in v2: -None Changes in v1: -None include/dt-bindings/clock/rk3399-cru.h | 1 + 1 file changed, 1 insertion(+) diff --git a/include/dt-bindings/clock/rk3399-cru.h

[PATCH v5 4/8] 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 v5: -None Changes in v4: -None Changes in v3: -None Changes in v2: -None Changes in v1: -None .../bindings/devfreq/event/rockchip-dfi.txt | 20

[PATCH v5 2/8] clk: rockchip: rk3399: add SCLK_DDRCLK ID for ddrc

Signed-off-by: Lin Huang --- Changes in v5: -None Changes in v4: -None Changes in v3: -None Changes in v2: -None Changes in v1: -None include/dt-bindings/clock/rk3399-cru.h | 1 + 1 file changed, 1 insertion(+) diff --git a/include/dt-bindings/clock/rk3399-cru.h

[PATCH v5 4/8] 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 v5: -None Changes in v4: -None Changes in v3: -None Changes in v2: -None Changes in v1: -None .../bindings/devfreq/event/rockchip-dfi.txt | 20 1

[PATCH v5 7/8] 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 --- Changes in v5: - improve dmc driver suggest by Chanwoo Choi Changes in v4: - use arm_smccc_smc() function talk to bl31 -

[PATCH v5 3/8] clk: rockchip: rk3399: add ddrc clock support

add ddrc clock setting, so we can do ddr frequency scaling on rk3399 platform in future. Signed-off-by: Lin Huang --- Changes in v5: - fit for the ddr type Changes in v4: - None Changes in v3: - None Changes in v2: - remove clk_ddrc_dpll_src from critical clock list

[PATCH v5 5/8] 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 Acked-by: Chanwoo Choi --- Changes in v5: -None Changes in v4: -None Changes in v3: -None Changes in v2:

[PATCH v5 7/8] 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 --- Changes in v5: - improve dmc driver suggest by Chanwoo Choi Changes in v4: - use arm_smccc_smc() function talk to bl31 - delete rockchip_dmc.c

[PATCH v5 3/8] clk: rockchip: rk3399: add ddrc clock support

add ddrc clock setting, so we can do ddr frequency scaling on rk3399 platform in future. Signed-off-by: Lin Huang --- Changes in v5: - fit for the ddr type Changes in v4: - None Changes in v3: - None Changes in v2: - remove clk_ddrc_dpll_src from critical clock list Changes in v1: - remove

[PATCH v5 5/8] 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 Acked-by: Chanwoo Choi --- Changes in v5: -None Changes in v4: -None Changes in v3: -None Changes in v2: -None Changes in v1: -None

Re: Regarding AHCI_MAX_SG and (ATA_HORKAGE_MAX_SEC_1024)

Hello, Tom. On Sun, Aug 07, 2016 at 10:10:17PM +0800, Tom Yan wrote: > So the (not so) recent bump of BLK_DEF_MAX_SECTORS from 1024 to 2560 > (commit d2be537c3ba3) seemed to have caused trouble to some of the ATA > devices, which were then worked around with ATA_HORKAGE_MAX_SEC_1024. > >

Re: Regarding AHCI_MAX_SG and (ATA_HORKAGE_MAX_SEC_1024)

Hello, Tom. On Sun, Aug 07, 2016 at 10:10:17PM +0800, Tom Yan wrote: > So the (not so) recent bump of BLK_DEF_MAX_SECTORS from 1024 to 2560 > (commit d2be537c3ba3) seemed to have caused trouble to some of the ATA > devices, which were then worked around with ATA_HORKAGE_MAX_SEC_1024. > >

Re: [PATCH v5 5/6] usb: chipidea: let chipidea core device of_node equal's glue layer device of_node

On Tue, Aug 09, 2016 at 05:15:36PM -0700, Stephen Boyd wrote: > Quoting Peter Chen (2016-08-08 01:52:10) > > From: Peter Chen > > > > At device tree, we have no device node for chipidea core, > > the glue layer's node is the parent node for host and udc > > device. But

Re: [PATCH v5 5/6] usb: chipidea: let chipidea core device of_node equal's glue layer device of_node

On Tue, Aug 09, 2016 at 05:15:36PM -0700, Stephen Boyd wrote: > Quoting Peter Chen (2016-08-08 01:52:10) > > From: Peter Chen > > > > At device tree, we have no device node for chipidea core, > > the glue layer's node is the parent node for host and udc > > device. But in related driver, the

Re: [PATCH v2] mm/slub: Run free_partial() outside of the kmem_cache_node->list_lock

On Tue, Aug 09, 2016 at 04:27:46PM +0100, Chris Wilson wrote: ... > diff --git a/mm/slub.c b/mm/slub.c > index 825ff45..58f0eb6 100644 > --- a/mm/slub.c > +++ b/mm/slub.c > @@ -3479,6 +3479,7 @@ static void list_slab_objects(struct kmem_cache *s, > struct page *page, > */ > static void

Re: [PATCH v2] mm/slub: Run free_partial() outside of the kmem_cache_node->list_lock

On Tue, Aug 09, 2016 at 04:27:46PM +0100, Chris Wilson wrote: ... > diff --git a/mm/slub.c b/mm/slub.c > index 825ff45..58f0eb6 100644 > --- a/mm/slub.c > +++ b/mm/slub.c > @@ -3479,6 +3479,7 @@ static void list_slab_objects(struct kmem_cache *s, > struct page *page, > */ > static void

Re: [PATCH V3 1/3] tracing: add a possibility of exporting function trace to other places instead of ring buffer only

On Tue, Aug 9, 2016 at 11:35 PM, Steven Rostedt wrote: > On Tue, 9 Aug 2016 14:32:39 +0800 > Chunyan Zhang wrote: > >> Currently ring buffer is the only output of Function traces, this patch >> added trace_export concept which would process the

Re: [PATCH V3 1/3] tracing: add a possibility of exporting function trace to other places instead of ring buffer only

On Tue, Aug 9, 2016 at 11:35 PM, Steven Rostedt wrote: > On Tue, 9 Aug 2016 14:32:39 +0800 > Chunyan Zhang wrote: > >> Currently ring buffer is the only output of Function traces, this patch >> added trace_export concept which would process the traces and export >> traces to a registered

Re: [PATCH v5 6/6] ARM: dts: imx6qdl-udoo.dtsi: fix onboard USB HUB property

On Tue, Aug 09, 2016 at 04:33:35PM -0700, Joshua Clayton wrote: > Hi Peter, > > On 08/08/2016 01:52 AM, Peter Chen wrote: > > The current dts describes USB HUB's property at USB controller's > > entry, it is improper. The USB HUB should be the child node > > under USB controller, and power

Re: [PATCH v5 6/6] ARM: dts: imx6qdl-udoo.dtsi: fix onboard USB HUB property

On Tue, Aug 09, 2016 at 04:33:35PM -0700, Joshua Clayton wrote: > Hi Peter, > > On 08/08/2016 01:52 AM, Peter Chen wrote: > > The current dts describes USB HUB's property at USB controller's > > entry, it is improper. The USB HUB should be the child node > > under USB controller, and power

Re: [PATCH 1/1] Add CPU temperature sensor support for i.MX53

Hello, Fabien. Is $SUBJ right? CPU temperature? On Wed, Aug 03, 2016 at 09:35:56AM +0200, Fabien Lahoudere wrote: > From: Csaba Kertesz > > The original patch was made by Richard Zhu for kernel 2.6.x: > > ENGR00134041-MX53-Add-the-SATA-AHCI-temperature-monitor.patch

Re: [PATCH 1/1] Add CPU temperature sensor support for i.MX53

Hello, Fabien. Is $SUBJ right? CPU temperature? On Wed, Aug 03, 2016 at 09:35:56AM +0200, Fabien Lahoudere wrote: > From: Csaba Kertesz > > The original patch was made by Richard Zhu for kernel 2.6.x: > > ENGR00134041-MX53-Add-the-SATA-AHCI-temperature-monitor.patch > > The old source code

Re: c6x linker issue on linux-next-20160808 + some linker table work

On Tue, 2016-08-09 at 19:09 -0700, Luis R. Rodriguez wrote: > On Aug 9, 2016 6:50 PM, "Mark Salter" wrote: > > > > On Tue, 2016-08-09 at 20:40 +0200, Luis R. Rodriguez wrote: > > > On Tue, Aug 09, 2016 at 01:04:00PM -0400, Mark Salter wrote: > > > > > > > > On Tue, 2016-08-09

Re: c6x linker issue on linux-next-20160808 + some linker table work

On Tue, 2016-08-09 at 19:09 -0700, Luis R. Rodriguez wrote: > On Aug 9, 2016 6:50 PM, "Mark Salter" wrote: > > > > On Tue, 2016-08-09 at 20:40 +0200, Luis R. Rodriguez wrote: > > > On Tue, Aug 09, 2016 at 01:04:00PM -0400, Mark Salter wrote: > > > > > > > > On Tue, 2016-08-09 at 06:37 -0700,

Re: [PATCH v6 1/3] PCI: Add Precision Time Measurement (PTM) support

On 06/14/2016 03:05, Bjorn Helgaas wrote: > From: Jonathan Yong > > Add Precision Time Measurement (PTM) support (see PCIe r3.1, sec 6.22). > > Enable PTM on PTM Root devices and switch ports. This does not enable PTM > on endpoints. > > There currently are no

Re: Kernel modules under new copyleft licence : (was Re: [PATCH v2] module.h: add copyleft-next >= 0.3.1 as GPL compatible)

On Tue, Aug 9, 2016 at 1:14 PM, Luis R. Rodriguez wrote: > > I'm personally fine with MODULE_LICENSE("GPL") being used with copyleft-next > code > and find it sensible. I'd rather have the kernel license be as clear as possible, so I'd tend to prefer that

Re: [PATCH v6 1/3] PCI: Add Precision Time Measurement (PTM) support

On 06/14/2016 03:05, Bjorn Helgaas wrote: > From: Jonathan Yong > > Add Precision Time Measurement (PTM) support (see PCIe r3.1, sec 6.22). > > Enable PTM on PTM Root devices and switch ports. This does not enable PTM > on endpoints. > > There currently are no PTM-capable devices on the

Re: Kernel modules under new copyleft licence : (was Re: [PATCH v2] module.h: add copyleft-next >= 0.3.1 as GPL compatible)

On Tue, Aug 9, 2016 at 1:14 PM, Luis R. Rodriguez wrote: > > I'm personally fine with MODULE_LICENSE("GPL") being used with copyleft-next > code > and find it sensible. I'd rather have the kernel license be as clear as possible, so I'd tend to prefer that MODULE_LICENSE("GPL") and then if

Re: [PATCH v6 2/4] mfd: lp873x: Add lp873x PMIC support

On Tuesday 09 August 2016 06:23 PM, Lee Jones wrote: On Mon, 08 Aug 2016, Keerthy wrote: The LP873X chip is a power management IC for Portable Navigation Systems and Tablet Computing devices. It contains the following components: - Regulators. - Configurable General Purpose

Re: [PATCH v6 2/4] mfd: lp873x: Add lp873x PMIC support

On Tuesday 09 August 2016 06:23 PM, Lee Jones wrote: On Mon, 08 Aug 2016, Keerthy wrote: The LP873X chip is a power management IC for Portable Navigation Systems and Tablet Computing devices. It contains the following components: - Regulators. - Configurable General Purpose

Re: [PATCH v6 1/4] Documentation: mfd: LP873X: Add information for the mfd driver

On Tuesday 09 August 2016 06:20 PM, Lee Jones wrote: On Mon, 08 Aug 2016, Keerthy wrote: The lp873x series of PMICs have a bunch of regulators and a couple of GPO(General Purpose Outputs). Add information for the MFD and regulator drivers. Acked-by: Rob Herring

Re: [PATCH v6 1/4] Documentation: mfd: LP873X: Add information for the mfd driver

On Tuesday 09 August 2016 06:20 PM, Lee Jones wrote: On Mon, 08 Aug 2016, Keerthy wrote: The lp873x series of PMICs have a bunch of regulators and a couple of GPO(General Purpose Outputs). Add information for the MFD and regulator drivers. Acked-by: Rob Herring Signed-off-by: Keerthy

  1   2   3   4   5   6   7   8   9   10   >