[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080924114231.GA8469@oksana.dev.rtsoft.ru>
Date: Wed, 24 Sep 2008 15:42:31 +0400
From: Anton Vorontsov <avorontsov@...mvista.com>
To: Kumar Gala <galak@...nel.crashing.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
David Brownell <dbrownell@...rs.sourceforge.net>,
Greg Kroah-Hartman <greg@...ah.com>,
Timur Tabi <timur@...escale.com>,
Li Yang <leoli@...escale.com>,
Laurent Pinchart <laurentp@...-semaphore.com>,
linuxppc-dev@...abs.org, linux-usb@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/4] powerpc/qe: new call to revert a gpio to a
dedicated function
On Tue, Sep 23, 2008 at 11:07:00PM -0500, Kumar Gala wrote:
>
> On Sep 23, 2008, at 7:03 PM, Anton Vorontsov wrote:
>
>> qe_gpio_set_dedicated() is a platform specific function, which is used
>> to revert a pin to a dedicated function. Caller should have already
>> obtained the gpio via gpio_request().
>>
>> This is needed to support Freescale USB Host Controller.
>>
>> Signed-off-by: Anton Vorontsov <avorontsov@...mvista.com>
>> ---
>> arch/powerpc/include/asm/qe.h | 1 +
>> arch/powerpc/sysdev/qe_lib/gpio.c | 46 ++++++++++++++++++++++++++++
>> +++++++++
>> 2 files changed, 47 insertions(+), 0 deletions(-)
>
> what do you mean by dedicated function.. be a bit clearer in the commit
> log.
This term is from the QE spec, I didn't invent anything. ;-)
"Each pin in the I/O ports can be configured as a general-purpose
I/O signal or as a dedicated peripheral interface signal. ...many
dedicated peripheral functions are multiplexed onto the ports."
> Also, does this depend on gpio_to_chip() patch?
Yeah, the point of exported gpio_to_chip is to let us write
this function.
Thanks!
--
Anton Vorontsov
email: cbouatmailru@...il.com
irc://irc.freenode.net/bd2
--
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