Re: [PATCH v2 2/4] dt-bindings: Add a binding for Mediatek MDP

On Thu, 2016-07-28 at 10:55 -0500, Rob Herring wrote: > On Tue, Jul 26, 2016 at 8:44 PM, Minghsiu Tsai > wrote: > > On Tue, 2016-07-26 at 13:54 -0500, Rob Herring wrote: > >> On Fri, Jul 22, 2016 at 04:33:01PM +0800, Minghsiu Tsai wrote: > >> > Add a DT binding

Re: [PATCH v2 2/4] dt-bindings: Add a binding for Mediatek MDP

On Thu, 2016-07-28 at 10:55 -0500, Rob Herring wrote: > On Tue, Jul 26, 2016 at 8:44 PM, Minghsiu Tsai > wrote: > > On Tue, 2016-07-26 at 13:54 -0500, Rob Herring wrote: > >> On Fri, Jul 22, 2016 at 04:33:01PM +0800, Minghsiu Tsai wrote: > >> > Add a DT binding documentation of MDP for the MT8173

[PATCH 2/2 v2] drm: bridge: add DesignWare HDMI I2S audio support

From: Kuninori Morimoto Current dw-hdmi is supporting sound via AHB bus, but it has I2S audio feature too. This patch adds I2S audio support to dw-hdmi. This HDMI I2S is supported by using ALSA SoC common HDMI encoder driver. Signed-off-by: Kuninori Morimoto

[PATCH 2/2 v2] drm: bridge: add DesignWare HDMI I2S audio support

From: Kuninori Morimoto Current dw-hdmi is supporting sound via AHB bus, but it has I2S audio feature too. This patch adds I2S audio support to dw-hdmi. This HDMI I2S is supported by using ALSA SoC common HDMI encoder driver. Signed-off-by: Kuninori Morimoto --- v1 -> v2 - tidyup return

Re: [PATCH] net/mlx5_core/pagealloc: Remove deprecated create_singlethread_workqueue

On Mon, Aug 01, 2016 at 11:11:19AM -0400, Tejun Heo wrote: > > Right now, I'm feeling that I'm participating in soapie where one sends > > patch for every line, waits and sends the same patch for another file. > > It is worth to send one patch set and let us to test it all in once. > > Yeah, I

Re: [PATCH] net/mlx5_core/pagealloc: Remove deprecated create_singlethread_workqueue

On Mon, Aug 01, 2016 at 11:11:19AM -0400, Tejun Heo wrote: > > Right now, I'm feeling that I'm participating in soapie where one sends > > patch for every line, waits and sends the same patch for another file. > > It is worth to send one patch set and let us to test it all in once. > > Yeah, I

[PATCH 1/2 v2] ASoC: hdmi-codec: enable multi probe for same device

From: Kuninori Morimoto hdmi-codec driver is common HDMI sound driver, but it doesn't care about multi sound ports. For example, hdmi-codec driver is supporting 1 I2S and 1 SPDIF ports, so, we can't use this driver if HDMI has 2 or more I2S ports. And we would

[PATCH 1/2 v2] ASoC: hdmi-codec: enable multi probe for same device

From: Kuninori Morimoto hdmi-codec driver is common HDMI sound driver, but it doesn't care about multi sound ports. For example, hdmi-codec driver is supporting 1 I2S and 1 SPDIF ports, so, we can't use this driver if HDMI has 2 or more I2S ports. And we would like to use multi detection. For

Re: [RFC v0 7/8] Input: ims-pcu: use firmware_stat instead of completion

Hi Luis, I was ignorant on all the nasty details around the firmware loading. If I parse Luis' patches correctly they introduce an API which calls kernel_read_file_from_path() asynchronously: sysdata_file_request_async(..., ) *coookie = async_schedule_domain(request_sysdata_file_work_func(),

Re: [RFC v0 7/8] Input: ims-pcu: use firmware_stat instead of completion

Hi Luis, I was ignorant on all the nasty details around the firmware loading. If I parse Luis' patches correctly they introduce an API which calls kernel_read_file_from_path() asynchronously: sysdata_file_request_async(..., ) *coookie = async_schedule_domain(request_sysdata_file_work_func(),

Re: [PATCH] mm/memblock.c: fix NULL dereference error

Hi All, this mail correct the following mistakes in last mail 1, remove test patch attached 2, format patch to satisfy rules i am so sorry for my mistake Hi Andrew, this patch is part of https://lkml.org/lkml/2016/7/26/347 and isn't merged in as you advised in another mail, i release this

