[PATCH net] rxrpc: Wake up the transmitter if Rx window size increases on the peer

The RxRPC ACK packet may contain an extension that includes the peer's current Rx window size for this call. We adjust the local Tx window size to match. However, the transmitter can stall if the receive window is reduced to 0 by the peer and then reopened. This is because the normal way that

[PATCH net] rxrpc: Wake up the transmitter if Rx window size increases on the peer

The RxRPC ACK packet may contain an extension that includes the peer's current Rx window size for this call. We adjust the local Tx window size to match. However, the transmitter can stall if the receive window is reduced to 0 by the peer and then reopened. This is because the normal way that

Re: [PATCH] powerpc: asm: convert directive .llong to .8byte

Daniel Axtens writes: > Hi Tobin, > >> .llong is an undocumented PPC specific directive. The generic >> equivalent is .quad, but even better (because it's self describing) is >> .8byte. >> >> Convert directives .llong -> .8byte >> >> Signed-off-by: Tobin C. Harding

Re: [PATCH] powerpc: asm: convert directive .llong to .8byte

Daniel Axtens writes: > Hi Tobin, > >> .llong is an undocumented PPC specific directive. The generic >> equivalent is .quad, but even better (because it's self describing) is >> .8byte. >> >> Convert directives .llong -> .8byte >> >> Signed-off-by: Tobin C. Harding >> --- >> >> Fixes: issue #33

Re: [RFC] mm/compaction: ignore block suitable after check large free page

On 03/10/2017 05:20 AM, Yisheng Xie wrote: > If the migrate target is a large free page and we ignore suitable, > it may not good for defrag. So move the ignore block suitable after > check large free page. Right. But in practice I expect close to no impact, because direct compaction shouldn't

Re: [RFC] mm/compaction: ignore block suitable after check large free page

On 03/10/2017 05:20 AM, Yisheng Xie wrote: > If the migrate target is a large free page and we ignore suitable, > it may not good for defrag. So move the ignore block suitable after > check large free page. Right. But in practice I expect close to no impact, because direct compaction shouldn't

Re: [PATCH v2 1/2] doc: bindings: Add bindings documentation for mtd nvmem

On 03/10/2017 07:38 AM, Maxime Ripard wrote: > Hi Marek, > > On Fri, Mar 10, 2017 at 05:52:36AM +0100, Marek Vasut wrote: >> On 03/10/2017 05:06 AM, Moritz Fischer wrote: >>> On Thu, Mar 9, 2017 at 7:17 PM, Marek Vasut wrote: On 03/07/2017 09:26 AM, Alban wrote: >

Re: [PATCH v2 1/2] doc: bindings: Add bindings documentation for mtd nvmem

On 03/10/2017 07:38 AM, Maxime Ripard wrote: > Hi Marek, > > On Fri, Mar 10, 2017 at 05:52:36AM +0100, Marek Vasut wrote: >> On 03/10/2017 05:06 AM, Moritz Fischer wrote: >>> On Thu, Mar 9, 2017 at 7:17 PM, Marek Vasut wrote: On 03/07/2017 09:26 AM, Alban wrote: > Config data for

Re: [PATCH] refcount: add refcount_t API kernel-doc comments

* David Windsor wrote: > This adds kernel-doc comments for the new refcount_t API. > > v2: incorporate fixes from Peter Zijlstra and Ingo Molnar > > Signed-off-by: David Windsor > --- > lib/refcount.c | 122 >

Re: [PATCH] refcount: add refcount_t API kernel-doc comments

* David Windsor wrote: > This adds kernel-doc comments for the new refcount_t API. > > v2: incorporate fixes from Peter Zijlstra and Ingo Molnar > > Signed-off-by: David Windsor > --- > lib/refcount.c | 122 > +++-- > 1 file changed, 110

Re: [GIT pull] CPU hotplug updates for 4.9

* Bart Van Assche wrote: > On Thu, 2017-03-09 at 18:43 +0100, Thomas Gleixner wrote: > > Ok, so it's random. Now it would be interesting what the rest of the system > > does when this happens. I still have no idea why that IOAT setting has any > > influence. > >

Re: [GIT pull] CPU hotplug updates for 4.9

* Bart Van Assche wrote: > On Thu, 2017-03-09 at 18:43 +0100, Thomas Gleixner wrote: > > Ok, so it's random. Now it would be interesting what the rest of the system > > does when this happens. I still have no idea why that IOAT setting has any > > influence. > > Hello Thomas, > > The

Re: [PATCH 1/2] x86/nmi: Optimize the check for being in the repeat_nmi code

* Andy Lutomirski wrote: > > It had nothing to do with speedup. Linus said that the current code makes > > the > > assembly programmer in him die a little. I want to cure that. > > One might argue that the world would be a better place if the assembly > programmer in

Re: [PATCH 1/2] x86/nmi: Optimize the check for being in the repeat_nmi code

* Andy Lutomirski wrote: > > It had nothing to do with speedup. Linus said that the current code makes > > the > > assembly programmer in him die a little. I want to cure that. > > One might argue that the world would be a better place if the assembly > programmer in some people died a

Re: [PATCH v19 0/4] Introduce usb charger framework to deal with the usb gadget power negotation

On 10 March 2017 at 14:30, Jun Li wrote: >> >> > >> >> > Will generic phy need add extcon as well? >> >> >> >> Yes, will add a 'struct extcon_dev*' in 'struct usb_phy', which will >> >> be common code. >> >> >> > >> > I mean the common code need add 'struct extcon_dev' into both

Re: [PATCH v19 0/4] Introduce usb charger framework to deal with the usb gadget power negotation

On 10 March 2017 at 14:30, Jun Li wrote: >> >> > >> >> > Will generic phy need add extcon as well? >> >> >> >> Yes, will add a 'struct extcon_dev*' in 'struct usb_phy', which will >> >> be common code. >> >> >> > >> > I mean the common code need add 'struct extcon_dev' into both 'struct >> > phy'

Re: [RFC PATCH] phy: samsung: move the Samsung specific phy files to "samsung" directory

Hi All, On 03/09/2017 09:10 PM, Krzysztof Kozlowski wrote: > On Thu, Mar 9, 2017 at 1:56 PM, Kishon Vijay Abraham I wrote: >> Hi, >> >> On Thursday 09 March 2017 05:03 PM, Jaehoon Chung wrote: >>> Make the "samsung" directory and move the Samsung specific files to >>> there for

Re: [RFC PATCH] phy: samsung: move the Samsung specific phy files to "samsung" directory

Hi All, On 03/09/2017 09:10 PM, Krzysztof Kozlowski wrote: > On Thu, Mar 9, 2017 at 1:56 PM, Kishon Vijay Abraham I wrote: >> Hi, >> >> On Thursday 09 March 2017 05:03 PM, Jaehoon Chung wrote: >>> Make the "samsung" directory and move the Samsung specific files to >>> there for maintaining the

Re: [PATCH] sched: Wake up all non-exclusive waiters in __wake_up_common()

On Wed, Mar 08, 2017 at 09:21:52AM +0900, Byungchul Park wrote: > __wake_up_common() should wake up all non-exclusive waiters and > exclusive waiters as many as nr_exclusive, but currently it does not. > > Consider a wait queue like the following for example: > >A(exclusive) ->

Re: [PATCH] sched: Wake up all non-exclusive waiters in __wake_up_common()

On Wed, Mar 08, 2017 at 09:21:52AM +0900, Byungchul Park wrote: > __wake_up_common() should wake up all non-exclusive waiters and > exclusive waiters as many as nr_exclusive, but currently it does not. > > Consider a wait queue like the following for example: > >A(exclusive) ->

Re: [PATCH] leds/trigger/activity: add a system activity LED trigger

Hi Jacek, On Thu, Mar 09, 2017 at 09:48:39PM +0100, Jacek Anaszewski wrote: > Hi Willy, > > Thanks for the patch. > > Unfortunately I'm getting following build break, while trying to > test it on recent linux-next: > > drivers/leds/trigger/ledtrig-activity.c: In function >

Re: [PATCH] leds/trigger/activity: add a system activity LED trigger

Hi Jacek, On Thu, Mar 09, 2017 at 09:48:39PM +0100, Jacek Anaszewski wrote: > Hi Willy, > > Thanks for the patch. > > Unfortunately I'm getting following build break, while trying to > test it on recent linux-next: > > drivers/leds/trigger/ledtrig-activity.c: In function >

[PATCH] Fix V8 device information issue

From: Masaki Ota -Fix the issue that V8(E7=73 03 28) devices are not assined correct device information from OTP. -Specified correct OTP bit for the V8 device setting of Button pad, DualPoint and Touchpad size. Signed-off-by: Masaki Ota ---

[PATCH] Fix V8 device information issue

From: Masaki Ota -Fix the issue that V8(E7=73 03 28) devices are not assined correct device information from OTP. -Specified correct OTP bit for the V8 device setting of Button pad, DualPoint and Touchpad size. Signed-off-by: Masaki Ota --- drivers/input/mouse/alps.c | 74

Re: [PATCH v2 1/2] doc: bindings: Add bindings documentation for mtd nvmem

Hi Marek, On Fri, Mar 10, 2017 at 05:52:36AM +0100, Marek Vasut wrote: > On 03/10/2017 05:06 AM, Moritz Fischer wrote: > > On Thu, Mar 9, 2017 at 7:17 PM, Marek Vasut wrote: > >> On 03/07/2017 09:26 AM, Alban wrote: > >>> Config data for drivers, like MAC addresses, is

Re: [PATCH v2 1/2] doc: bindings: Add bindings documentation for mtd nvmem

Hi Marek, On Fri, Mar 10, 2017 at 05:52:36AM +0100, Marek Vasut wrote: > On 03/10/2017 05:06 AM, Moritz Fischer wrote: > > On Thu, Mar 9, 2017 at 7:17 PM, Marek Vasut wrote: > >> On 03/07/2017 09:26 AM, Alban wrote: > >>> Config data for drivers, like MAC addresses, is often stored in MTD. > >>>

RE: [PATCH v19 0/4] Introduce usb charger framework to deal with the usb gadget power negotation

> -Original Message- > From: Baolin Wang [mailto:baolin.w...@linaro.org] > Sent: Thursday, March 09, 2017 7:23 PM > To: Jun Li > Cc: NeilBrown ; Felipe Balbi ; Greg KH > ; Sebastian Reichel ;

RE: [PATCH v19 0/4] Introduce usb charger framework to deal with the usb gadget power negotation

> -Original Message- > From: Baolin Wang [mailto:baolin.w...@linaro.org] > Sent: Thursday, March 09, 2017 7:23 PM > To: Jun Li > Cc: NeilBrown ; Felipe Balbi ; Greg KH > ; Sebastian Reichel ; Dmitry > Eremin-Solenikov ; David Woodhouse > ; r...@kernel.org; Marek Szyprowski > ; Ruslan

[PATCH v6 09/11] drivers: perf: hisi: Miscellanous node(MN) event counting in perf

From: Shaokun Zhang 1. Add support to count MN hardware events. 2. Mn events are listed in sysfs at /sys/devices/hisi_mn_2/events/ The events can be selected as shown in perf list e.g.: For MN_READ_REQUEST event for Super CPU cluster 2 the event format is -e

[PATCH v6 11/11] dts: arm64: hip07: Add Hisilicon SoC PMU support

Add nodes for djtag, L3 cache and MN to support uncore events. Signed-off-by: Anurup M --- arch/arm64/boot/dts/hisilicon/hip07.dtsi | 79 1 file changed, 79 insertions(+) diff --git a/arch/arm64/boot/dts/hisilicon/hip07.dtsi

[PATCH v6 08/11] drivers: perf: hisi: use poll method to avoid L3C counter overflow

Add hrtimer support which use poll method to avoid counter overflow when overflow IRQ is not supported in hardware. The L3 cache PMU use N-N SPI interrupt which has no support in kernel mainline. So use hrtimer to poll and update event counter to avoid overflow condition for L3 cache PMU. An

[PATCH v6 09/11] drivers: perf: hisi: Miscellanous node(MN) event counting in perf

From: Shaokun Zhang 1. Add support to count MN hardware events. 2. Mn events are listed in sysfs at /sys/devices/hisi_mn_2/events/ The events can be selected as shown in perf list e.g.: For MN_READ_REQUEST event for Super CPU cluster 2 the event format is -e "hisi_mn_2/read_req/"

[PATCH v6 11/11] dts: arm64: hip07: Add Hisilicon SoC PMU support

Add nodes for djtag, L3 cache and MN to support uncore events. Signed-off-by: Anurup M --- arch/arm64/boot/dts/hisilicon/hip07.dtsi | 79 1 file changed, 79 insertions(+) diff --git a/arch/arm64/boot/dts/hisilicon/hip07.dtsi

[PATCH v6 08/11] drivers: perf: hisi: use poll method to avoid L3C counter overflow

Add hrtimer support which use poll method to avoid counter overflow when overflow IRQ is not supported in hardware. The L3 cache PMU use N-N SPI interrupt which has no support in kernel mainline. So use hrtimer to poll and update event counter to avoid overflow condition for L3 cache PMU. An

[PATCH v6 07/11] drivers: perf: hisi: Add support for Hisilicon SoC event counters

1. HiP05/06/07 uncore PMU to support different hardware event counters. 2. Hisilicon PMU shall use the DJTAG hardware interface to access hardware event counters and configuration register. 3. Routines to enable/disable/add/del/start/stop hardware event counting. 4. Add support to count L3

[PATCH v6 10/11] drivers: perf: hisi: use poll method when no IRQ for MN counter overflow

When no IRQ is supported in hardware, use hrtimer to poll and update event counter and avoid overflow condition for MN PMU. An interval of 8 seconds is used for the hrtimer. Signed-off-by: Anurup M Signed-off-by: Shaokun Zhang Signed-off-by:

[PATCH v6 06/11] drivers: perf: hisi: Add support for Hisilicon Djtag driver

From: Tan Xiaojun The Hisilicon Djtag is an independent component which connects with some other components in the SoC by Debug Bus. This driver can be configured to access the registers of connecting components (like L3 cache) during real time debugging. Signed-off-by:

[PATCH v6 10/11] drivers: perf: hisi: use poll method when no IRQ for MN counter overflow

When no IRQ is supported in hardware, use hrtimer to poll and update event counter and avoid overflow condition for MN PMU. An interval of 8 seconds is used for the hrtimer. Signed-off-by: Anurup M Signed-off-by: Shaokun Zhang Signed-off-by: Dikshit N ---

[PATCH v6 06/11] drivers: perf: hisi: Add support for Hisilicon Djtag driver

From: Tan Xiaojun The Hisilicon Djtag is an independent component which connects with some other components in the SoC by Debug Bus. This driver can be configured to access the registers of connecting components (like L3 cache) during real time debugging. Signed-off-by: Tan Xiaojun

[PATCH v6 07/11] drivers: perf: hisi: Add support for Hisilicon SoC event counters

1. HiP05/06/07 uncore PMU to support different hardware event counters. 2. Hisilicon PMU shall use the DJTAG hardware interface to access hardware event counters and configuration register. 3. Routines to enable/disable/add/del/start/stop hardware event counting. 4. Add support to count L3

[PATCH v6 05/11] drivers: perf: hisi: Update Kconfig for Hisilicon PMU support

Update Kconfig for HiP05/06/07 PMU support. Signed-off-by: Anurup M Signed-off-by: Shaokun Zhang Signed-off-by: John Garry --- drivers/perf/Kconfig | 8 1 file changed, 8 insertions(+) diff --git

[PATCH v6 05/11] drivers: perf: hisi: Update Kconfig for Hisilicon PMU support

Update Kconfig for HiP05/06/07 PMU support. Signed-off-by: Anurup M Signed-off-by: Shaokun Zhang Signed-off-by: John Garry --- drivers/perf/Kconfig | 8 1 file changed, 8 insertions(+) diff --git a/drivers/perf/Kconfig b/drivers/perf/Kconfig index 1e95d6a..f0aa818 100644 ---

[PATCH v6 04/11] Documentation: perf: hisi: Documentation for HiP05/06/07 PMU event counting.

Documentation for perf usage and Hisilicon SoC PMU uncore events. The Hisilicon SOC has event counters for hardware modules like L3 cache, Miscellaneous node etc. These events are all uncore. Signed-off-by: Anurup M Signed-off-by: Shaokun Zhang

[PATCH v6 04/11] Documentation: perf: hisi: Documentation for HiP05/06/07 PMU event counting.

Documentation for perf usage and Hisilicon SoC PMU uncore events. The Hisilicon SOC has event counters for hardware modules like L3 cache, Miscellaneous node etc. These events are all uncore. Signed-off-by: Anurup M Signed-off-by: Shaokun Zhang --- Documentation/perf/hisi-pmu.txt | 76

[PATCH v6 03/11] dt-bindings: perf: hisi: Add Devicetree bindings for Hisilicon SoC PMU

1) Device tree bindings for Hisilicon SoC PMU. 2) Add example for Hisilicon L3 cache and MN PMU. 3) Add child nodes of L3C and MN in djtag bindings example. Signed-off-by: Anurup M Signed-off-by: Shaokun Zhang Acked-by: Rob Herring

[PATCH v6 02/11] dt-bindings: hisi: Add Hisilicon HiP05/06/07 Djtag dts bindings

From: Tan Xiaojun Add Hisilicon HiP05/06/07 Djtag dts bindings for CPU and IO Die Signed-off-by: Tan Xiaojun Signed-off-by: Anurup M Acked-by: Rob Herring --- .../devicetree/bindings/arm/hisilicon/djtag.txt

[PATCH v6 03/11] dt-bindings: perf: hisi: Add Devicetree bindings for Hisilicon SoC PMU

1) Device tree bindings for Hisilicon SoC PMU. 2) Add example for Hisilicon L3 cache and MN PMU. 3) Add child nodes of L3C and MN in djtag bindings example. Signed-off-by: Anurup M Signed-off-by: Shaokun Zhang Acked-by: Rob Herring --- .../devicetree/bindings/arm/hisilicon/djtag.txt| 25

[PATCH v6 02/11] dt-bindings: hisi: Add Hisilicon HiP05/06/07 Djtag dts bindings

From: Tan Xiaojun Add Hisilicon HiP05/06/07 Djtag dts bindings for CPU and IO Die Signed-off-by: Tan Xiaojun Signed-off-by: Anurup M Acked-by: Rob Herring --- .../devicetree/bindings/arm/hisilicon/djtag.txt| 51 ++ 1 file changed, 51 insertions(+) create mode 100644

[PATCH v6 01/11] arm64: MAINTAINERS: hisi: Add hisilicon SoC PMU support

Add support for Hisilicon SoC hardware event counters for HiP05/06/07 chip versions. Signed-off-by: Anurup M --- MAINTAINERS | 9 + 1 file changed, 9 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 6d7b7a7..c2f9806 100644 --- a/MAINTAINERS +++

[PATCH v6 01/11] arm64: MAINTAINERS: hisi: Add hisilicon SoC PMU support

Add support for Hisilicon SoC hardware event counters for HiP05/06/07 chip versions. Signed-off-by: Anurup M --- MAINTAINERS | 9 + 1 file changed, 9 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 6d7b7a7..c2f9806 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -5958,6

[PATCH v6 00/11] perf: arm64: Support for Hisilicon SoC Hardware event counters

Provide Support for Hisilicon SoC(HiP05/06/07) Hardware event counters. The Hisilicon SoC HiP0x series has many uncore or non-CPU performance events and counters units. This v6 version is rebased to 4.11-rc1. This patch series is implemented refering to arm-cci, Intel/AMD uncore and also the

[PATCH v6 00/11] perf: arm64: Support for Hisilicon SoC Hardware event counters

Provide Support for Hisilicon SoC(HiP05/06/07) Hardware event counters. The Hisilicon SoC HiP0x series has many uncore or non-CPU performance events and counters units. This v6 version is rebased to 4.11-rc1. This patch series is implemented refering to arm-cci, Intel/AMD uncore and also the

