[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkda=OLMXTOCowsv1CKxj5wXE_kOzM8YLBNLhTPh4dQ5e-A@mail.gmail.com>
Date: Sat, 17 Aug 2013 02:02:11 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Lars Poeschel <larsi@....tu-dresden.de>
Cc: Lars Poeschel <poeschel@...onage.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
Hi Lars,
On Tue, Aug 13, 2013 at 11:46 AM, Lars Poeschel <larsi@....tu-dresden.de> wrote:
> From: Linus Walleij <linus.walleij@...aro.org>
>
> Currently the kernel is ambigously treating GPIOs and interrupts
> from a GPIO controller: GPIOs and interrupts are treated as
> orthogonal. This unfortunately makes it unclear how to actually
> retrieve and request a GPIO line or interrupt from a GPIO
> controller in the device tree probe path.
I took the liberty to take your tweaked V2 version of my patch,
tweak it a bit more (addressing some of Tomasz comments)
and re-submit, along with two patches making it do the trick
on my Nomadik test-system.
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