[PATCH 1/3] DT/bindings: Add bindings for TI ADS7950 A/DC chips

This adds device tree bindings for the TI ADS7950 family of A/DC chips. Signed-off-by: David Lechner --- .../devicetree/bindings/iio/adc/ti-ads7950.txt | 23 ++ 1 file changed, 23 insertions(+) create mode 100644

[PATCH 1/3] DT/bindings: Add bindings for TI ADS7950 A/DC chips

This adds device tree bindings for the TI ADS7950 family of A/DC chips. Signed-off-by: David Lechner --- .../devicetree/bindings/iio/adc/ti-ads7950.txt | 23 ++ 1 file changed, 23 insertions(+) create mode 100644 Documentation/devicetree/bindings/iio/adc/ti-ads7950.txt

Re: [PATCH/RESEND v2 5/5] z3fold: add kref refcounting

On Wed, Jan 11, 2017 at 6:39 PM, Dan Streetman wrote: > On Wed, Jan 11, 2017 at 12:27 PM, Vitaly Wool wrote: >> On Wed, Jan 11, 2017 at 6:08 PM, Dan Streetman wrote: >>> On Wed, Jan 11, 2017 at 10:06 AM, Vitaly Wool

Re: [PATCH/RESEND v2 5/5] z3fold: add kref refcounting

On Wed, Jan 11, 2017 at 6:39 PM, Dan Streetman wrote: > On Wed, Jan 11, 2017 at 12:27 PM, Vitaly Wool wrote: >> On Wed, Jan 11, 2017 at 6:08 PM, Dan Streetman wrote: >>> On Wed, Jan 11, 2017 at 10:06 AM, Vitaly Wool wrote: With both coming and already present locking optimizations,

Re: [PATCH 56/62] watchdog: tangox_wdt: Convert to use device managed functions

On Wed, Jan 11, 2017 at 04:28:12PM +0100, Marc Gonzalez wrote: > On 11/01/2017 15:25, Guenter Roeck wrote: > > On 01/11/2017 04:31 AM, Marc Gonzalez wrote: > >> On 11/01/2017 11:52, Guenter Roeck wrote: > >> > >>> On 01/11/2017 01:07 AM, Marc Gonzalez wrote: > >>> > > @@ -134,12 +134,15 @@

Re: [PATCH 56/62] watchdog: tangox_wdt: Convert to use device managed functions

On Wed, Jan 11, 2017 at 04:28:12PM +0100, Marc Gonzalez wrote: > On 11/01/2017 15:25, Guenter Roeck wrote: > > On 01/11/2017 04:31 AM, Marc Gonzalez wrote: > >> On 11/01/2017 11:52, Guenter Roeck wrote: > >> > >>> On 01/11/2017 01:07 AM, Marc Gonzalez wrote: > >>> > > @@ -134,12 +134,15 @@

[PATCH] iio: magnetometer: ak8974: remove redundant zero timeout check

From: Colin Ian King At the end of the delay loop timeout will always be zero and hence the check for !timeout will always be true. Remove the redundant check and the redundant return 0 at the end of the function. Fixes CoverityScan CID#1357168 ("Logically dead code")

[PATCH] iio: magnetometer: ak8974: remove redundant zero timeout check

From: Colin Ian King At the end of the delay loop timeout will always be zero and hence the check for !timeout will always be true. Remove the redundant check and the redundant return 0 at the end of the function. Fixes CoverityScan CID#1357168 ("Logically dead code") Signed-off-by: Colin Ian

Re: [PATCH 0/2] Style fixes: open code obfuscating macros

On 10/01/17 11:50 PM, Greg Kroah-Hartman wrote: > You should be printing against the ntb struct device, as that's the > "correct" structure here, and not the PCI device at all, as that's too > far up the device chain from what the driver is supposed to be doing. Yup, agreed and thanks. My v2

Re: [PATCH 0/2] Style fixes: open code obfuscating macros

On 10/01/17 11:50 PM, Greg Kroah-Hartman wrote: > You should be printing against the ntb struct device, as that's the > "correct" structure here, and not the PCI device at all, as that's too > far up the device chain from what the driver is supposed to be doing. Yup, agreed and thanks. My v2

Re: [PATCH] Input: synaptics-rmi4 - make F03 a tristate symbol

On Jan 11 2017 or thereabouts, Arnd Bergmann wrote: > On Wednesday, January 11, 2017 5:28:28 PM CET Benjamin Tissoires wrote: > > Yep, it was initially written that way, and IIRC there was some issues > > depending on how the drivers were compiled. For example, if rmi4_core is > > Y and some

Re: [PATCH] Input: synaptics-rmi4 - make F03 a tristate symbol

On Jan 11 2017 or thereabouts, Arnd Bergmann wrote: > On Wednesday, January 11, 2017 5:28:28 PM CET Benjamin Tissoires wrote: > > Yep, it was initially written that way, and IIRC there was some issues > > depending on how the drivers were compiled. For example, if rmi4_core is > > Y and some

[PATCH V3] regulator: core: Don't use regulators as supplies until the parent is bound

When regulators are successfully registered, we check to see if the regulator is a supply for any other registered regulator and if so add the new regulator as the supply for the existing regulator(s). Some devices, such as Power Management ICs, may register a series of regulators when probed and

[PATCH V3] regulator: core: Don't use regulators as supplies until the parent is bound

When regulators are successfully registered, we check to see if the regulator is a supply for any other registered regulator and if so add the new regulator as the supply for the existing regulator(s). Some devices, such as Power Management ICs, may register a series of regulators when probed and

Re: [PATCH/RESEND v2 5/5] z3fold: add kref refcounting

On Wed, Jan 11, 2017 at 12:27 PM, Vitaly Wool wrote: > On Wed, Jan 11, 2017 at 6:08 PM, Dan Streetman wrote: >> On Wed, Jan 11, 2017 at 10:06 AM, Vitaly Wool wrote: >>> With both coming and already present locking optimizations, >>>

Re: [PATCH/RESEND v2 5/5] z3fold: add kref refcounting

On Wed, Jan 11, 2017 at 12:27 PM, Vitaly Wool wrote: > On Wed, Jan 11, 2017 at 6:08 PM, Dan Streetman wrote: >> On Wed, Jan 11, 2017 at 10:06 AM, Vitaly Wool wrote: >>> With both coming and already present locking optimizations, >>> introducing kref to reference-count z3fold objects is the

Re: [PATCH v2 1/1] platform/x86: Remove PMIC GPIO block support

On Wed, 2017-01-11 at 19:24 +0200, Andy Shevchenko wrote: > The Moorestown support was removed by commit 1a8359e411eb ("x86/mid: > Remove > Intel Moorestown"). > > Remove this leftover. > +Cc: Ingo Ingo, this is the driver we would like to remove as well. All users of it has been removed by

Re: [PATCH v2 1/1] platform/x86: Remove PMIC GPIO block support

On Wed, 2017-01-11 at 19:24 +0200, Andy Shevchenko wrote: > The Moorestown support was removed by commit 1a8359e411eb ("x86/mid: > Remove > Intel Moorestown"). > > Remove this leftover. > +Cc: Ingo Ingo, this is the driver we would like to remove as well. All users of it has been removed by

Re: [PATCH 1/3] gpio: davinci: Remove unwanted blank line

On 01/10/2017 11:00 PM, Keerthy wrote: Remove redundant blank line. i think it's better to drop this patch ;) Signed-off-by: Keerthy --- include/linux/platform_data/gpio-davinci.h | 1 - 1 file changed, 1 deletion(-) diff --git

Re: [PATCH 1/3] gpio: davinci: Remove unwanted blank line

On 01/10/2017 11:00 PM, Keerthy wrote: Remove redundant blank line. i think it's better to drop this patch ;) Signed-off-by: Keerthy --- include/linux/platform_data/gpio-davinci.h | 1 - 1 file changed, 1 deletion(-) diff --git a/include/linux/platform_data/gpio-davinci.h

[PATCH v2 1/4] platform/chrome: cros_ec_lightbar - Add lightbar program feature to sysfs

From: Eric Caruso Add a program feature so we can upload and run programs for lightbar sequences. We should be able to use this to shift sequences out of the EC and save space there. $ cat > /sys/devices/.../cros_ec/program $ echo program >

[PATCH v2 1/4] platform/chrome: cros_ec_lightbar - Add lightbar program feature to sysfs

From: Eric Caruso Add a program feature so we can upload and run programs for lightbar sequences. We should be able to use this to shift sequences out of the EC and save space there. $ cat > /sys/devices/.../cros_ec/program $ echo program > /sys/devices/.../cros_ec/sequence Signed-off-by:

[PATCH v2 2/4] platform/chrome: cros_ec_lightbar - Control of suspend/resume lightbar sequence

From: Eric Caruso Don't let EC control suspend/resume sequence. If the EC controls the lightbar and sets the sequence when it notices the chipset transitioning between states, we can't make exceptions for cases where we don't want to activate the lightbar. Instead, let's

[PATCH v2 3/4] platform/chrome: cros_ec_lightbar - Add userspace lightbar control bit to EC

From: Eric Caruso Some devices might want to turn off the lightbar if e.g. the system turns the screen off due to idleness. This prevents the kernel from going through its normal suspend/resume pathways. Signed-off-by: Eric Caruso Signed-off-by:

[PATCH v2 4/4] platform/chrome: cros_ec_lightbar - Avoid I2C xfer to EC during suspend

From: Jeffery Yu A Mutex lock in cros_ec_cmd_xfer which may be held by frozen Userspace thread during system suspending. So should not call this routine in suspend thread. Signed-off-by: Jeffery Yu Signed-off-by: Guenter Roeck

[PATCH v2 2/4] platform/chrome: cros_ec_lightbar - Control of suspend/resume lightbar sequence

From: Eric Caruso Don't let EC control suspend/resume sequence. If the EC controls the lightbar and sets the sequence when it notices the chipset transitioning between states, we can't make exceptions for cases where we don't want to activate the lightbar. Instead, let's move the suspend/resume

[PATCH v2 3/4] platform/chrome: cros_ec_lightbar - Add userspace lightbar control bit to EC

