From: Baruch Siach <baruch@tkos.co.il>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: "Florian Fainelli" <f.fainelli@gmail.com>,
devicetree@vger.kernel.org,
"Catalin Marinas" <catalin.marinas@arm.com>,
"Rob Herring" <robh+dt@kernel.org>,
bcm-kernel-feedback-list@broadcom.com,
"Rafał Miłecki" <rafal@milecki.pl>,
"Will Deacon" <will@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V3 1/3] arm64: add config for Broadcom BCM4908 SoCs
Date: Thu, 12 Nov 2020 09:34:35 +0200 [thread overview]
Message-ID: <87r1ozav04.fsf@tarshish> (raw)
In-Reply-To: <20201112072133.17039-1-zajec5@gmail.com>
Hi Rafał,
On Thu, Nov 12 2020, Rafał Miłecki wrote:
> From: Rafał Miłecki <rafal@milecki.pl>
>
> Add ARCH_BCM4908 config that can be used for compiling DTS files.
>
> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
> ---
> arch/arm64/Kconfig.platforms | 8 ++++++++
> arch/arm64/configs/defconfig | 1 +
> 2 files changed, 9 insertions(+)
>
> diff --git a/arch/arm64/Kconfig.platforms b/arch/arm64/Kconfig.platforms
> index 6f2494dd6d60..d1c02a4a93c8 100644
> --- a/arch/arm64/Kconfig.platforms
> +++ b/arch/arm64/Kconfig.platforms
> @@ -43,6 +43,14 @@ config ARCH_BCM2835
> This enables support for the Broadcom BCM2837 and BCM2711 SoC.
> These SoCs are used in the Raspberry Pi 3 and 4 devices.
>
> +config ARCH_BCM4908
> + bool "Broadcom BCM4908 family"
> + select GPIOLIB
> + help
> + This enables support for the Broadcom BCM4906, BCM4908 and
> + BCM49408 SoCs. These SoCs use Cortex-B53 cores and can be
Is Cortex-B53 an official name? I see reference to Brahma-B53 in other
places like Documentation/arm64/silicon-errata.rst.
baruch
> + found in home routers.
> +
> config ARCH_BCM_IPROC
> bool "Broadcom iProc SoC Family"
> select COMMON_CLK_IPROC
> diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
> index 17a2df6a263e..ead6fa942994 100644
> --- a/arch/arm64/configs/defconfig
> +++ b/arch/arm64/configs/defconfig
> @@ -32,6 +32,7 @@ CONFIG_ARCH_AGILEX=y
> CONFIG_ARCH_SUNXI=y
> CONFIG_ARCH_ALPINE=y
> CONFIG_ARCH_BCM2835=y
> +CONFIG_ARCH_BCM4908=y
> CONFIG_ARCH_BCM_IPROC=y
> CONFIG_ARCH_BERLIN=y
> CONFIG_ARCH_BRCMSTB=y
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
next prev parent reply other threads:[~2020-11-12 7:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-12 7:21 [PATCH V3 1/3] arm64: add config for Broadcom BCM4908 SoCs Rafał Miłecki
2020-11-12 7:21 ` [PATCH V3 2/3] dt-bindings: arm: bcm: document BCM4908 bindings Rafał Miłecki
2020-11-12 7:21 ` [PATCH V3 3/3] arm64: dts: broadcom: add BCM4908 and Asus GT-AC5300 early DTS files Rafał Miłecki
2020-11-12 7:34 ` Baruch Siach [this message]
2020-11-12 7:53 ` [PATCH V3 1/3] arm64: add config for Broadcom BCM4908 SoCs Rafał Miłecki
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=87r1ozav04.fsf@tarshish \
--to=baruch@tkos.co.il \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=rafal@milecki.pl \
--cc=robh+dt@kernel.org \
--cc=will@kernel.org \
--cc=zajec5@gmail.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).