[PATCH v2 6/7] IIO: add STM32 IIO timer driver

Timers IPs can be used to generate triggers for other IPs like DAC, ADC or other timers. Each trigger may result of timer internals signals like counter enable, reset or edge, this configuration could be done through "master_mode" device attribute. A timer device could be triggered by other

[PATCH v2 2/7] MFD: add stm32 general purpose timer driver

This hardware block could at used at same time for PWM generation and IIO timer for other IPs like DAC, ADC or other timers. PWM and IIO timer configuration are mixed in the same registers so we need a multi fonction driver to be able to share those registers. version 2: - rename driver

[PATCH v2 5/7] IIO: add bindings for stm32 IIO timer driver

Define bindings for stm32 IIO timer version 2: - only keep one compatible - add DT parameters to set lists of the triggers: one list describe the triggers created by the device another one give the triggers accepted by the device Signed-off-by: Benjamin Gaignard

[PATCH] clocksource/drivers/moxart: fix memory leak on timer on error exit paths

From: Colin Ian King The timer is not being free'd on the error exit paths, causing a small memory leak. Add an err exit path that free's timer and returns the error status in ret. Signed-off-by: Colin Ian King ---

[PATCH v2 2/7] MFD: add stm32 general purpose timer driver

This hardware block could at used at same time for PWM generation and IIO timer for other IPs like DAC, ADC or other timers. PWM and IIO timer configuration are mixed in the same registers so we need a multi fonction driver to be able to share those registers. version 2: - rename driver

[PATCH v2 5/7] IIO: add bindings for stm32 IIO timer driver

Define bindings for stm32 IIO timer version 2: - only keep one compatible - add DT parameters to set lists of the triggers: one list describe the triggers created by the device another one give the triggers accepted by the device Signed-off-by: Benjamin Gaignard ---

[PATCH] clocksource/drivers/moxart: fix memory leak on timer on error exit paths

From: Colin Ian King The timer is not being free'd on the error exit paths, causing a small memory leak. Add an err exit path that free's timer and returns the error status in ret. Signed-off-by: Colin Ian King --- drivers/clocksource/moxart_timer.c | 19 +-- 1 file changed,

[PATCH v2 6/7] IIO: add STM32 IIO timer driver

Timers IPs can be used to generate triggers for other IPs like DAC, ADC or other timers. Each trigger may result of timer internals signals like counter enable, reset or edge, this configuration could be done through "master_mode" device attribute. A timer device could be triggered by other

[PATCH v2 3/7] PWM: add pwm-stm32 DT bindings

Define bindings for pwm-stm32 version 2: - use parameters instead of compatible of handle the hardware configuration Signed-off-by: Benjamin Gaignard --- .../devicetree/bindings/pwm/pwm-stm32.txt | 37 ++ 1 file changed, 37 insertions(+)

[PATCH v2 1/7] MFD: add bindings for stm32 general purpose timer driver

Add bindings information for stm32 general purpose timer version 2: - rename stm32-mfd-timer to stm32-gptimer - only keep one compatible string Signed-off-by: Benjamin Gaignard --- .../bindings/mfd/stm32-general-purpose-timer.txt | 43 ++ 1 file

[PATCH v2 7/7] ARM: dts: stm32: add stm32 general purpose timer driver in DT

Add general purpose timers and it sub-nodes into DT for stm32f4. Define and enable pwm1 and pwm3 for stm32f469 discovery board version 2: - use parameters to describe hardware capabilities - do not use references for pwm and iio timer subnodes Signed-off-by: Benjamin Gaignard

[PATCH v2 3/7] PWM: add pwm-stm32 DT bindings

Define bindings for pwm-stm32 version 2: - use parameters instead of compatible of handle the hardware configuration Signed-off-by: Benjamin Gaignard --- .../devicetree/bindings/pwm/pwm-stm32.txt | 37 ++ 1 file changed, 37 insertions(+) create mode 100644

[PATCH v2 1/7] MFD: add bindings for stm32 general purpose timer driver

Add bindings information for stm32 general purpose timer version 2: - rename stm32-mfd-timer to stm32-gptimer - only keep one compatible string Signed-off-by: Benjamin Gaignard --- .../bindings/mfd/stm32-general-purpose-timer.txt | 43 ++ 1 file changed, 43 insertions(+)

[PATCH v2 7/7] ARM: dts: stm32: add stm32 general purpose timer driver in DT