From: Eric Caruso Some devices might want to turn off the lightbar if e.g. the system turns the screen off due to idleness. This prevents the kernel from going through its normal suspend/resume pathways. Signed-off-by: Eric Caruso Signed-off-by: Guenter Roeck Signed-off-by: Enric Balletbo i

[PATCH v2 4/4] platform/chrome: cros_ec_lightbar - Avoid I2C xfer to EC during suspend

From: Jeffery Yu A Mutex lock in cros_ec_cmd_xfer which may be held by frozen Userspace thread during system suspending. So should not call this routine in suspend thread. Signed-off-by: Jeffery Yu Signed-off-by: Guenter Roeck Signed-off-by: Enric Balletbo i Serra ---

[PATCH v2 0/4] platform/chrome: cros_ec_lightbar - Add new features

Dear all, The following patches taken from the ChromeOS 4.4 tree adds more features to the cros_ec_lightbar driver. The patches were forward ported to current mainline and were tested on a Chromebook Pixel 2015. Best regards, Enric Changes since v1: - Rebase on top of mainline. - Added Lee

[PATCH v2 0/4] platform/chrome: cros_ec_lightbar - Add new features

Dear all, The following patches taken from the ChromeOS 4.4 tree adds more features to the cros_ec_lightbar driver. The patches were forward ported to current mainline and were tested on a Chromebook Pixel 2015. Best regards, Enric Changes since v1: - Rebase on top of mainline. - Added Lee

Re: probably serious conntrack/netfilter panic, 4.8.14, timers and intel turbo

On 2017-01-11 19:22, Guillaume Nault wrote: Cc: netfilter-de...@vger.kernel.org, I'm afraid I'll need some help for this case. On Sat, Dec 17, 2016 at 09:48:13PM +0200, Denys Fedoryshchenko wrote: Hi, I posted recently several netfilter related crashes, didn't got any answers, one of them

Re: probably serious conntrack/netfilter panic, 4.8.14, timers and intel turbo

On 2017-01-11 19:22, Guillaume Nault wrote: Cc: netfilter-de...@vger.kernel.org, I'm afraid I'll need some help for this case. On Sat, Dec 17, 2016 at 09:48:13PM +0200, Denys Fedoryshchenko wrote: Hi, I posted recently several netfilter related crashes, didn't got any answers, one of them

Re: [PATCH V2] regulator: core: Don't use regulators as supplies until the parent is bound

On 11/01/17 17:14, Jon Hunter wrote: > When regulators are successfully registered, we check to see if the > regulator is a supply for any other registered regulator and if so > add the new regulator as the supply for the existing regulator(s). > > Some devices, such as Power Management ICs, may

Re: [PATCH V2] regulator: core: Don't use regulators as supplies until the parent is bound

On 11/01/17 17:14, Jon Hunter wrote: > When regulators are successfully registered, we check to see if the > regulator is a supply for any other registered regulator and if so > add the new regulator as the supply for the existing regulator(s). > > Some devices, such as Power Management ICs, may

Re: [PATCH 56/62] watchdog: tangox_wdt: Convert to use device managed functions

On Wed, Jan 11, 2017 at 03:39:17PM +0100, Uwe Kleine-König wrote: > On Wed, Jan 11, 2017 at 01:31:47PM +0100, Marc Gonzalez wrote: > > On 11/01/2017 11:52, Guenter Roeck wrote: > > > > > On 01/11/2017 01:07 AM, Marc Gonzalez wrote: > > > > > >>> @@ -134,12 +134,15 @@ static int

Re: [PATCH 56/62] watchdog: tangox_wdt: Convert to use device managed functions

On Wed, Jan 11, 2017 at 03:39:17PM +0100, Uwe Kleine-König wrote: > On Wed, Jan 11, 2017 at 01:31:47PM +0100, Marc Gonzalez wrote: > > On 11/01/2017 11:52, Guenter Roeck wrote: > > > > > On 01/11/2017 01:07 AM, Marc Gonzalez wrote: > > > > > >>> @@ -134,12 +134,15 @@ static int

[PATCH] Input: egalax_ts - do not release gpio if probe successful

Thus preventing anyone to later modify the interrupt GPIO direction and/or state without the driver knowing. Also checking if device is present before allocating the input device. Signed-off-by: Gary Bisson --- drivers/input/touchscreen/egalax_ts.c | 56

[PATCH] Input: egalax_ts - do not release gpio if probe successful

Thus preventing anyone to later modify the interrupt GPIO direction and/or state without the driver knowing. Also checking if device is present before allocating the input device. Signed-off-by: Gary Bisson --- drivers/input/touchscreen/egalax_ts.c | 56 --- 1

Re: [PATCH/RESEND v2 5/5] z3fold: add kref refcounting

On Wed, Jan 11, 2017 at 6:08 PM, Dan Streetman wrote: > On Wed, Jan 11, 2017 at 10:06 AM, Vitaly Wool wrote: >> With both coming and already present locking optimizations, >> introducing kref to reference-count z3fold objects is the right >> thing to do.

Re: [PATCH/RESEND v2 5/5] z3fold: add kref refcounting

