[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87bn3gu3to.fsf@eliezer.anholt.net>
Date: Sat, 04 Jun 2016 12:55:15 -0700
From: Eric Anholt <eric@...olt.net>
To: Catalin Marinas <catalin.marinas@....com>,
Gerd Hoffmann <kraxel@...hat.com>
Cc: linux-rpi-kernel@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org,
Will Deacon <will.deacon@....com>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 4/9] arm64: Add platform selection for BCM2835.
Catalin Marinas <catalin.marinas@....com> writes:
> 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?
Consensus last time around seemed to be to drop adding ARCH_BCM, in
favor of patch 1 of the series.
Download attachment "signature.asc" of type "application/pgp-signature" (819 bytes)
Powered by blists - more mailing lists