[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkda_HjzWNMD1H_a_fsWtbRWuTDsutS8kndb9jY31qf7Yyg@mail.gmail.com>
Date: Thu, 31 Jan 2013 21:51:36 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: Lars Poeschel <larsi@....tu-dresden.de>
Cc: poeschel@...onage.de, grant.likely@...retlab.ca,
rob.herring@...xeda.com, rob@...dley.net,
devicetree-discuss@...ts.ozlabs.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org,
spi-devel-general@...ts.sourceforge.net, w.sang@...gutronix.de,
ben-linux@...ff.org, linux-i2c@...r.kernel.org
Subject: Re: [PATCH RFC 1/1] gpio: mcp23s08: convert driver to DT
On Thu, Jan 31, 2013 at 4:58 PM, Lars Poeschel <larsi@....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)
> +
> +Required properties:
> +- compatible : Should be "mcp,mcp23s08-gpio", "mcp,mcp23s17-gpio",
> + "mcp,mcp23008-gpio" or "mcp,mcp23017-gpio"
> +- base : The first gpio number that should be assigned by this chip.
No. We do not tie the global GPIO numbers into the device tree.
In the DT GPIOs are referenced by ampersand <&gpio0 1 2>
notation referring to the instance, so as you realize DT itself
has no need for that number.
Further it is not OS-neutral.
You have to find another way to handle this in the driver code.
In worst case: use AUXDATA.
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists