From: Anton Vorontsov <avorontsov@ru.mvista.com>
To: Wolfgang Ocker <weo@reccoware.de>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] powerpc: Specify GPIO number base for controller in DT
Date: Fri, 24 Oct 2008 20:45:40 +0400 [thread overview]
Message-ID: <20081024164540.GB14350@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <1224764850.4082.54.camel@galileo.recco.de>
On Thu, Oct 23, 2008 at 02:27:30PM +0200, Wolfgang Ocker wrote:
> The GPIOLIB allows the specification of a base gpio number for a
> controller. That is not possible using OF. Instead, free gpio numbers
> are assigned.
>
> In order to allow static, predefined gpio numbers, a base property in
> the gpio controller node specifies the first gpio number.
>
> Signed-off-by: Wolfgang Ocker <weo@reccoware.de>
[...]
> --- linux-2.6.27-rc7/Documentation/powerpc/booting-without-of.txt.spi_gpio_doc 2008-09-29 14:14:08.000000000 +0200
> +++ linux-2.6.27-rc7/Documentation/powerpc/booting-without-of.txt 2008-09-29 14:24:26.000000000 +0200
> @@ -2586,6 +2588,7 @@
> #gpio-cells = <2>;
> compatible = "fsl,qe-pario-bank-a", "fsl,qe-pario-bank";
> reg = <0x1400 0x18>;
> + base = < 0x20 >;
The base has nothing to do with the hardware description, thus
device tree should not include it. Why exactly you need this?
I'm sure there is another way to solve the problem (whatever it
is).
--
Anton Vorontsov
email: cbouatmailru@gmail.com
irc://irc.freenode.net/bd2
prev parent reply other threads:[~2008-10-24 16:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-23 12:27 [PATCH] powerpc: Specify GPIO number base for controller in DT Wolfgang Ocker
2008-10-23 14:18 ` Kumar Gala
2008-10-23 14:30 ` [PATCH v2] " Wolfgang Ocker
2008-10-23 14:40 ` Kumar Gala
2008-10-23 14:49 ` [PATCH v3] " Wolfgang Ocker
2008-10-23 18:13 ` Stefan Roese
2008-10-24 16:54 ` Anton Vorontsov
2008-10-24 17:12 ` Grant Likely
2008-10-24 18:00 ` Wolfgang Ocker
2008-10-23 21:35 ` [PATCH] " Matt Sealey
2008-10-24 16:10 ` Wolfgang Ocker
2008-10-24 16:45 ` Anton Vorontsov [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=20081024164540.GB14350@oksana.dev.rtsoft.ru \
--to=avorontsov@ru.mvista.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=weo@reccoware.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).