Re: [PATCH v4 3/5] nvmem: core: Add consumer API to get nvmem cell from node

On 16-07-08 18:23:42, Srinivas Kandagatla wrote: > > > On 08/07/16 17:42, Stefan Agner wrote: > > On 2016-07-08 08:41, Srinivas Kandagatla wrote: > > > On 07/07/16 14:48, maitysancha...@gmail.com wrote: > > > > Hello Srinivas, > > > > > > > > On 16-07-07 1 > > ... > > > > > > > > > > > > >

Re: [PATCH] mm/memblock.c: fix NULL dereference error

Hi All, this mail correct the following mistakes in last mail 1, remove test patch attached 2, format patch to satisfy rules i am so sorry for my mistake Hi Andrew, this patch is part of https://lkml.org/lkml/2016/7/26/347 and isn't merged in as you advised in another mail, i release this

Re: [PATCH v4 3/5] nvmem: core: Add consumer API to get nvmem cell from node

On 16-07-08 18:23:42, Srinivas Kandagatla wrote: > > > On 08/07/16 17:42, Stefan Agner wrote: > > On 2016-07-08 08:41, Srinivas Kandagatla wrote: > > > On 07/07/16 14:48, maitysancha...@gmail.com wrote: > > > > Hello Srinivas, > > > > > > > > On 16-07-07 1 > > ... > > > > > > > > > > > > >

[PATCH 1/2 v5] perf sched: fix wrong conversion of task state

Currently sched_out_state() converts the prev_state u64 bitmask to a char using the bitmask as an index, which may cause invalid memory access. This fixes the issue by using the __ffs() returned value as an index. Signed-off-by: Tomoki Sekiyama Fixes:

[PATCH 2/2 v5] perf sched: adapt TASK_STATE_TO_CHAR_STR to the latest kernel

