Re: BUG?: kernel does not (re)set irq smp_affinity to reboot_cpu

On Mon, Jun 27, 2016 at 12:55:26PM +0200, Hans de Goede wrote: > Hi Russel, > > On 27-06-16 11:45, Russell King - ARM Linux wrote: > >On Mon, Jun 27, 2016 at 10:13:05AM +0100, Marc Zyngier wrote: > >>I'm wondering if that's not an effect of this patch: > >> > >>https://lkml.org/lkml/2015/9/24/138

Re: BUG?: kernel does not (re)set irq smp_affinity to reboot_cpu

On Mon, Jun 27, 2016 at 12:55:26PM +0200, Hans de Goede wrote: > Hi Russel, > > On 27-06-16 11:45, Russell King - ARM Linux wrote: > >On Mon, Jun 27, 2016 at 10:13:05AM +0100, Marc Zyngier wrote: > >>I'm wondering if that's not an effect of this patch: > >> > >>https://lkml.org/lkml/2015/9/24/138

Re: [GIT PULL] drm/mediatek: MT8173 gamma & dither support

On Mon, 2016-06-27 at 12:20 +0200, Matthias Brugger wrote: > > On 06/24/2016 09:27 AM, Bibby Hsieh wrote: > > Hi Dave, > > > > Please consider merging this tag, which contains the v2 MT8173 gamma & > > dither function patches I sent on 2016-06-17, rebased onto v4.7-rc1. There > > have been no

Re: [GIT PULL] drm/mediatek: MT8173 gamma & dither support

On Mon, 2016-06-27 at 12:20 +0200, Matthias Brugger wrote: > > On 06/24/2016 09:27 AM, Bibby Hsieh wrote: > > Hi Dave, > > > > Please consider merging this tag, which contains the v2 MT8173 gamma & > > dither function patches I sent on 2016-06-17, rebased onto v4.7-rc1. There > > have been no

[RFC PATCH 4/4] irqchip/gic: remove big.LITTLE switcher support

Remove no longer needed big.LITTLE switcher support. Cc: Jason Cooper Cc: Marc Zyngier Signed-off-by: Bartlomiej Zolnierkiewicz --- drivers/irqchip/irq-gic.c | 137 -- 1 file

[RFC PATCH 2/4] cpufreq: arm_big_little: remove big.LITTLE switcher support

Remove no longer needed big.LITTLE switcher support from arm_big_little CPUfreq driver. The arm_big_little CPUfreq driver itself may also be removed at later time (after converting platforms using it to use cpufreq-dt CPUfreq driver instead). Cc: Sudeep Holla Cc: Sudeep

[RFC PATCH 4/4] irqchip/gic: remove big.LITTLE switcher support

Remove no longer needed big.LITTLE switcher support. Cc: Jason Cooper Cc: Marc Zyngier Signed-off-by: Bartlomiej Zolnierkiewicz --- drivers/irqchip/irq-gic.c | 137 -- 1 file changed, 137 deletions(-) diff --git a/drivers/irqchip/irq-gic.c

[RFC PATCH 2/4] cpufreq: arm_big_little: remove big.LITTLE switcher support

Remove no longer needed big.LITTLE switcher support from arm_big_little CPUfreq driver. The arm_big_little CPUfreq driver itself may also be removed at later time (after converting platforms using it to use cpufreq-dt CPUfreq driver instead). Cc: Sudeep Holla Cc: Sudeep KarkadaNagesha

[RFC PATCH 1/4] ARM: remove big.LITTLE switcher support

It seems that in mainline kernel big.LITTLE switcher support may be usable only on ARM Versatile Express TC2 platform (but even this platform doesn't enable it in its defconfig). Remove big.LITTLE switcher support in favor of using HMP. Cc: Nicolas Pitre Cc: Lorenzo Pieralisi

[RFC PATCH 0/4] ARM: remove big.LITTLE switcher support

Hi, It seems that in mainline kernel big.LITTLE switcher support may be usable only on ARM Versatile Express TC2 platform (but even this platform doesn't enable it in its defconfig). The following patchset removes big.LITTLE switcher support (from both ARM core and arm_big_little CPUfreq driver)

[RFC PATCH 1/4] ARM: remove big.LITTLE switcher support

It seems that in mainline kernel big.LITTLE switcher support may be usable only on ARM Versatile Express TC2 platform (but even this platform doesn't enable it in its defconfig). Remove big.LITTLE switcher support in favor of using HMP. Cc: Nicolas Pitre Cc: Lorenzo Pieralisi Cc: Dave Martin

[RFC PATCH 0/4] ARM: remove big.LITTLE switcher support

Hi, It seems that in mainline kernel big.LITTLE switcher support may be usable only on ARM Versatile Express TC2 platform (but even this platform doesn't enable it in its defconfig). The following patchset removes big.LITTLE switcher support (from both ARM core and arm_big_little CPUfreq driver)

[RFC PATCH 3/4] cpufreq: exynos: remove big.LITTLE switcher dependency

Remove no longeer needed workaround for big.LITTLE switcher support. Signed-off-by: Bartlomiej Zolnierkiewicz --- drivers/cpufreq/cpufreq-dt-platdev.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/drivers/cpufreq/cpufreq-dt-platdev.c

Re: [PATCH 1/1] iommu/amd: initialize devid variable before using it

On Sun, Jun 26, 2016 at 10:33:29AM +0200, Nicolas Iooss wrote: > Commit 2a0cb4e2d423 ("iommu/amd: Add new map for storing IVHD dev entry > type HID") added a call to DUMP_printk in init_iommu_from_acpi() which > used the value of devid before this variable was initialized. > > Signed-off-by:

[RFC PATCH 3/4] cpufreq: exynos: remove big.LITTLE switcher dependency

Remove no longeer needed workaround for big.LITTLE switcher support. Signed-off-by: Bartlomiej Zolnierkiewicz --- drivers/cpufreq/cpufreq-dt-platdev.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/drivers/cpufreq/cpufreq-dt-platdev.c b/drivers/cpufreq/cpufreq-dt-platdev.c index

Re: [PATCH 1/1] iommu/amd: initialize devid variable before using it

On Sun, Jun 26, 2016 at 10:33:29AM +0200, Nicolas Iooss wrote: > Commit 2a0cb4e2d423 ("iommu/amd: Add new map for storing IVHD dev entry > type HID") added a call to DUMP_printk in init_iommu_from_acpi() which > used the value of devid before this variable was initialized. > > Signed-off-by:

Re: [PATCH v5 0/9] Output raw touch data via V4L2

On 06/23/2016 12:08 AM, Nick Dyer wrote: > This is a series of patches to add output of raw touch diagnostic data via > V4L2 > to the Atmel maXTouch and Synaptics RMI4 drivers. > > It's a rewrite of the previous implementation which output via debugfs: it now > uses a V4L2 device in a similar

Re: [PATCH v5 0/9] Output raw touch data via V4L2

On 06/23/2016 12:08 AM, Nick Dyer wrote: > This is a series of patches to add output of raw touch diagnostic data via > V4L2 > to the Atmel maXTouch and Synaptics RMI4 drivers. > > It's a rewrite of the previous implementation which output via debugfs: it now > uses a V4L2 device in a similar

Re: [PATCH v3 0/6] Introduce ZONE_CMA

On 26/05/16 16:22, js1...@gmail.com wrote: > From: Joonsoo Kim > > Hello, > > Changes from v2 > o Rebase on next-20160525 > o No other changes except following description > > There was a discussion with Mel [1] after LSF/MM 2016. I could summarise > it to help merge

Re: [PATCH v3 0/6] Introduce ZONE_CMA

On 26/05/16 16:22, js1...@gmail.com wrote: > From: Joonsoo Kim > > Hello, > > Changes from v2 > o Rebase on next-20160525 > o No other changes except following description > > There was a discussion with Mel [1] after LSF/MM 2016. I could summarise > it to help merge decision but it's better

Re: [PATCH 4/7] efi: Convert efi_call_virt to efi_call_virt_pointer

On Mon, Jun 27, 2016 at 01:00:50PM +0200, Ingo Molnar wrote: > > * Matt Fleming wrote: > > > +#define efi_call_virt_pointer(p, f, args...) > > \ > > +({ \ > > +

Re: [PATCH 4/7] efi: Convert efi_call_virt to efi_call_virt_pointer

On Mon, Jun 27, 2016 at 01:00:50PM +0200, Ingo Molnar wrote: > > * Matt Fleming wrote: > > > +#define efi_call_virt_pointer(p, f, args...) > > \ > > +({ \ > > + efi_status_t __s;

Re: [sched] 56c8928eba: INFO: trying to register non-static key.

On Mon, Jun 27, 2016 at 07:08:43PM +0800, kernel test robot wrote: > [ 36.894449] INFO: trying to register non-static key. > [ 36.894450] the code is fine but needs lockdep annotation. > [ 36.894451] turning off the locking correctness validator. > [ 36.894456] CPU: 0 PID: 817 Comm: mount

Re: [sched] 56c8928eba: INFO: trying to register non-static key.

On Mon, Jun 27, 2016 at 07:08:43PM +0800, kernel test robot wrote: > [ 36.894449] INFO: trying to register non-static key. > [ 36.894450] the code is fine but needs lockdep annotation. > [ 36.894451] turning off the locking correctness validator. > [ 36.894456] CPU: 0 PID: 817 Comm: mount

Re: [PATCH 2/2] drm: Add DT bindings documentation for OpenCores VGA/LCD controller

On Fri, Jun 10, 2016 at 7:36 PM, Rob Herring wrote: > On Thu, Jun 09, 2016 at 03:33:19PM +0200, Andrea Merello wrote: >> Signed-off-by: Andrea Merello >> Cc: Stefan Kristiansson >> Cc: Tomi Valkeinen

Re: [PATCH 2/2] drm: Add DT bindings documentation for OpenCores VGA/LCD controller

On Fri, Jun 10, 2016 at 7:36 PM, Rob Herring wrote: > On Thu, Jun 09, 2016 at 03:33:19PM +0200, Andrea Merello wrote: >> Signed-off-by: Andrea Merello >> Cc: Stefan Kristiansson >> Cc: Tomi Valkeinen >> Cc: Francesco Diotalevi >> Cc: Claudio Lorini >> --- >>

Re: powerpc/fadump: trivial fix of spelling mistake, clean up message

On Mon, 2016-06-27 at 03:51 -0700, Joe Perches wrote: > On Mon, 2016-06-27 at 11:38 +0100, Colin Ian King wrote: > > On 26/06/16 05:19, Michael Ellerman wrote: > > > On Fri, 2016-24-06 at 17:43:00 UTC, Colin King wrote: > > > > trivial fix to spelling mistake "rgistration" and minor clean up > > >

Re: powerpc/fadump: trivial fix of spelling mistake, clean up message

On Mon, 2016-06-27 at 03:51 -0700, Joe Perches wrote: > On Mon, 2016-06-27 at 11:38 +0100, Colin Ian King wrote: > > On 26/06/16 05:19, Michael Ellerman wrote: > > > On Fri, 2016-24-06 at 17:43:00 UTC, Colin King wrote: > > > > trivial fix to spelling mistake "rgistration" and minor clean up > > >

Re: [PATCH v3 1/2] iommu: Disable preemption around use of this_cpu_ptr()

On Sun, Jun 26, 2016 at 12:54:19PM +0200, Thorsten Leemhuis wrote: > Joerg, what's the status here? This made it on my 4.7 regressions > report, as the patches from this thread are supposed to fix a > regression; see > http://thread.gmane.org/gmane.linux.usb.general/143504/focus=153154 > for

Re: [PATCH v5 8/9] Input: synaptics-rmi4 - add support for F54 diagnostics

On 06/23/2016 12:08 AM, Nick Dyer wrote: > Function 54 implements access to various RMI4 diagnostic features. > > This patch adds support for retrieving this data. It registers a V4L2 > device to output the data to user space. > > Signed-off-by: Nick Dyer > --- >

Re: [PATCH v3 1/2] iommu: Disable preemption around use of this_cpu_ptr()

On Sun, Jun 26, 2016 at 12:54:19PM +0200, Thorsten Leemhuis wrote: > Joerg, what's the status here? This made it on my 4.7 regressions > report, as the patches from this thread are supposed to fix a > regression; see > http://thread.gmane.org/gmane.linux.usb.general/143504/focus=153154 > for

Re: [PATCH v5 8/9] Input: synaptics-rmi4 - add support for F54 diagnostics

On 06/23/2016 12:08 AM, Nick Dyer wrote: > Function 54 implements access to various RMI4 diagnostic features. > > This patch adds support for retrieving this data. It registers a V4L2 > device to output the data to user space. > > Signed-off-by: Nick Dyer > --- > drivers/input/rmi4/Kconfig

Re: [PATCH v3 1/2] iommu: Disable preemption around use of this_cpu_ptr()

On Wed, Jun 01, 2016 at 12:10:08PM +0100, Chris Wilson wrote: > drivers/iommu/iova.c | 8 ++-- > 1 file changed, 6 insertions(+), 2 deletions(-) Okay, applied this patch to iommu/fixes and will send it upstream this week.

Re: [PATCH v3 1/2] iommu: Disable preemption around use of this_cpu_ptr()

On Wed, Jun 01, 2016 at 12:10:08PM +0100, Chris Wilson wrote: > drivers/iommu/iova.c | 8 ++-- > 1 file changed, 6 insertions(+), 2 deletions(-) Okay, applied this patch to iommu/fixes and will send it upstream this week.

Re: [PATCH 2/7] efi: Document #define FOO_PROTOCOL_GUID layout

On Mon, 2016-06-27 at 12:49 +0200, Ingo Molnar wrote: > * Matt Fleming wrote: [] > > + * EFI Configuration Table and GUID definitions > > + * > > + * These should be formatted roughly like the ones in the UEFI SPEC has > > + * them.  It makes them easier to grep for, and

Re: [PATCH 2/7] efi: Document #define FOO_PROTOCOL_GUID layout

On Mon, 2016-06-27 at 12:49 +0200, Ingo Molnar wrote: > * Matt Fleming wrote: [] > > + * EFI Configuration Table and GUID definitions > > + * > > + * These should be formatted roughly like the ones in the UEFI SPEC has > > + * them.  It makes them easier to grep for, and they look the same when >

Re: [PATCH v5 7/9] Input: atmel_mxt_ts - add support for reference data

On 06/23/2016 12:08 AM, Nick Dyer wrote: > There are different datatypes available from a maXTouch chip. Add > support to retrieve reference data as well. > > Signed-off-by: Nick Dyer > --- > drivers/input/touchscreen/atmel_mxt_ts.c | 58 >

Re: [PATCH v5 7/9] Input: atmel_mxt_ts - add support for reference data

On 06/23/2016 12:08 AM, Nick Dyer wrote: > There are different datatypes available from a maXTouch chip. Add > support to retrieve reference data as well. > > Signed-off-by: Nick Dyer > --- > drivers/input/touchscreen/atmel_mxt_ts.c | 58 > > 1 file changed, 51

Re: [PATCH v5 3/9] Input: atmel_mxt_ts - output diagnostic debug via v4l2 device

On 06/23/2016 12:08 AM, Nick Dyer wrote: > Register a video device to output T37 diagnostic data. > > Signed-off-by: Nick Dyer > --- > drivers/input/touchscreen/Kconfig| 6 +- > drivers/input/touchscreen/atmel_mxt_ts.c | 244 > +++ >

Re: [PATCH v5 3/9] Input: atmel_mxt_ts - output diagnostic debug via v4l2 device

On 06/23/2016 12:08 AM, Nick Dyer wrote: > Register a video device to output T37 diagnostic data. > > Signed-off-by: Nick Dyer > --- > drivers/input/touchscreen/Kconfig| 6 +- > drivers/input/touchscreen/atmel_mxt_ts.c | 244 > +++ > 2 files changed, 248

[PATCH][V2] powerpc/fadump: trivial fix of spelling mistake, clean up message

From: Colin Ian King Fix trivial spelling mistake "rgistration". Also use pr_err instead of printk and unsplit the string to keep it all on one line. Signed-off-by: Colin Ian King --- arch/powerpc/kernel/fadump.c | 6 +++--- 1 file changed,

BUG: Kernel 3.10.65: Kernel panic while send-receive MMS on same device

Hi, Need a help or some pointer about this issue. Yesterday, received one kernel panic issue on one of our mobile device. Scenario is: Sender is sending an MMS content to its own number. After MMS is received, device vibrates and immediately went into kernel panic. We checked and could not found

[PATCH][V2] powerpc/fadump: trivial fix of spelling mistake, clean up message

From: Colin Ian King Fix trivial spelling mistake "rgistration". Also use pr_err instead of printk and unsplit the string to keep it all on one line. Signed-off-by: Colin Ian King --- arch/powerpc/kernel/fadump.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git

BUG: Kernel 3.10.65: Kernel panic while send-receive MMS on same device

Hi, Need a help or some pointer about this issue. Yesterday, received one kernel panic issue on one of our mobile device. Scenario is: Sender is sending an MMS content to its own number. After MMS is received, device vibrates and immediately went into kernel panic. We checked and could not found

Re: [PATCH v5 9/9] Input: sur40 - use new V4L2 touch input type

On 06/23/2016 12:08 AM, Nick Dyer wrote: > Signed-off-by: Nick Dyer > --- > drivers/input/touchscreen/sur40.c | 12 ++-- > 1 file changed, 6 insertions(+), 6 deletions(-) > > diff --git a/drivers/input/touchscreen/sur40.c > b/drivers/input/touchscreen/sur40.c >

Re: [PATCH v5 9/9] Input: sur40 - use new V4L2 touch input type

On 06/23/2016 12:08 AM, Nick Dyer wrote: > Signed-off-by: Nick Dyer > --- > drivers/input/touchscreen/sur40.c | 12 ++-- > 1 file changed, 6 insertions(+), 6 deletions(-) > > diff --git a/drivers/input/touchscreen/sur40.c > b/drivers/input/touchscreen/sur40.c > index 880c40b..841e045

[PATCH v2 3/8] mfd: tps65218: Use mfd_add_devices instead of of_platform_populate

mfd_add_devices enables parsing device tree nodes without compatibles for child nodes. Replace of_platform_populate with mfd_add_devices. mfd_cell currently is populated with only regulators. Signed-off-by: Keerthy --- Changes in v2: * Updated commit log. As of now only

[PATCH] mm, vmscan: set shrinker to the left page count

In my platform, there can be cache a lot of memory in ion page pool. When shrink memory the nr_to_scan to ion is always to little. to_scan: 395 ion_pool_cached: 27305 Currently, the shrinker nr_deferred is set to total_scan. But it's not the real left of the shrinker. Change it to the freeable -

[PATCH v2 6/8] ARM: dts: AM437X-SK-EVM: Remove redundant regulator compatibles

With the device tree parsing using the regulator framework there is a no longer a need for separate compatibles for individual regulator nodes. Hence removing them all. Signed-off-by: Keerthy --- arch/arm/boot/dts/am437x-sk-evm.dts | 5 - 1 file changed, 5 deletions(-)

[PATCH v2 7/8] ARM: dts: AM437X-CM-T43: Remove redundant regulator compatibles

With the device tree parsing using the regulator framework there is a no longer a need for separate compatibles for individual regulator nodes. Hence removing them all. Signed-off-by: Keerthy --- arch/arm/boot/dts/am437x-cm-t43.dts | 6 -- 1 file changed, 6 deletions(-)

[PATCH v2 3/8] mfd: tps65218: Use mfd_add_devices instead of of_platform_populate

mfd_add_devices enables parsing device tree nodes without compatibles for child nodes. Replace of_platform_populate with mfd_add_devices. mfd_cell currently is populated with only regulators. Signed-off-by: Keerthy --- Changes in v2: * Updated commit log. As of now only regulators driver is

[PATCH] mm, vmscan: set shrinker to the left page count

In my platform, there can be cache a lot of memory in ion page pool. When shrink memory the nr_to_scan to ion is always to little. to_scan: 395 ion_pool_cached: 27305 Currently, the shrinker nr_deferred is set to total_scan. But it's not the real left of the shrinker. Change it to the freeable -

[PATCH v2 6/8] ARM: dts: AM437X-SK-EVM: Remove redundant regulator compatibles

With the device tree parsing using the regulator framework there is a no longer a need for separate compatibles for individual regulator nodes. Hence removing them all. Signed-off-by: Keerthy --- arch/arm/boot/dts/am437x-sk-evm.dts | 5 - 1 file changed, 5 deletions(-) diff --git

[PATCH v2 7/8] ARM: dts: AM437X-CM-T43: Remove redundant regulator compatibles

With the device tree parsing using the regulator framework there is a no longer a need for separate compatibles for individual regulator nodes. Hence removing them all. Signed-off-by: Keerthy --- arch/arm/boot/dts/am437x-cm-t43.dts | 6 -- 1 file changed, 6 deletions(-) diff --git

[PATCH v2 1/8] mfd: tps65218: Remove redundant read wrapper

Currently read directly calls the repmap read function. Hence remove the redundant wrapper and use regmap read wherever needed. Signed-off-by: Keerthy --- drivers/mfd/tps65218.c | 16 +--- drivers/regulator/tps65218-regulator.c | 3 ++-

[PATCH v2 2/8] Documentation: regulator: tps65218: Update examples

This updates the device tree according to the preferred way of parsing the nodes using the regulator framework. Signed-off-by: Keerthy --- .../devicetree/bindings/regulator/tps65218.txt | 87 ++ 1 file changed, 71 insertions(+), 16 deletions(-) diff

[PATCH v2 2/8] Documentation: regulator: tps65218: Update examples

This updates the device tree according to the preferred way of parsing the nodes using the regulator framework. Signed-off-by: Keerthy --- .../devicetree/bindings/regulator/tps65218.txt | 87 ++ 1 file changed, 71 insertions(+), 16 deletions(-) diff --git

[PATCH v2 1/8] mfd: tps65218: Remove redundant read wrapper

Currently read directly calls the repmap read function. Hence remove the redundant wrapper and use regmap read wherever needed. Signed-off-by: Keerthy --- drivers/mfd/tps65218.c | 16 +--- drivers/regulator/tps65218-regulator.c | 3 ++- include/linux/mfd/tps65218.h

[PATCH v2 0/8] mfd/regulator: tps65218: Clean ups

The series cleans up mainly the regulator driver and implements the device tree parsing using the regulator framework. Removes all the redundant compatibles for the individual regulators. One of the patch removes redundant read wrapper and makes use of regmap_read wherever necessary. The series

[PATCH v2 4/8] regulator: tps65218: Remove all the compatibles

Remove all the individual compatibles for all the regulators and introduce id_table and update the driver accordingly to parse device tree nodes using the regulator framework. Acked-by: Mark Brown Signed-off-by: Keerthy --- Changes in v2: * Added Mark's

[PATCH v2 5/8] ARM: dts: AM437X-GP-EVM: Remove redundant regulator compatibles

With the device tree parsing using the regulator framework there is a no longer a need for separate compatibles for individual regulator nodes. Hence removing them all. Signed-off-by: Keerthy --- arch/arm/boot/dts/am437x-gp-evm.dts | 6 -- 1 file changed, 6 deletions(-)

[PATCH v2 8/8] ARM: dts: AM43X-EPOS-EVM: Remove redundant regulator compatibles

With the device tree parsing using the regulator framework there is a no longer a need for separate compatibles for individual regulator nodes. Hence removing them all. Signed-off-by: Keerthy --- arch/arm/boot/dts/am43x-epos-evm.dts | 7 --- 1 file changed, 7 deletions(-)

[PATCH v2 0/8] mfd/regulator: tps65218: Clean ups

The series cleans up mainly the regulator driver and implements the device tree parsing using the regulator framework. Removes all the redundant compatibles for the individual regulators. One of the patch removes redundant read wrapper and makes use of regmap_read wherever necessary. The series

[PATCH v2 4/8] regulator: tps65218: Remove all the compatibles

Remove all the individual compatibles for all the regulators and introduce id_table and update the driver accordingly to parse device tree nodes using the regulator framework. Acked-by: Mark Brown Signed-off-by: Keerthy --- Changes in v2: * Added Mark's Acked-by.

[PATCH v2 5/8] ARM: dts: AM437X-GP-EVM: Remove redundant regulator compatibles

With the device tree parsing using the regulator framework there is a no longer a need for separate compatibles for individual regulator nodes. Hence removing them all. Signed-off-by: Keerthy --- arch/arm/boot/dts/am437x-gp-evm.dts | 6 -- 1 file changed, 6 deletions(-) diff --git

[PATCH v2 8/8] ARM: dts: AM43X-EPOS-EVM: Remove redundant regulator compatibles

With the device tree parsing using the regulator framework there is a no longer a need for separate compatibles for individual regulator nodes. Hence removing them all. Signed-off-by: Keerthy --- arch/arm/boot/dts/am43x-epos-evm.dts | 7 --- 1 file changed, 7 deletions(-) diff --git

Re: [PATCH v5 1/9] [media] v4l2-core: Add support for touch devices

On 06/23/2016 12:08 AM, Nick Dyer wrote: > Some touch controllers send out touch data in a similar way to a > greyscale frame grabber. > > Use a new device prefix v4l-touch for these devices, to stop generic > capture software from treating them as webcams. > > Add formats: > -

Re: [PATCH v5 1/9] [media] v4l2-core: Add support for touch devices

On 06/23/2016 12:08 AM, Nick Dyer wrote: > Some touch controllers send out touch data in a similar way to a > greyscale frame grabber. > > Use a new device prefix v4l-touch for these devices, to stop generic > capture software from treating them as webcams. > > Add formats: > -

Re: [PATCH 4/7] efi: Convert efi_call_virt to efi_call_virt_pointer

* Matt Fleming wrote: > +#define efi_call_virt_pointer(p, f, args...) \ > +({ \ > + efi_status_t __s; \ > + unsigned long

Re: [PATCH 4/7] efi: Convert efi_call_virt to efi_call_virt_pointer

* Matt Fleming wrote: > +#define efi_call_virt_pointer(p, f, args...) \ > +({ \ > + efi_status_t __s; \ > + unsigned long flags;

[PATCH] ARM: s3c64xx: avoid warning about 'struct device_node'

The change to simplify of_platform_populate() had an unintended side-effect of introducing a build warning on s3c64xx: In file included from arch/arm/mach-s3c64xx/mach-s3c64xx-dt.c:18:0: arch/arm/mach-s3c64xx/common.h:27:30: error: 'struct device_node' declared inside parameter list will not be

[PATCH] ARM: s3c64xx: avoid warning about 'struct device_node'

The change to simplify of_platform_populate() had an unintended side-effect of introducing a build warning on s3c64xx: In file included from arch/arm/mach-s3c64xx/mach-s3c64xx-dt.c:18:0: arch/arm/mach-s3c64xx/common.h:27:30: error: 'struct device_node' declared inside parameter list will not be

Re: [PATCH] mwifiex: Reduce endian conversion for REG Host Commands

Prasun Maiti writes: >> If you send a new version of the patch mark it as [PATCH v2] and always >> include a change log so that people don't need to guess what has >> changed: >> >> http://kernelnewbies.org/FirstKernelPatch#head-5c81b3c517a1d0bbc24f92594cb734e155fcbbcb

Re: [PATCH] mwifiex: Reduce endian conversion for REG Host Commands

Prasun Maiti writes: >> If you send a new version of the patch mark it as [PATCH v2] and always >> include a change log so that people don't need to guess what has >> changed: >> >> http://kernelnewbies.org/FirstKernelPatch#head-5c81b3c517a1d0bbc24f92594cb734e155fcbbcb >> >> So now you should

Re: [PATCH net-next 6/6] r8152: add byte_enable for ocp_read_word function

Hello. On 6/27/2016 8:07 AM, Hayes Wang wrote: Add byte_enable for ocp_read_word() to replace reading 4 bytes data with reading the desired 2 bytes data. This is used to avoid the issue which is described in commit:b4d99def. scripts/checkpatch.pl now enforces certain commit citing style,

Re: [PATCH net-next 6/6] r8152: add byte_enable for ocp_read_word function

Hello. On 6/27/2016 8:07 AM, Hayes Wang wrote: Add byte_enable for ocp_read_word() to replace reading 4 bytes data with reading the desired 2 bytes data. This is used to avoid the issue which is described in commit:b4d99def. scripts/checkpatch.pl now enforces certain commit citing style,

Re: [PATCH 1/5] spi: do not fail if the CS line is not connected

Hi Mark, > > > > This is true, but there are cases where the CS is not connected > > > > and this case needs to be treated separately to allow the device > > > > to work. > > > > In what way? It is just as easy for a device with no physical chip > > > select to have a logical chip select of 0

Re: [PATCH 1/5] spi: do not fail if the CS line is not connected

Hi Mark, > > > > This is true, but there are cases where the CS is not connected > > > > and this case needs to be treated separately to allow the device > > > > to work. > > > > In what way? It is just as easy for a device with no physical chip > > > select to have a logical chip select of 0

[PATCH 1/1] gpio: max77620: get gpio value based on direction

Gpio direction is determined by DIRx bit of GPIO configuration register, return max77620 gpio value based on direction in or out. Signed-off-by: Venkat Reddy Talla --- drivers/gpio/gpio-max77620.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git

[PATCH 1/1] gpio: max77620: get gpio value based on direction

Gpio direction is determined by DIRx bit of GPIO configuration register, return max77620 gpio value based on direction in or out. Signed-off-by: Venkat Reddy Talla --- drivers/gpio/gpio-max77620.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git

Re: BUG?: kernel does not (re)set irq smp_affinity to reboot_cpu

Hi Russel, On 27-06-16 11:45, Russell King - ARM Linux wrote: On Mon, Jun 27, 2016 at 10:13:05AM +0100, Marc Zyngier wrote: I'm wondering if that's not an effect of this patch: https://lkml.org/lkml/2015/9/24/138 missing on the ARM side (the corresponding arm64 patch is 217d453d473c). No,

Re: BUG?: kernel does not (re)set irq smp_affinity to reboot_cpu

Hi Russel, On 27-06-16 11:45, Russell King - ARM Linux wrote: On Mon, Jun 27, 2016 at 10:13:05AM +0100, Marc Zyngier wrote: I'm wondering if that's not an effect of this patch: https://lkml.org/lkml/2015/9/24/138 missing on the ARM side (the corresponding arm64 patch is 217d453d473c). No,

Re: powerpc/fadump: trivial fix of spelling mistake, clean up message

On Mon, 2016-06-27 at 11:38 +0100, Colin Ian King wrote: > On 26/06/16 05:19, Michael Ellerman wrote: > > On Fri, 2016-24-06 at 17:43:00 UTC, Colin King wrote: [] > > > trivial fix to spelling mistake "rgistration" and minor clean up > > > of the printk error message > > Can you also: > >  - use

Re: powerpc/fadump: trivial fix of spelling mistake, clean up message

On Mon, 2016-06-27 at 11:38 +0100, Colin Ian King wrote: > On 26/06/16 05:19, Michael Ellerman wrote: > > On Fri, 2016-24-06 at 17:43:00 UTC, Colin King wrote: [] > > > trivial fix to spelling mistake "rgistration" and minor clean up > > > of the printk error message > > Can you also: > >  - use

Re: [PATCH 2/7] efi: Document #define FOO_PROTOCOL_GUID layout

* Matt Fleming wrote: > From: Peter Jones > > Add a comment documenting why EFI GUIDs are laid out like they are. > Ideally I'd like to change all the ", " to "," too, but right now the > format is such that checkpatch won't complain with new ones,

Re: [PATCH 2/7] efi: Document #define FOO_PROTOCOL_GUID layout

* Matt Fleming wrote: > From: Peter Jones > > Add a comment documenting why EFI GUIDs are laid out like they are. > Ideally I'd like to change all the ", " to "," too, but right now the > format is such that checkpatch won't complain with new ones, and staring > at checkpatch didn't get me

Re: [PATCH] ilp32: fix {GET,SET}SIGMASK request for ptrace

On 2016/6/27 13:39, Yury Norov wrote: Hi Zhou, Thank you for the patch. The idea is ok, but patch format got broken for some reason. Could you re-send it? Yury. Sorry for the broken patch, maybe my mail guest has some problems. So I send the patch as an attachment. Thanks! On Mon, Jun

Re: [PATCH] ilp32: fix {GET,SET}SIGMASK request for ptrace

On 2016/6/27 13:39, Yury Norov wrote: Hi Zhou, Thank you for the patch. The idea is ok, but patch format got broken for some reason. Could you re-send it? Yury. Sorry for the broken patch, maybe my mail guest has some problems. So I send the patch as an attachment. Thanks! On Mon, Jun

Re: powerpc/fadump: trivial fix of spelling mistake, clean up message

On 26/06/16 05:19, Michael Ellerman wrote: > On Fri, 2016-24-06 at 17:43:00 UTC, Colin King wrote: >> From: Colin Ian King >> >> trivial fix to spelling mistake "rgistration" and minor clean up >> of the printk error message > > Can you also: > - use pr_err() > -

Re: powerpc/fadump: trivial fix of spelling mistake, clean up message

On 26/06/16 05:19, Michael Ellerman wrote: > On Fri, 2016-24-06 at 17:43:00 UTC, Colin King wrote: >> From: Colin Ian King >> >> trivial fix to spelling mistake "rgistration" and minor clean up >> of the printk error message > > Can you also: > - use pr_err() > - unsplit the message, ie. keep

Re: [PATCH v3 00/13] Virtually mapped stacks with guard pages (x86, core)

On Fri 24-06-16 22:22:55, Oleg Nesterov wrote: > On 06/24, Michal Hocko wrote: > > > > On Fri 24-06-16 16:05:58, Michal Hocko wrote: > > > On Thu 23-06-16 20:52:21, Oleg Nesterov wrote: > > > > > > > > But I agree, this is fixable (and in fact I still hope TIF_MEMDIE will > > > > die, > > > > at

Re: [PATCH v3 00/13] Virtually mapped stacks with guard pages (x86, core)

On Fri 24-06-16 22:22:55, Oleg Nesterov wrote: > On 06/24, Michal Hocko wrote: > > > > On Fri 24-06-16 16:05:58, Michal Hocko wrote: > > > On Thu 23-06-16 20:52:21, Oleg Nesterov wrote: > > > > > > > > But I agree, this is fixable (and in fact I still hope TIF_MEMDIE will > > > > die, > > > > at

Re: [PATCH v5 0/6] Support calling functions on dedicated physical cpu

On 06/04/16 16:17, Juergen Gross wrote: > Some hardware (e.g. Dell Studio laptops) require special functions to > be called on physical cpu 0 in order to avoid occasional hangs. When > running as dom0 under Xen this could be achieved only via special boot > parameters (vcpu pinning) limiting the

Re: [PATCH v5 0/6] Support calling functions on dedicated physical cpu

On 06/04/16 16:17, Juergen Gross wrote: > Some hardware (e.g. Dell Studio laptops) require special functions to > be called on physical cpu 0 in order to avoid occasional hangs. When > running as dom0 under Xen this could be achieved only via special boot > parameters (vcpu pinning) limiting the

[PATCH V6 1/2] cpufreq: Handle sorted frequency tables more efficiently

cpufreq drivers aren't required to provide a sorted frequency table today, and even the ones which provide a sorted table aren't handled efficiently by cpufreq core. This patch adds infrastructure to verify if the freq-table provided by the drivers is sorted or not, and use efficient helpers if

[PATCH V6 1/2] cpufreq: Handle sorted frequency tables more efficiently

cpufreq drivers aren't required to provide a sorted frequency table today, and even the ones which provide a sorted table aren't handled efficiently by cpufreq core. This patch adds infrastructure to verify if the freq-table provided by the drivers is sorted or not, and use efficient helpers if

[PATCH v11 01/10] perf record: Prepare mmap multiple evlists

Following commits introduce multiple evlists to record. This patch extracts perf_evlist__mmap_ex() processing to a new function, creates record__mmap() and record__mmap_evlist() to wrap perf_evlist__mmap_ex() and its error processing. They will be improvemented to create mmap for all evlists.

[PATCH v11 04/10] perf evlist: Introduce aux evlist

An auxiliary evlist is created by perf_evlist__new_aux() using an existing evlist as its parent. An auxiliary evlist can have its own 'struct perf_mmap', but can't have any other data. User should use its parent instead when accessing other data. Auxiliary evlists are containers of 'struct

[PATCH v11 01/10] perf record: Prepare mmap multiple evlists

Following commits introduce multiple evlists to record. This patch extracts perf_evlist__mmap_ex() processing to a new function, creates record__mmap() and record__mmap_evlist() to wrap perf_evlist__mmap_ex() and its error processing. They will be improvemented to create mmap for all evlists.

[PATCH v11 04/10] perf evlist: Introduce aux evlist

An auxiliary evlist is created by perf_evlist__new_aux() using an existing evlist as its parent. An auxiliary evlist can have its own 'struct perf_mmap', but can't have any other data. User should use its parent instead when accessing other data. Auxiliary evlists are containers of 'struct

<    7   8   9   10   11   12   13   14   15   16   >