On Wed, Jan 11, 2017 at 6:08 PM, Dan Streetman wrote: > On Wed, Jan 11, 2017 at 10:06 AM, Vitaly Wool wrote: >> With both coming and already present locking optimizations, >> introducing kref to reference-count z3fold objects is the right >> thing to do. Moreover, it makes buddied list no longer

[PATCH v5 04/12] mmc: sdhci: Export sdhci_enable_sdio_irq() from sdhci.c

From: Hu Ziji Export sdhci_enable_sdio_irq() from sdhci.c. Thus vendor SDHC driver can implement its specific SDIO irq control. Signed-off-by: Hu Ziji Signed-off-by: Gregory CLEMENT --- drivers/mmc/host/sdhci.c | 3

[PATCH v5 03/12] mmc: sdhci: Export sdhci_start_signal_voltage_switch() in sdhci.c

From: Hu Ziji Export sdhci_start_signal_voltage_switch() from sdhci.c. Thus vendor sdhci driver can implement its own signal voltage switch routine. Signed-off-by: Hu Ziji Signed-off-by: Gregory CLEMENT ---

Re: [PATCH v2 4/5] firmware: add SmPL report for custom fallback mechanism

On Wed, Jan 11, 2017 at 9:49 AM, Greg KH wrote: > On Wed, Jan 11, 2017 at 03:02:22PM +0100, Luis R. Rodriguez wrote: >> On Wed, Jan 11, 2017 at 09:32:26AM +0100, Greg KH wrote: >> > On Fri, Dec 16, 2016 at 03:10:37AM -0800, Luis R. Rodriguez wrote: >> > > Even though

[PATCH v5 02/12] mmc: sdhci: Export sdhci_set_ios() from sdhci.c

From: Hu Ziji Export sdhci_set_ios() in sdhci.c. Thus vendor sdhci driver can implement its own set_ios() routine. Signed-off-by: Hu Ziji Signed-off-by: Gregory CLEMENT --- drivers/mmc/host/sdhci.c | 3 ++-

Re: [PATCH v7 3/7] perf/amd/iommu: Modify IOMMU API to allow specifying IOMMU index

On Mon, Jan 09, 2017 at 09:33:43PM -0600, Suravee Suthikulpanit wrote: > The current amd_iommu_pc_get_set_reg_val() cannot support multi-IOMMU. multiple IOMMUs. > It is also confusing since it is trying to support set and get in > one

[PATCH v5 04/12] mmc: sdhci: Export sdhci_enable_sdio_irq() from sdhci.c

From: Hu Ziji Export sdhci_enable_sdio_irq() from sdhci.c. Thus vendor SDHC driver can implement its specific SDIO irq control. Signed-off-by: Hu Ziji Signed-off-by: Gregory CLEMENT --- drivers/mmc/host/sdhci.c | 3 ++- drivers/mmc/host/sdhci.h | 1 + 2 files changed, 3 insertions(+), 1

[PATCH v5 03/12] mmc: sdhci: Export sdhci_start_signal_voltage_switch() in sdhci.c

From: Hu Ziji Export sdhci_start_signal_voltage_switch() from sdhci.c. Thus vendor sdhci driver can implement its own signal voltage switch routine. Signed-off-by: Hu Ziji Signed-off-by: Gregory CLEMENT --- drivers/mmc/host/sdhci.c | 5 +++-- drivers/mmc/host/sdhci.h | 2 ++ 2 files changed,

Re: [PATCH v2 4/5] firmware: add SmPL report for custom fallback mechanism

On Wed, Jan 11, 2017 at 9:49 AM, Greg KH wrote: > On Wed, Jan 11, 2017 at 03:02:22PM +0100, Luis R. Rodriguez wrote: >> On Wed, Jan 11, 2017 at 09:32:26AM +0100, Greg KH wrote: >> > On Fri, Dec 16, 2016 at 03:10:37AM -0800, Luis R. Rodriguez wrote: >> > > Even though most distributions today

[PATCH v5 02/12] mmc: sdhci: Export sdhci_set_ios() from sdhci.c

From: Hu Ziji Export sdhci_set_ios() in sdhci.c. Thus vendor sdhci driver can implement its own set_ios() routine. Signed-off-by: Hu Ziji Signed-off-by: Gregory CLEMENT --- drivers/mmc/host/sdhci.c | 3 ++- drivers/mmc/host/sdhci.h | 1 + 2 files changed, 3 insertions(+), 1 deletion(-) diff

Re: [PATCH v7 3/7] perf/amd/iommu: Modify IOMMU API to allow specifying IOMMU index

On Mon, Jan 09, 2017 at 09:33:43PM -0600, Suravee Suthikulpanit wrote: > The current amd_iommu_pc_get_set_reg_val() cannot support multi-IOMMU. multiple IOMMUs. > It is also confusing since it is trying to support set and get in > one

[PATCH v5 06/12] mmc: sdhci-xenon: Add Marvell Xenon SDHC core functionality

From: Hu Ziji Add Xenon eMMC/SD/SDIO host controller core functionality. Add Xenon specific intialization process. Add Xenon specific mmc_host_ops APIs. Add Xenon specific register definitions. Add CONFIG_MMC_SDHCI_XENON support in drivers/mmc/host/Kconfig. Marvell Xenon

[PATCH v5 09/12] MAINTAINERS: add entry for Marvell Xenon MMC Host Controller drivers

From: Hu Ziji Add maintainer entry for Marvell Xenon eMMC/SD/SDIO Host Controller drivers. Signed-off-by: Hu Ziji Signed-off-by: Gregory CLEMENT --- MAINTAINERS | 7 +++ 1 file changed, 7 insertions(+) diff

Re: probably serious conntrack/netfilter panic, 4.8.14, timers and intel turbo

Cc: netfilter-de...@vger.kernel.org, I'm afraid I'll need some help for this case. On Sat, Dec 17, 2016 at 09:48:13PM +0200, Denys Fedoryshchenko wrote: > Hi, > > I posted recently several netfilter related crashes, didn't got any answers, > one of them started to happen quite often on loaded

[PATCH v5 06/12] mmc: sdhci-xenon: Add Marvell Xenon SDHC core functionality

From: Hu Ziji Add Xenon eMMC/SD/SDIO host controller core functionality. Add Xenon specific intialization process. Add Xenon specific mmc_host_ops APIs. Add Xenon specific register definitions. Add CONFIG_MMC_SDHCI_XENON support in drivers/mmc/host/Kconfig. Marvell Xenon SDHC conforms to SD

[PATCH v5 09/12] MAINTAINERS: add entry for Marvell Xenon MMC Host Controller drivers

From: Hu Ziji Add maintainer entry for Marvell Xenon eMMC/SD/SDIO Host Controller drivers. Signed-off-by: Hu Ziji Signed-off-by: Gregory CLEMENT --- MAINTAINERS | 7 +++ 1 file changed, 7 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index cfff2c9e3d94..f4fea77165d5 100644 ---

Re: probably serious conntrack/netfilter panic, 4.8.14, timers and intel turbo

Cc: netfilter-de...@vger.kernel.org, I'm afraid I'll need some help for this case. On Sat, Dec 17, 2016 at 09:48:13PM +0200, Denys Fedoryshchenko wrote: > Hi, > > I posted recently several netfilter related crashes, didn't got any answers, > one of them started to happen quite often on loaded

[PATCH v2 1/1] platform/x86: Remove PMIC GPIO block support

The Moorestown support was removed by commit 1a8359e411eb ("x86/mid: Remove Intel Moorestown"). Remove this leftover. Signed-off-by: Andy Shevchenko --- In v2: - remove useless header inclusion arch/x86/platform/intel-mid/sfi.c | 1 -

[PATCH v5 00/12] mmc: Add support to Marvell Xenon SD Host Controller

Hello, This the fifth version of the series adding support for the SDHCI Xenon controller. It can be currently found on the Armada 37xx and the Armada 7K/8K but will be also used in more Marvell SoC (and not only the mvebu ones actually). v4->v5: - Remove the patch to export

[PATCH v2 1/1] platform/x86: Remove PMIC GPIO block support

The Moorestown support was removed by commit 1a8359e411eb ("x86/mid: Remove Intel Moorestown"). Remove this leftover. Signed-off-by: Andy Shevchenko --- In v2: - remove useless header inclusion arch/x86/platform/intel-mid/sfi.c | 1 - drivers/platform/x86/Kconfig | 7 -

[PATCH v5 00/12] mmc: Add support to Marvell Xenon SD Host Controller

Hello, This the fifth version of the series adding support for the SDHCI Xenon controller. It can be currently found on the Armada 37xx and the Armada 7K/8K but will be also used in more Marvell SoC (and not only the mvebu ones actually). v4->v5: - Remove the patch to export

[PATCH v5 07/12] mmc: sdhci-xenon: Add support to PHYs of Marvell Xenon SDHC.

From: Hu Ziji Marvell Xenon eMMC/SD/SDIO Host Controller contains PHY. Multiple types of PHYs are supported. Add support to multiple types of PHYs init and configuration. Add register definitions of PHYs. Xenon PHY cannot fit in kernel common PHY framework. Xenon SDHC PHY

[PATCH v5 08/12] mmc: sdhci-xenon: Add SoC PHY PAD voltage control

From: Hu Ziji Some SoCs have PHY PAD outside Xenon IP. PHY PAD voltage should match signalling voltage in use. Add generic SoC PHY PAD voltage control interface. Implement Aramda-3700 SoC PHY PAD voltage control. Signed-off-by: Hu Ziji Tested-by:

[PATCH v5 10/12] arm64: dts: marvell: add eMMC support for Armada 37xx

Add the eMMC support for Armada 37xx SoC and enable it in the Armada 3720 DB board. Signed-off-by: Gregory CLEMENT --- arch/arm64/boot/dts/marvell/armada-3720-db.dts | 16 arch/arm64/boot/dts/marvell/armada-37xx.dtsi | 11 +++ 2

[PATCH v5 01/12] clk: apn806: Add eMMC clock to system controller driver

From: Konstantin Porotchkin Add fixed clock of 400MHz to system controller driver. This clock is used as SD/eMMC clock source. Signed-off-by: Konstantin Porotchkin Reviewed-by: Omri Itach Reviewed-by: Hanna Hawa

