linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: amery@geeks.cl (Alejandro Mery)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/6] Add pinctrl driver for Allwinner A1X SoCs
Date: Wed, 12 Dec 2012 14:43:08 +0100	[thread overview]
Message-ID: <50C889EC.3020308@geeks.cl> (raw)
In-Reply-To: <50C8879E.5070401@free-electrons.com>

On 12/12/12 14:33, Maxime Ripard wrote:
> Le 12/12/2012 13:49, Alejandro Mery a ?crit :
>> On 12/12/12 10:11, Maxime Ripard wrote:
>>> Hi Alejandro,
>>>
>>> Le 11/12/2012 22:58, Alejandro Mery a ?crit :
>>>> On 10/12/12 23:08, Maxime Ripard wrote:
>>>>> Hi everyone,
>>>>>
>>>>> This patch set adds a pinctrl driver for the IP found in the Allwinner
>>>>> A10
>>>>> and A13, and the SoC-specific bits for the A13. It also adds the
>>>>> documentation
>>>>> for the device tree bindings.
>>>>
>>>> Hi. I just wanted to comment that there are 3 known sun5i SoCs, not only
>>>> the A13. The A10s and the A12 are also sun5i. For A10s and A13 there are
>>>> datasheets available with the pin info. So please don't assume the A13's
>>>> pins are "sun5i" pins, they are merely aw1626 (aka A13) pins.
>>>
>>> Ok, I will change the naming scheme to something like sun5i-a13. For the
>>> other SoC codenames like sun4i, are you aware of several actual SoCs
>>> using the same codename, or do we have only sun4i == A10?
>>
>> the A10 is the only sun4i we know of, the A31 is the only sun6i we know
>> of, and the A20 is the only sun7i we know of... they'll soon run out of
>> numbers... :|
>>
>> Also, to avoid confusions with their poorly chosen marketing name, you
>> could use the internal chip name aw1623 for the A10 and aw1626 for the
>> A13 instead. This value can be read from the BROM and it's commonly used
>> in allwinner sources.
>
> In what aspect are they poorly named? I'd really like to keep it as
> understandable as possible, at least in the device tree.
>
> I guess renaming the sun5i dtsi already there and all that relates to
> the A13 to sun5i-a13 would remove that collision of names, don't you
> think? Or am I missing something?

fine with me, but "The A10 is an A8, same as the A10s and A13, but the 
A13 is less than the A10 but larger and A10s is not the plural of A10. 
And the A20 been like an A10 but A7" doesn't make you dizzy? ;-)

sure prefixing the marketing name with sunxi- or sunNi- removes the 
ambiguity.

cheers,
Alejandro Mery

      reply	other threads:[~2012-12-12 13:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-10 22:08 [PATCH 0/6] Add pinctrl driver for Allwinner A1X SoCs Maxime Ripard
2012-12-10 22:08 ` [PATCH 1/6] ARM: sunxi: Add pinctrl driver for Allwinner SoCs Maxime Ripard
2012-12-11  0:28   ` Linus Walleij
2012-12-11 18:30     ` Maxime Ripard
2012-12-10 22:08 ` [PATCH 2/6] ARM: pinctrl: sunxi: Add the pinctrl pin set for sun5i Maxime Ripard
2012-12-10 22:08 ` [PATCH 3/6] ARM: sunxi: Add pinctrl node to the device tree Maxime Ripard
2012-12-10 22:08 ` [PATCH 4/6] ARM: sunxi: Add uart1 pinctrl groups Maxime Ripard
2012-12-10 22:08 ` [PATCH 5/6] tty: of_serial: Add pinctrl support Maxime Ripard
2012-12-10 22:08 ` [PATCH 6/6] ARM: sunxi: olinuxino: Add muxing for the uart Maxime Ripard
2012-12-11 21:58 ` [PATCH 0/6] Add pinctrl driver for Allwinner A1X SoCs Alejandro Mery
2012-12-12  9:11   ` Maxime Ripard
2012-12-12 12:49     ` Alejandro Mery
2012-12-12 13:33       ` Maxime Ripard
2012-12-12 13:43         ` Alejandro Mery [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=50C889EC.3020308@geeks.cl \
    --to=amery@geeks.cl \
    --cc=linux-arm-kernel@lists.infradead.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).