Re: [PATCH v5 3/4] dt-bindings: phy: Add support for QMP phy

On 03/09/2017 04:37 PM, Bjorn Andersson wrote: On Thu 09 Mar 10:07 CET 2017, Vivek Gautam wrote: [..] + phy@34000 { + compatible = "qcom,msm8996-qmp-pcie-phy"; + reg = <0x034000 0x488>; Drop the leading 0 from the address. Okay, will drop it. +

Re: [PATCH v5 3/4] dt-bindings: phy: Add support for QMP phy

On 03/09/2017 04:37 PM, Bjorn Andersson wrote: On Thu 09 Mar 10:07 CET 2017, Vivek Gautam wrote: [..] + phy@34000 { + compatible = "qcom,msm8996-qmp-pcie-phy"; + reg = <0x034000 0x488>; Drop the leading 0 from the address. Okay, will drop it. +

[PATCH 5/5] block_dev: make blkdev_dio_pool a non-rescuing bioset

Allocations from blkdev_dio_pool are never made under generic_make_request, so this bioset does not need a rescuer thread. Signed-off-by: NeilBrown --- fs/block_dev.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/block_dev.c b/fs/block_dev.c index

[PATCH 4/5] blk: use non-rescuing bioset for q->bio_split.

A rescuing bioset is only useful if there might be bios from that same bioset on the bio_list_on_stack queue at a time when bio_alloc_bioset() is called. This never applies to q->bio_split. Allocations from q->bio_split are only ever made from blk_queue_split() which is only ever called early in

[PATCH 5/5] block_dev: make blkdev_dio_pool a non-rescuing bioset

Allocations from blkdev_dio_pool are never made under generic_make_request, so this bioset does not need a rescuer thread. Signed-off-by: NeilBrown --- fs/block_dev.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/block_dev.c b/fs/block_dev.c index

[PATCH 4/5] blk: use non-rescuing bioset for q->bio_split.

A rescuing bioset is only useful if there might be bios from that same bioset on the bio_list_on_stack queue at a time when bio_alloc_bioset() is called. This never applies to q->bio_split. Allocations from q->bio_split are only ever made from blk_queue_split() which is only ever called early in

[PATCH 2/5] blk: remove bio_set arg from blk_queue_split()

blk_queue_split() is always called with the last arg being q->bio_split, where 'q' is the first arg. Also blk_queue_split() sometimes uses the passed-in 'bs' and sometimes uses q->bio_split. This is inconsistent and unnecessary. Remove the last arg and always use q->bio_split inside

[PATCH 3/5] blk: make the bioset rescue_workqueue optional.

This patch converts bioset_create() and bioset_create_nobvec() to not create a workqueue so alloctions will never trigger punt_bios_to_rescuer(). It also introduces bioset_create_rescued() and bioset_create_nobvec_rescued() which preserve the old behaviour. *All* callers of bioset_create() and

[PATCH 2/5] blk: remove bio_set arg from blk_queue_split()

blk_queue_split() is always called with the last arg being q->bio_split, where 'q' is the first arg. Also blk_queue_split() sometimes uses the passed-in 'bs' and sometimes uses q->bio_split. This is inconsistent and unnecessary. Remove the last arg and always use q->bio_split inside

[PATCH 3/5] blk: make the bioset rescue_workqueue optional.

This patch converts bioset_create() and bioset_create_nobvec() to not create a workqueue so alloctions will never trigger punt_bios_to_rescuer(). It also introduces bioset_create_rescued() and bioset_create_nobvec_rescued() which preserve the old behaviour. *All* callers of bioset_create() and

[PATCH 1/5] blk: Ensure users for current->bio_list can see the full list.

Commit 79bd99596b73 ("blk: improve order of bio handling in generic_make_request()") changed current->bio_list so that it did not contain *all* of the queued bios, but only those submitted by the currently running make_request_fn. There are two places which walk the list and requeue selected

[PATCH 1/5] blk: Ensure users for current->bio_list can see the full list.

Commit 79bd99596b73 ("blk: improve order of bio handling in generic_make_request()") changed current->bio_list so that it did not contain *all* of the queued bios, but only those submitted by the currently running make_request_fn. There are two places which walk the list and requeue selected

[PATCH 0/5] Updates following recent generic_make_request improvement

This is a rebase of the series I sent earlier, based on the very latest from Linus, which included my first patch. The first fixes a problem that patch introduced, and so should go to Linux promptly. The others are more general improvements and can go in the normal course of events. It is

[PATCH 0/5] Updates following recent generic_make_request improvement

This is a rebase of the series I sent earlier, based on the very latest from Linus, which included my first patch. The first fixes a problem that patch introduced, and so should go to Linux promptly. The others are more general improvements and can go in the normal course of events. It is

Re: outreachy

On Thu, Mar 09, 2017 at 02:15:21PM -0800, Florian Fainelli wrote: > On 03/09/2017 01:20 PM, Greg KH wrote: > > On Thu, Mar 09, 2017 at 01:56:49PM -0700, Stephen Warren wrote: > >> On 03/09/2017 01:51 PM, Scott Branden wrote: > >>> Hi Julia, > >>> > >>> On 17-03-09 12:36 PM, Julia Lawall wrote: >

Re: outreachy

On Thu, Mar 09, 2017 at 02:15:21PM -0800, Florian Fainelli wrote: > On 03/09/2017 01:20 PM, Greg KH wrote: > > On Thu, Mar 09, 2017 at 01:56:49PM -0700, Stephen Warren wrote: > >> On 03/09/2017 01:51 PM, Scott Branden wrote: > >>> Hi Julia, > >>> > >>> On 17-03-09 12:36 PM, Julia Lawall wrote: >

[PATCH net, v2] dccp/tcp: fix routing redirect race

As Eric Dumazet pointed out this also needs to be fixed in IPv6. v2: Contains the IPv6 tcp/Ipv6 dccp patches as well. We have seen a few incidents lately where a dst_enty has been freed with a dangling TCP socket reference (sk->sk_dst_cache) pointing to that dst_entry. If the conditions/timings

[PATCH net, v2] dccp/tcp: fix routing redirect race

As Eric Dumazet pointed out this also needs to be fixed in IPv6. v2: Contains the IPv6 tcp/Ipv6 dccp patches as well. We have seen a few incidents lately where a dst_enty has been freed with a dangling TCP socket reference (sk->sk_dst_cache) pointing to that dst_entry. If the conditions/timings

Re: [PATCH] Minor coding guideline Fix in lusture module

On Mar 9, 2017, at 05:22, Pushkar Jambhlekar wrote: > Subject: Minor coding guideline Fix in lusture module I suspect the patchbot is unhappy with the subject line not containing anything useful, and not containing the subsystem name. Something like: staging/lustre/llite:

Re: [PATCH] Minor coding guideline Fix in lusture module

On Mar 9, 2017, at 05:22, Pushkar Jambhlekar wrote: > Subject: Minor coding guideline Fix in lusture module I suspect the patchbot is unhappy with the subject line not containing anything useful, and not containing the subsystem name. Something like: staging/lustre/llite: replace "unsigned"

Re: [PATCH v2] blk: improve order of bio handling in generic_make_request()

On Thu, Mar 09 2017, Jens Axboe wrote: > On 03/09/2017 09:32 PM, NeilBrown wrote: >> >> I started looking further at the improvements we can make once >> generic_make_request is fixed, and realised that I had missed an >> important detail in this patch. >> Several places test current->bio_list,

Re: [PATCH v2] blk: improve order of bio handling in generic_make_request()

On Thu, Mar 09 2017, Jens Axboe wrote: > On 03/09/2017 09:32 PM, NeilBrown wrote: >> >> I started looking further at the improvements we can make once >> generic_make_request is fixed, and realised that I had missed an >> important detail in this patch. >> Several places test current->bio_list,

Re: [PATCH net, v1] dccp/tcp: fix routing redirect race

On Fri, Mar 10, 2017 at 3:23 PM, Eric Dumazet wrote: > On Fri, 2017-03-10 at 14:31 +1100, Jon Maxwell wrote: >> As Eric Dumazet pointed out this also needs to be fixed in IPv6. >> v1: Contains the IPv6 patch as well. > >> Fixes: ceb3320610d6 ("ipv4: Kill routes during

Re: [PATCH net, v1] dccp/tcp: fix routing redirect race

On Fri, Mar 10, 2017 at 3:23 PM, Eric Dumazet wrote: > On Fri, 2017-03-10 at 14:31 +1100, Jon Maxwell wrote: >> As Eric Dumazet pointed out this also needs to be fixed in IPv6. >> v1: Contains the IPv6 patch as well. > >> Fixes: ceb3320610d6 ("ipv4: Kill routes during PMTU/redirect updates.") >>

[PATCH v5 02/39] [media] dt-bindings: Add bindings for i.MX media driver

Add bindings documentation for the i.MX media driver. Signed-off-by: Steve Longerbeam --- Documentation/devicetree/bindings/media/imx.txt | 74 + 1 file changed, 74 insertions(+) create mode 100644

[PATCH v5 02/39] [media] dt-bindings: Add bindings for i.MX media driver

Add bindings documentation for the i.MX media driver. Signed-off-by: Steve Longerbeam --- Documentation/devicetree/bindings/media/imx.txt | 74 + 1 file changed, 74 insertions(+) create mode 100644 Documentation/devicetree/bindings/media/imx.txt diff --git

[PATCH v5 04/39] ARM: dts: imx6qdl: Add compatible, clocks, irqs to MIPI CSI-2 node

Add to the MIPI CSI2 receiver node: compatible strings, interrupt sources, and clocks. Signed-off-by: Steve Longerbeam --- arch/arm/boot/dts/imx6qdl.dtsi | 7 +++ 1 file changed, 7 insertions(+) diff --git a/arch/arm/boot/dts/imx6qdl.dtsi

[PATCH v5 04/39] ARM: dts: imx6qdl: Add compatible, clocks, irqs to MIPI CSI-2 node

Add to the MIPI CSI2 receiver node: compatible strings, interrupt sources, and clocks. Signed-off-by: Steve Longerbeam --- arch/arm/boot/dts/imx6qdl.dtsi | 7 +++ 1 file changed, 7 insertions(+) diff --git a/arch/arm/boot/dts/imx6qdl.dtsi b/arch/arm/boot/dts/imx6qdl.dtsi index

[PATCH v5 07/39] ARM: dts: imx6qdl-sabrelite: remove erratum ERR006687 workaround

There is a pin conflict with GPIO_6. This pin functions as a power input pin to the OV5642 camera sensor, but ENET uses it as the h/w workaround for erratum ERR006687, to wake-up the ARM cores on normal RX and TX packet done events. So we need to remove the h/w workaround to support the OV5642.

[PATCH v5 07/39] ARM: dts: imx6qdl-sabrelite: remove erratum ERR006687 workaround

There is a pin conflict with GPIO_6. This pin functions as a power input pin to the OV5642 camera sensor, but ENET uses it as the h/w workaround for erratum ERR006687, to wake-up the ARM cores on normal RX and TX packet done events. So we need to remove the h/w workaround to support the OV5642.

[PATCH v5 06/39] ARM: dts: imx6qdl: add capture-subsystem device

Signed-off-by: Steve Longerbeam --- arch/arm/boot/dts/imx6dl.dtsi | 5 + arch/arm/boot/dts/imx6q.dtsi | 5 + 2 files changed, 10 insertions(+) diff --git a/arch/arm/boot/dts/imx6dl.dtsi b/arch/arm/boot/dts/imx6dl.dtsi index 8958c4a..a959c76 100644 ---

[PATCH v5 06/39] ARM: dts: imx6qdl: add capture-subsystem device

Signed-off-by: Steve Longerbeam --- arch/arm/boot/dts/imx6dl.dtsi | 5 + arch/arm/boot/dts/imx6q.dtsi | 5 + 2 files changed, 10 insertions(+) diff --git a/arch/arm/boot/dts/imx6dl.dtsi b/arch/arm/boot/dts/imx6dl.dtsi index 8958c4a..a959c76 100644 --- a/arch/arm/boot/dts/imx6dl.dtsi

[PATCH v5 12/39] ARM: dts: imx6-sabreauto: add pinctrl for gpt input capture

Add pinctrl groups for both GPT input capture channels. Signed-off-by: Steve Longerbeam --- arch/arm/boot/dts/imx6qdl-sabreauto.dtsi | 12 1 file changed, 12 insertions(+) diff --git a/arch/arm/boot/dts/imx6qdl-sabreauto.dtsi

[PATCH v5 12/39] ARM: dts: imx6-sabreauto: add pinctrl for gpt input capture

Add pinctrl groups for both GPT input capture channels. Signed-off-by: Steve Longerbeam --- arch/arm/boot/dts/imx6qdl-sabreauto.dtsi | 12 1 file changed, 12 insertions(+) diff --git a/arch/arm/boot/dts/imx6qdl-sabreauto.dtsi b/arch/arm/boot/dts/imx6qdl-sabreauto.dtsi index

[PATCH v5 18/39] [media] v4l: subdev: Add function to validate frame interval

If the pads on both sides of a link specify a frame interval, then those frame intervals should match. Create the exported function v4l2_subdev_link_validate_frame_interval() to verify this. This function can be called in a subdevice's media_entity_operations or v4l2_subdev_pad_ops link_validate

[PATCH v5 18/39] [media] v4l: subdev: Add function to validate frame interval

If the pads on both sides of a link specify a frame interval, then those frame intervals should match. Create the exported function v4l2_subdev_link_validate_frame_interval() to verify this. This function can be called in a subdevice's media_entity_operations or v4l2_subdev_pad_ops link_validate

[PATCH v5 14/39] add mux and video interface bridge entity functions

From: Philipp Zabel Signed-off-by: Philipp Zabel - renamed MEDIA_ENT_F_MUX to MEDIA_ENT_F_VID_MUX Signed-off-by: Steve Longerbeam --- Documentation/media/uapi/mediactl/media-types.rst | 22 ++

[PATCH v5 14/39] add mux and video interface bridge entity functions

From: Philipp Zabel Signed-off-by: Philipp Zabel - renamed MEDIA_ENT_F_MUX to MEDIA_ENT_F_VID_MUX Signed-off-by: Steve Longerbeam --- Documentation/media/uapi/mediactl/media-types.rst | 22 ++ include/uapi/linux/media.h| 6 ++ 2 files

[PATCH v5 16/39] [media] v4l2: add a new-frame before end-of-frame event

Add a NEW_FRAME_BEFORE_EOF event to signal that a video capture or output device has signaled a new frame is ready before a previous frame has completed reception or transmission. This usually indicates a DMA read/write channel is having trouble gaining bus access. Signed-off-by: Steve Longerbeam

[PATCH v5 16/39] [media] v4l2: add a new-frame before end-of-frame event

Add a NEW_FRAME_BEFORE_EOF event to signal that a video capture or output device has signaled a new frame is ready before a previous frame has completed reception or transmission. This usually indicates a DMA read/write channel is having trouble gaining bus access. Signed-off-by: Steve Longerbeam

Re: [PATCH v4] soc/imx: Add GPCv2 power gating driver

On Wed, Mar 8, 2017 at 3:39 AM, Shawn Guo wrote: > On Tue, Feb 28, 2017 at 04:09:16PM -0800, Andrey Smirnov wrote: >> Add code allowing for control of various power domains managed by GPCv2 > > GPCv2, is it the name used in i.MX7 SoC manual? No, the manual refers to it as

Re: [PATCH v4] soc/imx: Add GPCv2 power gating driver

On Wed, Mar 8, 2017 at 3:39 AM, Shawn Guo wrote: > On Tue, Feb 28, 2017 at 04:09:16PM -0800, Andrey Smirnov wrote: >> Add code allowing for control of various power domains managed by GPCv2 > > GPCv2, is it the name used in i.MX7 SoC manual? No, the manual refers to it as GPC. GPCv2 came from

[PATCH v5 13/39] ARM: dts: imx6-sabreauto: add the ADV7180 video decoder

Enables the ADV7180 decoder sensor. The ADV7180 connects to the parallel-bus mux input on ipu1_csi0_mux. The ADV7180 power pin is via max7310_b port expander. Signed-off-by: Steve Longerbeam --- arch/arm/boot/dts/imx6qdl-sabreauto.dtsi | 58

[PATCH v5 13/39] ARM: dts: imx6-sabreauto: add the ADV7180 video decoder

Enables the ADV7180 decoder sensor. The ADV7180 connects to the parallel-bus mux input on ipu1_csi0_mux. The ADV7180 power pin is via max7310_b port expander. Signed-off-by: Steve Longerbeam --- arch/arm/boot/dts/imx6qdl-sabreauto.dtsi | 58 1 file changed, 58

[PATCH v5 17/39] [media] v4l2-mc: add a function to inherit controls from a pipeline

v4l2_pipeline_inherit_controls() will add the v4l2 controls from all subdev entities in a pipeline to a given video device. Signed-off-by: Steve Longerbeam --- drivers/media/v4l2-core/v4l2-mc.c | 48 +++ include/media/v4l2-mc.h

[PATCH v5 17/39] [media] v4l2-mc: add a function to inherit controls from a pipeline

v4l2_pipeline_inherit_controls() will add the v4l2 controls from all subdev entities in a pipeline to a given video device. Signed-off-by: Steve Longerbeam --- drivers/media/v4l2-core/v4l2-mc.c | 48 +++ include/media/v4l2-mc.h | 25

[PATCH v5 23/39] media: Add i.MX media core driver

Add the core media driver for i.MX SOC. Signed-off-by: Steve Longerbeam --- Documentation/media/v4l-drivers/imx.rst | 560 drivers/staging/media/Kconfig | 2 + drivers/staging/media/Makefile| 1 +

[PATCH v5 23/39] media: Add i.MX media core driver

Add the core media driver for i.MX SOC. Signed-off-by: Steve Longerbeam --- Documentation/media/v4l-drivers/imx.rst | 560 drivers/staging/media/Kconfig | 2 + drivers/staging/media/Makefile| 1 +

  1   2   3   4   5   6   7   8   9   10   >