Re: [RFC][PATCH 1/3 v2] usb: dwc2: Add extcon support to dwc2 driver

Hi John, I give a some guide for extcon API. This patch uses the deprecated extcon API (extcon_get_cable_state_). So, I recommend that you better to use following extcon API: - extcon_get_cable_state_() -> extcon_get_state() - extcon_register_notifier() -> devm_extcon_register_notifier() Best

Re: [RFC][PATCH 1/3 v2] usb: dwc2: Add extcon support to dwc2 driver

Hi John, I give a some guide for extcon API. This patch uses the deprecated extcon API (extcon_get_cable_state_). So, I recommend that you better to use following extcon API: - extcon_get_cable_state_() -> extcon_get_state() - extcon_register_notifier() -> devm_extcon_register_notifier() Best

Re: [RFC][PATCH] HACK: usb: dwc2: Workaround case where GOTGCTL state is wrong

On 12/6/2016 5:48 PM, John Stultz wrote: > Hey John, > Just wanted to send this by you, as it seems something is > slightly off with the GOTGCTL state when removing a otg adapter > cable. The following seems to work around the issue I'm seeing. > > Let me know if you have any thoughts on this.

Re: [RFC][PATCH] HACK: usb: dwc2: Workaround case where GOTGCTL state is wrong

On 12/6/2016 5:48 PM, John Stultz wrote: > Hey John, > Just wanted to send this by you, as it seems something is > slightly off with the GOTGCTL state when removing a otg adapter > cable. The following seems to work around the issue I'm seeing. > > Let me know if you have any thoughts on this.

Re: [PATCH 03/12] power_supply: axp288_charger: Replace the extcon API

Hi Sebastian, On 2016년 12월 07일 12:05, Sebastian Reichel wrote: > Hi Chanwoo, > > On Tue, Dec 06, 2016 at 09:26:14AM +0900, Chanwoo Choi wrote: >> Could you please review and pick the patch3/4 for power-supply driver? > > Patches look fine. As I expect the merge window to open next week I >

Re: [PATCH 03/12] power_supply: axp288_charger: Replace the extcon API

Hi Sebastian, On 2016년 12월 07일 12:05, Sebastian Reichel wrote: > Hi Chanwoo, > > On Tue, Dec 06, 2016 at 09:26:14AM +0900, Chanwoo Choi wrote: >> Could you please review and pick the patch3/4 for power-supply driver? > > Patches look fine. As I expect the merge window to open next week I >

Re: [PATCH v2] tun: Use netif_receive_skb instead of netif_rx

On 2016年12月07日 11:25, David Miller wrote: From: Jason Wang Date: Wed, 7 Dec 2016 11:21:11 +0800 David, looks like this commit is not in net-next.git. Please help to check. Take a look, it should be there now. Yes, thanks.

Re: [PATCH v2] tun: Use netif_receive_skb instead of netif_rx

On 2016年12月07日 11:25, David Miller wrote: From: Jason Wang Date: Wed, 7 Dec 2016 11:21:11 +0800 David, looks like this commit is not in net-next.git. Please help to check. Take a look, it should be there now. Yes, thanks.

Re: [PATCH] i2c: rk3x: keep i2c irq ON in suspend

Hi Doug, 在 2016/12/7 0:31, Doug Anderson 写道: Hi, On Tue, Dec 6, 2016 at 12:12 AM, David.Wu wrote: Hi Heiko, 在 2016/12/5 18:54, Heiko Stuebner 写道: Hi David, Am Montag, 5. Dezember 2016, 16:02:59 CET schrieb David Wu: During suspend there may still be some i2c

Re: [PATCH] i2c: rk3x: keep i2c irq ON in suspend

Hi Doug, 在 2016/12/7 0:31, Doug Anderson 写道: Hi, On Tue, Dec 6, 2016 at 12:12 AM, David.Wu wrote: Hi Heiko, 在 2016/12/5 18:54, Heiko Stuebner 写道: Hi David, Am Montag, 5. Dezember 2016, 16:02:59 CET schrieb David Wu: During suspend there may still be some i2c access happening. And if we

[PATCH] tracing: fix "softirq" flag detection

The 's' flag is supposed to indicate that a softirq is running. This can be detected by testing the preempt_count with SOFTIRQ_OFFSET. The current code tests the preempt_count with SOFTIRQ_MASK, which would be true even when softirqs are disabled but not serving a softirq. Change-Id:

[PATCH] tracing: fix "softirq" flag detection

The 's' flag is supposed to indicate that a softirq is running. This can be detected by testing the preempt_count with SOFTIRQ_OFFSET. The current code tests the preempt_count with SOFTIRQ_MASK, which would be true even when softirqs are disabled but not serving a softirq. Change-Id:

Re: [PATCH v2] tun: Use netif_receive_skb instead of netif_rx

On 2016年12月02日 03:43, David Miller wrote: From: Andrey Konovalov Date: Thu, 1 Dec 2016 10:34:40 +0100 This patch changes tun.c to call netif_receive_skb instead of netif_rx when a packet is received (if CONFIG_4KSTACKS is not enabled to avoid stack exhaustion). The

Re: [PATCH v2] tun: Use netif_receive_skb instead of netif_rx

On 2016年12月02日 03:43, David Miller wrote: From: Andrey Konovalov Date: Thu, 1 Dec 2016 10:34:40 +0100 This patch changes tun.c to call netif_receive_skb instead of netif_rx when a packet is received (if CONFIG_4KSTACKS is not enabled to avoid stack exhaustion). The difference between the

Re: [PATCH v4 2/2] perf probe: add sdt probes arguments into the uprobe cmd string

Hello Alexis, On Sat, 26 Nov 2016 01:58:03 +0100 Alexis Berlemont wrote: > An sdt probe can be associated with arguments but they were not passed > to the user probe tracing interface (uprobe_events); this patch adapts > the sdt argument descriptors according to the

Re: [PATCH v4 2/2] perf probe: add sdt probes arguments into the uprobe cmd string

Hello Alexis, On Sat, 26 Nov 2016 01:58:03 +0100 Alexis Berlemont wrote: > An sdt probe can be associated with arguments but they were not passed > to the user probe tracing interface (uprobe_events); this patch adapts > the sdt argument descriptors according to the uprobe input format. Great!

Re: [PATCH v2] tun: Use netif_receive_skb instead of netif_rx

From: Jason Wang Date: Wed, 7 Dec 2016 11:21:11 +0800 > David, looks like this commit is not in net-next.git. > > Please help to check. Take a look, it should be there now.

Re: [PATCH v2] tun: Use netif_receive_skb instead of netif_rx

From: Jason Wang Date: Wed, 7 Dec 2016 11:21:11 +0800 > David, looks like this commit is not in net-next.git. > > Please help to check. Take a look, it should be there now.

Re: [PATCH v2] drm/bridge: analogix: Don't return -EINVAL when panel not support PSR in PSR functions

On 12/07/2016 06:27 AM, zain wang wrote: We will ignored PSR setting if panel not support it. So, in this case, we should return from analogix_dp_enable/disable_psr() without any error code. Let's retrun 0 instead of -EINVAL when panel not support PSR in analogix_dp_enable/disable_psr().

Re: [PATCH v2] drm/bridge: analogix: Don't return -EINVAL when panel not support PSR in PSR functions

On 12/07/2016 06:27 AM, zain wang wrote: We will ignored PSR setting if panel not support it. So, in this case, we should return from analogix_dp_enable/disable_psr() without any error code. Let's retrun 0 instead of -EINVAL when panel not support PSR in analogix_dp_enable/disable_psr().

Re: [PATCH] n900 device tree: cleanup

Hi Tony, It looks like this fell through the cracks. Apart from inconsistent patch subject: Reviewed-By: Sebastian Reichel -- Sebastian On Tue, Oct 11, 2016 at 10:12:43AM +0200, Pavel Machek wrote: > Fix GPIO comment to be consistent with rest of file and add comment what >

Re: [PATCH] n900 device tree: cleanup

Hi Tony, It looks like this fell through the cracks. Apart from inconsistent patch subject: Reviewed-By: Sebastian Reichel -- Sebastian On Tue, Oct 11, 2016 at 10:12:43AM +0200, Pavel Machek wrote: > Fix GPIO comment to be consistent with rest of file and add comment what > tpa6130 is. > >

Re: [PATCH 03/12] power_supply: axp288_charger: Replace the extcon API

Hi Chanwoo, On Tue, Dec 06, 2016 at 09:26:14AM +0900, Chanwoo Choi wrote: > Could you please review and pick the patch3/4 for power-supply driver? Patches look fine. As I expect the merge window to open next week I would rather not queue this for 4.10 and instead do it once 4.10-rc1 has been

Re: [PATCH 03/12] power_supply: axp288_charger: Replace the extcon API

Hi Chanwoo, On Tue, Dec 06, 2016 at 09:26:14AM +0900, Chanwoo Choi wrote: > Could you please review and pick the patch3/4 for power-supply driver? Patches look fine. As I expect the merge window to open next week I would rather not queue this for 4.10 and instead do it once 4.10-rc1 has been

Re: [PATCH] vfio/pci: Support error recovery

On 12/06/2016 11:25 PM, Alex Williamson wrote: > On Tue, 6 Dec 2016 14:11:03 +0800 > Cao jin wrote: > >> On 12/06/2016 12:17 AM, Alex Williamson wrote: >>> On Mon, 5 Dec 2016 13:52:03 +0800 >>> Cao jin wrote: >>> On 12/04/2016 11:30

