[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkda6XuZko8tF0BDYy9NuxSu5rd+b7kcB6ptUUaiv8V_2YQ@mail.gmail.com>
Date: Sat, 17 Aug 2013 02:26:28 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Tomasz Figa <tomasz.figa@...il.com>
Cc: Lars Poeschel <poeschel@...onage.de>,
Lars Poeschel <larsi@....tu-dresden.de>,
Grant Likely <grant.likely@...aro.org>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
Javier Martinez Canillas <javier.martinez@...labora.co.uk>,
Enric Balletbo i Serra <eballetbo@...il.com>,
Jean-Christophe PLAGNIOL-VILLARD <plagnioj@...osoft.com>,
Santosh Shilimkar <santosh.shilimkar@...com>,
Kevin Hilman <khilman@...aro.org>,
Balaji T K <balajitk@...com>,
Tony Lindgren <tony@...mide.com>,
Jon Hunter <jgchunter@...il.com>
Subject: Re: [PATCH v2] RFC: interrupt consistency check for OF GPIO IRQs
On Thu, Aug 15, 2013 at 2:31 PM, Tomasz Figa <tomasz.figa@...il.com> wrote:
> On Thursday 15 of August 2013 14:12:43 Lars Poeschel wrote:
> Well, there are basically no restrictions over the format of GPIO and
> interrupt specifiers. Any driver is free to define its own and provide
> private .xlate() callback to parse it. No assumptions should be made about
> the format, other than each GPIO/interrupt is specified by numer of cells
> specified in #interrupt- or #gpio-cells property of the controller.
Surely we can assume that the binding documents can be trusted?
And for this we only need this:
Documentation/devicetree/bindings/interrupt-controller/interrupts.txt
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