[RFC] omap3isp: add support for CSI1 bus

omap3isp: add rest of CSI1 support CSI1 needs one more bit to be set up. Do just that. Signed-off-by: Pavel Machek --- Hmm. Looking at that... num_data_lanes probably should be modified in local variable, not globally like this. Should I do that? Anything else that needs

[RFC] omap3isp: add support for CSI1 bus

omap3isp: add rest of CSI1 support CSI1 needs one more bit to be set up. Do just that. Signed-off-by: Pavel Machek --- Hmm. Looking at that... num_data_lanes probably should be modified in local variable, not globally like this. Should I do that? Anything else that needs fixing? index

Re: [PATCH] ARM: dts: exynos: Add power button for Odroid XU3/4

On Mon, Mar 6, 2017 at 4:52 AM, Brian Kim wrote: > The power button on Odroid XU3/4 is connected with the PWRON pin of > s2mps11 PMIC. The s2mps11 sends low signal to GPIO input in exynos 5422 > via ONOB pin. > > This patch adds devicetree bindings for the power button

Re: [PATCH] ARM: dts: exynos: Add power button for Odroid XU3/4

On Mon, Mar 6, 2017 at 4:52 AM, Brian Kim wrote: > The power button on Odroid XU3/4 is connected with the PWRON pin of > s2mps11 PMIC. The s2mps11 sends low signal to GPIO input in exynos 5422 > via ONOB pin. > > This patch adds devicetree bindings for the power button of Odroid > XU3/4. > >

[PATCH] x86: thinkpad_acpi: Handle return error.

This patch is for handling a return error. Signed-off-by: Arvind Yadav --- drivers/platform/x86/thinkpad_acpi.c | 15 --- 1 file changed, 12 insertions(+), 3 deletions(-) diff --git a/drivers/platform/x86/thinkpad_acpi.c

[PATCH] x86: thinkpad_acpi: Handle return error.

This patch is for handling a return error. Signed-off-by: Arvind Yadav --- drivers/platform/x86/thinkpad_acpi.c | 15 --- 1 file changed, 12 insertions(+), 3 deletions(-) diff --git a/drivers/platform/x86/thinkpad_acpi.c b/drivers/platform/x86/thinkpad_acpi.c index

Re: [PATCH RFC 00/14] Add the BFQ I/O Scheduler to blk-mq

On 2017.03.04 at 17:01 +0100, Paolo Valente wrote: > Hi, > at last, here is my first patch series meant for merging. It adds BFQ > to blk-mq. Don't worry, in this message I won't bore you again with > the wonderful properties of BFQ :) I gave BFQ a quick try. Unfortunately it hangs when I try to

[PATCH] x86: thinkpad_acpi: Handle return error.

This patch is for handling a return error. Signed-off-by: Arvind Yadav --- drivers/platform/x86/thinkpad_acpi.c | 15 --- 1 file changed, 12 insertions(+), 3 deletions(-) diff --git a/drivers/platform/x86/thinkpad_acpi.c

Re: [PATCH RFC 00/14] Add the BFQ I/O Scheduler to blk-mq

On 2017.03.04 at 17:01 +0100, Paolo Valente wrote: > Hi, > at last, here is my first patch series meant for merging. It adds BFQ > to blk-mq. Don't worry, in this message I won't bore you again with > the wonderful properties of BFQ :) I gave BFQ a quick try. Unfortunately it hangs when I try to

[PATCH] x86: thinkpad_acpi: Handle return error.

This patch is for handling a return error. Signed-off-by: Arvind Yadav --- drivers/platform/x86/thinkpad_acpi.c | 15 --- 1 file changed, 12 insertions(+), 3 deletions(-) diff --git a/drivers/platform/x86/thinkpad_acpi.c b/drivers/platform/x86/thinkpad_acpi.c index

Re: [PATCH v2] Input: sparse-keymap - use a managed allocation for keymap copy

On Mon, Mar 6, 2017 at 9:09 AM, Michał Kępień wrote: >> On Thu, Mar 2, 2017 at 2:02 PM, Michał Kępień wrote: >> > + * Since sparse_keymap_setup() now uses a managed allocation for the >> > + * keymap copy, use of this function is deprecated. >> >> So... >>

Re: [PATCH v2] Input: sparse-keymap - use a managed allocation for keymap copy

On Mon, Mar 6, 2017 at 9:09 AM, Michał Kępień wrote: >> On Thu, Mar 2, 2017 at 2:02 PM, Michał Kępień wrote: >> > + * Since sparse_keymap_setup() now uses a managed allocation for the >> > + * keymap copy, use of this function is deprecated. >> >> So... >> >> > */ >> > void

Re: [PATCH] scsi: sr: fix oob access in get_capabilities

Hi all， On 2017/3/3 18:17, Kefeng Wang wrote: > 'n = header_length + block_descriptor_length' could be greater than 512, > and will lead to oob access, so enlarge transfer buffer to fix it. I am not familiar with scsi protocol，so the patch may be wrong. Question, is it reasonable for

Re: [PATCH] scsi: sr: fix oob access in get_capabilities

Hi all， On 2017/3/3 18:17, Kefeng Wang wrote: > 'n = header_length + block_descriptor_length' could be greater than 512, > and will lead to oob access, so enlarge transfer buffer to fix it. I am not familiar with scsi protocol，so the patch may be wrong. Question, is it reasonable for

[PATCH] v4l2-fwnode: Fix clock lane parsing

Fix clock lane parsing in v4l2-fwnode. Signed-off-by: Pavel Machek diff --git a/drivers/media/v4l2-core/v4l2-fwnode.c b/drivers/media/v4l2-core/v4l2-fwnode.c index dd3..44036b8 100644 --- a/drivers/media/v4l2-core/v4l2-fwnode.c +++ b/drivers/media/v4l2-core/v4l2-fwnode.c

[PATCH] v4l2-fwnode: Fix clock lane parsing

Fix clock lane parsing in v4l2-fwnode. Signed-off-by: Pavel Machek diff --git a/drivers/media/v4l2-core/v4l2-fwnode.c b/drivers/media/v4l2-core/v4l2-fwnode.c index dd3..44036b8 100644 --- a/drivers/media/v4l2-core/v4l2-fwnode.c +++ b/drivers/media/v4l2-core/v4l2-fwnode.c @@ -167,7

Re: [PATCH] ARM: dts: exynos: Use thermal fuse value for thermal zone 0 on Exynos5420

Hi Krzysztof, On 4 March 2017 at 13:31, Krzysztof Kozlowski wrote: > On Fri, Mar 03, 2017 at 06:50:06PM -0300, Javier Martinez Canillas wrote: >> Hello Krzysztof, >> >> On 02/11/2017 05:14 PM, Krzysztof Kozlowski wrote: >> > In Odroid XU3 Lite board, the temperature levels

Re: [PATCH] ARM: dts: exynos: Use thermal fuse value for thermal zone 0 on Exynos5420

Hi Krzysztof, On 4 March 2017 at 13:31, Krzysztof Kozlowski wrote: > On Fri, Mar 03, 2017 at 06:50:06PM -0300, Javier Martinez Canillas wrote: >> Hello Krzysztof, >> >> On 02/11/2017 05:14 PM, Krzysztof Kozlowski wrote: >> > In Odroid XU3 Lite board, the temperature levels reported for thermal

Re: Question Regarding ERMS memcpy

On 03/05/17 23:01, Logan Gunthorpe wrote: > > On 05/03/17 12:54 PM, Borislav Petkov wrote: >> Logan, wanna give that a try, see if it takes care of your issue? > > Well honestly my issue was solved by fixing my kernel config. I have no > idea why I had optimize for size in there in the first

Re: Question Regarding ERMS memcpy

On 03/05/17 23:01, Logan Gunthorpe wrote: > > On 05/03/17 12:54 PM, Borislav Petkov wrote: >> Logan, wanna give that a try, see if it takes care of your issue? > > Well honestly my issue was solved by fixing my kernel config. I have no > idea why I had optimize for size in there in the first

[PATCH v9 2/8] devicetree: property-units: Add uWh and uAh units

From: Matt Ranostay Add entries for microwatt-hours and microamp-hours. Cc: Rob Herring Cc: Mark Rutland Cc: devicet...@vger.kernel.org Cc: linux-kernel@vger.kernel.org Signed-off-by: Matt Ranostay

[PATCH v9 2/8] devicetree: property-units: Add uWh and uAh units

From: Matt Ranostay Add entries for microwatt-hours and microamp-hours. Cc: Rob Herring Cc: Mark Rutland Cc: devicet...@vger.kernel.org Cc: linux-kernel@vger.kernel.org Signed-off-by: Matt Ranostay Signed-off-by: Liam Breck Acked-by: Sebastian Reichel Acked-by: Rob Herring ---

[PATCH] Revert "kref: double kref_put() in my_data_handler()"

This reverts commit 8f1ecc9fbc5b223e4f5d5bb8bcd6f5672c4bc4b6. The correction is incorrect, see discussion at http://stackoverflow.com/questions/20093127/why-kref-doc-of-linux-kernel-omits-kref-put-when-kthread-run-fail Reported-by: KrishnamRaju raju Cc: Roel Kluin

[PATCH] Revert "kref: double kref_put() in my_data_handler()"

This reverts commit 8f1ecc9fbc5b223e4f5d5bb8bcd6f5672c4bc4b6. The correction is incorrect, see discussion at http://stackoverflow.com/questions/20093127/why-kref-doc-of-linux-kernel-omits-kref-put-when-kthread-run-fail Reported-by: KrishnamRaju raju Cc: Roel Kluin Cc: Randy Dunlap Cc:

Re: [4.11.0-rc1] kernel warning due to commit 3bb434cd, "vmw_vmci: switch to pci_irq_alloc_vectors"

On Mon, Mar 06, 2017 at 07:02:16AM +, 허종만 wrote: >   > > Hi, > > I'm running kernel 4.11-rc1 on VMWare Workstation 12 Pro (Host : windows 10, > Guest : Fedora 25). > > > I got kernel warning with latest kernel. > > According to git bisect, first bad commit is >

