From: elder@ieee.org (Alex Elder)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/6] ARM: BCM63XX: add support for BCM63138 SoC
Date: Thu, 13 Mar 2014 16:05:49 -0500 [thread overview]
Message-ID: <53221DAD.4010708@ieee.org> (raw)
In-Reply-To: <CAJiQ=7BrCqo3VijjEvt2JLifM0MNGYmAA+VG_YQbSHfyBqsbtg@mail.gmail.com>
On 03/06/2014 10:44 PM, Kevin Cernekee wrote:
> On Thu, Mar 6, 2014 at 7:41 PM, Alex Elder <elder@ieee.org> wrote:
>>> This patchset adds very minimal support for the BCM63138 SoC which is
>>> a xDSL SoC using a dual Cortex A9 CPU complex.
>>
>>
>> Why do you use "63xx" for the generic name, when the specific
>> part you are defining here is 63138? I would have expected
>> "63xxx".
>
> The product line has a mix of 4-digit and 5-digit part numbers. The
> drivers for onchip peripherals all used "bcm63xx":
That's too bad. I would suggest that one or the other be used
consistently, apparently "63xx" (not 63xxx) would be it.
-Alex
> $ find drivers/ | grep 63xx
> drivers/tty/serial/bcm63xx_uart.c
> drivers/pcmcia/bcm63xx_pcmcia.h
> drivers/pcmcia/bcm63xx_pcmcia.c
> drivers/usb/gadget/bcm63xx_udc.c
> drivers/watchdog/max63xx_wdt.c
> drivers/watchdog/bcm63xx_wdt.c
> drivers/char/hw_random/bcm63xx-rng.c
> drivers/mtd/bcm63xxpart.c
> drivers/net/phy/bcm63xx.c
> drivers/net/ethernet/broadcom/bcm63xx_enet.h
> drivers/net/ethernet/broadcom/bcm63xx_enet.c
> drivers/spi/spi-bcm63xx.c
> drivers/spi/spi-bcm63xx-hsspi.c
>
next prev parent reply other threads:[~2014-03-13 21:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 17:45 [PATCH 0/6] ARM: BCM63XX: add support for BCM63138 SoC Florian Fainelli
2014-03-06 17:45 ` [PATCH 1/6] ARM: BCM63XX: add basic support for the Broadcom BCM63138 DSL SoC Florian Fainelli
2014-03-06 17:45 ` [PATCH 2/6] ARM: restrict BCM_KONA_UART to ARCH_BCM_MOBILE Florian Fainelli
2014-03-07 3:25 ` Tim Kryger
2014-03-14 16:51 ` Matt Porter
2014-03-06 17:45 ` [PATCH 3/6] ARM: BCM63XX: add low-level UART debug support Florian Fainelli
2014-03-06 17:45 ` [PATCH 4/6] ARM: BCM63XX: add BCM63138 minimal Device Tree Florian Fainelli
2014-03-06 17:45 ` [PATCH 5/6] ARM: BCM63XX: add BCM963138DVT Reference platform DTS Florian Fainelli
2014-03-06 17:45 ` [PATCH 6/6] MAINTAINERS: add entry for the Broadcom BCM63xx ARM SoCs Florian Fainelli
2014-03-07 3:41 ` [PATCH 0/6] ARM: BCM63XX: add support for BCM63138 SoC Alex Elder
2014-03-07 4:44 ` Kevin Cernekee
2014-03-13 21:05 ` Alex Elder [this message]
2014-03-11 17:10 ` Florian Fainelli
2014-04-02 19:41 ` Florian Fainelli
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=53221DAD.4010708@ieee.org \
--to=elder@ieee.org \
--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).