[PATCH] i2c: pca954x: improve usage of gpiod API

2015-02-17 Thread Uwe Kleine-König
Since 39b2bbe3d715 (gpio: add flags argument to gpiod_get*() functions) which appeared in v3.17-rc1, the gpiod_get* functions take an additional parameter that allows to specify direction and initial value for outputs. Also there is an *_optional variant that serves well here. The sematics is sli

ARM: shmobile: koelsch: da9210/da9063 interrupt storm (was: Re: [PATCH 3/4] ARM: shmobile: koelsch: Add DA9063 PMIC device node for system restart)

2015-02-17 Thread Geert Uytterhoeven
On Mon, Dec 22, 2014 at 2:21 PM, Geert Uytterhoeven wrote: > On Sun, Dec 21, 2014 at 11:52 AM, Simon Horman wrote: >> On Tue, Dec 09, 2014 at 12:22:48PM +0100, Geert Uytterhoeven wrote: >>> Add a minimal device node for the DA9063 PMIC, which is connected to i2c6. >>> This allows the system to be

Re: ARM: shmobile: koelsch: da9210/da9063 interrupt storm (was: Re: [PATCH 3/4] ARM: shmobile: koelsch: Add DA9063 PMIC device node for system restart)

2015-02-17 Thread Mark Brown
On Tue, Feb 17, 2015 at 01:05:07PM +0100, Geert Uytterhoeven wrote: > However, as soon as the da9210 driver will get interrupt support (I wrote > something, based on the da9211 driver) and the da9210 will have an interrupts > property in DTS, the interrupt storm will reappear, irrespectively of th

Re: linux-next: Tree for Feb 17 (i2c-designware-baytrail.c)

2015-02-17 Thread Randy Dunlap
On 02/16/15 21:02, Stephen Rothwell wrote: > Hi all, > > Please do not add any material destined for v3.21 to your linux-next > included trees until after v3.20-rc1 has been released. > > Changes since 20150216: > on i386, when CONFIG_IOSF_MBI=m and CONFIG_I2C_DESIGNWARE_BAYTRAIL=y: drivers/bu

[PATCH 7/8] ARM: dts: dove: Add internal i2c multiplexer node

2015-02-17 Thread Sebastian Hesselbarth
This adds a i2c-mux-pinctrl node to dove.dtsi for the internal i2c mux found on Dove SoCs. Up to now, we had no board using any of the two additional i2c busses, so make sure the change does not break any existing boards. Therefore, we rename the i2c-controller node label to "i2c" and enable it by

[PATCH 0/8] Add proper support for Compulab CM-A510/SBC-A510

2015-02-17 Thread Sebastian Hesselbarth
This patch set improves current mainline support for the Compulab CM-A510 System-on-Module (SoM) and its default Compulab SBC-A510 base board. Thanks to Gabriel Dobato who agreed to remote debug and test the provided DT changes. On the way to proper support, we - Rework i2c-mux-pinctrl to honor di

[PATCH 1/8] i2c: mux-pinctrl: Rework to honor disabled child nodes

2015-02-17 Thread Sebastian Hesselbarth
I2C mux pinctrl driver currently determines the number of sub-busses by counting available pinctrl-names. Unfortunately, this requires each incarnation of the devicetree node with different available sub-busses to be rewritten. This patch reworks i2c-mux-pinctrl driver to count the number of avail

Re: linux-next: Tree for Feb 17 (i2c-designware-baytrail.c)

2015-02-17 Thread Wolfram Sang
Randy, thanks for the report! > I suppose someone could make that: > > depends on I2C_DESIGNWARE_PLATFORM && IOSF_MBI=y && ACPI > > or even make I2C_DESIGNWARE_BAYTRAIL be a tristate symbol. I'll wait a day for input from David what he prefers, because I don't own/know this platform. If

Re: [PATCH] i2c: pca954x: improve usage of gpiod API

2015-02-17 Thread Laurent Pinchart
Hi Uwe, Thank you for the patch. On Tuesday 17 February 2015 10:12:08 Uwe Kleine-König wrote: > Since 39b2bbe3d715 (gpio: add flags argument to gpiod_get*() functions) > which appeared in v3.17-rc1, the gpiod_get* functions take an additional > parameter that allows to specify direction and initi

Re: [PATCH 1/8] i2c: mux-pinctrl: Rework to honor disabled child nodes

2015-02-17 Thread Stephen Warren
On 02/17/2015 11:52 AM, Sebastian Hesselbarth wrote: I2C mux pinctrl driver currently determines the number of sub-busses by counting available pinctrl-names. Unfortunately, this requires each incarnation of the devicetree node with different available sub-busses to be rewritten. Can you be mor

Re: linux-next: Tree for Feb 17 (i2c-designware-baytrail.c)

2015-02-17 Thread David E. Box
Hi Wolfram, On Tue, Feb 17, 2015 at 08:11:58PM +0100, Wolfram Sang wrote: > Randy, > > thanks for the report! > > > I suppose someone could make that: > > > > depends on I2C_DESIGNWARE_PLATFORM && IOSF_MBI=y && ACPI > > > > or even make I2C_DESIGNWARE_BAYTRAIL be a tristate symbol. > > I'

Re: [PATCH 1/8] i2c: mux-pinctrl: Rework to honor disabled child nodes

2015-02-17 Thread Sebastian Hesselbarth
On 17.02.2015 21:46, Stephen Warren wrote: On 02/17/2015 11:52 AM, Sebastian Hesselbarth wrote: I2C mux pinctrl driver currently determines the number of sub-busses by counting available pinctrl-names. Unfortunately, this requires each incarnation of the devicetree node with different available

Re: [PATCH 1/8] i2c: mux-pinctrl: Rework to honor disabled child nodes

2015-02-17 Thread Stephen Warren
On 02/17/2015 02:08 PM, Sebastian Hesselbarth wrote: On 17.02.2015 21:46, Stephen Warren wrote: On 02/17/2015 11:52 AM, Sebastian Hesselbarth wrote: I2C mux pinctrl driver currently determines the number of sub-busses by counting available pinctrl-names. Unfortunately, this requires each incarn

Re: [PATCH 1/8] i2c: mux-pinctrl: Rework to honor disabled child nodes

2015-02-17 Thread Sebastian Hesselbarth
On 17.02.2015 22:15, Stephen Warren wrote: On 02/17/2015 02:08 PM, Sebastian Hesselbarth wrote: On 17.02.2015 21:46, Stephen Warren wrote: Can you be more explicit about the problem here? Why does anything need to be re-written if a child node is disabled; presumably there's no need for the chi