Re: [4.11.0-rc1] kernel warning due to commit 3bb434cd, "vmw_vmci: switch to pci_irq_alloc_vectors"

On Mon, Mar 06, 2017 at 07:02:16AM +, 허종만 wrote: >   > > Hi, > > I'm running kernel 4.11-rc1 on VMWare Workstation 12 Pro (Host : windows 10, > Guest : Fedora 25). > > > I got kernel warning with latest kernel. > > According to git bisect, first bad commit is >

Re: [PATCH v2] Input: sparse-keymap - use a managed allocation for keymap copy

> On Thu, Mar 2, 2017 at 2:02 PM, Michał Kępień wrote: > > Some platform drivers use devm_input_allocate_device() together with > > sparse_keymap_setup() in their .probe callbacks. While using the former > > simplifies error handling, using the latter necessitates calling > >

Re: [PATCH v2] Input: sparse-keymap - use a managed allocation for keymap copy

> On Thu, Mar 2, 2017 at 2:02 PM, Michał Kępień wrote: > > Some platform drivers use devm_input_allocate_device() together with > > sparse_keymap_setup() in their .probe callbacks. While using the former > > simplifies error handling, using the latter necessitates calling > >

Re: [PATCH] mmc: mediatek: Fixed bug where clock frequency could be set wrong

Hi Yong, On Sat, Mar 4, 2017 at 3:10 PM, Yong Mao wrote: > From: yong mao > > This patch can fix two issues: > > Issue 1: > In previous code, div may be overflow when setting clock frequency > as f_min. We can use DIV_ROUND_UP to fix this boundary

Re: Re: [4.11.0-rc1] kernel warning due to commit 3bb434cd, "vmw_vmci: switch to pci_irq_alloc_vectors"

> - Original Message - > Sender : gre...@linuxfoundation.org  > Date : 2017-03-06 16:08 (GMT+9) > Title : Re: [4.11.0-rc1] kernel warning due to commit 3bb434cd, "vmw_vmci: > switch to pci_irq_alloc_vectors" >   > On Mon, Mar 06, 2017 at 07:02:16AM 

Re: [PATCH] mmc: mediatek: Fixed bug where clock frequency could be set wrong

Hi Yong, On Sat, Mar 4, 2017 at 3:10 PM, Yong Mao wrote: > From: yong mao > > This patch can fix two issues: > > Issue 1: > In previous code, div may be overflow when setting clock frequency > as f_min. We can use DIV_ROUND_UP to fix this boundary related > issue. > > Issue 2: > In previous

Re: Re: [4.11.0-rc1] kernel warning due to commit 3bb434cd, "vmw_vmci: switch to pci_irq_alloc_vectors"

> - Original Message - > Sender : gre...@linuxfoundation.org  > Date : 2017-03-06 16:08 (GMT+9) > Title : Re: [4.11.0-rc1] kernel warning due to commit 3bb434cd, "vmw_vmci: > switch to pci_irq_alloc_vectors" >   > On Mon, Mar 06, 2017 at 07:02:16AM +, 허종만 wrote: >   >  > 

[4.11.0-rc1] kernel warning due to commit 3bb434cd, "vmw_vmci: switch to pci_irq_alloc_vectors"

  Hi, I'm running kernel 4.11-rc1 on VMWare Workstation 12 Pro (Host : windows 10, Guest : Fedora 25). I got kernel warning with latest kernel. According to git bisect, first bad commit is [3bb434cdcc6af3d4e70ba041e6f596e465d11e14] vmw_vmci: switch to pci_irq_alloc_vectors. Reverting the

[4.11.0-rc1] kernel warning due to commit 3bb434cd, "vmw_vmci: switch to pci_irq_alloc_vectors"

  Hi, I'm running kernel 4.11-rc1 on VMWare Workstation 12 Pro (Host : windows 10, Guest : Fedora 25). I got kernel warning with latest kernel. According to git bisect, first bad commit is [3bb434cdcc6af3d4e70ba041e6f596e465d11e14] vmw_vmci: switch to pci_irq_alloc_vectors. Reverting the

Re: [PATCH] avr32: Fix build error caused by include file reshuffling

Around Sun 05 Mar 2017 17:05:57 -0800 or thereabout, Guenter Roeck wrote: > Various avr32 builds fail as follows. > > arch/avr32/oprofile/backtrace.c:58: error: > dereferencing pointer to incomplete type > arch/avr32/oprofile/backtrace.c:60: error: > implicit declaration of function

Re: [PATCH] avr32: Fix build error caused by include file reshuffling

Around Sun 05 Mar 2017 17:05:57 -0800 or thereabout, Guenter Roeck wrote: > Various avr32 builds fail as follows. > > arch/avr32/oprofile/backtrace.c:58: error: > dereferencing pointer to incomplete type > arch/avr32/oprofile/backtrace.c:60: error: > implicit declaration of function

Re: [PATCH v2 06/12] dmaengine: sun6i: make gate bit in sun8i's DMA engines a common quirk

On Sun, Mar 5, 2017 at 9:37 PM, Icenowy Zheng wrote: > Originally we enable a special gate bit when the compatible indicates > A23/33. > > But according to BSP sources and user manuals, more SoCs will need this > gate bit. > > So make it a common quirk configured in the config

Re: [PATCH v2 06/12] dmaengine: sun6i: make gate bit in sun8i's DMA engines a common quirk

On Sun, Mar 5, 2017 at 9:37 PM, Icenowy Zheng wrote: > Originally we enable a special gate bit when the compatible indicates > A23/33. > > But according to BSP sources and user manuals, more SoCs will need this > gate bit. > > So make it a common quirk configured in the config struct. > > The BSP

Re: Question Regarding ERMS memcpy

On Sun, Mar 05, 2017 at 11:19:42AM -0800, Linus Torvalds wrote: >> But it is *not* the right thing to use on IO memory, because the CPU >> only does the magic cacheline access optimizations on cacheable >> memory! Yes, and actually this is where I started. I thought my memcpy was using byte

Re: Question Regarding ERMS memcpy

On Sun, Mar 05, 2017 at 11:19:42AM -0800, Linus Torvalds wrote: >> But it is *not* the right thing to use on IO memory, because the CPU >> only does the magic cacheline access optimizations on cacheable >> memory! Yes, and actually this is where I started. I thought my memcpy was using byte

Re: stack frame unwindind KASAN errors

On 27 February 2017 at 23:47, Josh Poimboeuf wrote: > On Mon, Feb 27, 2017 at 12:49:59PM +0800, Daniel J Blueman wrote: >> On 4.9.13 with KASAN enabled [1], we see a number of stack unwinding >> errors reported [2,3]. >> >> This seems to occur at half of boots. >> >> Let me

Re: stack frame unwindind KASAN errors

On 27 February 2017 at 23:47, Josh Poimboeuf wrote: > On Mon, Feb 27, 2017 at 12:49:59PM +0800, Daniel J Blueman wrote: >> On 4.9.13 with KASAN enabled [1], we see a number of stack unwinding >> errors reported [2,3]. >> >> This seems to occur at half of boots. >> >> Let me know for further debug

[PATCH -stable 4.1 4/4] perf/core: Fix the perf_cpu_time_max_percent check

Use "proc_dointvec_minmax" instead of "proc_dointvec" to check the input value from user-space. If not, we can set a big value and some vars will overflow like "sysctl_perf_event_sample_rate" which will cause a lot of unexpected problems. Signed-off-by: Tan Xiaojun

[PATCH -stable 4.1 4/4] perf/core: Fix the perf_cpu_time_max_percent check

Use "proc_dointvec_minmax" instead of "proc_dointvec" to check the input value from user-space. If not, we can set a big value and some vars will overflow like "sysctl_perf_event_sample_rate" which will cause a lot of unexpected problems. Signed-off-by: Tan Xiaojun Signed-off-by: Peter Zijlstra

Re: [v10, 2/2] Documentation/ABI: Add ABI information for QCOM socinfo driver

On 2/22/2017 7:34 PM, Rob Herring wrote: > On Mon, Feb 20, 2017 at 10:17:15PM +0530, Khan, Imran wrote: >> The socinfo ABI document describes the information provided >> by socinfo driver and the corresponding attributes to access >> that information. >> >> Signed-off-by: Imran Khan

Re: [PATCH] extcon: int3496: add dependency on X86 as it's Intel specific

On 2017년 03월 03일 03:10, Peter Robinson wrote: > Add dependency on X86 so it doesn't show up on other arches and > add a option for compile test so it still gets build coverage. > > Signed-off-by: Peter Robinson > --- > drivers/extcon/Kconfig | 2 +- > 1 file changed, 1

Re: [PATCH] extcon: int3496: add dependency on X86 as it's Intel specific

On 2017년 03월 03일 03:10, Peter Robinson wrote: > Add dependency on X86 so it doesn't show up on other arches and > add a option for compile test so it still gets build coverage. > > Signed-off-by: Peter Robinson > --- > drivers/extcon/Kconfig | 2 +- > 1 file changed, 1 insertion(+), 1

Re: [v10, 2/2] Documentation/ABI: Add ABI information for QCOM socinfo driver

On 2/22/2017 7:34 PM, Rob Herring wrote: > On Mon, Feb 20, 2017 at 10:17:15PM +0530, Khan, Imran wrote: >> The socinfo ABI document describes the information provided >> by socinfo driver and the corresponding attributes to access >> that information. >> >> Signed-off-by: Imran Khan >> --- >>

[PATCH -stable 4.1 0/4] perf/core: Fix dynamic interrupt throttle

These four patches are needed for stable 4.1. They fix function of dynamic interrupt throttle. Kan Liang (1): perf/core: Fix implicitly enable dynamic interrupt throttle Peter Zijlstra (2): perf/core: Fix dynamic interrupt throttle perf/core: Make sysctl_perf_cpu_time_max_percent conform

[PATCH -stable 4.1 0/4] perf/core: Fix dynamic interrupt throttle

These four patches are needed for stable 4.1. They fix function of dynamic interrupt throttle. Kan Liang (1): perf/core: Fix implicitly enable dynamic interrupt throttle Peter Zijlstra (2): perf/core: Fix dynamic interrupt throttle perf/core: Make sysctl_perf_cpu_time_max_percent conform