[PATCH v5 12/12] arm64: configs: enable SDHCI driver for Xenon

This patch enables the driver for the SDHCI controller found on the Marvell Armada 3700 and 7K/8K ARM64 SoCs. Signed-off-by: Gregory CLEMENT --- arch/arm64/configs/defconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm64/configs/defconfig

[PATCH v5 01/12] clk: apn806: Add eMMC clock to system controller driver

From: Konstantin Porotchkin Add fixed clock of 400MHz to system controller driver. This clock is used as SD/eMMC clock source. Signed-off-by: Konstantin Porotchkin Reviewed-by: Omri Itach Reviewed-by: Hanna Hawa [fixed up conflicts, added error handling --rmk] Signed-off-by: Russell King

[PATCH v5 12/12] arm64: configs: enable SDHCI driver for Xenon

This patch enables the driver for the SDHCI controller found on the Marvell Armada 3700 and 7K/8K ARM64 SoCs. Signed-off-by: Gregory CLEMENT --- arch/arm64/configs/defconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig index

[PATCH v5 08/12] mmc: sdhci-xenon: Add SoC PHY PAD voltage control

From: Hu Ziji Some SoCs have PHY PAD outside Xenon IP. PHY PAD voltage should match signalling voltage in use. Add generic SoC PHY PAD voltage control interface. Implement Aramda-3700 SoC PHY PAD voltage control. Signed-off-by: Hu Ziji Tested-by: Russell King Signed-off-by: Gregory CLEMENT

[PATCH v5 10/12] arm64: dts: marvell: add eMMC support for Armada 37xx

Add the eMMC support for Armada 37xx SoC and enable it in the Armada 3720 DB board. Signed-off-by: Gregory CLEMENT --- arch/arm64/boot/dts/marvell/armada-3720-db.dts | 16 arch/arm64/boot/dts/marvell/armada-37xx.dtsi | 11 +++ 2 files changed, 27 insertions(+) diff

[PATCH v5 07/12] mmc: sdhci-xenon: Add support to PHYs of Marvell Xenon SDHC.

From: Hu Ziji Marvell Xenon eMMC/SD/SDIO Host Controller contains PHY. Multiple types of PHYs are supported. Add support to multiple types of PHYs init and configuration. Add register definitions of PHYs. Xenon PHY cannot fit in kernel common PHY framework. Xenon SDHC PHY register is a part of

[PATCH v5 11/12] arm64: dts: marvell: add sdhci support for Armada 7K/8K

Also enable it on the Armada 7040 DB board Signed-off-by: Gregory CLEMENT --- arch/arm64/boot/dts/marvell/armada-7040-db.dts | 14 +- arch/arm64/boot/dts/marvell/armada-ap806.dtsi| 10 +-

[PATCH v5 11/12] arm64: dts: marvell: add sdhci support for Armada 7K/8K

Also enable it on the Armada 7040 DB board Signed-off-by: Gregory CLEMENT --- arch/arm64/boot/dts/marvell/armada-7040-db.dts | 14 +- arch/arm64/boot/dts/marvell/armada-ap806.dtsi| 10 +- arch/arm64/boot/dts/marvell/armada-cp110-master.dtsi | 11 ++- 3

[PATCH v5 05/12] dt: bindings: Add bindings for Marvell Xenon SD Host Controller

From: Hu Ziji Marvell Xenon SDHC can support eMMC/SD/SDIO. Add Xenon-specific properties. Also add properties for Xenon PHY setting. Signed-off-by: Hu Ziji Signed-off-by: Gregory CLEMENT ---

[PATCH v5 05/12] dt: bindings: Add bindings for Marvell Xenon SD Host Controller

From: Hu Ziji Marvell Xenon SDHC can support eMMC/SD/SDIO. Add Xenon-specific properties. Also add properties for Xenon PHY setting. Signed-off-by: Hu Ziji Signed-off-by: Gregory CLEMENT --- Documentation/devicetree/bindings/mmc/marvell,xenon-sdhci.txt | 197 +++- 1 file changed, 197

Re: [PATCH v4 2/4] mm: Add function to support extra actions on swap in/out

On 01/11/2017 09:56 AM, Dave Hansen wrote: On 01/11/2017 08:12 AM, Khalid Aziz wrote: +#ifndef set_swp_pte_at +#define set_swp_pte_at(mm, addr, ptep, pte, oldpte)\ + set_pte_at(mm, addr, ptep, pte) +#endif BTW, thanks for the *much* improved description of the series. This

Re: [PATCH v4 2/4] mm: Add function to support extra actions on swap in/out

On 01/11/2017 09:56 AM, Dave Hansen wrote: On 01/11/2017 08:12 AM, Khalid Aziz wrote: +#ifndef set_swp_pte_at +#define set_swp_pte_at(mm, addr, ptep, pte, oldpte)\ + set_pte_at(mm, addr, ptep, pte) +#endif BTW, thanks for the *much* improved description of the series. This

Re: Dell XPS13 does not suspend with Linux 4.10-rc3

On 01/11/17 10:49, Winkler, Tomas wrote: Subject: Re: Dell XPS13 does not suspend with Linux 4.10-rc3 On 01/11/17 10:36, Greg Kroah-Hartman wrote: On Wed, Jan 11, 2017 at 09:53:38AM +0100, Paul Menzel wrote: On 01/10/17 23:24, Jan Niehusmann wrote: On Tue, Jan 10, 2017 at 09:43:31PM

Re: Dell XPS13 does not suspend with Linux 4.10-rc3

On 01/11/17 10:49, Winkler, Tomas wrote: Subject: Re: Dell XPS13 does not suspend with Linux 4.10-rc3 On 01/11/17 10:36, Greg Kroah-Hartman wrote: On Wed, Jan 11, 2017 at 09:53:38AM +0100, Paul Menzel wrote: On 01/10/17 23:24, Jan Niehusmann wrote: On Tue, Jan 10, 2017 at 09:43:31PM

[PATCH V2] regulator: core: Don't use regulators as supplies until the parent is bound

When regulators are successfully registered, we check to see if the regulator is a supply for any other registered regulator and if so add the new regulator as the supply for the existing regulator(s). Some devices, such as Power Management ICs, may register a series of regulators when probed and

[PATCH V2] regulator: core: Don't use regulators as supplies until the parent is bound

When regulators are successfully registered, we check to see if the regulator is a supply for any other registered regulator and if so add the new regulator as the supply for the existing regulator(s). Some devices, such as Power Management ICs, may register a series of regulators when probed and

Re: [PATCH/RESEND v2 5/5] z3fold: add kref refcounting

On Wed, Jan 11, 2017 at 10:06 AM, Vitaly Wool wrote: > With both coming and already present locking optimizations, > introducing kref to reference-count z3fold objects is the right > thing to do. Moreover, it makes buddied list no longer necessary, > and allows for a simpler

Re: [PATCH/RESEND v2 5/5] z3fold: add kref refcounting

On Wed, Jan 11, 2017 at 10:06 AM, Vitaly Wool wrote: > With both coming and already present locking optimizations, > introducing kref to reference-count z3fold objects is the right > thing to do. Moreover, it makes buddied list no longer necessary, > and allows for a simpler handling of headless

Re: [PATCH 1/2] drm: fix drm_vm for NOMMU builds

2017-01-11 17:59 GMT+01:00 Arnd Bergmann : > On Wed, Jan 11, 2017 at 5:36 PM, Daniel Vetter wrote: >> On Wed, Jan 11, 2017 at 5:33 PM, Arnd Bergmann wrote: >>> CONFIG_DRM_VM=y >> >> Does randconfig just set this for fun, despite that it's a hidden

Re: [PATCH 1/2] drm: fix drm_vm for NOMMU builds

2017-01-11 17:59 GMT+01:00 Arnd Bergmann : > On Wed, Jan 11, 2017 at 5:36 PM, Daniel Vetter wrote: >> On Wed, Jan 11, 2017 at 5:33 PM, Arnd Bergmann wrote: >>> CONFIG_DRM_VM=y >> >> Does randconfig just set this for fun, despite that it's a hidden >> Kconfig symbol? Should we add a depends

Re: [PATCH/RESEND 5/5] z3fold: add kref refcounting

On Wed, Jan 11, 2017 at 5:58 PM, Dan Streetman wrote: > On Wed, Jan 11, 2017 at 5:52 AM, Vitaly Wool wrote: >> On Wed, Jan 4, 2017 at 7:42 PM, Dan Streetman wrote: >>> On Sun, Dec 25, 2016 at 7:40 PM, Vitaly Wool

Re: [PATCH/RESEND 5/5] z3fold: add kref refcounting

On Wed, Jan 11, 2017 at 5:58 PM, Dan Streetman wrote: > On Wed, Jan 11, 2017 at 5:52 AM, Vitaly Wool wrote: >> On Wed, Jan 4, 2017 at 7:42 PM, Dan Streetman wrote: >>> On Sun, Dec 25, 2016 at 7:40 PM, Vitaly Wool wrote: With both coming and already present locking optimizations,

Re: [Intel-gfx] GPU hang with kernel 4.10rc3

On Wed, Jan 11, 2017 at 05:33:34PM +0100, Juergen Gross wrote: > With kernel 4.10rc3 running as Xen dm0 I get at each boot: > > [ 49.213697] [drm] GPU HANG: ecode 7:0:0x3d1d3d3d, in gnome-shell > [1431], reason: Hang on render ring, action: reset > [ 49.213699] [drm] GPU hangs can indicate a

Re: [Intel-gfx] GPU hang with kernel 4.10rc3

On Wed, Jan 11, 2017 at 05:33:34PM +0100, Juergen Gross wrote: > With kernel 4.10rc3 running as Xen dm0 I get at each boot: > > [ 49.213697] [drm] GPU HANG: ecode 7:0:0x3d1d3d3d, in gnome-shell > [1431], reason: Hang on render ring, action: reset > [ 49.213699] [drm] GPU hangs can indicate a

Re: [PATCH] usb: dwc3 dwc3_exynos_probe() change goto labels to meaningful names

