From: Catalin Marinas <catalin.marinas@arm.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
Eric Anholt <eric@anholt.net>, Will Deacon <will.deacon@arm.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 4/9] arm64: Add platform selection for BCM2835.
Date: Fri, 3 Jun 2016 12:27:21 +0100 [thread overview]
Message-ID: <20160603112721.GC1128@e104818-lin.cambridge.arm.com> (raw)
In-Reply-To: <1464934708-24769-5-git-send-email-kraxel@redhat.com>
On Fri, Jun 03, 2016 at 08:18:23AM +0200, Gerd Hoffmann wrote:
> diff --git a/arch/arm64/Kconfig.platforms b/arch/arm64/Kconfig.platforms
> index 7ef1d05..ea88402 100644
> --- a/arch/arm64/Kconfig.platforms
> +++ b/arch/arm64/Kconfig.platforms
> @@ -13,6 +13,19 @@ config ARCH_ALPINE
> This enables support for the Annapurna Labs Alpine
> Soc family.
>
> +config ARCH_BCM2835
> + bool "Broadcom BCM2835 family"
> + select ARCH_REQUIRE_GPIOLIB
> + select CLKSRC_OF
> + select PINCTRL
> + select PINCTRL_BCM2835
> + select ARM_AMBA
> + select ARM_TIMER_SP804
> + select HAVE_ARM_ARCH_TIMER
> + help
> + This enables support for the Broadcom BCM2837 SoC.
> + This SoC is used in the Raspberry Pi 3 device.
I thought we would just use ARCH_BCM, or is it too generic?
--
Catalin
next prev parent reply other threads:[~2016-06-03 11:27 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1464934708-24769-1-git-send-email-kraxel@redhat.com>
2016-06-03 6:18 ` [PATCH v2 1/9] pinctrl: walk into bcm subdir unconditionally Gerd Hoffmann
2016-06-08 8:12 ` Linus Walleij
2016-06-10 0:16 ` Eric Anholt
2016-06-13 7:26 ` Linus Walleij
2016-06-14 17:37 ` Eric Anholt
2016-06-03 6:18 ` [PATCH v2 2/9] irqchip: bcm2835: Avoid arch/arm-specific handle_IRQ Gerd Hoffmann
2016-06-03 6:18 ` [PATCH v2 3/9] arm64: Allow for different DMA and CPU bus offsets Gerd Hoffmann
2016-06-03 6:18 ` [PATCH v2 4/9] arm64: Add platform selection for BCM2835 Gerd Hoffmann
2016-06-03 11:27 ` Catalin Marinas [this message]
2016-06-04 19:55 ` Eric Anholt
2016-06-08 9:12 ` Catalin Marinas
2016-06-10 0:21 ` Eric Anholt
2016-06-10 9:56 ` Catalin Marinas
2016-06-15 6:48 ` Eric Anholt
2016-06-15 8:07 ` Catalin Marinas
2016-06-15 21:57 ` Eric Anholt
2016-06-03 6:18 ` [PATCH v2 5/9] arm64: Add BCM2835 support to the defconfig Gerd Hoffmann
2016-06-03 7:36 ` Arnd Bergmann
2016-06-03 8:50 ` Gerd Hoffmann
2016-06-03 8:58 ` Arnd Bergmann
2016-06-03 9:53 ` Gerd Hoffmann
2016-06-07 22:16 ` Eric Anholt
2016-06-03 6:18 ` [PATCH v2 6/9] dt-bindings: Add root properties for Raspberry Pi 3 Gerd Hoffmann
2016-06-03 6:18 ` [PATCH v2 7/9] ARM: bcm2835: Add devicetree for the " Gerd Hoffmann
2016-06-03 7:38 ` Arnd Bergmann
2016-06-03 8:45 ` Gerd Hoffmann
2016-06-03 8:55 ` Arnd Bergmann
2016-06-03 10:39 ` Gerd Hoffmann
2016-06-03 11:15 ` Arnd Bergmann
2016-06-03 16:17 ` Rob Herring
2016-06-04 21:39 ` Arnd Bergmann
2016-06-06 7:20 ` Gerd Hoffmann
2016-06-06 7:28 ` Arnd Bergmann
2016-06-06 7:47 ` Gerd Hoffmann
2016-06-03 9:04 ` Stefan Wahren
2016-06-03 6:18 ` [PATCH v2 8/9] ARM: bcm2835: dt: Add the ethernet to the device trees Gerd Hoffmann
2016-06-03 6:18 ` [PATCH v2 9/9] ARM: bcm2837: " Gerd Hoffmann
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=20160603112721.GC1128@e104818-lin.cambridge.arm.com \
--to=catalin.marinas@arm.com \
--cc=eric@anholt.net \
--cc=kraxel@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=will.deacon@arm.com \
/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).