From: Matt Sealey <matt@genesi-usa•com>
To: Kumar Gala <galak@kernel•crashing.org>
Cc: linuxppc-dev@ozlabs•org, Wolfgang Ocker <weo@reccoware•de>
Subject: Re: [PATCH] powerpc: Specify GPIO number base for controller in DT
Date: Thu, 23 Oct 2008 16:35:11 -0500 [thread overview]
Message-ID: <4900EE0F.3090105@genesi-usa.com> (raw)
In-Reply-To: <5535CAC8-11C4-4262-9B18-5F6416A51DE3@kernel.crashing.org>
Kumar Gala wrote:
>
> On Oct 23, 2008, at 7:27 AM, 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.
See my latest mail.
I don't think it's enough to say which pin the GPIOs exposed
start at; you need some sort of mask, or array of applicable
GPIOs so that GPIOLIB can check which perhaps 3 pins out of a
possible 32 are allocated to a controller and usable (these
may be pin 5, pin 9 and pin 20, so a "base" of pin 5 would be
outrageously inadequate).
--
Matt Sealey <matt@genesi-usa•com>
Genesi, Manager, Developer Relations
next prev parent reply other threads:[~2008-10-23 21:35 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 ` Matt Sealey [this message]
2008-10-24 16:10 ` [PATCH] " Wolfgang Ocker
2008-10-24 16:45 ` Anton Vorontsov
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=4900EE0F.3090105@genesi-usa.com \
--to=matt@genesi-usa$(echo .)com \
--cc=galak@kernel$(echo .)crashing.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=weo@reccoware$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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