[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdYUJ3v-DoVbK6Pc6Y833Hn_0KS9PtEpjUCnMr57zfH5Bw@mail.gmail.com>
Date: Sat, 14 Jul 2012 22:16:30 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Tony Lindgren <tony@...mide.com>
Cc: Stephen Warren <swarren@...dotorg.org>,
Stephen Warren <swarren@...dia.com>,
Arnd Bergmann <arnd@...db.de>, linux-kernel@...r.kernel.org,
Rob Herring <rob.herring@...xeda.com>,
Grant Likely <grant.likely@...retlab.ca>,
Olof Johansson <olof@...om.net>, linux-omap@...r.kernel.org,
devicetree-discuss@...ts.ozlabs.org,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] pinctrl: Add one-register-per-pin type device tree based
pinctrl driver
On Tue, Jul 10, 2012 at 11:11 AM, Tony Lindgren <tony@...mide.com> wrote:
> OK so no comments for a while. Here's the patch updated to leave out
> the comments in the binding example.
I reason like this:
- My fears is that the code gets hopeless to understand the mux, the
only way to understand that aspect of the system will be to read the DTS
and have the data sheet ready at hand.
But:
- Tony knows what he's doing and what is best for OMAP. And this gets
(hopefully) all that OMAP mux code out of arch/arm.
- Surely it will be better to go through this subsystem if we're refactoring
it all again later, and all drivers can be transferred to the abstract
pinctrl API which is a big win in itself, bringing coherency to the
drivers/* at large.
So applied it, so it can be evaluated in real operating environments.
But if I don't see OMAP transferred to use this I'll simply delete it
again. :-)
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