On Wed, 6 Feb 2013 10:31:04 +0100, Lars Poeschel wrote:
> On Tuesday 05 February 2013 at 15:29:09, Grant Likely wrote:
> > On Thu, 31 Jan 2013 21:51:36 +0100, Linus Walleij
> wrote:
> > > On Thu, Jan 31, 2013 at 4:58 PM, Lars Poeschel
> wrote:
> > > > --- /dev/null
> > > > +++
On Wed, 6 Feb 2013 10:31:04 +0100, Lars Poeschel poesc...@lemonage.de wrote:
On Tuesday 05 February 2013 at 15:29:09, Grant Likely wrote:
On Thu, 31 Jan 2013 21:51:36 +0100, Linus Walleij
linus.wall...@linaro.org wrote:
On Thu, Jan 31, 2013 at 4:58 PM, Lars Poeschel la...@wh2.tu-dresden.de
On Wed, Feb 6, 2013 at 10:31 AM, Lars Poeschel wrote:
> The thing that confused me was, that the platform_data for the chip has a
> mandatory "base" member, that sets the linux global gpio number at which the
> chip should appear.
Yes this is common. I think you should look at other drivers
On Tuesday 05 February 2013 at 15:29:09, Grant Likely wrote:
> On Thu, 31 Jan 2013 21:51:36 +0100, Linus Walleij
wrote:
> > On Thu, Jan 31, 2013 at 4:58 PM, Lars Poeschel
wrote:
> > > --- /dev/null
> > > +++ b/Documentation/devicetree/bindings/gpio/gpio-mcp23s08.txt
> > > @@ -0,0 +1,27 @@
> >
On Tuesday 05 February 2013 at 15:29:09, Grant Likely wrote:
On Thu, 31 Jan 2013 21:51:36 +0100, Linus Walleij
linus.wall...@linaro.org wrote:
On Thu, Jan 31, 2013 at 4:58 PM, Lars Poeschel la...@wh2.tu-dresden.de
wrote:
--- /dev/null
+++
On Wed, Feb 6, 2013 at 10:31 AM, Lars Poeschel poesc...@lemonage.de wrote:
The thing that confused me was, that the platform_data for the chip has a
mandatory base member, that sets the linux global gpio number at which the
chip should appear.
Yes this is common. I think you should look at
On Thu, 31 Jan 2013 21:51:36 +0100, Linus Walleij
wrote:
> On Thu, Jan 31, 2013 at 4:58 PM, Lars Poeschel
> wrote:
>
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/gpio/gpio-mcp23s08.txt
> > @@ -0,0 +1,27 @@
> > +Microchip MCP2308/MCP23S08/MCP23017/MCP23S17 driver for
> >
On Thu, 31 Jan 2013 21:51:36 +0100, Linus Walleij linus.wall...@linaro.org
wrote:
On Thu, Jan 31, 2013 at 4:58 PM, Lars Poeschel la...@wh2.tu-dresden.de
wrote:
--- /dev/null
+++ b/Documentation/devicetree/bindings/gpio/gpio-mcp23s08.txt
@@ -0,0 +1,27 @@
+Microchip
On Thu, Jan 31, 2013 at 4:58 PM, Lars Poeschel wrote:
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/gpio/gpio-mcp23s08.txt
> @@ -0,0 +1,27 @@
> +Microchip MCP2308/MCP23S08/MCP23017/MCP23S17 driver for
> +8-/16-bit I/O expander with serial interface (I2C/SPI)
> +
> +Required
From: Lars Poeschel
This converts the mcp23s08 driver to be able to be used with device
tree.
There are two properties taken, that correspond to the members of
the struct mcp23s08_platform_data, that is the base member and the
chip array member.
Signed-off-by: Lars Poeschel
---
From: Lars Poeschel poesc...@lemonage.de
This converts the mcp23s08 driver to be able to be used with device
tree.
There are two properties taken, that correspond to the members of
the struct mcp23s08_platform_data, that is the base member and the
chip array member.
Signed-off-by: Lars Poeschel
On Thu, Jan 31, 2013 at 4:58 PM, Lars Poeschel la...@wh2.tu-dresden.de wrote:
--- /dev/null
+++ b/Documentation/devicetree/bindings/gpio/gpio-mcp23s08.txt
@@ -0,0 +1,27 @@
+Microchip MCP2308/MCP23S08/MCP23017/MCP23S17 driver for
+8-/16-bit I/O expander with serial interface (I2C/SPI)
+
12 matches
Mail list logo
