From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Peter Tyser <ptyser@xes-inc.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Grant Likely <grant.likely@secretlab.ca>,
linux-kernel@vger.kernel.org, Alek Du <alek.du@intel.com>,
Samuel Ortiz <sameo@linux.intel.com>,
David Brownell <dbrownell@users.sourceforge.net>,
Eric Miao <eric.y.miao@gmail.com>,
Uwe Kleine-K?nig <u.kleine-koenig@pengutronix.de>,
Joe Perches <joe@perches.com>
Subject: Re: [PATCH 1/3] gpiolib: Add ability to get GPIO pin direction
Date: Tue, 15 Feb 2011 23:55:18 +0000 [thread overview]
Message-ID: <20110215235517.GA2462@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1297726502.965.6921.camel@petert>
On Mon, Feb 14, 2011 at 05:35:02PM -0600, Peter Tyser wrote:
> Also, in most cases I'd think that the BIOS/U-Boot/firmware should have
> configured the GPIO pins appropriately, which Linux should inherit in
> general. Linux currently inherits GPIO states that were set in firmware
> when a GPIO is requested, but it doesn't properly report those values
> via sysfs - that's the only bug I'm trying to fix.
That's one model for these things but it's *far* from universal.
Another model which is at least as common is that the bootloader does
the minimum possible to transfer control to Linux which then does the
actual configuration for the system.
> Are there many cases where people need to swap a pin from GPIO to alt
> functionality, and back again in Linux? I have never seen them used
> like that; generally they are either wired up to an alt_func device (I2C
> pins, serial pins, etc), or as a GPIO - not both dynamically. If some
> hardware does need to do that, isn't it very chipset/board specific? I
No, it's very rare. One example we have in the kernel is the PXA27x
AC'97 driver - the controller doesn't generate one of the resets
correctly so the driver puts the signals into GPIO mode and manually
generates the reset on the bus for the CODEC when it needs to do so.
> guess I'm just not really grasping the big advantage of the alt_func
> feature, or how it'd be implemented as common code. It looks like there
> was a thread about it back in 2009 that didn't go anywhere:
> http://thread.gmane.org/gmane.linux.kernel/851818
I tend to agree; I strongly expect that any alternate function code
would just wind up feeding at best device specific if not system
specific constants through and give us no more generality than we have
now.
next prev parent reply other threads:[~2011-02-15 23:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 19:54 [PATCH 1/3] gpiolib: Add ability to get GPIO pin direction Peter Tyser
2011-01-06 19:54 ` [PATCH 2/3] gpio: pca953x: Implement get_direction() hook Peter Tyser
2011-01-06 23:16 ` David Brownell
2011-01-06 19:54 ` [PATCH 3/3] gpio: Add support for Intel ICHx/3100/Series[56] GPIO Peter Tyser
2011-01-06 23:12 ` David Brownell
2011-02-14 15:48 ` [PATCH 1/3] gpiolib: Add ability to get GPIO pin direction Peter Tyser
2011-02-14 16:02 ` Grant Likely
2011-02-14 19:14 ` Grant Likely
2011-02-14 20:01 ` Peter Tyser
2011-02-14 17:08 ` Alan Cox
2011-02-14 17:26 ` Grant Likely
2011-02-14 17:39 ` Mark Brown
2011-02-14 17:45 ` Peter Tyser
2011-02-14 18:04 ` Grant Likely
2011-02-14 18:46 ` Peter Tyser
2011-02-14 19:35 ` Alan Cox
2011-02-14 23:35 ` Peter Tyser
2011-02-15 11:42 ` Alan Cox
2011-02-15 17:05 ` Peter Tyser
2011-02-15 17:19 ` Alan Cox
2011-02-15 17:49 ` Peter Tyser
2011-02-15 19:41 ` Alan Cox
2011-02-17 8:06 ` Uwe Kleine-König
2011-03-06 7:53 ` Grant Likely
2011-02-15 23:55 ` Mark Brown [this message]
2011-03-06 7:49 ` Grant Likely
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=20110215235517.GA2462@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=alek.du@intel.com \
--cc=dbrownell@users.sourceforge.net \
--cc=eric.y.miao@gmail.com \
--cc=grant.likely@secretlab.ca \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ptyser@xes-inc.com \
--cc=sameo@linux.intel.com \
--cc=u.kleine-koenig@pengutronix.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