Hello Shuah, On 01/11/2017 01:45 PM, Shuah Khan wrote: > Change goto labels to meaningful names from a series of errNs. > > Signed-off-by: Shuah Khan > --- > drivers/usb/dwc3/dwc3-exynos.c | 22 +++--- > 1 file changed, 11 insertions(+), 11 deletions(-)

Re: [PATCH] usb: dwc3 dwc3_exynos_probe() change goto labels to meaningful names

Hello Shuah, On 01/11/2017 01:45 PM, Shuah Khan wrote: > Change goto labels to meaningful names from a series of errNs. > > Signed-off-by: Shuah Khan > --- > drivers/usb/dwc3/dwc3-exynos.c | 22 +++--- > 1 file changed, 11 insertions(+), 11 deletions(-) > > diff --git

Re: [RFC v4 2/6] sched/deadline: improve the tracking of active utilization

Hi, On 30/12/16 12:33, Luca Abeni wrote: > From: Luca Abeni > > This patch implements a more theoretically sound algorithm for > tracking active utilization: instead of decreasing it when a > task blocks, use a timer (the "inactive timer", named after the > "Inactive" task

Re: [RFC v4 2/6] sched/deadline: improve the tracking of active utilization

Hi, On 30/12/16 12:33, Luca Abeni wrote: > From: Luca Abeni > > This patch implements a more theoretically sound algorithm for > tracking active utilization: instead of decreasing it when a > task blocks, use a timer (the "inactive timer", named after the > "Inactive" task state of the GRUB

Re: [PATCH] drm: Fix broken VT switch with video=1366x768 option

On Tue, Jan 10, 2017 at 01:41:42PM +0100, Daniel Vetter wrote: > On Tue, Jan 10, 2017 at 12:36:50PM +0100, Takashi Iwai wrote: > > On Tue, 10 Jan 2017 12:28:36 +0100, > > Ville Syrjälä wrote: > > > > > > On Mon, Jan 09, 2017 at 03:56:14PM +0100, Takashi Iwai wrote: > > > > I noticed that the VT

Re: [PATCH] drm: Fix broken VT switch with video=1366x768 option

On Tue, Jan 10, 2017 at 01:41:42PM +0100, Daniel Vetter wrote: > On Tue, Jan 10, 2017 at 12:36:50PM +0100, Takashi Iwai wrote: > > On Tue, 10 Jan 2017 12:28:36 +0100, > > Ville Syrjälä wrote: > > > > > > On Mon, Jan 09, 2017 at 03:56:14PM +0100, Takashi Iwai wrote: > > > > I noticed that the VT

Re: [PATCH v4 2/4] mm: Add function to support extra actions on swap in/out

On 01/11/2017 08:12 AM, Khalid Aziz wrote: > +#ifndef set_swp_pte_at > +#define set_swp_pte_at(mm, addr, ptep, pte, oldpte) \ > + set_pte_at(mm, addr, ptep, pte) > +#endif BTW, thanks for the *much* improved description of the series. This is way easier to understand. I really

Re: [PATCH v4 2/4] mm: Add function to support extra actions on swap in/out

On 01/11/2017 08:12 AM, Khalid Aziz wrote: > +#ifndef set_swp_pte_at > +#define set_swp_pte_at(mm, addr, ptep, pte, oldpte) \ > + set_pte_at(mm, addr, ptep, pte) > +#endif BTW, thanks for the *much* improved description of the series. This is way easier to understand. I really

Re: [PATCH 1/2] drm: fix drm_vm for NOMMU builds

On Wed, Jan 11, 2017 at 5:36 PM, Daniel Vetter wrote: > On Wed, Jan 11, 2017 at 5:33 PM, Arnd Bergmann wrote: >> CONFIG_DRM_VM=y > > Does randconfig just set this for fun, despite that it's a hidden > Kconfig symbol? Should we add a depends !NOMMU to it to make

Re: [PATCH 1/2] drm: fix drm_vm for NOMMU builds

On Wed, Jan 11, 2017 at 5:36 PM, Daniel Vetter wrote: > On Wed, Jan 11, 2017 at 5:33 PM, Arnd Bergmann wrote: >> CONFIG_DRM_VM=y > > Does randconfig just set this for fun, despite that it's a hidden > Kconfig symbol? Should we add a depends !NOMMU to it to make sure it > never gets enabled when

Re: ANNOUNCE: mdadm 4.0 - A tool for managing md Soft RAID under Linux

On 01/11/17 11:52, Shaohua Li wrote: > On Tue, Jan 10, 2017 at 11:49:04AM -0600, Bruce Dubbs wrote: >> Jes Sorensen wrote: >>> I am pleased to announce the availability of >>> mdadm version 4.0 >>> >>> It is available at the usual places: >>>

Re: ANNOUNCE: mdadm 4.0 - A tool for managing md Soft RAID under Linux

On 01/11/17 11:52, Shaohua Li wrote: > On Tue, Jan 10, 2017 at 11:49:04AM -0600, Bruce Dubbs wrote: >> Jes Sorensen wrote: >>> I am pleased to announce the availability of >>> mdadm version 4.0 >>> >>> It is available at the usual places: >>>

<    4   5   6   7   8   9   10   11   12   13   >