Add general purpose timers and it sub-nodes into DT for stm32f4. Define and enable pwm1 and pwm3 for stm32f469 discovery board version 2: - use parameters to describe hardware capabilities - do not use references for pwm and iio timer subnodes Signed-off-by: Benjamin Gaignard ---

[PATCH v2 0/7] Add pwm and IIO timer drivers for stm32

version 2: - keep only one compatible per driver - use DT parameters to describe hardware block configuration: - pwm channels, complementary output, counter size, break input - triggers accepted and create by IIO timers - change DT to limite use of reference to the node - interrupt is now in

[PATCH v2 0/7] Add pwm and IIO timer drivers for stm32

version 2: - keep only one compatible per driver - use DT parameters to describe hardware block configuration: - pwm channels, complementary output, counter size, break input - triggers accepted and create by IIO timers - change DT to limite use of reference to the node - interrupt is now in

Re: many "changed bandwidth, new config is" messages in the log

On Thu, 2016-11-24 at 15:07 +, Michal Hocko wrote: > I have only now managed to move to 4.9-rc5 (from 4.8) and started > seeing quite a lot of following messages > " > [  346.612211] wlan0: AP c0:4a:00:f1:48:f2 changed bandwidth, new > config is 2472 MHz, width 1 (2472/0 MHz) > [  352.655929]

Re: many "changed bandwidth, new config is" messages in the log

On Thu, 2016-11-24 at 15:07 +, Michal Hocko wrote: > I have only now managed to move to 4.9-rc5 (from 4.8) and started > seeing quite a lot of following messages > " > [  346.612211] wlan0: AP c0:4a:00:f1:48:f2 changed bandwidth, new > config is 2472 MHz, width 1 (2472/0 MHz) > [  352.655929]

[PATCH 4.4 16/31] clk: mmp: pxa168: fix return value check in pxa168_clk_init()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Wei Yongjun commit deab07261d54b4db7b627d38e0efac97f176c6d6 upstream. Fix the retrn value check which testing the wrong variable in pxa168_clk_init(). Fixes:

Re: [PATCH net-next 1/4] net: mvneta: Convert to be 64 bits compatible

Hi Gregory, 2016-11-24 16:01 GMT+01:00 Gregory CLEMENT : > Hi Arnd, > > On jeu., nov. 24 2016, Arnd Bergmann wrote: > >> On Thursday, November 24, 2016 4:37:36 PM CET Jisheng Zhang wrote: >>> solB (a SW shadow cookie) perhaps gives a better

Re: [PATCH] gpio: tegra186: Add support for T186 GPIO

On Wed, Nov 23, 2016 at 8:40 PM, Thierry Reding wrote: > On Wed, Nov 23, 2016 at 02:25:51PM +0100, Linus Walleij wrote: >> Everything, all kernel users and all character device users, end up >> calling gpiod_request(). > > It looks like I stumbled across the only case

[PATCH 4.4 21/31] uwb: fix device reference leaks

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit d6124b409ca33c100170ffde51cd8dff761454a1 upstream. This subsystem consistently fails to drop the device reference taken by class_find_device(). Note that

[PATCH 4.4 18/31] rtc: omap: Fix selecting external osc

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Lokesh Vutla commit 3984903a2e3906d3def220e688040ce93368200a upstream. RTC can be clocked from an external 32KHz oscillator, or from the Peripheral PLL. The RTC has an

many "changed bandwidth, new config is" messages in the log

Hi, I have only now managed to move to 4.9-rc5 (from 4.8) and started seeing quite a lot of following messages " [ 346.612211] wlan0: AP c0:4a:00:f1:48:f2 changed bandwidth, new config is 2472 MHz, width 1 (2472/0 MHz) [ 352.655929] wlan0: AP c0:4a:00:f1:48:f2 changed bandwidth, new config is

[PATCH 4.4 16/31] clk: mmp: pxa168: fix return value check in pxa168_clk_init()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Wei Yongjun commit deab07261d54b4db7b627d38e0efac97f176c6d6 upstream. Fix the retrn value check which testing the wrong variable in pxa168_clk_init(). Fixes: ab08aefcd12d ("clk: mmp: add

Re: [PATCH net-next 1/4] net: mvneta: Convert to be 64 bits compatible

Hi Gregory, 2016-11-24 16:01 GMT+01:00 Gregory CLEMENT : > Hi Arnd, > > On jeu., nov. 24 2016, Arnd Bergmann wrote: > >> On Thursday, November 24, 2016 4:37:36 PM CET Jisheng Zhang wrote: >>> solB (a SW shadow cookie) perhaps gives a better performance: in hot path, >>> such as mvneta_rx(), the

Re: [PATCH] gpio: tegra186: Add support for T186 GPIO

On Wed, Nov 23, 2016 at 8:40 PM, Thierry Reding wrote: > On Wed, Nov 23, 2016 at 02:25:51PM +0100, Linus Walleij wrote: >> Everything, all kernel users and all character device users, end up >> calling gpiod_request(). > > It looks like I stumbled across the only case where this isn't true. >

[PATCH 4.4 21/31] uwb: fix device reference leaks

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit d6124b409ca33c100170ffde51cd8dff761454a1 upstream. This subsystem consistently fails to drop the device reference taken by class_find_device(). Note that some of these

[PATCH 4.4 18/31] rtc: omap: Fix selecting external osc

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Lokesh Vutla commit 3984903a2e3906d3def220e688040ce93368200a upstream. RTC can be clocked from an external 32KHz oscillator, or from the Peripheral PLL. The RTC has an internal oscillator

many "changed bandwidth, new config is" messages in the log

Hi, I have only now managed to move to 4.9-rc5 (from 4.8) and started seeing quite a lot of following messages " [ 346.612211] wlan0: AP c0:4a:00:f1:48:f2 changed bandwidth, new config is 2472 MHz, width 1 (2472/0 MHz) [ 352.655929] wlan0: AP c0:4a:00:f1:48:f2 changed bandwidth, new config is

Re: [PATCH v5 6/6] i2c: use an IRQ to report Host Notify events, not alert

On Nov 24 2016 or thereabouts, Wolfram Sang wrote: > On Tue, Nov 22, 2016 at 12:49:22PM +0100, Wolfram Sang wrote: > > On Mon, Nov 21, 2016 at 11:52:48AM +0100, Benjamin Tissoires wrote: > > > Hi Wolfram, > > > > > > On Nov 07 2016 or thereabouts, Wolfram Sang wrote: > > > > On Thu, Oct 13, 2016

Re: [PATCH] gpio: Add Tegra186 support

On Thu, Nov 24, 2016 at 08:14:31PM +0530, Laxman Dewangan wrote: > > On Thursday 24 November 2016 08:14 PM, Thierry Reding wrote: > > * PGP Signed by an unknown key > > > > On Thu, Nov 24, 2016 at 12:23:56PM +0530, Laxman Dewangan wrote: > > > On Tuesday 22 November 2016 11:25 PM, Thierry Reding

Re: [RFC PATCH] ARM: dts: Add support for Turris Omnia

> @Tomas: I think it doesn't make sense when we alternate sending patches > without prior arrangement. Do you already work on a v5? If not I can do > that to fix the last few comments. Not sure when a submission is too > late to enter v4.10, but I think the window isn't that big any more. It is

[PATCH 4.4 17/31] clk: mmp: mmp2: fix return value check in mmp2_clk_init()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Wei Yongjun commit a29e52a6e66f4c0c895e7083e4bad2e7957f1fb5 upstream. Fix the retrn value check which testing the wrong variable in mmp2_clk_init(). Fixes:

Re: [PATCH v5 6/6] i2c: use an IRQ to report Host Notify events, not alert

On Nov 24 2016 or thereabouts, Wolfram Sang wrote: > On Tue, Nov 22, 2016 at 12:49:22PM +0100, Wolfram Sang wrote: > > On Mon, Nov 21, 2016 at 11:52:48AM +0100, Benjamin Tissoires wrote: > > > Hi Wolfram, > > > > > > On Nov 07 2016 or thereabouts, Wolfram Sang wrote: > > > > On Thu, Oct 13, 2016

Re: [PATCH] gpio: Add Tegra186 support

On Thu, Nov 24, 2016 at 08:14:31PM +0530, Laxman Dewangan wrote: > > On Thursday 24 November 2016 08:14 PM, Thierry Reding wrote: > > * PGP Signed by an unknown key > > > > On Thu, Nov 24, 2016 at 12:23:56PM +0530, Laxman Dewangan wrote: > > > On Tuesday 22 November 2016 11:25 PM, Thierry Reding

Re: [RFC PATCH] ARM: dts: Add support for Turris Omnia

> @Tomas: I think it doesn't make sense when we alternate sending patches > without prior arrangement. Do you already work on a v5? If not I can do > that to fix the last few comments. Not sure when a submission is too > late to enter v4.10, but I think the window isn't that big any more. It is

[PATCH 4.4 17/31] clk: mmp: mmp2: fix return value check in mmp2_clk_init()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Wei Yongjun commit a29e52a6e66f4c0c895e7083e4bad2e7957f1fb5 upstream. Fix the retrn value check which testing the wrong variable in mmp2_clk_init(). Fixes: 1ec770d92a62 ("clk: mmp: add mmp2

Re: [PATCH v2 1/3] perf: add PERF_RECORD_NAMESPACES to include namespaces related info

On Thu, Nov 24, 2016 at 08:14:29PM +0530, Hari Bathini wrote: > @@ -862,6 +875,19 @@ enum perf_event_type { >*/ > PERF_RECORD_SWITCH_CPU_WIDE = 15, > > + /* > + * struct { > + * struct perf_event_headerheader; > + * > + * u32

Re: [PATCH v2 1/3] perf: add PERF_RECORD_NAMESPACES to include namespaces related info

On Thu, Nov 24, 2016 at 08:14:29PM +0530, Hari Bathini wrote: > @@ -862,6 +875,19 @@ enum perf_event_type { >*/ > PERF_RECORD_SWITCH_CPU_WIDE = 15, > > + /* > + * struct { > + * struct perf_event_headerheader; > + * > + * u32

[PATCH 4.4 15/31] clk: mmp: pxa910: fix return value check in pxa910_clk_init()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Wei Yongjun commit 10f2bfb092e3b49000526c02cfe8b2abbbdbb752 upstream. Fix the retrn value check which testing the wrong variable in pxa910_clk_init(). Fixes:

[PATCH 4.4 19/31] iwlwifi: pcie: fix SPLC structure parsing

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Luca Coelho commit e0d9727c111a5917a1184c71c1a8e6f78c7fc41d upstream. The SPLC data parsing is too restrictive and was not trying find the correct element for WiFi.

Re: [PATCH] arm64: mm: Fix memmap to be initialized for the entire section

On 24.11.16 14:23:16, Ard Biesheuvel wrote: > On 24 November 2016 at 14:11, Robert Richter > wrote: > > On 24.11.16 13:58:30, Ard Biesheuvel wrote: > >> On 24 November 2016 at 13:51, Robert Richter > >> wrote: > >> > On 24.11.16 13:44:31,

[PATCH 4.4 15/31] clk: mmp: pxa910: fix return value check in pxa910_clk_init()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Wei Yongjun commit 10f2bfb092e3b49000526c02cfe8b2abbbdbb752 upstream. Fix the retrn value check which testing the wrong variable in pxa910_clk_init(). Fixes: 2bc61da9f7ff ("clk: mmp: add

[PATCH 4.4 19/31] iwlwifi: pcie: fix SPLC structure parsing

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Luca Coelho commit e0d9727c111a5917a1184c71c1a8e6f78c7fc41d upstream. The SPLC data parsing is too restrictive and was not trying find the correct element for WiFi. This causes problems with

Re: [PATCH] arm64: mm: Fix memmap to be initialized for the entire section

On 24.11.16 14:23:16, Ard Biesheuvel wrote: > On 24 November 2016 at 14:11, Robert Richter > wrote: > > On 24.11.16 13:58:30, Ard Biesheuvel wrote: > >> On 24 November 2016 at 13:51, Robert Richter > >> wrote: > >> > On 24.11.16 13:44:31, Ard Biesheuvel wrote: > >> >> On 24 November 2016 at

[PATCH v2 1/3] ARM: davinci: hawk: use gpio descriptor for mmc pins

Currently the mmc driver is polling the gpio to know if the card was removed. By using a gpio descriptor instead of the platform callbacks, the driver will be able to register the gpio using the mmc core API's designed for this purpose. This has the advantage that an irq will be registered, and

Re: [PATCH v5 6/6] i2c: use an IRQ to report Host Notify events, not alert

On Tue, Nov 22, 2016 at 12:49:22PM +0100, Wolfram Sang wrote: > On Mon, Nov 21, 2016 at 11:52:48AM +0100, Benjamin Tissoires wrote: > > Hi Wolfram, > > > > On Nov 07 2016 or thereabouts, Wolfram Sang wrote: > > > On Thu, Oct 13, 2016 at 02:10:40PM +0200, Benjamin Tissoires wrote: > > > > The

[PATCH 4.4 20/31] mfd: core: Fix device reference leak in mfd_clone_cell

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 722f191080de641f023feaa7d5648caf377844f5 upstream. Make sure to drop the reference taken by bus_find_device_by_name() before returning from

[PATCH 4.4 20/31] mfd: core: Fix device reference leak in mfd_clone_cell

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 722f191080de641f023feaa7d5648caf377844f5 upstream. Make sure to drop the reference taken by bus_find_device_by_name() before returning from mfd_clone_cell(). Fixes:

[PATCH v2 1/3] ARM: davinci: hawk: use gpio descriptor for mmc pins

Currently the mmc driver is polling the gpio to know if the card was removed. By using a gpio descriptor instead of the platform callbacks, the driver will be able to register the gpio using the mmc core API's designed for this purpose. This has the advantage that an irq will be registered, and

Re: [PATCH v5 6/6] i2c: use an IRQ to report Host Notify events, not alert

On Tue, Nov 22, 2016 at 12:49:22PM +0100, Wolfram Sang wrote: > On Mon, Nov 21, 2016 at 11:52:48AM +0100, Benjamin Tissoires wrote: > > Hi Wolfram, > > > > On Nov 07 2016 or thereabouts, Wolfram Sang wrote: > > > On Thu, Oct 13, 2016 at 02:10:40PM +0200, Benjamin Tissoires wrote: > > > > The

[PATCH v2 2/3] ARM: davinci: da850-evm: use gpio descriptor for mmc pins

Currently the mmc driver is polling the gpio to know if the card was removed. By using a gpio descriptor instead of the platform callbacks, the driver will be able to register the gpio using the mmc core API's designed for this purpose. This has the advantage that an irq will be registered, and

[GIT PULL] USB driver fixes for 4.9-rc7

The following changes since commit a25f0944ba9b1d8a6813fd6f1a86f1bd59ac25a6: Linux 4.9-rc5 (2016-11-13 10:32:32 -0800) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/ tags/usb-4.9-rc7 for you to fetch changes up to

[PATCH v2 2/3] ARM: davinci: da850-evm: use gpio descriptor for mmc pins

Currently the mmc driver is polling the gpio to know if the card was removed. By using a gpio descriptor instead of the platform callbacks, the driver will be able to register the gpio using the mmc core API's designed for this purpose. This has the advantage that an irq will be registered, and

[GIT PULL] USB driver fixes for 4.9-rc7

The following changes since commit a25f0944ba9b1d8a6813fd6f1a86f1bd59ac25a6: Linux 4.9-rc5 (2016-11-13 10:32:32 -0800) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/ tags/usb-4.9-rc7 for you to fetch changes up to

[PATCH v5 2/2] DW DMAC: add multi-block property to device tree

Several versions of DW DMAC have multi block transfers hardware support. Hardware support of multi block transfers is disabled by default if we use DT to configure DMAC and software emulation of multi block transfers used instead. Add multi-block property, so it is possible to enable hardware

[GIT PULL] MMC fixes for v.4.9 rc7

Hi Linus, Here are some mmc fixes intended for v4.9 rc7. They are based on v4.9-rc5. Details are as usual found in the signed tag. Please pull this in! Kind regards Ulf Hansson The following changes since commit a25f0944ba9b1d8a6813fd6f1a86f1bd59ac25a6: Linux 4.9-rc5 (2016-11-13 10:32:32

[PATCH v5 2/2] DW DMAC: add multi-block property to device tree

Several versions of DW DMAC have multi block transfers hardware support. Hardware support of multi block transfers is disabled by default if we use DT to configure DMAC and software emulation of multi block transfers used instead. Add multi-block property, so it is possible to enable hardware

[GIT PULL] MMC fixes for v.4.9 rc7

Hi Linus, Here are some mmc fixes intended for v4.9 rc7. They are based on v4.9-rc5. Details are as usual found in the signed tag. Please pull this in! Kind regards Ulf Hansson The following changes since commit a25f0944ba9b1d8a6813fd6f1a86f1bd59ac25a6: Linux 4.9-rc5 (2016-11-13 10:32:32

[PATCH v5 0/2] DW DMAC: update device tree

It wasn't possible to enable some features like memory-to-memory transfers or multi block transfers via DT. It is fixed by these patches. Changes for v5: * Update existing DTS. Pointed by Andy Shevchenko. * Read multi-block per chanel instead of per master (Move DW_DMA_MAX_NR_CHANNELS

[PATCH v2 3/3] ARM: davinci: da830-evm: use gpio descriptor for mmc pins

Currently the mmc driver is polling the gpio to know if the card was removed. By using a gpio descriptor instead of the platform callbacks, the driver will be able to register the gpio using the mmc core API's designed for this purpose. This has the advantage that an irq will be registered, and

[PATCH v5 0/2] DW DMAC: update device tree

It wasn't possible to enable some features like memory-to-memory transfers or multi block transfers via DT. It is fixed by these patches. Changes for v5: * Update existing DTS. Pointed by Andy Shevchenko. * Read multi-block per chanel instead of per master (Move DW_DMA_MAX_NR_CHANNELS

[PATCH v2 3/3] ARM: davinci: da830-evm: use gpio descriptor for mmc pins

Currently the mmc driver is polling the gpio to know if the card was removed. By using a gpio descriptor instead of the platform callbacks, the driver will be able to register the gpio using the mmc core API's designed for this purpose. This has the advantage that an irq will be registered, and

[PATCH 4.4 22/31] PM / sleep: fix device reference leak in test_suspend

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit ceb75787bc75d0a7b88519ab8a68067ac690f55a upstream. Make sure to drop the reference taken by class_find_device() after opening the RTC device. Fixes:

[PATCH v5 1/2] DW DMAC: enable memory-to-memory transfers support

All known devices, which use DT for configuration, support memory-to-memory transfers. So enable it by default, if we read configuration from DT. Acked-by: Andy Shevchenko Signed-off-by: Eugeniy Paltsev ---

[PATCH v5 1/2] DW DMAC: enable memory-to-memory transfers support

All known devices, which use DT for configuration, support memory-to-memory transfers. So enable it by default, if we read configuration from DT. Acked-by: Andy Shevchenko Signed-off-by: Eugeniy Paltsev --- drivers/dma/dw/platform.c | 6 ++ 1 file changed, 6 insertions(+) diff --git

[PATCH 4.4 22/31] PM / sleep: fix device reference leak in test_suspend

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit ceb75787bc75d0a7b88519ab8a68067ac690f55a upstream. Make sure to drop the reference taken by class_find_device() after opening the RTC device. Fixes: 77437fd4e61f (pm: boot

[PATCH v2 0/3] ARM: davinci: use gpio descriptors for mmc pins

For the boards that use gpios managed by the davinci gpio driver, we can use gpio descriptors to control the the mmc pins. This will let the mmc driver register an interrupt for the card detect pin, and also allows us to remove the dependency on platform callbacks for these boards. For boards

Re: [PATCH V12 1/1] usb:serial: Add Fintek F81532/534 driver

On Mon, Nov 14, 2016 at 01:37:59PM +0800, Ji-Ze Hong (Peter Hong) wrote: > This driver is for Fintek F81532/F81534 USB to Serial Ports IC. > > F81532 spec: > https://drive.google.com/file/d/0B8vRwwYO7aMFOTRRMmhWQVNvajQ/view?usp= > sharing > > F81534 spec: >

Re: [PATCH V12 1/1] usb:serial: Add Fintek F81532/534 driver

On Mon, Nov 14, 2016 at 01:37:59PM +0800, Ji-Ze Hong (Peter Hong) wrote: > This driver is for Fintek F81532/F81534 USB to Serial Ports IC. > > F81532 spec: > https://drive.google.com/file/d/0B8vRwwYO7aMFOTRRMmhWQVNvajQ/view?usp= > sharing > > F81534 spec: >

[PATCH v2 0/3] ARM: davinci: use gpio descriptors for mmc pins

For the boards that use gpios managed by the davinci gpio driver, we can use gpio descriptors to control the the mmc pins. This will let the mmc driver register an interrupt for the card detect pin, and also allows us to remove the dependency on platform callbacks for these boards. For boards

Re: linux-next: build failure after merge of the akpm-current tree

Hello Stephen, Am Donnerstag, 24. November 2016, 16:01:51 BRST schrieb Stephen Rothwell: > Hi Andrew, > > After merging the akpm-current tree, today's linux-next build (powerpc > ppc64_defconfig) failed like this: > > powerpc-linux-ld: unrecognized option '--no-dynamic-linker' > > Caused by

Re: linux-next: build failure after merge of the akpm-current tree

Hello Stephen, Am Donnerstag, 24. November 2016, 16:01:51 BRST schrieb Stephen Rothwell: > Hi Andrew, > > After merging the akpm-current tree, today's linux-next build (powerpc > ppc64_defconfig) failed like this: > > powerpc-linux-ld: unrecognized option '--no-dynamic-linker' > > Caused by

Re: [PATCH] gpio: tegra186: Add support for T186 GPIO

On Thu, Nov 24, 2016 at 12:06:16PM +0530, Laxman Dewangan wrote: > > On Thursday 24 November 2016 01:10 AM, Thierry Reding wrote: > > * PGP Signed by an unknown key > > > > On Wed, Nov 23, 2016 at 02:25:51PM +0100, Linus Walleij wrote: > > > > > > This is already possible and several drivers

Re: [PATCH net-next 1/4] net: mvneta: Convert to be 64 bits compatible

Hi Arnd, On jeu., nov. 24 2016, Arnd Bergmann wrote: > On Thursday, November 24, 2016 4:37:36 PM CET Jisheng Zhang wrote: >> solB (a SW shadow cookie) perhaps gives a better performance: in hot path, >> such as mvneta_rx(), the driver accesses buf_cookie and buf_phys_addr of >>

Re: [PATCH] gpio: tegra186: Add support for T186 GPIO

On Thu, Nov 24, 2016 at 12:06:16PM +0530, Laxman Dewangan wrote: > > On Thursday 24 November 2016 01:10 AM, Thierry Reding wrote: > > * PGP Signed by an unknown key > > > > On Wed, Nov 23, 2016 at 02:25:51PM +0100, Linus Walleij wrote: > > > > > > This is already possible and several drivers

Re: [PATCH net-next 1/4] net: mvneta: Convert to be 64 bits compatible

Hi Arnd, On jeu., nov. 24 2016, Arnd Bergmann wrote: > On Thursday, November 24, 2016 4:37:36 PM CET Jisheng Zhang wrote: >> solB (a SW shadow cookie) perhaps gives a better performance: in hot path, >> such as mvneta_rx(), the driver accesses buf_cookie and buf_phys_addr of >> rx_desc which

Re: [PATCH] gpio: Add Tegra186 support

On Thursday 24 November 2016 08:14 PM, Thierry Reding wrote: * PGP Signed by an unknown key On Thu, Nov 24, 2016 at 12:23:56PM +0530, Laxman Dewangan wrote: On Tuesday 22 November 2016 11:25 PM, Thierry Reding wrote: +static inline struct tegra_gpio *to_tegra_gpio(struct gpio_chip *chip) +{

Re: [PATCH] gpio: Add Tegra186 support

On Thursday 24 November 2016 08:14 PM, Thierry Reding wrote: * PGP Signed by an unknown key On Thu, Nov 24, 2016 at 12:23:56PM +0530, Laxman Dewangan wrote: On Tuesday 22 November 2016 11:25 PM, Thierry Reding wrote: +static inline struct tegra_gpio *to_tegra_gpio(struct gpio_chip *chip) +{

Re: [PATCH 6/10] mmc: sdhci-xenon: Add Marvell Xenon SDHC core functionality

Hi Ulf, On 2016/11/24 21:34, Ulf Hansson wrote: > On 24 November 2016 at 13:41, Ziji Hu wrote: >> Hi Ulf, >> >> On 2016/11/24 18:43, Ulf Hansson wrote: >>> On 31 October 2016 at 12:09, Gregory CLEMENT >>> wrote: From: Ziji Hu

Re: [PATCH 6/10] mmc: sdhci-xenon: Add Marvell Xenon SDHC core functionality

Hi Ulf, On 2016/11/24 21:34, Ulf Hansson wrote: > On 24 November 2016 at 13:41, Ziji Hu wrote: >> Hi Ulf, >> >> On 2016/11/24 18:43, Ulf Hansson wrote: >>> On 31 October 2016 at 12:09, Gregory CLEMENT >>> wrote: From: Ziji Hu >> +static int

[PATCH 4.4 26/31] IB/mlx5: Use cache line size to select CQE stride

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Jurgens commit 16b0e0695a73b68d8ca40288c8f9614ef208917b upstream. When creating kernel CQs use 128B CQE stride if the cache line size is 128B, 64B otherwise. This

[PATCH 4.4 26/31] IB/mlx5: Use cache line size to select CQE stride

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Jurgens commit 16b0e0695a73b68d8ca40288c8f9614ef208917b upstream. When creating kernel CQs use 128B CQE stride if the cache line size is 128B, 64B otherwise. This prevents multiple

[PATCH 4.4 29/31] IB/uverbs: Fix leak of XRC target QPs

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Tariq Toukan commit 5b810a242c28e1d8d64d718cebe75b79d86a0b2d upstream. The real QP is destroyed in case of the ref count reaches zero, but for XRC target QPs this call was

[PATCH 4.4 07/31] i2c: mux: fix up dependencies

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Linus Walleij commit 93d710a65ef02fb7fd48ae207e78f460bd7a6089 upstream. We get the following build error from UM Linux after adding an entry to

[PATCH 4.4 07/31] i2c: mux: fix up dependencies

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Linus Walleij commit 93d710a65ef02fb7fd48ae207e78f460bd7a6089 upstream. We get the following build error from UM Linux after adding an entry to drivers/iio/gyro/Kconfig that issues "select

[PATCH 4.4 29/31] IB/uverbs: Fix leak of XRC target QPs

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Tariq Toukan commit 5b810a242c28e1d8d64d718cebe75b79d86a0b2d upstream. The real QP is destroyed in case of the ref count reaches zero, but for XRC target QPs this call was missed and caused to

[PATCH 4.4 27/31] IB/mlx5: Fix fatal error dispatching

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Eli Cohen commit dbaaff2a2caa03d472b5cc53a3fbfd415c97dc26 upstream. When an internal error condition is detected, make sure to set the device inactive after dispatching the

[PATCH 4.4 27/31] IB/mlx5: Fix fatal error dispatching

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Eli Cohen commit dbaaff2a2caa03d472b5cc53a3fbfd415c97dc26 upstream. When an internal error condition is detected, make sure to set the device inactive after dispatching the event so ULPs can

[PATCH 4.4 09/31] scripts/has-stack-protector: add -fno-PIE

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior commit 82031ea29e454b574bc6f49a33683a693ca5d907 upstream. Adding -no-PIE to the fstack protector check. -no-PIE was introduced before

[PATCH 4.4 28/31] IB/core: Avoid unsigned int overflow in sg_alloc_table

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Mark Bloch commit 3c7ba5760ab8eedec01159b267bb9bfcffe522ac upstream. sg_alloc_table gets unsigned int as parameter while the driver returns it as size_t. Check npages isn't

[PATCH 4.4 09/31] scripts/has-stack-protector: add -fno-PIE

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior commit 82031ea29e454b574bc6f49a33683a693ca5d907 upstream. Adding -no-PIE to the fstack protector check. -no-PIE was introduced before -fstack-protector so there is no

[PATCH 4.4 28/31] IB/core: Avoid unsigned int overflow in sg_alloc_table

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Mark Bloch commit 3c7ba5760ab8eedec01159b267bb9bfcffe522ac upstream. sg_alloc_table gets unsigned int as parameter while the driver returns it as size_t. Check npages isn't greater than

[PATCH 4.4 25/31] IB/mlx4: Fix create CQ error flow

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Matan Barak commit 593ff73bcfdc79f79a8a0df55504f75ad3e5d1a9 upstream. Currently, if ib_copy_to_udata fails, the CQ won't be deleted from the radix tree and the HW (HW2SW).

[PATCH 4.4 25/31] IB/mlx4: Fix create CQ error flow

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Matan Barak commit 593ff73bcfdc79f79a8a0df55504f75ad3e5d1a9 upstream. Currently, if ib_copy_to_udata fails, the CQ won't be deleted from the radix tree and the HW (HW2SW). Fixes: 225c7b1feef1

[PATCH 4.4 05/31] mfd: intel-lpss: Do not put device in reset state on suspend

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Azhar Shaikh commit 274e43edcda6f709aa67e436b3123e45a6270923 upstream. Commit 41a3da2b8e163 ("mfd: intel-lpss: Save register context on suspend") saved the register

[PATCH 4.4 30/31] IB/cm: Mark stale CM ids whenever the mad agent was unregistered

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Mark Bloch commit 9db0ff53cb9b43ed75bacd42a89c1a0ab048b2b0 upstream. When there is a CM id object that has port assigned to it, it means that the cm-id asked for the

[PATCH 4.4 31/31] netfilter: nft_dynset: fix element timeout for HZ != 1000

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Anders K. Pedersen commit a8b1e36d0d1d6f51490e7adce35367ed6adb10e7 upstream. With HZ=100 element timeout in dynamic sets (i.e. flow tables) is 10 times higher than

[PATCH 4.4 23/31] PM / sleep: dont suspend parent when async child suspend_{noirq, late} fails

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Brian Norris commit 6f75c3fd56daf547d684127a7f83c283c3c160d1 upstream. Consider two devices, A and B, where B is a child of A, and B utilizes asynchronous suspend (it

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