From: David Brownell <david-b@pacbell.net>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 00/05] sh: GPIO for SuperH using gpiolib
Date: Mon, 20 Oct 2008 04:30:23 +0000 [thread overview]
Message-ID: <200810192130.24189.david-b@pacbell.net> (raw)
In-Reply-To: <20080927181008.11246.53495.sendpatchset@rx1.opensource.se>
On Saturday 27 September 2008, Magnus Damm wrote:
> The pinmux code is written so multiple GPIOs map to one physical pin.
> So for example on sh7723, pin PTS5 can be accessed as regular Port S pin 5
> GPIO, but it can also be locked to two different functions - as TX pin of
> the SCIF1 serial port or as SDHI0D3 - a D3 pin on the first MMC interface.
I've lost track of the status of these patches, but as a terminology
point I think it's best to keep in mind that those alternate functions
are not what's called a "GPIO". The GPIO framework only expects to
handle the first function -- "GPIO".
> This specific PTS5 pin is exported as 3 different GPIOs:
> GPIO_PTS5
> GPIO_FN_SCIF1_PTS_TXD
> GPIO_FN_SDHI0D3_PTS
> Only one at a time can be selected using gpio_request().
>
next prev parent reply other threads:[~2008-10-20 4:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-27 18:10 [PATCH 00/05] sh: GPIO for SuperH using gpiolib Magnus Damm
2008-09-29 11:44 ` Paul Mundt
2008-10-20 4:30 ` David Brownell [this message]
2008-10-20 4:32 ` David Brownell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200810192130.24189.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=linux-sh@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox