[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <AANLkTikpRcqPJay-7zjDiZg3w=+gUk3kks=payPazxxj@mail.gmail.com>
Date: Mon, 30 Aug 2010 11:54:41 -0600
From: Grant Likely <grant.likely@...retlab.ca>
To: David Brownell <david-b@...bell.net>
Cc: linux-kernel@...r.kernel.org,
MyungJoo Ham <myungjoo.ham@...sung.com>,
Kyungmin Park <kyungmin.park@...sung.com>,
David Brownell <dbrownell@...rs.sourceforge.net>,
Andrew Morton <akpm@...ux-foundation.org>,
Jani Nikula <ext-jani.1.nikula@...ia.com>,
Greg Kroah-Hartman <gregkh@...e.de>,
MyungJoo Ham <myungjoo.ham@...il.com>
Subject: Re: [RFC PATCH] GPIO: add control of powerdown modes and pull-up/down configurations.
On Mon, Aug 30, 2010 at 11:35 AM, David Brownell <david-b@...bell.net> wrote:
>
>
> --- On Mon, 8/30/10, MyungJoo Ham <myungjoo.ham@...sung.com> wrote:
>
>> From: MyungJoo Ham <myungjoo.ham@...sung.com>
>> Subject: [RFC PATCH] GPIO: add control of powerdown modes and pull-up/down configurations.
>
> NAK.
Seconded. I completely agree with David's comments.
g.
>
> Note that Documentation/gpio.txt specifies such
> pinmux/configuration as out of scope. There isn't
> even uniformity of models about such things between
> SOCs (and ASICs etc).
>
> Put these kinds of things in arch-specific code,
> which has good reason to know about all the ways
> each platform differs from others, and to cope.
>
> Look at OMAP and AT91 for some examples of SOCs
> which have addressed these issues cleanly, and
> without committing mayhem on the GPIO framework.
>
>
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
--
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