Re: [RFC 03/13] mm, page_alloc: don't retry initial attempt in slowpath

On Tue 10-05-16 09:35:53, Vlastimil Babka wrote: > After __alloc_pages_slowpath() sets up new alloc_flags and wakes up kswapd, it > first tries get_page_from_freelist() with the new alloc_flags, as it may > succeed e.g. due to using min watermark instead of low watermark. This attempt > does not

Re: [RFC 03/13] mm, page_alloc: don't retry initial attempt in slowpath

On Tue 10-05-16 09:35:53, Vlastimil Babka wrote: > After __alloc_pages_slowpath() sets up new alloc_flags and wakes up kswapd, it > first tries get_page_from_freelist() with the new alloc_flags, as it may > succeed e.g. due to using min watermark instead of low watermark. This attempt > does not

Re: [PATCH] nand: nandsim: Implement approximation mode

Boris, Am 12.05.2016 um 14:36 schrieb Boris Brezillon: > Hi Richard, > > On Thu, 12 May 2016 13:32:45 +0200 > Richard Weinberger wrote: > >> Sometimes all you need is a NAND with a given page, erase and chip size >> to load and inspect a certain image. >> OOB, ECC sizes and

Re: [tip:perf/core] perf/x86/intel/pt: Generate PMI in the STOP region as well

* Alexander Shishkin wrote: > tip-bot for Alexander Shishkin writes: > > > Commit-ID: 5fbe4788b55540a6c4fe2c47e05482ac356eaf74 > > Gitweb: > > http://git.kernel.org/tip/5fbe4788b55540a6c4fe2c47e05482ac356eaf74 > > Author:

Re: [PATCH] nand: nandsim: Implement approximation mode

Boris, Am 12.05.2016 um 14:36 schrieb Boris Brezillon: > Hi Richard, > > On Thu, 12 May 2016 13:32:45 +0200 > Richard Weinberger wrote: > >> Sometimes all you need is a NAND with a given page, erase and chip size >> to load and inspect a certain image. >> OOB, ECC sizes and other metrics don't

Re: [tip:perf/core] perf/x86/intel/pt: Generate PMI in the STOP region as well

* Alexander Shishkin wrote: > tip-bot for Alexander Shishkin writes: > > > Commit-ID: 5fbe4788b55540a6c4fe2c47e05482ac356eaf74 > > Gitweb: > > http://git.kernel.org/tip/5fbe4788b55540a6c4fe2c47e05482ac356eaf74 > > Author: Alexander Shishkin > > AuthorDate: Tue, 10 May 2016 16:18:32

Re: [PATCH] nbd: Move socket shutdown out of spinlock

Hi, On Thursday 12 May 2016 16:42:31 Pranay Srivastava wrote: > Hi Markus, > > > On Thu, May 12, 2016 at 3:13 PM, Markus Pargmann wrote: > > spinlocked ranges should be small and not contain calls into huge > > subfunctions. Fix my mistake and just get the pointer to the

Re: [PATCH] nbd: Move socket shutdown out of spinlock

Hi, On Thursday 12 May 2016 16:42:31 Pranay Srivastava wrote: > Hi Markus, > > > On Thu, May 12, 2016 at 3:13 PM, Markus Pargmann wrote: > > spinlocked ranges should be small and not contain calls into huge > > subfunctions. Fix my mistake and just get the pointer to the socket > > instead of

Re: [PATCH v8 1/2] Documentation: DT: dma: Add Xilinx zynqmp dma device tree binding documentation

On 05/12/2016 02:29 PM, Kedareswara rao Appana wrote: [...] > +- xlnx,include-sg: Indicates the controller to operate in simple or > + scatter gather dma mode This is also a software runtime configuration parameter.

Re: [PATCH v8 1/2] Documentation: DT: dma: Add Xilinx zynqmp dma device tree binding documentation

On 05/12/2016 02:29 PM, Kedareswara rao Appana wrote: [...] > +- xlnx,include-sg: Indicates the controller to operate in simple or > + scatter gather dma mode This is also a software runtime configuration parameter.

Re: [RFC 02/13] mm, page_alloc: set alloc_flags only once in slowpath

On Tue 10-05-16 14:30:11, Vlastimil Babka wrote: [...] > >From 68f09f1d4381c7451238b4575557580380d8bf30 Mon Sep 17 00:00:00 2001 > From: Vlastimil Babka > Date: Fri, 29 Apr 2016 11:51:17 +0200 > Subject: [RFC 02/13] mm, page_alloc: set alloc_flags only once in slowpath > > In

Re: [RFC 02/13] mm, page_alloc: set alloc_flags only once in slowpath

On Tue 10-05-16 14:30:11, Vlastimil Babka wrote: [...] > >From 68f09f1d4381c7451238b4575557580380d8bf30 Mon Sep 17 00:00:00 2001 > From: Vlastimil Babka > Date: Fri, 29 Apr 2016 11:51:17 +0200 > Subject: [RFC 02/13] mm, page_alloc: set alloc_flags only once in slowpath > > In

