From: cavokz@gmail.com (Domenico Andreoli)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 2/5] ARM: bcm4760: Add platform infrastructure
Date: Tue, 10 Sep 2013 18:16:34 +0200 [thread overview]
Message-ID: <20130910161633.GA7655@glitch> (raw)
In-Reply-To: <CAOesGMh=jdTacefrEo8pcwAOggqmOypz3dZuORdHJS9F2vKjcQ@mail.gmail.com>
On Fri, Aug 30, 2013 at 02:58:58PM -0700, Olof Johansson wrote:
> On Fri, Aug 30, 2013 at 2:52 PM, Christian Daudt <csd@broadcom.com> wrote:
> > On 13-08-30 12:53 AM, Domenico Andreoli wrote:
> >>>>
> >>>> Index: b/arch/arm/mach-bcm/Kconfig
> >>>> ===================================================================
> >>>> --- a/arch/arm/mach-bcm/Kconfig
> >>>> +++ b/arch/arm/mach-bcm/Kconfig
> >>>> @@ -17,3 +17,10 @@ config ARCH_BCM
> >>>> It currently supports the 'BCM281XX' family, which includes
> >>>> BCM11130, BCM11140, BCM11351, BCM28145 and
> >>>> BCM28155 variants.
> >>>> +
> >>>> +config ARCH_BCM4760
> >>>> + bool "Broadcom BCM4760 based SoCs (ARM11)" if ARCH_MULTI_V6
> >>>> + select ARM_AMBA
> >>>> + select ARM_VIC
> >>>> + select CLKSRC_OF
> >>>> + select SOC_BUS
> >>>
> >>> So I think I mentioned this during previous discussions, but I think this
> >>> should be solved by having:
> >>>
> >>> config ARCH_BCM
> >>> bool "Broadcom platforms"
> >>> help
> >>> This enables support for Broadcom based systems
> >>>
> >>> menu "Broadcom platform selection"
> >>> depends on ARCH_BCM
> >>>
> >>> config ARCH_BCM281XX
> >>> ... current ARCH_BCM contents
> >>>
> >>> config ARCH_BCM4760
> >>> ... above conents
> >>> endmenu
> >>
> >> got it.
> >>
> >> need to sync with Christian, the current owner of ARCH_BCM.
> >
> > This is fine, but it is better to name it MOBILEBCM instead for our
> > platform, as it plan to keep it single zImage. My plan was to switch the
> > current usage of ARCH_BCM for chips to ARCH_MOBILEBCM, and then leave
> > ARCH_BCM as a generic BCM menu option as above. I can send a patch to that
> > effect if everyone is okay with that.
>
> Sounds good. Let's do that for 2.13.
Christian, can I assume you will prepare a patch to rename ARCH_BCM or do
you prefer I include it my series, maybe simplifying the merge of it? I'm
fine with both.
Regards,
Domenico
next prev parent reply other threads:[~2013-09-10 16:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-14 22:10 [PATCH v3 0/5] ARM: Broadcom BCM4760 support Domenico Andreoli
2013-08-14 22:10 ` [PATCH v3 1/5] ARM: remove duplicates in mach-* and plat-* Domenico Andreoli
2013-08-14 22:10 ` [PATCH v3 2/5] ARM: bcm4760: Add platform infrastructure Domenico Andreoli
2013-08-15 13:28 ` Jason Cooper
2013-08-29 23:17 ` Olof Johansson
2013-08-30 7:53 ` Domenico Andreoli
2013-08-30 21:52 ` Christian Daudt
2013-08-30 21:58 ` Olof Johansson
2013-09-10 16:16 ` Domenico Andreoli [this message]
2013-09-13 23:16 ` Christian Daudt
2013-08-14 22:10 ` [PATCH v3 3/5] ARM: bcm4760: Add system timer Domenico Andreoli
2013-08-15 0:30 ` Stephen Boyd
2013-08-15 6:32 ` Domenico Andreoli
2013-08-29 23:20 ` Olof Johansson
2013-08-29 23:21 ` Olof Johansson
2013-08-30 7:54 ` Domenico Andreoli
2013-08-14 22:10 ` [PATCH v3 4/5] ARM: bcm4760: Add ripple counter Domenico Andreoli
2013-08-14 22:10 ` [PATCH v3 5/5] ARM: bcm4760: Add restart hook Domenico Andreoli
2013-08-29 23:36 ` Olof Johansson
2013-08-30 8:01 ` Domenico Andreoli
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=20130910161633.GA7655@glitch \
--to=cavokz@gmail.com \
--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).