From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] efikamx: Configure the pins as GPIOs prior to using gpio_get_value.
Date: Wed, 23 Nov 2011 14:44:31 -0500 [thread overview]
Message-ID: <201111231444.32309.vapier@gentoo.org> (raw)
In-Reply-To: <4ECCACA4.5040701@denx.de>
On Wednesday 23 November 2011 03:19:48 Stefano Babic wrote:
> On 22/11/2011 22:07, Mike Frysinger wrote:
> > if it's different physical pins, then perhaps it should be
> > different GPIO numbers ?
>
> No, they are not. Depending on the "daisy chain" functionality and
> based on different alternate function, a single GPIO can be routed to
> different physical pins.
the GPIO # can represent the AF as well as the GPIO itself. this is what bit
shifts and masks are good at.
there's no requirement that the GPIO #'s be contiguous, or have a specific
range.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20111123/1dbc8083/attachment.pgp>
prev parent reply other threads:[~2011-11-23 19:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-21 14:09 [U-Boot] [PATCH 1/2] efikamx: Configure the pins as GPIOs prior to using gpio_get_value Fabio Estevam
2011-11-21 14:09 ` [U-Boot] [PATCH 2/2] vision2: " Fabio Estevam
2011-11-21 14:20 ` [U-Boot] [PATCH 1/2] efikamx: " Marek Vasut
2011-11-21 18:53 ` Mike Frysinger
2011-11-21 19:29 ` Marek Vasut
2011-11-21 20:14 ` Mike Frysinger
2011-11-21 20:53 ` Marek Vasut
2011-11-21 21:22 ` Mike Frysinger
2011-11-22 8:15 ` Stefano Babic
2011-11-22 21:07 ` Mike Frysinger
2011-11-23 7:02 ` Igor Grinberg
2011-11-23 19:43 ` Mike Frysinger
2011-11-23 8:19 ` Stefano Babic
2011-11-23 19:44 ` Mike Frysinger [this message]
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=201111231444.32309.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.