Re: [PATCH] vfio/pci: Support error recovery

On 12/06/2016 11:25 PM, Alex Williamson wrote: > On Tue, 6 Dec 2016 14:11:03 +0800 > Cao jin wrote: > >> On 12/06/2016 12:17 AM, Alex Williamson wrote: >>> On Mon, 5 Dec 2016 13:52:03 +0800 >>> Cao jin wrote: >>> On 12/04/2016 11:30 PM, Alex Williamson wrote: > On Sun, 4 Dec

Re: [PATCH v3 0/7] irda: w83977af_ir: Neatening

From: Joe Perches Date: Tue, 6 Dec 2016 10:15:59 -0800 > Originally on top of Arnd's overly long udelay patches because I > noticed a misindented block. That's now already fixed along with some > other whitespace problems. These patches are the remainder style > issues from

Re: [PATCH v3 0/7] irda: w83977af_ir: Neatening

From: Joe Perches Date: Tue, 6 Dec 2016 10:15:59 -0800 > Originally on top of Arnd's overly long udelay patches because I > noticed a misindented block. That's now already fixed along with some > other whitespace problems. These patches are the remainder style > issues from my original

Re: [PATCH] vfio/pci: Support error recovery

On 12/06/2016 11:35 PM, Alex Williamson wrote: > On Tue, 6 Dec 2016 18:46:04 +0800 > Cao jin wrote: > >> On 12/06/2016 12:59 PM, Alex Williamson wrote: >>> On Tue, 6 Dec 2016 05:55:28 +0200 >>> "Michael S. Tsirkin" wrote: >>> On Mon, Dec 05,

Re: [PATCH] vfio/pci: Support error recovery

On 12/06/2016 11:35 PM, Alex Williamson wrote: > On Tue, 6 Dec 2016 18:46:04 +0800 > Cao jin wrote: > >> On 12/06/2016 12:59 PM, Alex Williamson wrote: >>> On Tue, 6 Dec 2016 05:55:28 +0200 >>> "Michael S. Tsirkin" wrote: >>> On Mon, Dec 05, 2016 at 09:17:30AM -0700, Alex Williamson

Re: [PATCH 7/7] arm: Add livepatch necessary arch selects into Kconfig

On Tue, 6 Dec 2016 17:06:07 + Abel Vesa wrote: > This adds HAVE_LIVEPATCH, MODULES_USE_ELF_RELA and HAVE_LIVEPATCH > to arm Kconfig. > > Signed-off-by: Abel Vesa Patch 5, 6 and 7 really ought to be one patch. -- Steve

Re: [PATCH 7/7] arm: Add livepatch necessary arch selects into Kconfig

On Tue, 6 Dec 2016 17:06:07 + Abel Vesa wrote: > This adds HAVE_LIVEPATCH, MODULES_USE_ELF_RELA and HAVE_LIVEPATCH > to arm Kconfig. > > Signed-off-by: Abel Vesa Patch 5, 6 and 7 really ought to be one patch. -- Steve

Re: [PATCH v4 1/2] perf sdt: add scanning of sdt probles arguments

On Sat, 26 Nov 2016 01:58:02 +0100 Alexis Berlemont wrote: > During a "perf buildid-cache --add" command, the section > ".note.stapsdt" of the "added" binary is scanned in order to list the > available SDT markers available in a binary. The parts containing the >

Re: [PATCH v4 1/2] perf sdt: add scanning of sdt probles arguments

On Sat, 26 Nov 2016 01:58:02 +0100 Alexis Berlemont wrote: > During a "perf buildid-cache --add" command, the section > ".note.stapsdt" of the "added" binary is scanned in order to list the > available SDT markers available in a binary. The parts containing the > probes arguments were left

Re: [PATCH 4/7] arm: Add ftrace with regs support

On Tue, 6 Dec 2016 17:06:04 + Abel Vesa wrote: > This adds __ftrace_regs_caller which, unlike __ftrace_caller, > adds register saving/restoring and livepatch handling if > the pc register gets modified by klp_ftrace_handler. > > Signed-off-by: Abel Vesa

Re: [PATCH 4/7] arm: Add ftrace with regs support

On Tue, 6 Dec 2016 17:06:04 + Abel Vesa wrote: > This adds __ftrace_regs_caller which, unlike __ftrace_caller, > adds register saving/restoring and livepatch handling if > the pc register gets modified by klp_ftrace_handler. > > Signed-off-by: Abel Vesa > --- >

Re: [PATCH] spi: davinci: Allow device tree devices to use DMA

On 11/21/2016 02:37 AM, Sekhar Nori wrote: On Sunday 20 November 2016 10:31 PM, David Lechner wrote: On 11/20/2016 06:59 AM, Sekhar Nori wrote: On Saturday 19 November 2016 10:11 AM, David Lechner wrote: @@ -400,6 +401,9 @@ static int davinci_spi_of_setup(struct spi_device *spi)

Re: [PATCH] spi: davinci: Allow device tree devices to use DMA

On 11/21/2016 02:37 AM, Sekhar Nori wrote: On Sunday 20 November 2016 10:31 PM, David Lechner wrote: On 11/20/2016 06:59 AM, Sekhar Nori wrote: On Saturday 19 November 2016 10:11 AM, David Lechner wrote: @@ -400,6 +401,9 @@ static int davinci_spi_of_setup(struct spi_device *spi)

Re: [PATCH RFC] drm/sun4i: rgb: Add 5% tolerance to dot clock frequency check

On Wed, Dec 7, 2016 at 1:29 AM, Maxime Ripard wrote: > On Thu, Nov 24, 2016 at 07:22:31PM +0800, Chen-Yu Tsai wrote: >> The panels shipped with Allwinner devices are very "generic", i.e. >> they do not have model numbers or reliable sources of information >> for

Re: [PATCH RFC] drm/sun4i: rgb: Add 5% tolerance to dot clock frequency check

On Wed, Dec 7, 2016 at 1:29 AM, Maxime Ripard wrote: > On Thu, Nov 24, 2016 at 07:22:31PM +0800, Chen-Yu Tsai wrote: >> The panels shipped with Allwinner devices are very "generic", i.e. >> they do not have model numbers or reliable sources of information >> for the timings (that we know of)

Re: [PATCH 3/3] ARM: Add support for CONFIG_DEBUG_VIRTUAL

On 12/06/2016 06:00 PM, Laura Abbott wrote: >> @@ -261,6 +261,16 @@ static inline unsigned long __phys_to_virt(phys_addr_t >> x) >> unsigned long)(kaddr) - PAGE_OFFSET) >> PAGE_SHIFT) + \ >> PHYS_PFN_OFFSET) >> >> +#define __pa_symbol_nodebug(x) ((x) - (unsigned

Re: [PATCH 3/3] ARM: Add support for CONFIG_DEBUG_VIRTUAL

On 12/06/2016 06:00 PM, Laura Abbott wrote: >> @@ -261,6 +261,16 @@ static inline unsigned long __phys_to_virt(phys_addr_t >> x) >> unsigned long)(kaddr) - PAGE_OFFSET) >> PAGE_SHIFT) + \ >> PHYS_PFN_OFFSET) >> >> +#define __pa_symbol_nodebug(x) ((x) - (unsigned

Re: [PATCH 03/10] perf sched timehist: Handle zero sample->tid properly

On Mon, Dec 05, 2016 at 07:52:57PM -0800, David Ahern wrote: > On 12/5/16 7:40 PM, Namhyung Kim wrote: > > Sometimes samples have tid of 0 but non-0 pid. It ends up having a > > Any idea how that happens? It seems that an exiting task wakes up its parent and the parent might call wait(2)

Re: [PATCH 03/10] perf sched timehist: Handle zero sample->tid properly

On Mon, Dec 05, 2016 at 07:52:57PM -0800, David Ahern wrote: > On 12/5/16 7:40 PM, Namhyung Kim wrote: > > Sometimes samples have tid of 0 but non-0 pid. It ends up having a > > Any idea how that happens? It seems that an exiting task wakes up its parent and the parent might call wait(2)

Re: [PATCH 3/3] iio: cros_ec_activity: add ChromeOS EC Activity Sensors

Hi Gwendal, [auto build test WARNING on iio/togreg] [also build test WARNING on next-20161206] [cannot apply to v4.9-rc8] [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/Thierry-Escande/mfd

[PATCH] arm: dts: rockchip: add qos node for rk3288

when pd power on/off, the qos regs need to save and restore. Signed-off-by: Elaine Zhang --- arch/arm/boot/dts/rk3288.dtsi | 84 +++ 1 file changed, 84 insertions(+) diff --git a/arch/arm/boot/dts/rk3288.dtsi

Re: [PATCH 3/3] iio: cros_ec_activity: add ChromeOS EC Activity Sensors

Hi Gwendal, [auto build test WARNING on iio/togreg] [also build test WARNING on next-20161206] [cannot apply to v4.9-rc8] [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/Thierry-Escande/mfd

[PATCH] arm: dts: rockchip: add qos node for rk3288

when pd power on/off, the qos regs need to save and restore. Signed-off-by: Elaine Zhang --- arch/arm/boot/dts/rk3288.dtsi | 84 +++ 1 file changed, 84 insertions(+) diff --git a/arch/arm/boot/dts/rk3288.dtsi b/arch/arm/boot/dts/rk3288.dtsi index

Re: [PATCH 06/10] perf sched timehist: Introduce struct idle_time_data

On Mon, Dec 05, 2016 at 08:07:09PM -0800, David Ahern wrote: > On 12/5/16 7:40 PM, Namhyung Kim wrote: > > The struct idle_time_data is to keep idle stats with callchains entering > > to the idle task. The normal thread_runtime calculation is done > > transparently since it extends the struct

Re: [PATCH 06/10] perf sched timehist: Introduce struct idle_time_data

On Mon, Dec 05, 2016 at 08:07:09PM -0800, David Ahern wrote: > On 12/5/16 7:40 PM, Namhyung Kim wrote: > > The struct idle_time_data is to keep idle stats with callchains entering > > to the idle task. The normal thread_runtime calculation is done > > transparently since it extends the struct

[PATCH 08/16] drivers/fsi: Add crc4 helpers

From: Jeremy Kerr Add some helpers for the crc checks for the slave configuration table. This works 4-bits-at-a-time, using a simple table approach. We will need this in the FSI core code, as well as any master implementations that need to calculate CRCs in software.

[PATCH 09/16] drivers/fsi: Implement slave initialisation

From: Jeremy Kerr Create fsi_slave devices during the master scan. Signed-off-by: Jeremy Kerr Signed-off-by: Chris Bostic --- drivers/fsi/fsi-core.c | 55 -- 1 file changed, 53

[PATCH 09/16] drivers/fsi: Implement slave initialisation

From: Jeremy Kerr Create fsi_slave devices during the master scan. Signed-off-by: Jeremy Kerr Signed-off-by: Chris Bostic --- drivers/fsi/fsi-core.c | 55 -- 1 file changed, 53 insertions(+), 2 deletions(-) diff --git a/drivers/fsi/fsi-core.c

[PATCH 08/16] drivers/fsi: Add crc4 helpers

From: Jeremy Kerr Add some helpers for the crc checks for the slave configuration table. This works 4-bits-at-a-time, using a simple table approach. We will need this in the FSI core code, as well as any master implementations that need to calculate CRCs in software. Signed-off-by: Jeremy Kerr

[PATCH 11/16] drivers/fsi: Add device read/write/peek functions

From: Jeremy Kerr This change introduces the fsi device API: simple read, write and peek accessors for the devices' address spaces. Includes contributions from Chris Bostic Signed-off-by: Jeremy Kerr Signed-off-by: Chris Bostic

[PATCH 12/16] drivers/fsi: Set up links for slave communication

From: Chris Bostic Enable each link and send a break command in preparation for scanning each link for slaves. Signed-off-by: Chris Bostic --- drivers/fsi/fsi-core.c | 39 --- drivers/fsi/fsi-master.h | 2 ++ 2

[PATCH 04/16] drivers/fsi: Add fsi master definition

From: Jeremy Kerr Signed-off-by: Jeremy Kerr Signed-off-by: Chris Bostic --- drivers/fsi/fsi-core.c | 20 drivers/fsi/fsi-master.h | 37 + 2 files changed, 57 insertions(+) create

[PATCH 11/16] drivers/fsi: Add device read/write/peek functions

From: Jeremy Kerr This change introduces the fsi device API: simple read, write and peek accessors for the devices' address spaces. Includes contributions from Chris Bostic Signed-off-by: Jeremy Kerr Signed-off-by: Chris Bostic --- drivers/fsi/fsi-core.c | 47

[PATCH 12/16] drivers/fsi: Set up links for slave communication

From: Chris Bostic Enable each link and send a break command in preparation for scanning each link for slaves. Signed-off-by: Chris Bostic --- drivers/fsi/fsi-core.c | 39 --- drivers/fsi/fsi-master.h | 2 ++ 2 files changed, 38 insertions(+), 3

[PATCH 04/16] drivers/fsi: Add fsi master definition

From: Jeremy Kerr Signed-off-by: Jeremy Kerr Signed-off-by: Chris Bostic --- drivers/fsi/fsi-core.c | 20 drivers/fsi/fsi-master.h | 37 + 2 files changed, 57 insertions(+) create mode 100644 drivers/fsi/fsi-master.h diff --git

Re: [PATCH 3/7] arm: module: Add apply_relocate_add

Hi Abel, [auto build test ERROR on linus/master] [also build test ERROR on v4.9-rc8 next-20161206] [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/Abel-Vesa/arm-Add-livepatch-support/20161207

Re: [PATCH 3/7] arm: module: Add apply_relocate_add

Hi Abel, [auto build test ERROR on linus/master] [also build test ERROR on v4.9-rc8 next-20161206] [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/Abel-Vesa/arm-Add-livepatch-support/20161207

Re: [PATCH v3 3/3] ARM: da850: fix da850_set_pll0rate()

On 12/05/2016 04:09 AM, Bartosz Golaszewski wrote: This function is confusing - its second argument is an index to the freq table, not the requested clock rate in Hz, but it's used as the set_rate callback for the pll0 clock. It leads to an oops when the caller doesn't know the internals and

Re: [PATCH v3 3/3] ARM: da850: fix da850_set_pll0rate()

On 12/05/2016 04:09 AM, Bartosz Golaszewski wrote: This function is confusing - its second argument is an index to the freq table, not the requested clock rate in Hz, but it's used as the set_rate callback for the pll0 clock. It leads to an oops when the caller doesn't know the internals and

Re: [PATCH 3/3] ARM: Add support for CONFIG_DEBUG_VIRTUAL

On 12/06/2016 11:53 AM, Florian Fainelli wrote: > x86 has an option: CONFIG_DEBUG_VIRTUAL to do additional checks on > virt_to_phys calls. The goal is to catch users who are calling > virt_to_phys on non-linear addresses immediately. This includes caller > using __virt_to_phys() on image addresses

Re: [PATCH 3/3] ARM: Add support for CONFIG_DEBUG_VIRTUAL

On 12/06/2016 11:53 AM, Florian Fainelli wrote: > x86 has an option: CONFIG_DEBUG_VIRTUAL to do additional checks on > virt_to_phys calls. The goal is to catch users who are calling > virt_to_phys on non-linear addresses immediately. This includes caller > using __virt_to_phys() on image addresses

Re: [PATCH v3 10/30] perf clang: Add builtin clang support ant test case

On Tue, Dec 6, 2016 at 1:02 PM, Arnaldo Carvalho de Melo wrote: [acme@jouet linux]$ ls -lah /tmp/perf > -rwxr-xr-x. 1 acme acme 41M Dec 6 17:58 /tmp/perf awesome. that's reasonable and matches to what I see with libbcc.so We had few tricks before to reduce it into <30M

Re: [PATCH v3 10/30] perf clang: Add builtin clang support ant test case

On Tue, Dec 6, 2016 at 1:02 PM, Arnaldo Carvalho de Melo wrote: [acme@jouet linux]$ ls -lah /tmp/perf > -rwxr-xr-x. 1 acme acme 41M Dec 6 17:58 /tmp/perf awesome. that's reasonable and matches to what I see with libbcc.so We had few tricks before to reduce it into <30M range, but they were too

Re: [PATCH 04/10] perf sched timehist: Split is_idle_sample()

Hi David, On Mon, Dec 05, 2016 at 07:57:43PM -0800, David Ahern wrote: > On 12/5/16 7:40 PM, Namhyung Kim wrote: > > The is_idle_sample() function actually does more than determining > > whether sample come from idle task. Split the callchain part into > > save_task_callchain() to make it

Re: [PATCH 04/10] perf sched timehist: Split is_idle_sample()

Hi David, On Mon, Dec 05, 2016 at 07:57:43PM -0800, David Ahern wrote: > On 12/5/16 7:40 PM, Namhyung Kim wrote: > > The is_idle_sample() function actually does more than determining > > whether sample come from idle task. Split the callchain part into > > save_task_callchain() to make it

Re: [PATCH v4 2/7] MFD: add STM32 General Purpose Timer driver

Hi Benjamin, [auto build test ERROR on iio/togreg] [also build test ERROR on v4.9-rc8] [cannot apply to next-20161206] [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/Benjamin-Gaignard/Add-PWM

Re: [PATCH v4 2/7] MFD: add STM32 General Purpose Timer driver

Hi Benjamin, [auto build test ERROR on iio/togreg] [also build test ERROR on v4.9-rc8] [cannot apply to next-20161206] [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/Benjamin-Gaignard/Add-PWM

Re: [PATCH v3 1/3] ARM: da850: fix infinite loop in clk_set_rate()

On 12/05/2016 04:09 AM, Bartosz Golaszewski wrote: The aemif clock is added twice to the lookup table in da850.c. This breaks the children list of pll0_sysclk3 as we're using the same list links in struct clk. When calling clk_set_rate(), we get stuck in propagate_rate(). _clk is used twice in

Re: [PATCH v3 1/3] ARM: da850: fix infinite loop in clk_set_rate()

On 12/05/2016 04:09 AM, Bartosz Golaszewski wrote: The aemif clock is added twice to the lookup table in da850.c. This breaks the children list of pll0_sysclk3 as we're using the same list links in struct clk. When calling clk_set_rate(), we get stuck in propagate_rate(). _clk is used twice in

Re: [PATCH 00/16] FSI device driver introduction

Hi. On Tue, Dec 06, 2016 at 06:14:21PM -0600, Chris Bostic wrote: > [...] > > Introduction of the IBM 'Flexible Support Interface' (FSI) bus device > driver. FSI is a high fan out serial bus consisting of a clock and a serial > data line capable of running at speeds up to 166 MHz. > > [...] I

Re: [PATCH 00/16] FSI device driver introduction

Hi. On Tue, Dec 06, 2016 at 06:14:21PM -0600, Chris Bostic wrote: > [...] > > Introduction of the IBM 'Flexible Support Interface' (FSI) bus device > driver. FSI is a high fan out serial bus consisting of a clock and a serial > data line capable of running at speeds up to 166 MHz. > > [...] I

Re: [PATCH v2] tty: serial: fsl_lpuart: fix del_timer_sync() vs timer routine deadlock

On 2016-12-04 07:49, Nikita Yushchenko wrote: > Problem found via lockdep: > > - lpuart_set_termios() calls del_timer_sync(>lpuart_timer) while > holding sport->port.lock > > - sport->lpuart_timer routine is lpuart_timer_func() that calls > lpuart_copy_rx_to_tty() that acquires same lock. >

Re: [PATCH v2] tty: serial: fsl_lpuart: fix del_timer_sync() vs timer routine deadlock

On 2016-12-04 07:49, Nikita Yushchenko wrote: > Problem found via lockdep: > > - lpuart_set_termios() calls del_timer_sync(>lpuart_timer) while > holding sport->port.lock > > - sport->lpuart_timer routine is lpuart_timer_func() that calls > lpuart_copy_rx_to_tty() that acquires same lock. >

[RFC][PATCH] HACK: usb: dwc2: Workaround case where GOTGCTL state is wrong

Hey John, Just wanted to send this by you, as it seems something is slightly off with the GOTGCTL state when removing a otg adapter cable. The following seems to work around the issue I'm seeing. Let me know if you have any thoughts on this. thanks -john When removing a USB-A to USB-otg

[RFC][PATCH] HACK: usb: dwc2: Workaround case where GOTGCTL state is wrong

Hey John, Just wanted to send this by you, as it seems something is slightly off with the GOTGCTL state when removing a otg adapter cable. The following seems to work around the issue I'm seeing. Let me know if you have any thoughts on this. thanks -john When removing a USB-A to USB-otg

Re: [PATCH 4/5] acpi, nfit: fix bus vs dimm confusion in xlat_status

On Tue, Dec 6, 2016 at 4:39 PM, Dan Williams wrote: > Given dimms and bus commands share the same command number space we need > to be careful that we are translating status in the correct context. > Otherwise we can, for example, fail an ND_CMD_GET_CONFIG_SIZE command >

Re: [PATCH 4/5] acpi, nfit: fix bus vs dimm confusion in xlat_status

On Tue, Dec 6, 2016 at 4:39 PM, Dan Williams wrote: > Given dimms and bus commands share the same command number space we need > to be careful that we are translating status in the correct context. > Otherwise we can, for example, fail an ND_CMD_GET_CONFIG_SIZE command > because max_xfer is zero.

Re: [RFC][PATCH 1/3 v2] usb: dwc2: Add extcon support to dwc2 driver

On Tue, Dec 6, 2016 at 4:35 PM, John Stultz wrote: > On Tue, Dec 6, 2016 at 4:26 PM, John Youn wrote: >> On 12/6/2016 4:05 PM, John Stultz wrote: >>> On Tue, Dec 6, 2016 at 3:17 PM, John Youn wrote: Also, do you really

Re: [RFC][PATCH 1/3 v2] usb: dwc2: Add extcon support to dwc2 driver

On Tue, Dec 6, 2016 at 4:35 PM, John Stultz wrote: > On Tue, Dec 6, 2016 at 4:26 PM, John Youn wrote: >> On 12/6/2016 4:05 PM, John Stultz wrote: >>> On Tue, Dec 6, 2016 at 3:17 PM, John Youn wrote: Also, do you really need this at all? Wasn't your system previously able to detect the

Re: [PATCH 0/7] arm: Add livepatch support

On 2016/12/7 1:06, Abel Vesa wrote: This is just an idea I've been trying out for a while now. Just in case somebody wants to play with it, this applies to linux-arm/for-next. Also please note that this was only tested in qemu, but I will do some testing on some real hardware in the following

Re: [PATCH 0/7] arm: Add livepatch support

On 2016/12/7 1:06, Abel Vesa wrote: This is just an idea I've been trying out for a while now. Just in case somebody wants to play with it, this applies to linux-arm/for-next. Also please note that this was only tested in qemu, but I will do some testing on some real hardware in the following

linux-next: build failure after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (powerpc64le perf) failed like this: LINK /home/sfr/next/perf/fixdep /bin/sh: 1: /home/sfr/next/perf//fixdep: Permission denied tools/build/Makefile.build:91: recipe for target '/home/sfr/next/perf/pmu-events/jevents.o' failed

linux-next: build failure after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (powerpc64le perf) failed like this: LINK /home/sfr/next/perf/fixdep /bin/sh: 1: /home/sfr/next/perf//fixdep: Permission denied tools/build/Makefile.build:91: recipe for target '/home/sfr/next/perf/pmu-events/jevents.o' failed

[PATCH] device-dax: fix private mapping restriction, permit read-only

Hugh notes in response to commit 4cb19355ea19 "device-dax: fail all private mapping attempts": "I think that is more restrictive than you intended: haven't tried, but I believe it rejects a PROT_READ, MAP_SHARED, O_RDONLY fd mmap, leaving no way to mmap /dev/dax without write permission to

[PATCH] device-dax: fix private mapping restriction, permit read-only

Hugh notes in response to commit 4cb19355ea19 "device-dax: fail all private mapping attempts": "I think that is more restrictive than you intended: haven't tried, but I believe it rejects a PROT_READ, MAP_SHARED, O_RDONLY fd mmap, leaving no way to mmap /dev/dax without write permission to

Re: [PATCH] clk: uniphier: Fix build with gcc-4.4.

Hi Stephen, 2016-12-07 8:16 GMT+09:00 Stephen Boyd : > On 12/03, Masahiro Yamada wrote: >> Hi Vinson, >> >> 2016-12-03 9:37 GMT+09:00 Vinson Lee : >> > gcc-4.4 has issues with anonymous unions in initializers. >> > >> > CC

Re: [PATCH] clk: uniphier: Fix build with gcc-4.4.

Hi Stephen, 2016-12-07 8:16 GMT+09:00 Stephen Boyd : > On 12/03, Masahiro Yamada wrote: >> Hi Vinson, >> >> 2016-12-03 9:37 GMT+09:00 Vinson Lee : >> > gcc-4.4 has issues with anonymous unions in initializers. >> > >> > CC drivers/clk/uniphier/clk-uniphier-sys.o >> >

[PATCH v3 1/2] clk: uniphier: add CPU-gear change (cpufreq) support

Core support code for CPU frequency changes, which will be used by the generic cpufreq driver. The register view is different from the generic clk-mux; it has a separate status register, and an update bit to load the register setting. Signed-off-by: Masahiro Yamada

[PATCH v3 2/2] clk: uniphier: add cpufreq data for LD11, LD20 SoCs

Add more data to 64bit SoCs for the cpufreq support. Signed-off-by: Masahiro Yamada --- Changes in v3: - Do not use anonymous union Changes in v2: - Drop clock data of 32 bit SoCs. Add 64 bit SoC data for now. drivers/clk/uniphier/clk-uniphier-sys.c | 32

[PATCH v3 1/2] clk: uniphier: add CPU-gear change (cpufreq) support

Core support code for CPU frequency changes, which will be used by the generic cpufreq driver. The register view is different from the generic clk-mux; it has a separate status register, and an update bit to load the register setting. Signed-off-by: Masahiro Yamada --- Changes in v3: - Do

[PATCH v3 2/2] clk: uniphier: add cpufreq data for LD11, LD20 SoCs

Add more data to 64bit SoCs for the cpufreq support. Signed-off-by: Masahiro Yamada --- Changes in v3: - Do not use anonymous union Changes in v2: - Drop clock data of 32 bit SoCs. Add 64 bit SoC data for now. drivers/clk/uniphier/clk-uniphier-sys.c | 32

[PATCH v7 2/3] media: change au0828 to use Media Device Allocator API

Change au0828 to use Media Device Allocator API to allocate media device with the parent usb struct device as the key, so it can be shared with the snd_usb_audio driver. Signed-off-by: Shuah Khan --- No changes since v6 drivers/media/usb/au0828/au0828-core.c | 12

[PATCH v7 2/3] media: change au0828 to use Media Device Allocator API

Change au0828 to use Media Device Allocator API to allocate media device with the parent usb struct device as the key, so it can be shared with the snd_usb_audio driver. Signed-off-by: Shuah Khan --- No changes since v6 drivers/media/usb/au0828/au0828-core.c | 12

[PATCH v7 1/3] media: Media Device Allocator API

Media Device Allocator API to allows multiple drivers share a media device. Using this API, drivers can allocate a media device with the shared struct device as the key. Once the media device is allocated by a driver, other drivers can get a reference to it. The media device is released when all

[PATCH v7 1/3] media: Media Device Allocator API

Media Device Allocator API to allows multiple drivers share a media device. Using this API, drivers can allocate a media device with the shared struct device as the key. Once the media device is allocated by a driver, other drivers can get a reference to it. The media device is released when all

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