[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20121030184828.GB4804@arwen.pp.htv.fi>
Date: Tue, 30 Oct 2012 20:48:28 +0200
From: Felipe Balbi <balbi@...com>
To: Dmitry Torokhov <dmitry.torokhov@...il.com>
CC: Felipe Balbi <balbi@...com>,
Mark Brown <broonie@...nsource.wolfsonmicro.com>,
Linus Walleij <linus.walleij@...aro.org>,
Benoit Cousson <b-cousson@...com>,
Sourav Poddar <sourav.poddar@...com>, <tony@...mide.com>,
<linux-omap@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<devicetree-discuss@...ts.ozlabs.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-input@...r.kernel.org>
Subject: Re: [PATCHv2] Input: omap4-keypad: Add pinctrl support
Hi,
On Tue, Oct 30, 2012 at 11:20:07AM -0700, Dmitry Torokhov wrote:
> On Tue, Oct 30, 2012 at 07:25:13PM +0200, Felipe Balbi wrote:
> > On Tue, Oct 30, 2012 at 03:58:21PM +0000, Mark Brown wrote:
> > >
> > > But then this comes round to the mindless code that ought to be factored
> > > out :) Only the more interesting cases that do something unusual really
> > > register here.
> >
> > fair enough. I see your point. Not saying I agree though, just that this
> > discussion has been flying for far too long, so feel free to provide
> > patches implementing what you're defending here ;-)
> >
> > Guess code will speak for itself. On way or another, we need OMAP keypad
> > driver working in mainline
>
> Are you saying that introducing pincrtl infrastructure actually _broke_
> the driver in mainline?
no dude, I'm saying we need pinctrl working for this driver because we
need to remove OMAP-specific MUX settings. One way or another, this has
to work.
--
balbi
Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)
Powered by blists - more mailing lists