[PATCH -stable 4.1 2/4] perf/core: Fix implicitly enable dynamic interrupt throttle

From: Kan Liang This patch fixes an issue which was introduced by commit: 91a612eea9a3 ("perf/core: Fix dynamic interrupt throttle") ... which commit unconditionally sets the perf_sample_allowed_ns value to !0. But that could trigger a bug in the following corner case:

[PATCH -stable 4.1 2/4] perf/core: Fix implicitly enable dynamic interrupt throttle

From: Kan Liang This patch fixes an issue which was introduced by commit: 91a612eea9a3 ("perf/core: Fix dynamic interrupt throttle") ... which commit unconditionally sets the perf_sample_allowed_ns value to !0. But that could trigger a bug in the following corner case: The user can disable

[PATCH -stable 4.1 3/4] perf/core: Make sysctl_perf_cpu_time_max_percent conform to documentation

From: Peter Zijlstra Markus reported that 0 should also disable the throttling we per Documentation/sysctl/kernel.txt. Reported-by: Markus Trippelsdorf Signed-off-by: Peter Zijlstra (Intel) Cc: Alexander Shishkin

[PATCH -stable 4.1 1/4] perf/core: Fix dynamic interrupt throttle

From: Peter Zijlstra There were two problems with the dynamic interrupt throttle mechanism, both triggered by the same action. When you (or perf_fuzzer) write a huge value into /proc/sys/kernel/perf_event_max_sample_rate the computed perf_sample_allowed_ns becomes 0. This

[PATCH -stable 4.1 3/4] perf/core: Make sysctl_perf_cpu_time_max_percent conform to documentation

From: Peter Zijlstra Markus reported that 0 should also disable the throttling we per Documentation/sysctl/kernel.txt. Reported-by: Markus Trippelsdorf Signed-off-by: Peter Zijlstra (Intel) Cc: Alexander Shishkin Cc: Arnaldo Carvalho de Melo Cc: Jiri Olsa Cc: Linus Torvalds Cc: Peter

[PATCH -stable 4.1 1/4] perf/core: Fix dynamic interrupt throttle

From: Peter Zijlstra There were two problems with the dynamic interrupt throttle mechanism, both triggered by the same action. When you (or perf_fuzzer) write a huge value into /proc/sys/kernel/perf_event_max_sample_rate the computed perf_sample_allowed_ns becomes 0. This effectively disables

Re: [PATCH] Staging: wlan-ng: hfa384x.h: fixed a newline coding style issue

On Sun, Mar 05, 2017 at 09:09:12PM -0500, Mark Stenglein wrote: > Fixed a coding style issue. What issue would that be? > Signed-off-by: Mark Stenglein > --- > drivers/staging/wlan-ng/hfa384x.h | 1 + > 1 file changed, 1 insertion(+) > > diff --git

Re: [PATCH] Staging: wlan-ng: hfa384x.h: fixed a newline coding style issue

On Sun, Mar 05, 2017 at 09:09:12PM -0500, Mark Stenglein wrote: > Fixed a coding style issue. What issue would that be? > Signed-off-by: Mark Stenglein > --- > drivers/staging/wlan-ng/hfa384x.h | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/drivers/staging/wlan-ng/hfa384x.h >

Re: [linux-sunxi] [PATCH v2 02/12] ASoC: sun8i-codec-analog: split out line in

On Sun, Mar 5, 2017 at 9:36 PM, Icenowy Zheng wrote: > Allwinner V3s features an analog codec without LINEIN. > > Split out this part, in order to prepare for the V3s analog codec. > > Signed-off-by: Icenowy Zheng Acked-by: Chen-Yu Tsai

Re: [linux-sunxi] [PATCH v2 02/12] ASoC: sun8i-codec-analog: split out line in

On Sun, Mar 5, 2017 at 9:36 PM, Icenowy Zheng wrote: > Allwinner V3s features an analog codec without LINEIN. > > Split out this part, in order to prepare for the V3s analog codec. > > Signed-off-by: Icenowy Zheng Acked-by: Chen-Yu Tsai

Re: [linux-sunxi] [PATCH v2 01/12] ASoC: sun8i-codec-analog: split out mic2

On Sun, Mar 5, 2017 at 9:36 PM, Icenowy Zheng wrote: > Allwinner V3s features an analog codec without MIC2. > > Split out this part, in order to prepare for the V3s analog codec. > > Signed-off-by: Icenowy Zheng Acked-by: Chen-Yu Tsai

Re: [linux-sunxi] [PATCH v2 01/12] ASoC: sun8i-codec-analog: split out mic2

On Sun, Mar 5, 2017 at 9:36 PM, Icenowy Zheng wrote: > Allwinner V3s features an analog codec without MIC2. > > Split out this part, in order to prepare for the V3s analog codec. > > Signed-off-by: Icenowy Zheng Acked-by: Chen-Yu Tsai

Re: [PATCH v3 1/3] dt-bindings: phy: add assign clock property in usb2-phy node

Hi Daniel, Am Montag, 6. März 2017, 09:29:36 CET schrieb Meng Dongyang: > On some platform such as RK3328, the 480m clock may need to assign > clock parent in dts in stead of clock driver. So this patch add > property of assigned-clocks and assigned-clock-parents to assign > parent for 480m

Re: [PATCH v3 1/3] dt-bindings: phy: add assign clock property in usb2-phy node

Hi Daniel, Am Montag, 6. März 2017, 09:29:36 CET schrieb Meng Dongyang: > On some platform such as RK3328, the 480m clock may need to assign > clock parent in dts in stead of clock driver. So this patch add > property of assigned-clocks and assigned-clock-parents to assign > parent for 480m

Re: nvme, allocation failures, and aborted commands

Tonight I decided to try kernel 4.11-rc1. Still getting page allocation failures and aborted nvme commands once iozone gets to the fwrite/fread testing. The taint seems to be comming from previos warnings from the radeon kernel driver. Its a pretty simple: iozone -a -s 64G run. new log: [

Re: nvme, allocation failures, and aborted commands

Tonight I decided to try kernel 4.11-rc1. Still getting page allocation failures and aborted nvme commands once iozone gets to the fwrite/fread testing. The taint seems to be comming from previos warnings from the radeon kernel driver. Its a pretty simple: iozone -a -s 64G run. new log: [

Re: [PATCH v3 2/3] dt-bindings: phy: add DT bindings for usb2-phy grf

Am Montag, 6. März 2017, 09:29:37 CET schrieb Meng Dongyang: > Adds the device tree bindings description for usb2-phy grf > of RK3328 platform. > > Changes in v2: > - add usb2-phy grf specification > Chagnes in v3: > - remove the example of usb2-phy grf > > Signed-off-by: Meng Dongyang

Re: [PATCH v3 2/3] dt-bindings: phy: add DT bindings for usb2-phy grf

Am Montag, 6. März 2017, 09:29:37 CET schrieb Meng Dongyang: > Adds the device tree bindings description for usb2-phy grf > of RK3328 platform. > > Changes in v2: > - add usb2-phy grf specification > Chagnes in v3: > - remove the example of usb2-phy grf > > Signed-off-by: Meng Dongyang looks

[PATCH] MAINTAINERS: Remove self from Tegra maintainers

I have not been doing any Tegra maintainance work for a while, and this is unlikely to change in the foreseeable future. Better reflect the actual state of things by removing myself from the list. Signed-off-by: Alexandre Courbot --- MAINTAINERS | 1 - 1 file changed, 1

[PATCH] MAINTAINERS: Remove self from Tegra maintainers

I have not been doing any Tegra maintainance work for a while, and this is unlikely to change in the foreseeable future. Better reflect the actual state of things by removing myself from the list. Signed-off-by: Alexandre Courbot --- MAINTAINERS | 1 - 1 file changed, 1 deletion(-) diff --git

Re: [RFC] remove support for AVR32 architecture

On Wed, Mar 1, 2017 at 12:44 PM, Hans-Christian Noren Egtvedt wrote: > I have prepared three patches in my for-linus branch in git tree > https://git.kernel.org/cgit/linux/kernel/git/egtvedt/linux-avr32.git Acked-by: Haavard Skinnemoen Thank you for

Re: [RFC] remove support for AVR32 architecture

On Wed, Mar 1, 2017 at 12:44 PM, Hans-Christian Noren Egtvedt wrote: > I have prepared three patches in my for-linus branch in git tree > https://git.kernel.org/cgit/linux/kernel/git/egtvedt/linux-avr32.git Acked-by: Haavard Skinnemoen Thank you for keeping it alive for so long! I looked

Re: [greybus-dev] [PATCH 2/3] staging: greybus: Replace "is is" with "is"

On 04-03-17, 21:37, simran singhal wrote: > This patch replace "is is " with "is". The replacement couldn't be > automated because sometimes the first "is" was meant to be another > word. > > Signed-off-by: simran singhal > --- > drivers/staging/greybus/uart.c | 2 +- >

Re: [greybus-dev] [PATCH 2/3] staging: greybus: Replace "is is" with "is"

On 04-03-17, 21:37, simran singhal wrote: > This patch replace "is is " with "is". The replacement couldn't be > automated because sometimes the first "is" was meant to be another > word. > > Signed-off-by: simran singhal > --- > drivers/staging/greybus/uart.c | 2 +- > 1 file changed, 1

[RFC] mm, swap: VMA based swap readahead

From: Huang Ying The swap readahead is a important mechanism to reduce the swap in latency. But the original swap readahead algorithm has some issues. a) The original swap readahead algorithm does readahead based on the consecutive blocks in swap device. But the

[RFC] mm, swap: VMA based swap readahead

From: Huang Ying The swap readahead is a important mechanism to reduce the swap in latency. But the original swap readahead algorithm has some issues. a) The original swap readahead algorithm does readahead based on the consecutive blocks in swap device. But the consecutive blocks in

[PATCH v2] MIPS: Fix build breakage caused by header file changes

Since commit f3ac60671954 ("sched/headers: Move task-stack related APIs from to ") and commit f780d89a0e82 ("sched/headers: Remove from "), various mips builds fail as follows. arch/mips/kernel/smp-mt.c: In function ‘vsmp_boot_secondary’: arch/mips/include/asm/processor.h:384:41: error:

[PATCH v2] MIPS: Fix build breakage caused by header file changes

Since commit f3ac60671954 ("sched/headers: Move task-stack related APIs from to ") and commit f780d89a0e82 ("sched/headers: Remove from "), various mips builds fail as follows. arch/mips/kernel/smp-mt.c: In function ‘vsmp_boot_secondary’: arch/mips/include/asm/processor.h:384:41: error:

RE: [PATCH] phy: core: fix the condition to enable pm_runtime in phy_create()

Hi, > From: Yoshihiro Shimoda > Sent: Friday, March 03, 2017 8:33 PM > > This patch fixes an issue that phy_create() never enables the pm_runtime. > And then, we can remove calling the pm_runtime_{en,dis}able from some > phy drivers. > > Fixes: ff764963479a ("drivers: phy: add generic PHY

RE: [PATCH] phy: core: fix the condition to enable pm_runtime in phy_create()

Hi, > From: Yoshihiro Shimoda > Sent: Friday, March 03, 2017 8:33 PM > > This patch fixes an issue that phy_create() never enables the pm_runtime. > And then, we can remove calling the pm_runtime_{en,dis}able from some > phy drivers. > > Fixes: ff764963479a ("drivers: phy: add generic PHY

Re: [PATCH V3 0/4] Define coherent device memory node

On 02/22/2017 10:24 PM, Michal Hocko wrote: > On Wed 22-02-17 09:59:15, Jerome Glisse wrote: >> On Wed, Feb 22, 2017 at 10:29:21AM +0100, Michal Hocko wrote: >>> On Tue 21-02-17 18:39:17, Anshuman Khandual wrote: On 02/17/2017 07:02 PM, Mel Gorman wrote: >> >> [...] >> >>> [...] These

Re: [PATCH V3 0/4] Define coherent device memory node

On 02/22/2017 10:24 PM, Michal Hocko wrote: > On Wed 22-02-17 09:59:15, Jerome Glisse wrote: >> On Wed, Feb 22, 2017 at 10:29:21AM +0100, Michal Hocko wrote: >>> On Tue 21-02-17 18:39:17, Anshuman Khandual wrote: On 02/17/2017 07:02 PM, Mel Gorman wrote: >> >> [...] >> >>> [...] These

Re: [linux-sunxi] [PATCH v2 08/12] ARM: dts: sun8i: restore the inclusion of ccu headers in V3s DTSI

Hi, On Sun, Mar 5, 2017 at 9:37 PM, Icenowy Zheng wrote: > When the V3s support patchset is applied, CCU headers and V3s DTSI went > into different trees, so the CCU inclusion is removed in the DTSI. > > Add back them. > > Signed-off-by: Icenowy Zheng > --- >

Re: [linux-sunxi] [PATCH v2 08/12] ARM: dts: sun8i: restore the inclusion of ccu headers in V3s DTSI

Hi, On Sun, Mar 5, 2017 at 9:37 PM, Icenowy Zheng wrote: > When the V3s support patchset is applied, CCU headers and V3s DTSI went > into different trees, so the CCU inclusion is removed in the DTSI. > > Add back them. > > Signed-off-by: Icenowy Zheng > --- > arch/arm/boot/dts/sun8i-v3s.dtsi |

Re: [PATCH 2/6] cpufreq: schedutil: ignore the sugov kthread for frequencies selections

On 03-03-17, 12:12, Patrick Bellasi wrote: > On 03-Mar 10:49, Viresh Kumar wrote: > > I always wanted to avoid such hacks when I moved to the RT thread :( > > Indeed, it is a bit of an hack... but still it's true that this is a > "special" RT thread which must not bias OPP selection. I agree. We

Re: [PATCH 2/6] cpufreq: schedutil: ignore the sugov kthread for frequencies selections

On 03-03-17, 12:12, Patrick Bellasi wrote: > On 03-Mar 10:49, Viresh Kumar wrote: > > I always wanted to avoid such hacks when I moved to the RT thread :( > > Indeed, it is a bit of an hack... but still it's true that this is a > "special" RT thread which must not bias OPP selection. I agree. We

Re: [PATCH V3 0/4] Define coherent device memory node

On 02/23/2017 09:27 PM, Mel Gorman wrote: > On Tue, Feb 21, 2017 at 06:39:17PM +0530, Anshuman Khandual wrote: > In itself, the series does very little and as Vlastimil already pointed > out, it's not a good idea to try merge piecemeal when people could not > agree on the big picture

Re: [PATCH V3 0/4] Define coherent device memory node

On 02/23/2017 09:27 PM, Mel Gorman wrote: > On Tue, Feb 21, 2017 at 06:39:17PM +0530, Anshuman Khandual wrote: > In itself, the series does very little and as Vlastimil already pointed > out, it's not a good idea to try merge piecemeal when people could not > agree on the big picture

Re: [PATCH v4 1/5] arm64: dts: exynos: Add the burst and esc clock frequency properties to DSI node

On 03/06/2017 01:49 PM, Andi Shyti wrote: Hi Hoegeun, On Mon, Mar 06, 2017 at 01:42:19PM +0900, Hoegeun Kwon wrote: The OF graph is not needed because the panel is a child of dsi. Add the burst and esc clock frequency properties to the parent (DSI node). Signed-off-by: Hoegeun Kwon

Re: [PATCH v4 1/5] arm64: dts: exynos: Add the burst and esc clock frequency properties to DSI node

On 03/06/2017 01:49 PM, Andi Shyti wrote: Hi Hoegeun, On Mon, Mar 06, 2017 at 01:42:19PM +0900, Hoegeun Kwon wrote: The OF graph is not needed because the panel is a child of dsi. Add the burst and esc clock frequency properties to the parent (DSI node). Signed-off-by: Hoegeun Kwon

Re: [PATCH v4 2/5] arm: dts: Add the burst and esc clock frequency properties to DSI node

Hi Hoegeun, On Mon, Mar 06, 2017 at 01:42:20PM +0900, Hoegeun Kwon wrote: > The OF graph is not needed because the panel is a child of dsi. Add > the burst and esc clock frequency properties to the parent (DSI node). > > Signed-off-by: Hoegeun Kwon > Reviewed-by:

Re: [PATCH v4 2/5] arm: dts: Add the burst and esc clock frequency properties to DSI node

Hi Hoegeun, On Mon, Mar 06, 2017 at 01:42:20PM +0900, Hoegeun Kwon wrote: > The OF graph is not needed because the panel is a child of dsi. Add > the burst and esc clock frequency properties to the parent (DSI node). > > Signed-off-by: Hoegeun Kwon > Reviewed-by: Andrzej Hajda Reviewed-by:

Re: [PATCH v2 0/4] fujitsu_init() cleanup

Hi Michael On Mon, Mar 06, 2017 at 05:49:05AM +0100, Micha?? K??pie?? wrote: > > > With regard to patch 2/4 you wrote: > > > > Jonathan, this *really* needs testing on relevant hardware. After > > > > applying this patch, you should be able to turn LCD backlight on and off > > > > using

Re: [PATCH v2 0/4] fujitsu_init() cleanup

Hi Michael On Mon, Mar 06, 2017 at 05:49:05AM +0100, Micha?? K??pie?? wrote: > > > With regard to patch 2/4 you wrote: > > > > Jonathan, this *really* needs testing on relevant hardware. After > > > > applying this patch, you should be able to turn LCD backlight on and off > > > > using

Re: [PATCH v4 4/5] arm64: dts: exynos: Remove the OF graph from DSI node

Hi Hoegeun, On Mon, Mar 06, 2017 at 01:42:22PM +0900, Hoegeun Kwon wrote: > The OF graph is not needed because the panel is a child of dsi. Remove > the ports node in DSI node. > > Signed-off-by: Hoegeun Kwon > Reviewed-by: Andrzej Hajda

Re: [PATCH v4 4/5] arm64: dts: exynos: Remove the OF graph from DSI node

Hi Hoegeun, On Mon, Mar 06, 2017 at 01:42:22PM +0900, Hoegeun Kwon wrote: > The OF graph is not needed because the panel is a child of dsi. Remove > the ports node in DSI node. > > Signed-off-by: Hoegeun Kwon > Reviewed-by: Andrzej Hajda Reviewed-by: Andi Shyti Andi

Re: [PATCH v2 1/3] phy: sun4i-usb: support automatically switch PHY0 route to MUSB/HCI

Hi, On Thu, Mar 2, 2017 at 11:11 PM, Icenowy Zheng wrote: > On newer Allwinner SoCs (H3 and after), the PHY0 node is routed to both > MUSB controller for peripheral and host support (the host support is > slightly broken), and a pair of EHCI/OHCI controllers, which provide a >

Re: [PATCH v2 1/3] phy: sun4i-usb: support automatically switch PHY0 route to MUSB/HCI

Hi, On Thu, Mar 2, 2017 at 11:11 PM, Icenowy Zheng wrote: > On newer Allwinner SoCs (H3 and after), the PHY0 node is routed to both > MUSB controller for peripheral and host support (the host support is > slightly broken), and a pair of EHCI/OHCI controllers, which provide a > better support for

Re: [PATCH 08/12] gpio: davinci: use devm_irq_alloc_descs()

On Saturday 04 March 2017 09:53 PM, Bartosz Golaszewski wrote: This driver never frees the interrupt descriptors it allocates. Fix it by using the resource managed version of irq_alloc_descs(). Acked-by: Keerthy Signed-off-by: Bartosz Golaszewski

Re: [PATCH 08/12] gpio: davinci: use devm_irq_alloc_descs()

On Saturday 04 March 2017 09:53 PM, Bartosz Golaszewski wrote: This driver never frees the interrupt descriptors it allocates. Fix it by using the resource managed version of irq_alloc_descs(). Acked-by: Keerthy Signed-off-by: Bartosz Golaszewski --- drivers/gpio/gpio-davinci.c | 2 +-

  1   2   3   4   5   6   >