From: Kumar Gala <galak@kernel.crashing.org>
To: avorontsov@ru.mvista.com
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH v2] powerpc: implement support for MPC8349-compatible SOC GPIOs
Date: Fri, 19 Sep 2008 13:02:11 -0500 [thread overview]
Message-ID: <1BA571BA-BA43-4C18-9CBF-0F1461E6734E@kernel.crashing.org> (raw)
In-Reply-To: <20080919153325.GA548@oksana.dev.rtsoft.ru>
On Sep 19, 2008, at 10:33 AM, Anton Vorontsov wrote:
> On Fri, Sep 19, 2008 at 05:11:15PM +0200, Peter Korsgaard wrote:
>>>>>>> "Anton" == Anton Vorontsov <avorontsov@ru.mvista.com> writes:
>>
>> Hi,
>>
>>>> It seems basically the same as my patch (gpio driver for
>>>> mpc831x/mpc834x/mpc837x with OF bindings) from September 5th except
>>>> you don't have any documentation
>>
>> Anton> Well, do we really need documentation for every trivial gpio
>> Anton> controller? The bindings are the same, only different
>> compatible
>> Anton> entries...
>>
>> Well, we need some way of knowing that atleast. Having people
>> grepping
>> through arch/powerpc/boot/dts/ (and knowing that they should look for
>> 8349 even though they might use 8313 or 8610) doesn't seem optimal to
>> me - I take it that's why we created
>> Documentation/powerpc/dts-bindings in the first place?
>
> Ok.
>
>> Anton> If we do need the documentation for this, I can readily
>> include it.
>>
>>>> and the Kconfig doesn't depend on
>>>> 831x/834x/837x.
>>
>> Anton> This is purposely. We also need support for 8610, and maybe
>> Anton> later we'll find another chip with the same unit. So, to not
>> touch
>> Anton> the Kconfig for every new chip I just made it PPC32-wide.
>> Other
>> Anton> option is to depend on FSL_SOC, but the driver really does not
>> Anton> depend on any fsl_soc stuff...
>>
>> Adding another symbol to the Kconfig once it is verified that a new
>> SoC is compatible doesn't seem like a big deal - Figuring out all the
>> knobs we already have is, without having options for stuff that is
>> known to be irrelevant for the SoC.
>>
>> The other 83xx specific drivers also depend on PPC_83xx.
>
> Lets wait for Kumar's comments. We've already had a PPC_* mess
> for the USB_EHCI_FSL symbol. What I've learned from it, is that
> huge PPC_* list isn't perfect either.
I've alone glanced over this, but some initial comments are.. lets
rename the thing to not be 83xx specific since 8610 uses it and I'm
sure we'll have other parts that do similar things.
With regards to the binding, lets make it generic like 'fsl,mpc8xxx-
gpio", "fsl,CHIP-gpio" and than we can use cpm1/cpm2/pq1/pq2 as
prefixes to distinguish and major differences.
- k
next prev parent reply other threads:[~2008-09-19 18:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-17 17:58 [PATCH v2] powerpc: implement support for MPC8349-compatible SOC GPIOs Anton Vorontsov
2008-09-17 19:30 ` Peter Korsgaard
2008-09-18 11:20 ` Anton Vorontsov
2008-09-19 15:11 ` Peter Korsgaard
2008-09-19 15:33 ` Anton Vorontsov
2008-09-19 18:02 ` Kumar Gala [this message]
2008-09-19 18:12 ` Anton Vorontsov
2008-09-19 18:46 ` Kumar Gala
2008-09-21 19:30 ` Peter Korsgaard
2008-09-25 16:41 ` Scott Wood
2008-09-25 16:43 ` Scott Wood
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=1BA571BA-BA43-4C18-9CBF-0F1461E6734E@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=avorontsov@ru.mvista.com \
--cc=linuxppc-dev@ozlabs.org \
/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).