Re: [PATCH 4/5] iommu/mediatek: add support for mtk iommu generation one HW

Hi, Robin, Thanks very much for your comment, and sorry for the last reply format. On Tue, 2016-05-10 at 11:28 +0100, Robin Murphy wrote: > On 09/05/16 09:00, honghui.zh...@mediatek.com wrote: > [...] > > +static void *mtk_iommu_alloc_pgt(struct device *dev, size_t size, gfp_t > > gfp) > > +{ >

Re: [PATCH 4/5] iommu/mediatek: add support for mtk iommu generation one HW

Hi, Robin, Thanks very much for your comment, and sorry for the last reply format. On Tue, 2016-05-10 at 11:28 +0100, Robin Murphy wrote: > On 09/05/16 09:00, honghui.zh...@mediatek.com wrote: > [...] > > +static void *mtk_iommu_alloc_pgt(struct device *dev, size_t size, gfp_t > > gfp) > > +{ >

[PATCH 4/4] ARM: bcm2835_defconfig: add bcm2835-sdram controller

From: Martin Sperl Add the bcm2835-sdram controller driver to the default config. (as the driver is enabled by default vi KConfig, we only need to enable CONFIG_MEMORY) Signed-off-by: Martin Sperl --- arch/arm/configs/bcm2835_defconfig | 1 +

[PATCH v2 2/2] powerpc/fadump: add support to parse size based on memory range

Currently, memory for fadump can be specified with fadump_reserve_mem=size, where only a fixed size can be specified. Add the below syntax as well, to support conditional reservation based on system memory size: fadump_reserve_mem=:[,:,...] This syntax helps using the same commandline

[PATCH 4/4] ARM: bcm2835_defconfig: add bcm2835-sdram controller

From: Martin Sperl Add the bcm2835-sdram controller driver to the default config. (as the driver is enabled by default vi KConfig, we only need to enable CONFIG_MEMORY) Signed-off-by: Martin Sperl --- arch/arm/configs/bcm2835_defconfig | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCH v2 2/2] powerpc/fadump: add support to parse size based on memory range

Currently, memory for fadump can be specified with fadump_reserve_mem=size, where only a fixed size can be specified. Add the below syntax as well, to support conditional reservation based on system memory size: fadump_reserve_mem=:[,:,...] This syntax helps using the same commandline

[PATCH 3/4] ARM: dts: bcm2835: add the bcm2835-sdram-controller to the dt

From: Martin Sperl Add the bcm2835 sdram controller to the device tree. Signed-off-by: Martin Sperl --- arch/arm/boot/dts/bcm283x.dtsi | 6 ++ 1 file changed, 6 insertions(+) diff --git a/arch/arm/boot/dts/bcm283x.dtsi

[PATCH 1/4] dt: bindings: add bcm2835-memory-controller documentation

From: Martin Sperl Add memory controller dt-binding documentation for the bcm2835 soc. Signed-off-by: Martin Sperl --- .../bindings/memory-controllers/brcm,bcm2835-sdram.txt | 16 1 file changed, 16 insertions(+) create

[PATCH 3/4] ARM: dts: bcm2835: add the bcm2835-sdram-controller to the dt

From: Martin Sperl Add the bcm2835 sdram controller to the device tree. Signed-off-by: Martin Sperl --- arch/arm/boot/dts/bcm283x.dtsi | 6 ++ 1 file changed, 6 insertions(+) diff --git a/arch/arm/boot/dts/bcm283x.dtsi b/arch/arm/boot/dts/bcm283x.dtsi index 8aaf193..9db9d97 100644 ---

[PATCH 1/4] dt: bindings: add bcm2835-memory-controller documentation

From: Martin Sperl Add memory controller dt-binding documentation for the bcm2835 soc. Signed-off-by: Martin Sperl --- .../bindings/memory-controllers/brcm,bcm2835-sdram.txt | 16 1 file changed, 16 insertions(+) create mode 100644

[PATCH 2/4] memory: bcm2835: add bcm2835-memory controller

From: Martin Sperl Add a memory-controller driver for the bcm2835 SOC. This is mostly needed to claim the SDRAM clock so that this (and the corresponding parent pll) never gets disabled. It also exposes the sdram registers via debugfs. Signed-off-by: Martin Sperl

[PATCH 0/4] add minimal bcm2835-sdram driver

From: Martin Sperl As the sdram clock is a critical clock to the system the minimal bcm2835-sdram driver claims (and enables) this clock and also exposes the corresponding sdram registers via debugfs. Martin Sperl (4): dt: bindings: add bcm2835-memory-controller

[PATCH 2/4] memory: bcm2835: add bcm2835-memory controller

From: Martin Sperl Add a memory-controller driver for the bcm2835 SOC. This is mostly needed to claim the SDRAM clock so that this (and the corresponding parent pll) never gets disabled. It also exposes the sdram registers via debugfs. Signed-off-by: Martin Sperl --- drivers/memory/Kconfig

[PATCH 0/4] add minimal bcm2835-sdram driver

From: Martin Sperl As the sdram clock is a critical clock to the system the minimal bcm2835-sdram driver claims (and enables) this clock and also exposes the corresponding sdram registers via debugfs. Martin Sperl (4): dt: bindings: add bcm2835-memory-controller documentation memory:

[PATCH 1/2] Refactor code parsing size based on memory range

Currently, crashkernel parameter supports the below syntax to parse size based on memory range: crashkernel=:[,:,...] While such parsing is implemented for crashkernel parameter, it applies to other parameters with similar syntax. So, move this code to a more generic place for code

[PATCH 1/2] Refactor code parsing size based on memory range

Currently, crashkernel parameter supports the below syntax to parse size based on memory range: crashkernel=:[,:,...] While such parsing is implemented for crashkernel parameter, it applies to other parameters with similar syntax. So, move this code to a more generic place for code

Re: [PATCH] nand: nandsim: Implement approximation mode

Hi Richard, On Thu, 12 May 2016 13:32:45 +0200 Richard Weinberger wrote: > Sometimes all you need is a NAND with a given page, erase and chip size > to load and inspect a certain image. > OOB, ECC sizes and other metrics don't matter much then. > In such a situation I find

Re: [PATCH] nand: nandsim: Implement approximation mode

Hi Richard, On Thu, 12 May 2016 13:32:45 +0200 Richard Weinberger wrote: > Sometimes all you need is a NAND with a given page, erase and chip size > to load and inspect a certain image. > OOB, ECC sizes and other metrics don't matter much then. > In such a situation I find myself often fiddling

[PATCH V5 3/3] soc/tegra: pmc: Add support for IO pads power state and voltage

The IO pins of Tegra SoCs are grouped for common control of IO interface like setting voltage signal levels and power state of the interface. The group is generally referred as IO pads. The power state and voltage control of IO pins can be done at IO pads level. Tegra generation SoC supports the

[PATCH V5 3/3] soc/tegra: pmc: Add support for IO pads power state and voltage

The IO pins of Tegra SoCs are grouped for common control of IO interface like setting voltage signal levels and power state of the interface. The group is generally referred as IO pads. The power state and voltage control of IO pins can be done at IO pads level. Tegra generation SoC supports the

[tip:x86/urgent] x86: Use compat version for preadv2 and pwritev2

Commit-ID: 9a7a076e8e4ffcfec05e3cafe4c4e31d41ddbaa0 Gitweb: http://git.kernel.org/tip/9a7a076e8e4ffcfec05e3cafe4c4e31d41ddbaa0 Author: Dmitry V. Levin AuthorDate: Wed, 11 May 2016 11:48:17 +0300 Committer: Thomas Gleixner CommitDate: Thu, 12 May

[tip:x86/urgent] x86/tsc: Add missing Cherrytrail frequency to the table

Commit-ID: e2724e9d969294879936daf7833d4adda26c8efc Gitweb: http://git.kernel.org/tip/e2724e9d969294879936daf7833d4adda26c8efc Author: Jeremy Compostella AuthorDate: Wed, 11 May 2016 17:23:34 +0200 Committer: Thomas Gleixner CommitDate:

[tip:x86/urgent] x86: Use compat version for preadv2 and pwritev2

Commit-ID: 9a7a076e8e4ffcfec05e3cafe4c4e31d41ddbaa0 Gitweb: http://git.kernel.org/tip/9a7a076e8e4ffcfec05e3cafe4c4e31d41ddbaa0 Author: Dmitry V. Levin AuthorDate: Wed, 11 May 2016 11:48:17 +0300 Committer: Thomas Gleixner CommitDate: Thu, 12 May 2016 14:27:13 +0200 x86: Use compat

[tip:x86/urgent] x86/tsc: Add missing Cherrytrail frequency to the table

Commit-ID: e2724e9d969294879936daf7833d4adda26c8efc Gitweb: http://git.kernel.org/tip/e2724e9d969294879936daf7833d4adda26c8efc Author: Jeremy Compostella AuthorDate: Wed, 11 May 2016 17:23:34 +0200 Committer: Thomas Gleixner CommitDate: Thu, 12 May 2016 14:27:14 +0200 x86/tsc: Add

[PATCH V5 2/3] soc/tegra: pmc: Correct type of variable for tegra_pmc_readl()

The function tegra_pmc_readl() returns the u32 type data and hence change the data type of variable where this data is stored to u32 type. Signed-off-by: Laxman Dewangan Reviewed-by: Jon Hunter --- Changes from V1: -This is new in series as per

[PATCH V5 2/3] soc/tegra: pmc: Correct type of variable for tegra_pmc_readl()

The function tegra_pmc_readl() returns the u32 type data and hence change the data type of variable where this data is stored to u32 type. Signed-off-by: Laxman Dewangan Reviewed-by: Jon Hunter --- Changes from V1: -This is new in series as per discussion on V1 series to use u32 for

[PATCH V5 0/3] soc/tegra: Add support for IO pads power and voltage control

The IO pins of Tegra SoCs are grouped for common control of IO interface like setting voltage signal levels and power state of the interface. The group is generally referred as IO pads. The power state and voltage control of IO pins can be done at IO pads level. Tegra124 onwards IO pads support

[PATCH V5 0/3] soc/tegra: Add support for IO pads power and voltage control

The IO pins of Tegra SoCs are grouped for common control of IO interface like setting voltage signal levels and power state of the interface. The group is generally referred as IO pads. The power state and voltage control of IO pins can be done at IO pads level. Tegra124 onwards IO pads support

[PATCH V5 1/3] soc/tegra: pmc: Use BIT macro for register field definition

Use BIT macro for register field definition and make constant as U when using in shift operator like (3 << 30) to (3U << 30) Signed-off-by: Laxman Dewangan Acked-by: Jon Hunter --- Changes from V1: - Remove the indenting of line which is not for BIT

[PATCH V5 1/3] soc/tegra: pmc: Use BIT macro for register field definition

Use BIT macro for register field definition and make constant as U when using in shift operator like (3 << 30) to (3U << 30) Signed-off-by: Laxman Dewangan Acked-by: Jon Hunter --- Changes from V1: - Remove the indenting of line which is not for BIT macro usage. Changes from V2: - None

[PATCH v8 2/2] dmaengine: Add Xilinx zynqmp dma engine driver support

Added the driver for zynqmp dma engine used in Zynq UltraScale+ MPSoC. This dma controller supports memory to memory and memory to I/O buffer transfers. Signed-off-by: Punnaiah Choudary Kalluri Signed-off-by: Kedareswara rao Appana --- Changes for v8: -

[PATCH v8 2/2] dmaengine: Add Xilinx zynqmp dma engine driver support

Added the driver for zynqmp dma engine used in Zynq UltraScale+ MPSoC. This dma controller supports memory to memory and memory to I/O buffer transfers. Signed-off-by: Punnaiah Choudary Kalluri Signed-off-by: Kedareswara rao Appana --- Changes for v8: - Derive the software runtime configuration

[PATCH v8 1/2] Documentation: DT: dma: Add Xilinx zynqmp dma device tree binding documentation

Device-tree binding documentation for Xilinx zynqmp dma engine used in Zynq UltraScale+ MPSoC. Signed-off-by: Punnaiah Choudary Kalluri Signed-off-by: Kedareswara rao Appana --- Changes in v8: - Removed all the software runtime configuration parameters

[PATCH v8 1/2] Documentation: DT: dma: Add Xilinx zynqmp dma device tree binding documentation

Device-tree binding documentation for Xilinx zynqmp dma engine used in Zynq UltraScale+ MPSoC. Signed-off-by: Punnaiah Choudary Kalluri Signed-off-by: Kedareswara rao Appana --- Changes in v8: - Removed all the software runtime configuration parameters from the binding doc as suggested by the

[PATCH] arm: tegra: initial support for apalis tk1

This patch adds the device tree to support Toradex Apalis TK1 a computer on module which can be used on different carrier boards. The module consists of a Tegra TK1 SoC, a PMIC solution, 2 GB of DDR3L RAM, a bunch of level shifters, an eMMC, a TMP451 temperature sensor chip and an I210 gigabit

[PATCH] arm: tegra: initial support for apalis tk1

This patch adds the device tree to support Toradex Apalis TK1 a computer on module which can be used on different carrier boards. The module consists of a Tegra TK1 SoC, a PMIC solution, 2 GB of DDR3L RAM, a bunch of level shifters, an eMMC, a TMP451 temperature sensor chip and an I210 gigabit

Re: [tip:perf/core] perf/x86/intel/pt: Generate PMI in the STOP region as well

tip-bot for Alexander Shishkin writes: > Commit-ID: 5fbe4788b55540a6c4fe2c47e05482ac356eaf74 > Gitweb: http://git.kernel.org/tip/5fbe4788b55540a6c4fe2c47e05482ac356eaf74 > Author: Alexander Shishkin > AuthorDate: Tue, 10 May 2016

Re: [tip:perf/core] perf/x86/intel/pt: Generate PMI in the STOP region as well

tip-bot for Alexander Shishkin writes: > Commit-ID: 5fbe4788b55540a6c4fe2c47e05482ac356eaf74 > Gitweb: http://git.kernel.org/tip/5fbe4788b55540a6c4fe2c47e05482ac356eaf74 > Author: Alexander Shishkin > AuthorDate: Tue, 10 May 2016 16:18:32 +0300 > Committer: Ingo Molnar > CommitDate:

[PATCH v9 1/8] i2c: octeon: Rename driver to prepare for split

This is an intermediate commit in preparation of the driver split. The module rename in this commit will be reverted in the next patch, this is just done to make the series bisectible. Signed-off-by: Jan Glauber --- drivers/i2c/busses/Makefile| 2

[PATCH v9 1/8] i2c: octeon: Rename driver to prepare for split

This is an intermediate commit in preparation of the driver split. The module rename in this commit will be reverted in the next patch, this is just done to make the series bisectible. Signed-off-by: Jan Glauber --- drivers/i2c/busses/Makefile| 2 +-

[PATCH v9 8/8] i2c: octeon: thunderx: Add MAINTAINERS entry

The i2c Octeon and ThunderX drivers are maintained by Cavium. While at it fix the whitespace errors of the next entry. Signed-off-by: Jan Glauber Acked-by: David Daney --- MAINTAINERS | 25 + 1 file changed, 17 insertions(+),

[PATCH v9 8/8] i2c: octeon: thunderx: Add MAINTAINERS entry

The i2c Octeon and ThunderX drivers are maintained by Cavium. While at it fix the whitespace errors of the next entry. Signed-off-by: Jan Glauber Acked-by: David Daney --- MAINTAINERS | 25 + 1 file changed, 17 insertions(+), 8 deletions(-) diff --git a/MAINTAINERS

[PATCH v9 4/8] i2c: thunderx: Add SMBUS alert support

Add SMBUS alert interrupt support. For now only device tree is supported for specifying the alert. In case of ACPI an error is returned. Signed-off-by: Jan Glauber --- drivers/i2c/busses/i2c-cavium.h| 6 drivers/i2c/busses/i2c-thunderx-core.c | 51

[PATCH v9 2/8] i2c: octeon: Split the driver into two parts

Move common functionality into a separate file in preparation of the re-use from the ThunderX i2c driver. Functions are slightly re-ordered but no other changes are included. Signed-off-by: Jan Glauber --- drivers/i2c/busses/Makefile | 3 +-

[PATCH v9 4/8] i2c: thunderx: Add SMBUS alert support

Add SMBUS alert interrupt support. For now only device tree is supported for specifying the alert. In case of ACPI an error is returned. Signed-off-by: Jan Glauber --- drivers/i2c/busses/i2c-cavium.h| 6 drivers/i2c/busses/i2c-thunderx-core.c | 51

[PATCH v9 2/8] i2c: octeon: Split the driver into two parts

Move common functionality into a separate file in preparation of the re-use from the ThunderX i2c driver. Functions are slightly re-ordered but no other changes are included. Signed-off-by: Jan Glauber --- drivers/i2c/busses/Makefile | 3 +- drivers/i2c/busses/i2c-cavium.c |

[PATCH v9 6/8] i2c: octeon: Sort include files alphabetically

Sort include files alphabetically to reduce probability of merge conflicts. Signed-off-by: Jan Glauber --- drivers/i2c/busses/i2c-octeon-core.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/drivers/i2c/busses/i2c-octeon-core.c

[PATCH v9 5/8] i2c: octeon,thunderx: Move register offsets to struct

The register offsets are different between Octeon and ThunderX so move them into the algorithm struct and get rid of the define. Signed-off-by: Jan Glauber --- drivers/i2c/busses/i2c-cavium.c| 28 +-- drivers/i2c/busses/i2c-cavium.h|

[PATCH v9 6/8] i2c: octeon: Sort include files alphabetically

Sort include files alphabetically to reduce probability of merge conflicts. Signed-off-by: Jan Glauber --- drivers/i2c/busses/i2c-octeon-core.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/drivers/i2c/busses/i2c-octeon-core.c

[PATCH v9 5/8] i2c: octeon,thunderx: Move register offsets to struct

The register offsets are different between Octeon and ThunderX so move them into the algorithm struct and get rid of the define. Signed-off-by: Jan Glauber --- drivers/i2c/busses/i2c-cavium.c| 28 +-- drivers/i2c/busses/i2c-cavium.h| 35

[PATCH v9 7/8] i2c: cavium: Use booleon values for booleon variables

Initialize booleon values with true instead of 1. Signed-off-by: Jan Glauber --- drivers/i2c/busses/i2c-cavium.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/i2c/busses/i2c-cavium.c b/drivers/i2c/busses/i2c-cavium.c index e95ee5c..140f0d1

[PATCH v9 7/8] i2c: cavium: Use booleon values for booleon variables

Initialize booleon values with true instead of 1. Signed-off-by: Jan Glauber --- drivers/i2c/busses/i2c-cavium.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/i2c/busses/i2c-cavium.c b/drivers/i2c/busses/i2c-cavium.c index e95ee5c..140f0d1 100644 ---

[PATCH v9 0/8] i2c-octeon and i2c-thunderx driver

Hi Wolfram, this update adds ACPI support for the clock-frequency setting in the thunderx driver. For SMBUS alert support it is currently unclear how it will look like in ACPI so I left that unimplemented. Patch #5 - #7 are (final) cleanup patches. Patches are on-top of next-20160512. Changes

[PATCH v9 3/8] i2c: thunderx: Add i2c driver for ThunderX SOC

The ThunderX SOC uses the same i2c block as the Octeon SOC. The main difference is that on ThunderX the device is a PCI device so device probing is done via PCI, interrupts are MSI-X. The clock rates can be set via device tree or ACPI. Signed-off-by: Jan Glauber ---

[PATCH v9 0/8] i2c-octeon and i2c-thunderx driver

Hi Wolfram, this update adds ACPI support for the clock-frequency setting in the thunderx driver. For SMBUS alert support it is currently unclear how it will look like in ACPI so I left that unimplemented. Patch #5 - #7 are (final) cleanup patches. Patches are on-top of next-20160512. Changes

[PATCH v9 3/8] i2c: thunderx: Add i2c driver for ThunderX SOC

The ThunderX SOC uses the same i2c block as the Octeon SOC. The main difference is that on ThunderX the device is a PCI device so device probing is done via PCI, interrupts are MSI-X. The clock rates can be set via device tree or ACPI. Signed-off-by: Jan Glauber --- drivers/i2c/busses/Kconfig

[PATCH v2] Xen: EFI: Parse DT parameters for Xen specific UEFI

From: Shannon Zhao The EFI DT parameters for bare metal are located under /chosen node, while for Xen Dom0 they are located under /hyperviosr/uefi node. These parameters under /chosen and /hyperviosr/uefi are not expected to appear at the same time. Parse these EFI

[PATCH v2] Xen: EFI: Parse DT parameters for Xen specific UEFI

From: Shannon Zhao The EFI DT parameters for bare metal are located under /chosen node, while for Xen Dom0 they are located under /hyperviosr/uefi node. These parameters under /chosen and /hyperviosr/uefi are not expected to appear at the same time. Parse these EFI parameters and initialize EFI

Re: [PATCH] Input: pwm-beeper - defer pwm config if pwm can sleep

On Mon, Feb 22, 2016 at 11:46:39AM -0800, Dmitry Torokhov wrote: > On Wed, Feb 17, 2016 at 02:19:26PM +0100, Manfred Schlaegl wrote: > > If the pwm can sleep defer actions to it using a worker. > > A similar approach was used in leds-pwm (c971ff185) > > > > Trigger: > > On a Freescale i.MX53

Re: [PATCH 03/11] locking, rwsem: introduce basis for down_write_killable

On Thu 12-05-16 14:12:04, Peter Zijlstra wrote: > On Wed, May 11, 2016 at 08:03:46PM +0200, Michal Hocko wrote: > > I still cannot say I would understand why the pending > > RWSEM_WAITING_BIAS matters but I would probably need to look at the code > > again with a clean head, __rwsem_wake is quite

Re: [PATCH] Input: pwm-beeper - defer pwm config if pwm can sleep

On Mon, Feb 22, 2016 at 11:46:39AM -0800, Dmitry Torokhov wrote: > On Wed, Feb 17, 2016 at 02:19:26PM +0100, Manfred Schlaegl wrote: > > If the pwm can sleep defer actions to it using a worker. > > A similar approach was used in leds-pwm (c971ff185) > > > > Trigger: > > On a Freescale i.MX53

Re: [PATCH 03/11] locking, rwsem: introduce basis for down_write_killable

On Thu 12-05-16 14:12:04, Peter Zijlstra wrote: > On Wed, May 11, 2016 at 08:03:46PM +0200, Michal Hocko wrote: > > I still cannot say I would understand why the pending > > RWSEM_WAITING_BIAS matters but I would probably need to look at the code > > again with a clean head, __rwsem_wake is quite

[tip:locking/rwsem] locking/rwsem: Fix down_write_killable()

Commit-ID: 6d4acadc1ca37a3aca10892d32fb7205bc5b0cfc Gitweb: http://git.kernel.org/tip/6d4acadc1ca37a3aca10892d32fb7205bc5b0cfc Author: Peter Zijlstra AuthorDate: Thu, 12 May 2016 13:57:45 +0200 Committer: Ingo Molnar CommitDate: Thu, 12 May 2016

[tip:locking/rwsem] locking/rwsem: Fix down_write_killable()

Commit-ID: 6d4acadc1ca37a3aca10892d32fb7205bc5b0cfc Gitweb: http://git.kernel.org/tip/6d4acadc1ca37a3aca10892d32fb7205bc5b0cfc Author: Peter Zijlstra AuthorDate: Thu, 12 May 2016 13:57:45 +0200 Committer: Ingo Molnar CommitDate: Thu, 12 May 2016 14:10:39 +0200 locking/rwsem: Fix

[PATCH v2 0/2] videobuf2: Fix kernel memory overwriting

Hi folks, There was a bug in the first version of the set --- the pb argument to __vb2_get_done_vb() is NULL in cases which did not get tested the last time. The second patch in the set was reverted for that reason. This set contains a patch originally from David and again the second reverted

Re: [PATCH -v2] x86/hweight: Get rid of the special calling convention

On Thu, May 12, 2016 at 01:57:38PM +0200, Borislav Petkov wrote: > #ifdef CONFIG_X86_32 > # define PUSH_DX"pushl %%edx\n\t" > # define POP_DX "popl %%edx\n\t" > #else > # define PUSH_DX"pushq %%rdx\n\t" > # define POP_DX "popq %%rdx\n\t" > #endif > > unsigned int

[PATCH v2 1/2] vb2: core: Skip planes array verification if pb is NULL

An earlier patch fixing an input validation issue introduced another issue: vb2_core_dqbuf() is called with pb argument value NULL in some cases, causing a NULL pointer dereference. Fix this by skipping the verification as there's nothing to verify. Signed-off-by: David R

[PATCH v2 2/2] [media] videobuf2-v4l2: Verify planes array in buffer dequeueing

When a buffer is being dequeued using VIDIOC_DQBUF IOCTL, the exact buffer which will be dequeued is not known until the buffer has been removed from the queue. The number of planes is specific to a buffer, not to the queue. This does lead to the situation where multi-plane buffers may be

[PATCH v2 0/2] videobuf2: Fix kernel memory overwriting

Hi folks, There was a bug in the first version of the set --- the pb argument to __vb2_get_done_vb() is NULL in cases which did not get tested the last time. The second patch in the set was reverted for that reason. This set contains a patch originally from David and again the second reverted

Re: [PATCH -v2] x86/hweight: Get rid of the special calling convention

On Thu, May 12, 2016 at 01:57:38PM +0200, Borislav Petkov wrote: > #ifdef CONFIG_X86_32 > # define PUSH_DX"pushl %%edx\n\t" > # define POP_DX "popl %%edx\n\t" > #else > # define PUSH_DX"pushq %%rdx\n\t" > # define POP_DX "popq %%rdx\n\t" > #endif > > unsigned int

[PATCH v2 1/2] vb2: core: Skip planes array verification if pb is NULL

An earlier patch fixing an input validation issue introduced another issue: vb2_core_dqbuf() is called with pb argument value NULL in some cases, causing a NULL pointer dereference. Fix this by skipping the verification as there's nothing to verify. Signed-off-by: David R Use if () instead of ?

[PATCH v2 2/2] [media] videobuf2-v4l2: Verify planes array in buffer dequeueing

When a buffer is being dequeued using VIDIOC_DQBUF IOCTL, the exact buffer which will be dequeued is not known until the buffer has been removed from the queue. The number of planes is specific to a buffer, not to the queue. This does lead to the situation where multi-plane buffers may be

Re: pwm: atmel: PWM may not properly disable

On Thu, May 12, 2016 at 01:49:12PM +0200, Guillermo Rodriguez Garcia wrote: > Hello, > > [...] > >>> One thing that I'd request is that instead of the cpu_relax() you use a > >>> usleep_range() within the loop instead. I assume it can potentially take > >>> a long time for the current period to

Re: [PATCH v7 10/14] usb: otg: add hcd companion support

Hi, On 12/05/16 13:31, Yoshihiro Shimoda wrote: > Hi, > >> From: Roger Quadros >> Sent: Thursday, May 12, 2016 6:32 PM >> >> Hi, >> >> On 12/05/16 11:34, Roger Quadros wrote: >>> On 12/05/16 07:00, Yoshihiro Shimoda wrote: Hi, > From: Alan Stern > Sent: Wednesday, May 11, 2016

Re: pwm: atmel: PWM may not properly disable

On Thu, May 12, 2016 at 01:49:12PM +0200, Guillermo Rodriguez Garcia wrote: > Hello, > > [...] > >>> One thing that I'd request is that instead of the cpu_relax() you use a > >>> usleep_range() within the loop instead. I assume it can potentially take > >>> a long time for the current period to

Re: [PATCH v7 10/14] usb: otg: add hcd companion support

Hi, On 12/05/16 13:31, Yoshihiro Shimoda wrote: > Hi, > >> From: Roger Quadros >> Sent: Thursday, May 12, 2016 6:32 PM >> >> Hi, >> >> On 12/05/16 11:34, Roger Quadros wrote: >>> On 12/05/16 07:00, Yoshihiro Shimoda wrote: Hi, > From: Alan Stern > Sent: Wednesday, May 11, 2016

Re: [PATCH 03/11] locking, rwsem: introduce basis for down_write_killable

On Wed, May 11, 2016 at 08:03:46PM +0200, Michal Hocko wrote: > I still cannot say I would understand why the pending > RWSEM_WAITING_BIAS matters but I would probably need to look at the code > again with a clean head, __rwsem_wake is quite tricky... Ah, you're asking why an unconditional

Re: [PATCH 03/11] locking, rwsem: introduce basis for down_write_killable

On Wed, May 11, 2016 at 08:03:46PM +0200, Michal Hocko wrote: > I still cannot say I would understand why the pending > RWSEM_WAITING_BIAS matters but I would probably need to look at the code > again with a clean head, __rwsem_wake is quite tricky... Ah, you're asking why an unconditional

[PATCH v4 17/18] of: unittest: use of_platform_default_populate() to populate default bus

Use helper of_platform_default_populate() in linux/of_platform when possible, instead of calling of_platform_populate() with the default match table. Cc: Rob Herring Cc: Frank Rowand Cc: Grant Likely Signed-off-by: Kefeng

[PATCH v4 17/18] of: unittest: use of_platform_default_populate() to populate default bus

Use helper of_platform_default_populate() in linux/of_platform when possible, instead of calling of_platform_populate() with the default match table. Cc: Rob Herring Cc: Frank Rowand Cc: Grant Likely Signed-off-by: Kefeng Wang --- drivers/of/unittest.c | 5 ++--- 1 file changed, 2

Re: [PATCH V7 07/11] pci, acpi: Handle ACPI companion assignment.

On Thu, May 12, 2016 at 12:50:07PM +0200, Tomasz Nowicki wrote: > On 12.05.2016 00:43, Bjorn Helgaas wrote: > >@@ -70,9 +71,11 @@ struct pci_config_window *pci_ecam_create(struct device > >*dev, > > cfg->res.flags = IORESOURCE_MEM | IORESOURCE_BUSY; > > cfg->res.name = "PCI ECAM"; > > >

[PATCH v4 18/18] Revert "of/platform: export of_default_bus_match_table"

This reverts commit b80443c2211c7daaabd20fbbe9e7beb3fa3408e0. After covering to use helper of_platform_default_populate() to populate the default bus, no need to export of_default_bus_match_table anymore. Reviewed-by: Masahiro Yamada Cc: Masahiro Yamada

Re: [PATCH V7 07/11] pci, acpi: Handle ACPI companion assignment.

On Thu, May 12, 2016 at 12:50:07PM +0200, Tomasz Nowicki wrote: > On 12.05.2016 00:43, Bjorn Helgaas wrote: > >@@ -70,9 +71,11 @@ struct pci_config_window *pci_ecam_create(struct device > >*dev, > > cfg->res.flags = IORESOURCE_MEM | IORESOURCE_BUSY; > > cfg->res.name = "PCI ECAM"; > > >

[PATCH v4 18/18] Revert "of/platform: export of_default_bus_match_table"

This reverts commit b80443c2211c7daaabd20fbbe9e7beb3fa3408e0. After covering to use helper of_platform_default_populate() to populate the default bus, no need to export of_default_bus_match_table anymore. Reviewed-by: Masahiro Yamada Cc: Masahiro Yamada Cc: Rob Herring Cc: Frank Rowand Cc:

[PATCH v4 14/18] bus: imx-weim: use of_platform_default_populate() to populate default bus

Use helper of_platform_default_populate() in linux/of_platform when possible, instead of calling of_platform_populate() with the default match table. Acked-by: Shawn Guo Cc: Signed-off-by: Huang Shijie Cc: Shawn Guo

[PATCH v4 14/18] bus: imx-weim: use of_platform_default_populate() to populate default bus

Use helper of_platform_default_populate() in linux/of_platform when possible, instead of calling of_platform_populate() with the default match table. Acked-by: Shawn Guo Cc: Signed-off-by: Huang Shijie Cc: Shawn Guo Signed-off-by: Kefeng Wang --- drivers/bus/imx-weim.c | 5 ++--- 1 file

Re: [PATCH v9 1/2] gpio: mmio: add DT support for memory-mapped GPIOs

On Thursday, May 12, 2016 07:26:32 PM Alexandre Courbot wrote: > On Wednesday, May 11, 2016 6:34:34 PM JST, Christian Lamparter wrote: > > From: Álvaro Fernández Rojas > > > > This patch adds support for defining memory-mapped GPIOs which > > are compatible with the existing

Re: [PATCH v9 1/2] gpio: mmio: add DT support for memory-mapped GPIOs

On Thursday, May 12, 2016 07:26:32 PM Alexandre Courbot wrote: > On Wednesday, May 11, 2016 6:34:34 PM JST, Christian Lamparter wrote: > > From: Álvaro Fernández Rojas > > > > This patch adds support for defining memory-mapped GPIOs which > > are compatible with the existing gpio-mmio interface.

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