From: Stefano Babic <sbabic@denx.de>
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 09:19:48 +0100 [thread overview]
Message-ID: <4ECCACA4.5040701@denx.de> (raw)
In-Reply-To: <201111221607.09360.vapier@gentoo.org>
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.
> this is shaking out in Linux with the pinmux framework, so probably
> best to grit our teeth until that's done and then adopt what they
> implement.
Agree.
Best regards,
Stefano Babic
--
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================
next prev parent reply other threads:[~2011-11-23 8:19 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 [this message]
2011-11-23 19:44 ` Mike Frysinger
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=4ECCACA4.5040701@denx.de \
--to=sbabic@denx.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox