Re: [PATCH 1/3] dt-bindings: Add a binding for the RPi firmware GPIO driver.

2016-09-28 Thread Stephen Warren
On 09/26/2016 12:42 PM, Stefan Wahren wrote: Stephen Warren hat am 26. September 2016 um 18:38 geschrieben: On 09/23/2016 12:39 PM, Stefan Wahren wrote: Hi Eric, Eric Anholt hat am 19. September 2016 um 18:13 geschrieben: The RPi firmware

Re: [PATCH 1/3] dt-bindings: Add a binding for the RPi firmware GPIO driver.

2016-09-28 Thread Stephen Warren
On 09/26/2016 12:42 PM, Stefan Wahren wrote: Stephen Warren hat am 26. September 2016 um 18:38 geschrieben: On 09/23/2016 12:39 PM, Stefan Wahren wrote: Hi Eric, Eric Anholt hat am 19. September 2016 um 18:13 geschrieben: The RPi firmware exposes all of the board's GPIO lines through

Re: [PATCH 1/3] dt-bindings: Add a binding for the RPi firmware GPIO driver.

2016-09-26 Thread Stefan Wahren
> Stephen Warren hat am 26. September 2016 um 18:38 > geschrieben: > > > On 09/23/2016 12:39 PM, Stefan Wahren wrote: > > Hi Eric, > > > >> Eric Anholt hat am 19. September 2016 um 18:13 > >> geschrieben: > >> > >> > >> The RPi firmware exposes all of

Re: [PATCH 1/3] dt-bindings: Add a binding for the RPi firmware GPIO driver.

2016-09-26 Thread Stefan Wahren
> Stephen Warren hat am 26. September 2016 um 18:38 > geschrieben: > > > On 09/23/2016 12:39 PM, Stefan Wahren wrote: > > Hi Eric, > > > >> Eric Anholt hat am 19. September 2016 um 18:13 > >> geschrieben: > >> > >> > >> The RPi firmware exposes all of the board's GPIO lines through > >>

Re: [PATCH 1/3] dt-bindings: Add a binding for the RPi firmware GPIO driver.

2016-09-26 Thread Stephen Warren
On 09/23/2016 07:08 AM, Eric Anholt wrote: Linus Walleij writes: On Mon, Sep 19, 2016 at 6:13 PM, Eric Anholt wrote: The RPi firmware exposes all of the board's GPIO lines through property calls. Linux chooses to control most lines directly

Re: [PATCH 1/3] dt-bindings: Add a binding for the RPi firmware GPIO driver.

2016-09-26 Thread Stephen Warren
On 09/23/2016 07:08 AM, Eric Anholt wrote: Linus Walleij writes: On Mon, Sep 19, 2016 at 6:13 PM, Eric Anholt wrote: The RPi firmware exposes all of the board's GPIO lines through property calls. Linux chooses to control most lines directly through the pinctrl driver, but for the FXL6408

Re: [PATCH 1/3] dt-bindings: Add a binding for the RPi firmware GPIO driver.

2016-09-26 Thread Stephen Warren
On 09/23/2016 12:39 PM, Stefan Wahren wrote: Hi Eric, Eric Anholt hat am 19. September 2016 um 18:13 geschrieben: The RPi firmware exposes all of the board's GPIO lines through property calls. Linux chooses to control most lines directly through the pinctrl driver, but for

Re: [PATCH 1/3] dt-bindings: Add a binding for the RPi firmware GPIO driver.

2016-09-26 Thread Stephen Warren
On 09/23/2016 12:39 PM, Stefan Wahren wrote: Hi Eric, Eric Anholt hat am 19. September 2016 um 18:13 geschrieben: The RPi firmware exposes all of the board's GPIO lines through property calls. Linux chooses to control most lines directly through the pinctrl driver, but for the FXL6408 GPIO

Re: [PATCH 1/3] dt-bindings: Add a binding for the RPi firmware GPIO driver.

2016-09-23 Thread Stefan Wahren
Hi Eric, > Eric Anholt hat am 19. September 2016 um 18:13 geschrieben: > > > The RPi firmware exposes all of the board's GPIO lines through > property calls. Linux chooses to control most lines directly through > the pinctrl driver, but for the FXL6408 GPIO expander on the

Re: [PATCH 1/3] dt-bindings: Add a binding for the RPi firmware GPIO driver.

2016-09-23 Thread Stefan Wahren
Hi Eric, > Eric Anholt hat am 19. September 2016 um 18:13 geschrieben: > > > The RPi firmware exposes all of the board's GPIO lines through > property calls. Linux chooses to control most lines directly through > the pinctrl driver, but for the FXL6408 GPIO expander on the Pi3, we > need to

Re: [PATCH 1/3] dt-bindings: Add a binding for the RPi firmware GPIO driver.

2016-09-23 Thread Linus Walleij
On Fri, Sep 23, 2016 at 3:08 PM, Eric Anholt wrote: > Sort of related: I also worry that we have races with the firmware for > the platform GPIO bits, since both ARM and firmware are doing RMWs (or, > even worse, maybe just Ws?) of the registers controlled by the pinctrl >

Re: [PATCH 1/3] dt-bindings: Add a binding for the RPi firmware GPIO driver.

2016-09-23 Thread Linus Walleij
On Fri, Sep 23, 2016 at 3:08 PM, Eric Anholt wrote: > Sort of related: I also worry that we have races with the firmware for > the platform GPIO bits, since both ARM and firmware are doing RMWs (or, > even worse, maybe just Ws?) of the registers controlled by the pinctrl > driver. Hopefully I

Re: [PATCH 1/3] dt-bindings: Add a binding for the RPi firmware GPIO driver.

2016-09-23 Thread Eric Anholt
Linus Walleij writes: > On Mon, Sep 19, 2016 at 6:13 PM, Eric Anholt wrote: > >> The RPi firmware exposes all of the board's GPIO lines through >> property calls. Linux chooses to control most lines directly through >> the pinctrl driver, but for the

Re: [PATCH 1/3] dt-bindings: Add a binding for the RPi firmware GPIO driver.

2016-09-23 Thread Eric Anholt
Linus Walleij writes: > On Mon, Sep 19, 2016 at 6:13 PM, Eric Anholt wrote: > >> The RPi firmware exposes all of the board's GPIO lines through >> property calls. Linux chooses to control most lines directly through >> the pinctrl driver, but for the FXL6408 GPIO expander on the Pi3, we >>

Re: [PATCH 1/3] dt-bindings: Add a binding for the RPi firmware GPIO driver.

2016-09-23 Thread Linus Walleij
On Mon, Sep 19, 2016 at 6:13 PM, Eric Anholt wrote: > The RPi firmware exposes all of the board's GPIO lines through > property calls. Linux chooses to control most lines directly through > the pinctrl driver, but for the FXL6408 GPIO expander on the Pi3, we > need to access

Re: [PATCH 1/3] dt-bindings: Add a binding for the RPi firmware GPIO driver.

2016-09-23 Thread Linus Walleij
On Mon, Sep 19, 2016 at 6:13 PM, Eric Anholt wrote: > The RPi firmware exposes all of the board's GPIO lines through > property calls. Linux chooses to control most lines directly through > the pinctrl driver, but for the FXL6408 GPIO expander on the Pi3, we > need to access them through the