Update TASK_STATE_TO_CHAR_STR macro to one from sched.h in the latest kernel. Related kernel commits: - commit ad86622b478e ("wait: swap EXIT_ZOMBIE and EXIT_DEAD to hide EXIT_TRACE from user-space"): 'Z' and 'X' are swapped - commit 80ed87c8a9ca ("sched/wait: Introduce TASK_NOLOAD and

[PATCH 1/2 v5] perf sched: fix wrong conversion of task state

Currently sched_out_state() converts the prev_state u64 bitmask to a char using the bitmask as an index, which may cause invalid memory access. This fixes the issue by using the __ffs() returned value as an index. Signed-off-by: Tomoki Sekiyama Fixes: cdce9d738b91e ("perf sched: Add sched

[PATCH 2/2 v5] perf sched: adapt TASK_STATE_TO_CHAR_STR to the latest kernel

Update TASK_STATE_TO_CHAR_STR macro to one from sched.h in the latest kernel. Related kernel commits: - commit ad86622b478e ("wait: swap EXIT_ZOMBIE and EXIT_DEAD to hide EXIT_TRACE from user-space"): 'Z' and 'X' are swapped - commit 80ed87c8a9ca ("sched/wait: Introduce TASK_NOLOAD and

Re: [PATCH] mm/memblock.c: fix NULL dereference error

i am sorry, the second patch is only a test patch, please don't apply it i will send another mail for correct this On 08/02/2016 01:23 PM, kbuild test robot wrote: > Hi zijun_hu, > > [auto build test WARNING on mmotm/master] > [also build test WARNING on v4.7 next-20160801] >

Re: [PATCH] mm/memblock.c: fix NULL dereference error

i am sorry, the second patch is only a test patch, please don't apply it i will send another mail for correct this On 08/02/2016 01:23 PM, kbuild test robot wrote: > Hi zijun_hu, > > [auto build test WARNING on mmotm/master] > [also build test WARNING on v4.7 next-20160801] >

[PATCH 3/5] arm64: Handle TRAP_HWBRKPT for user mode as well

uprobe registers a handler at step_hook. So, single_step_handler now checks for user mode as well if there is a valid hook. Signed-off-by: Pratyush Anand --- arch/arm64/kernel/debug-monitors.c | 22 -- 1 file changed, 12 insertions(+), 10 deletions(-)

[PATCH 5/5] arm64: Add uprobe support

This patch adds support for uprobe on ARM64 architecture. Unit test for following has been done so far and they have been found working 1. Step-able instructions, like sub, ldr, add etc. 2. Simulation-able like ret, cbnz, cbz etc. 3. uretprobe 4. Reject-able instructions like sev,

[PATCH 4/5] arm64: Handle TRAP_BRKPT for user mode as well

uprobe is registered at break_hook with a unique ESR code. So, when a TRAP_BRKPT occurs, call_break_hook checks if it was for uprobe. If not, then send a SIGTRAP to user. Signed-off-by: Pratyush Anand --- arch/arm64/kernel/debug-monitors.c | 18 +++--- 1 file

[PATCH] ARM: dts: am57xx-idk-common: Enable support for QSPI

AM572x IDK has a Spansion s25fl256s1 QSPI flash on the EVM connected to TI QSPI IP over CS0. Hence, add QSPI and flash slave DT nodes. Signed-off-by: Vignesh R --- arch/arm/boot/dts/am57xx-idk-common.dtsi | 49 1 file changed, 49 insertions(+)

[PATCH 3/5] arm64: Handle TRAP_HWBRKPT for user mode as well

uprobe registers a handler at step_hook. So, single_step_handler now checks for user mode as well if there is a valid hook. Signed-off-by: Pratyush Anand --- arch/arm64/kernel/debug-monitors.c | 22 -- 1 file changed, 12 insertions(+), 10 deletions(-) diff --git

[PATCH 5/5] arm64: Add uprobe support

This patch adds support for uprobe on ARM64 architecture. Unit test for following has been done so far and they have been found working 1. Step-able instructions, like sub, ldr, add etc. 2. Simulation-able like ret, cbnz, cbz etc. 3. uretprobe 4. Reject-able instructions like sev,

[PATCH 4/5] arm64: Handle TRAP_BRKPT for user mode as well

uprobe is registered at break_hook with a unique ESR code. So, when a TRAP_BRKPT occurs, call_break_hook checks if it was for uprobe. If not, then send a SIGTRAP to user. Signed-off-by: Pratyush Anand --- arch/arm64/kernel/debug-monitors.c | 18 +++--- 1 file changed, 11

[PATCH] ARM: dts: am57xx-idk-common: Enable support for QSPI

AM572x IDK has a Spansion s25fl256s1 QSPI flash on the EVM connected to TI QSPI IP over CS0. Hence, add QSPI and flash slave DT nodes. Signed-off-by: Vignesh R --- arch/arm/boot/dts/am57xx-idk-common.dtsi | 49 1 file changed, 49 insertions(+) diff --git

[PATCH 2/5] arm64: kgdb_step_brk_fn: ignore other's exception

ARM64 step exception does not have any syndrome information. So, it is responsibility of exception handler to take care that they handle it only if exception was raised for them. Since kgdb_step_brk_fn() always returns 0, therefore we might have problem when we will have other step handler

[PATCH 1/5] arm64: kprobe: protect/rename few definitions to be reused by uprobe

decode-insn code has to be reused by arm64 uprobe implementation as well. Therefore, this patch protects some portion of kprobe code and renames few other, so that decode-insn functionality can be reused by uprobe even when CONFIG_KPROBES is not defined. kprobe_opcode_t and struct

[PATCH 0/5] ARM64: Uprobe support added

ARM64 kprobe support is lying in torvalds/linux.git:master now. Therefore sending my uprobe patches which were dependent on decode-insn code of kprobe patches. Unit tests for following have been done so far and they have been found working. 1. Step-able instructions, like sub, ldr, add etc.

[PATCH 1/5] arm64: kprobe: protect/rename few definitions to be reused by uprobe

decode-insn code has to be reused by arm64 uprobe implementation as well. Therefore, this patch protects some portion of kprobe code and renames few other, so that decode-insn functionality can be reused by uprobe even when CONFIG_KPROBES is not defined. kprobe_opcode_t and struct

[PATCH 0/5] ARM64: Uprobe support added

ARM64 kprobe support is lying in torvalds/linux.git:master now. Therefore sending my uprobe patches which were dependent on decode-insn code of kprobe patches. Unit tests for following have been done so far and they have been found working. 1. Step-able instructions, like sub, ldr, add etc.

[PATCH 2/5] arm64: kgdb_step_brk_fn: ignore other's exception

ARM64 step exception does not have any syndrome information. So, it is responsibility of exception handler to take care that they handle it only if exception was raised for them. Since kgdb_step_brk_fn() always returns 0, therefore we might have problem when we will have other step handler

Re: [PATCH] mm/memblock.c: fix NULL dereference error

Hi zijun_hu, [auto build test WARNING on mmotm/master] [also build test WARNING on v4.7 next-20160801] [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/linux/commits/zijun_hu/mm-memblock-c-fix-NULL-dereference

Re: [PATCH] mm/memblock.c: fix NULL dereference error

Hi zijun_hu, [auto build test WARNING on mmotm/master] [also build test WARNING on v4.7 next-20160801] [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/linux/commits/zijun_hu/mm-memblock-c-fix-NULL-dereference

Re: [PATCH 0/3] DesignWare HDMI I2S suport

Hi > These are DesignWare HDMI I2S support patches. > It will use ALSA SoC hdmi-codec driver, but we can't use it as-is. > So, 2), 3) patches modify hdmi-codec style. > > Kuninori Morimoto (3): > 1) drm: bridge: add DesignWare HDMI I2S audio support > 2) ASoC: hdmi-codec: callback function

Re: [PATCH 0/3] DesignWare HDMI I2S suport

Hi > These are DesignWare HDMI I2S support patches. > It will use ALSA SoC hdmi-codec driver, but we can't use it as-is. > So, 2), 3) patches modify hdmi-codec style. > > Kuninori Morimoto (3): > 1) drm: bridge: add DesignWare HDMI I2S audio support > 2) ASoC: hdmi-codec: callback function

Re: [PATCH v2 0/6] extcon: Add the support for extcon type and property

On Mon, Aug 1, 2016 at 6:52 PM, Chanwoo Choi wrote: > Hi Guenter, > > On 2016년 08월 02일 03:18, Guenter Roeck wrote: >> On Sun, Jul 31, 2016 at 10:50 PM, Chanwoo Choi wrote: >>> This patch-set add the support the extcon type, extcon property >>> and

Re: [PATCH v2 0/6] extcon: Add the support for extcon type and property

On Mon, Aug 1, 2016 at 6:52 PM, Chanwoo Choi wrote: > Hi Guenter, > > On 2016년 08월 02일 03:18, Guenter Roeck wrote: >> On Sun, Jul 31, 2016 at 10:50 PM, Chanwoo Choi wrote: >>> This patch-set add the support the extcon type, extcon property >>> and the synchronization functions. >>> >>> The each

[PATCH 1/2] tools lib traceevent: Ignore generated library files

Signed-off-by: Namhyung Kim --- tools/lib/traceevent/.gitignore | 1 + 1 file changed, 1 insertion(+) diff --git a/tools/lib/traceevent/.gitignore b/tools/lib/traceevent/.gitignore index 3c60335fe7be..9e9f25fb1922 100644 --- a/tools/lib/traceevent/.gitignore +++

[PATCH 1/2] tools lib traceevent: Ignore generated library files

Signed-off-by: Namhyung Kim --- tools/lib/traceevent/.gitignore | 1 + 1 file changed, 1 insertion(+) diff --git a/tools/lib/traceevent/.gitignore b/tools/lib/traceevent/.gitignore index 3c60335fe7be..9e9f25fb1922 100644 --- a/tools/lib/traceevent/.gitignore +++

[PATCH 2/2] tools lib traceevent: Add str_error_r()

The libtraceevent uses str_error_r() but its implementation is outside of the library. So if an external program wants to link the libtraceevent it'd fail due to missing str_error_r. Add it. Signed-off-by: Namhyung Kim --- tools/lib/traceevent/Build | 4 1 file

[PATCH 2/2] tools lib traceevent: Add str_error_r()

The libtraceevent uses str_error_r() but its implementation is outside of the library. So if an external program wants to link the libtraceevent it'd fail due to missing str_error_r. Add it. Signed-off-by: Namhyung Kim --- tools/lib/traceevent/Build | 4 1 file changed, 4 insertions(+)

Re: [PATCH 1/2] sparc: fix incorrect value returned by copy_from_user_fixup

From: Mikulas Patocka Date: Sun, 31 Jul 2016 19:50:57 -0400 (EDT) > @@ -18,9 +25,9 @@ > * of the cases, just fix things up simply here. > */ > > -static unsigned long compute_size(unsigned long start, unsigned long size, > unsigned long *offset) > +static unsigned

Re: [PATCH 1/2] sparc: fix incorrect value returned by copy_from_user_fixup

From: Mikulas Patocka Date: Sun, 31 Jul 2016 19:50:57 -0400 (EDT) > @@ -18,9 +25,9 @@ > * of the cases, just fix things up simply here. > */ > > -static unsigned long compute_size(unsigned long start, unsigned long size, > unsigned long *offset) > +static unsigned long

Re: [PATCH] memcg: put soft limit reclaim out of way if the excess tree is empty

On Mon, Aug 01, 2016 at 04:12:28PM +0200, Michal Hocko wrote: ... > From: Michal Hocko > Date: Mon, 1 Aug 2016 10:42:06 +0200 > Subject: [PATCH] memcg: put soft limit reclaim out of way if the excess tree > is empty > > We've had a report about soft lockups caused by lock

Re: [PATCH] memcg: put soft limit reclaim out of way if the excess tree is empty

On Mon, Aug 01, 2016 at 04:12:28PM +0200, Michal Hocko wrote: ... > From: Michal Hocko > Date: Mon, 1 Aug 2016 10:42:06 +0200 > Subject: [PATCH] memcg: put soft limit reclaim out of way if the excess tree > is empty > > We've had a report about soft lockups caused by lock bouncing in the > soft

[PATCH] vhost: drop vringh dependency

vringh isn't used by vhost net or scsi - it's used by CAIF only at the moment. Drop the dependency. Signed-off-by: Michael S. Tsirkin --- Including vhost directory twice isn't pretty - we just want it scanned if either of the symbols is defined. Something along the lines of

[PATCH] vhost: drop vringh dependency

vringh isn't used by vhost net or scsi - it's used by CAIF only at the moment. Drop the dependency. Signed-off-by: Michael S. Tsirkin --- Including vhost directory twice isn't pretty - we just want it scanned if either of the symbols is defined. Something along the lines of obj-$(subst

[PATCH] mm/memblock.c: fix NULL dereference error

Hi Andrew, this patch is part of https://lkml.org/lkml/2016/7/26/347 and isn't merged in as you advised in another mail, i release this patch against linus's mainline for fixing relevant bugs completely, see test patch attached for verification details >From

[PATCH] mm/memblock.c: fix NULL dereference error

Hi Andrew, this patch is part of https://lkml.org/lkml/2016/7/26/347 and isn't merged in as you advised in another mail, i release this patch against linus's mainline for fixing relevant bugs completely, see test patch attached for verification details >From

Re: [PATCH net v2] 8139too: fix system hang when there is a tx timeout event.

From: Chunhao Lin Date: Mon, 1 Aug 2016 13:45:30 +0800 > If tx timeout event occur, kernel will call rtl8139_tx_timeout_task() to reset > hardware. But in this function, driver does not stop tx and rx function before > reset hardware, that will cause system hang. > > In this

Re: [PATCH net v2] 8139too: fix system hang when there is a tx timeout event.

From: Chunhao Lin Date: Mon, 1 Aug 2016 13:45:30 +0800 > If tx timeout event occur, kernel will call rtl8139_tx_timeout_task() to reset > hardware. But in this function, driver does not stop tx and rx function before > reset hardware, that will cause system hang. > > In this patch, add stop tx

[PATCH v6 0/2] clk: uniphier: add clock drivers for UniPhier SoCs

I split into two patches to make review easier. 1/2: core support code 2/2: data arrays Changes in v6: - Fix provided clock description a bit Changes in v5: - Assign each gating register bit with a separate clk - Fix examples in binding document to add specific compatible - Document

[PATCH v6 0/2] clk: uniphier: add clock drivers for UniPhier SoCs

I split into two patches to make review easier. 1/2: core support code 2/2: data arrays Changes in v6: - Fix provided clock description a bit Changes in v5: - Assign each gating register bit with a separate clk - Fix examples in binding document to add specific compatible - Document

[PATCH 1/3] perf/core: check return value of perf_event_read IPI

The call to smp_call_function_single in perf_event_read() may fail and, when it does, its error value is the one to return. Signed-off-by: David Carrillo-Cisneros Reviewed-by: Stephane Eranian --- kernel/events/core.c | 4 ++-- 1 file changed, 2

[PATCH 1/3] perf/core: check return value of perf_event_read IPI

The call to smp_call_function_single in perf_event_read() may fail and, when it does, its error value is the one to return. Signed-off-by: David Carrillo-Cisneros Reviewed-by: Stephane Eranian --- kernel/events/core.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

[RFC PATCH] softirq: fix tasklet_kill() usage and users

Semantically the expectation from the tasklet init/kill API should be as below. tasklet_init() == Init and Enable scheduling tasklet_kill() == Disable scheduling and Destroy tasklet_init() API exibit above behavior but not the tasklet_kill(). The tasklet handler can still get scheduled and run

[RFC PATCH] softirq: fix tasklet_kill() usage and users

Semantically the expectation from the tasklet init/kill API should be as below. tasklet_init() == Init and Enable scheduling tasklet_kill() == Disable scheduling and Destroy tasklet_init() API exibit above behavior but not the tasklet_kill(). The tasklet handler can still get scheduled and run

[PATCH v5 2/2] clk: uniphier: add clock data for UniPhier SoCs

Add clock data arrays for all UniPhier SoCs. Signed-off-by: Masahiro Yamada --- .../devicetree/bindings/clock/uniphier-clock.txt | 134 ++ drivers/clk/uniphier/Makefile | 3 + drivers/clk/uniphier/clk-uniphier-core.c

Re: [PULL] modules-next

Linus Torvalds writes: > So this feels wrong to me, can you guys please explain: > > On Sun, Jul 31, 2016 at 9:02 PM, Rusty Russell wrote: >> >> Ben Hutchings (3): >> module: Invalidate signatures on force-loaded modules >>

[PATCH v5 2/2] clk: uniphier: add clock data for UniPhier SoCs

Add clock data arrays for all UniPhier SoCs. Signed-off-by: Masahiro Yamada --- .../devicetree/bindings/clock/uniphier-clock.txt | 134 ++ drivers/clk/uniphier/Makefile | 3 + drivers/clk/uniphier/clk-uniphier-core.c | 91 +

Re: [PULL] modules-next

Linus Torvalds writes: > So this feels wrong to me, can you guys please explain: > > On Sun, Jul 31, 2016 at 9:02 PM, Rusty Russell wrote: >> >> Ben Hutchings (3): >> module: Invalidate signatures on force-loaded modules >> module: Disable MODULE_FORCE_LOAD when MODULE_SIG_FORCE is

[PATCH v6 1/2] clk: uniphier: add core support code for UniPhier clock driver

This includes UniPhier clock driver code, except SoC-specific data arrays. Signed-off-by: Masahiro Yamada --- MAINTAINERS | 1 + drivers/clk/Kconfig | 1 + drivers/clk/Makefile

[PATCH v6 1/2] clk: uniphier: add core support code for UniPhier clock driver

This includes UniPhier clock driver code, except SoC-specific data arrays. Signed-off-by: Masahiro Yamada --- MAINTAINERS | 1 + drivers/clk/Kconfig | 1 + drivers/clk/Makefile | 1 +

linux-next: Tree for Aug 2

Hi all, Please do not add material destined for v4.9 to your linux-next included branches until after v4.8-rc1 has been released. Changes since 20160801: My fixes tree contains: clocksource/drivers/clps_711x: fixup for "ARM: clps711x: Switch to MULTIPLATFORM" The akpm t

[PATCH v6 1/2] clk: uniphier: add core support code for UniPhier clock driver

This includes UniPhier clock driver code, except SoC-specific data arrays. Signed-off-by: Masahiro Yamada --- MAINTAINERS | 1 + drivers/clk/Kconfig | 1 + drivers/clk/Makefile

[PATCH v6 1/2] clk: uniphier: add core support code for UniPhier clock driver

This includes UniPhier clock driver code, except SoC-specific data arrays. Signed-off-by: Masahiro Yamada --- MAINTAINERS | 1 + drivers/clk/Kconfig | 1 + drivers/clk/Makefile | 1 +

linux-next: Tree for Aug 2

Hi all, Please do not add material destined for v4.9 to your linux-next included branches until after v4.8-rc1 has been released. Changes since 20160801: My fixes tree contains: clocksource/drivers/clps_711x: fixup for "ARM: clps711x: Switch to MULTIPLATFORM" The akpm t

[PATCH v6 0/2] clk: uniphier: add clock drivers for UniPhier SoCs

I split into two patches to make review easier. 1/2: core support code 2/2: data arrays Changes in v6: - Fix provided clock description a bit Changes in v5: - Assign each gating register bit with a separate clk - Fix examples in binding document to add specific compatible - Document

[PATCH v6 2/2] clk: uniphier: add clock data for UniPhier SoCs

Add clock data arrays for all UniPhier SoCs. Signed-off-by: Masahiro Yamada --- .../devicetree/bindings/clock/uniphier-clock.txt | 134 ++ drivers/clk/uniphier/Makefile | 3 + drivers/clk/uniphier/clk-uniphier-core.c

[PATCH v6 0/2] clk: uniphier: add clock drivers for UniPhier SoCs

I split into two patches to make review easier. 1/2: core support code 2/2: data arrays Changes in v6: - Fix provided clock description a bit Changes in v5: - Assign each gating register bit with a separate clk - Fix examples in binding document to add specific compatible - Document

[PATCH v6 2/2] clk: uniphier: add clock data for UniPhier SoCs

Add clock data arrays for all UniPhier SoCs. Signed-off-by: Masahiro Yamada --- .../devicetree/bindings/clock/uniphier-clock.txt | 134 ++ drivers/clk/uniphier/Makefile | 3 + drivers/clk/uniphier/clk-uniphier-core.c | 91 +

[PATCH v6 2/2] clk: uniphier: add clock data for UniPhier SoCs

Add clock data arrays for all UniPhier SoCs. Signed-off-by: Masahiro Yamada --- .../devicetree/bindings/clock/uniphier-clock.txt | 134 ++ drivers/clk/uniphier/Makefile | 3 + drivers/clk/uniphier/clk-uniphier-core.c

[PATCH v6 2/2] clk: uniphier: add clock data for UniPhier SoCs

Add clock data arrays for all UniPhier SoCs. Signed-off-by: Masahiro Yamada --- .../devicetree/bindings/clock/uniphier-clock.txt | 134 ++ drivers/clk/uniphier/Makefile | 3 + drivers/clk/uniphier/clk-uniphier-core.c | 91 +

Re: [PATCH v4 6/7] PM / devfreq: rockchip: add devfreq driver for rk3399 dmc

Hi Lin, On the next version, I'd like you to add the 'linux...@vger.kernel.org' because devfreq is a subsystem of power management. On 2016년 08월 02일 10:03, hl wrote: > Hi Chanwoo Choi, > > Thanks for reviewing so carefully. And i have some question: > > On 2016年08月01日 18:28, Chanwoo Choi

Re: [PATCH v4 6/7] PM / devfreq: rockchip: add devfreq driver for rk3399 dmc

Hi Lin, On the next version, I'd like you to add the 'linux...@vger.kernel.org' because devfreq is a subsystem of power management. On 2016년 08월 02일 10:03, hl wrote: > Hi Chanwoo Choi, > > Thanks for reviewing so carefully. And i have some question: > > On 2016年08月01日 18:28, Chanwoo Choi

[PATCH v3] reset: uniphier: add reset controller driver for UniPhier SoCs

This is the initial commit for UniPhier reset controller driver. Signed-off-by: Masahiro Yamada --- Changes in v3: - Fix examples in binding document to add specific compatible string - Assign each reset signal with a separate ID - Simplify reset_control

[PATCH v3] reset: uniphier: add reset controller driver for UniPhier SoCs

This is the initial commit for UniPhier reset controller driver. Signed-off-by: Masahiro Yamada --- Changes in v3: - Fix examples in binding document to add specific compatible string - Assign each reset signal with a separate ID - Simplify reset_control operations - Unify to a single

[PATCH v5 1/2] clk: uniphier: add core support code for UniPhier clock driver

This includes UniPhier clock driver code, except SoC-specific data arrays. Signed-off-by: Masahiro Yamada --- MAINTAINERS | 1 + drivers/clk/Kconfig | 1 + drivers/clk/Makefile

[PATCH v5 1/2] clk: uniphier: add core support code for UniPhier clock driver

This includes UniPhier clock driver code, except SoC-specific data arrays. Signed-off-by: Masahiro Yamada --- MAINTAINERS | 1 + drivers/clk/Kconfig | 1 + drivers/clk/Makefile | 1 +

[PATCH v5 0/2] clk: uniphier: add clock drivers for UniPhier SoCs

I split into two patches to make review easier. 1/2: core support code 2/2: data arrays Changes in v5: - Assign each gating register bit with a separate clk - Fix examples in binding document to add specific compatible - Document provided clocks for system clock Changes in v4: -

[PATCH v5 0/2] clk: uniphier: add clock drivers for UniPhier SoCs

I split into two patches to make review easier. 1/2: core support code 2/2: data arrays Changes in v5: - Assign each gating register bit with a separate clk - Fix examples in binding document to add specific compatible - Document provided clocks for system clock Changes in v4: -

Re: [PATCH v3 3/3] mac80211: mesh: fixed HT ies in beacon template

On 2016年08月01日 19:03, Johannes Berg wrote: But why is that behaviour *correct*? We still support 40 MHz bandwidth things, we just don't use them if we disable HT40. Or do you mean difference between "hardware capability" and "software capability" ? Do you think

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

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 sequence properties are under it. Signed-off-by: Peter Chen --- arch/arm/boot/dts/imx6qdl-udoo.dtsi | 26

Re: [PATCH v3 3/3] mac80211: mesh: fixed HT ies in beacon template

On 2016年08月01日 19:03, Johannes Berg wrote: But why is that behaviour *correct*? We still support 40 MHz bandwidth things, we just don't use them if we disable HT40. Or do you mean difference between "hardware capability" and "software capability" ? Do you think

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

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 sequence properties are under it. Signed-off-by: Peter Chen --- arch/arm/boot/dts/imx6qdl-udoo.dtsi | 26 +- 1

[PATCH v3] vfio : add aer process

During aer err occurs and resume do following to protect device from being accessed. 1. Make config space read only. 2. Disable INTx/MSI Interrupt. 3. Do nothing for bar regions. Signed-off-by: Zhou Jie --- v2-v3: 1. Call init_completion() in vfio_pci_probe. 2.

[PATCH v3] vfio : add aer process

During aer err occurs and resume do following to protect device from being accessed. 1. Make config space read only. 2. Disable INTx/MSI Interrupt. 3. Do nothing for bar regions. Signed-off-by: Zhou Jie --- v2-v3: 1. Call init_completion() in vfio_pci_probe. 2. Call reinit_completion() in

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

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 parent device is chipidea core. So, in order to let the common driver get parent's node, we let the

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

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 parent device is chipidea core. So, in order to let the common driver get parent's node, we let the core's device node equals

Re: [v3,2/6] power: add power sequence library

On Fri, Jul 29, 2016 at 01:06:48PM -0700, Matthias Kaehlcke wrote: > >... > > > >+static int pwrseq_generic_get(struct device_node *np, struct pwrseq *pwrseq) > >+{ > >+struct pwrseq_generic *pwrseq_gen = to_generic_pwrseq(pwrseq); > >+enum of_gpio_flags flags; > >+int reset_gpio, ret

Re: [v3,2/6] power: add power sequence library

On Fri, Jul 29, 2016 at 01:06:48PM -0700, Matthias Kaehlcke wrote: > >... > > > >+static int pwrseq_generic_get(struct device_node *np, struct pwrseq *pwrseq) > >+{ > >+struct pwrseq_generic *pwrseq_gen = to_generic_pwrseq(pwrseq); > >+enum of_gpio_flags flags; > >+int reset_gpio, ret

[PATCH v4 3/6] binding-doc: usb: usb-device: add optional properties for power sequence

Add optional properties for power sequence. Signed-off-by: Peter Chen Acked-by: Rob Herring --- Documentation/devicetree/bindings/usb/usb-device.txt | 10 +- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git

[PATCH v4 3/6] binding-doc: usb: usb-device: add optional properties for power sequence

Add optional properties for power sequence. Signed-off-by: Peter Chen Acked-by: Rob Herring --- Documentation/devicetree/bindings/usb/usb-device.txt | 10 +- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/Documentation/devicetree/bindings/usb/usb-device.txt

[PATCH v4 1/6] binding-doc: power: pwrseq-generic: add binding doc for generic power sequence library

Add binding doc for generic power sequence library. Signed-off-by: Peter Chen Acked-by: Philipp Zabel Acked-by: Rob Herring --- .../bindings/power/pwrseq/pwrseq-generic.txt | 48 ++ 1 file changed, 48

[PATCH v4 4/6] usb: core: add power sequence handling for USB devices

Some hard-wired USB devices need to do power sequence to let the device work normally, the typical power sequence like: enable USB PHY clock, toggle reset pin, etc. But current Linux USB driver lacks of such code to do it, it may cause some hard-wired USB devices works abnormal or can't be

[PATCH v4 1/6] binding-doc: power: pwrseq-generic: add binding doc for generic power sequence library

Add binding doc for generic power sequence library. Signed-off-by: Peter Chen Acked-by: Philipp Zabel Acked-by: Rob Herring --- .../bindings/power/pwrseq/pwrseq-generic.txt | 48 ++ 1 file changed, 48 insertions(+) create mode 100644

[PATCH v4 4/6] usb: core: add power sequence handling for USB devices

Some hard-wired USB devices need to do power sequence to let the device work normally, the typical power sequence like: enable USB PHY clock, toggle reset pin, etc. But current Linux USB driver lacks of such code to do it, it may cause some hard-wired USB devices works abnormal or can't be

  1   2   3   4   5   6   7   8   9   10   >