From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Sascha Hauer" <s.hauer@pengutronix.de>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] add gpiolib support for mpc5200
Date: Fri, 25 Apr 2008 13:30:49 -0600 [thread overview]
Message-ID: <fa686aa40804251230w3306ece2x1a10d06e3a83ed45@mail.gmail.com> (raw)
In-Reply-To: <20080425185141.GA17951@pengutronix.de>
On Fri, Apr 25, 2008 at 12:51 PM, Sascha Hauer <s.hauer@pengutronix.de> wrote:
> On Fri, Apr 25, 2008 at 04:30:55PM +0100, Matt Sealey wrote:
> > Can I make a suggestion for this chip support?
> >
> > On certain 5200 boards these devices are not usable since they are not
> > connected. My concern is the Efika where we only have 2 wakeup and 1 simple
> > GPIO available on the board and maybe a few others with a bit of tweaking
> > and messing around.
>
> This is probably true for most boards.
> I haven't tested if this is true for all gpios, but the peripheral usage
> settings seem to take precedence over the gpio settings. So at least you
> can play with already for peripheral claimed gpios without bad things
> happening. But ok, seems to be a bad idea to rely on this.
There must also be some level of assumption that the device tree data
is accurate. If a pin is specified that is not enabled as a GPIO pin,
then it's not going to work.
Cheers,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2008-04-25 19:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-24 15:36 [PATCH] add gpiolib support for mpc5200 Sascha Hauer
2008-04-24 18:45 ` Grant Likely
2008-04-25 10:53 ` Sascha Hauer
2008-04-25 12:32 ` Anton Vorontsov
2008-04-25 15:30 ` Matt Sealey
2008-04-25 18:51 ` Sascha Hauer
2008-04-25 19:30 ` Grant Likely [this message]
2008-04-24 19:11 ` Grant Likely
2008-04-25 8:22 ` Stephen Rothwell
2008-04-25 10:56 ` Sascha Hauer
2008-04-25 13:07 ` Anton Vorontsov
2008-04-25 13:42 ` Sascha Hauer
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=fa686aa40804251230w3306ece2x1a10d06e3a83ed45@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=linuxppc-dev@ozlabs.org \
--cc=s.hauer@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;
as well as URLs for NNTP newsgroup(s).