From: William Zhang <william.zhang@broadcom.com>
To: Linux ARM List <linux-arm-kernel@lists.infradead.org>,
Broadcom Kernel List <bcm-kernel-feedback-list@broadcom.com>
Cc: joel.peshkin@broadcom.com, tomer.yacoby@broadcom.com,
kursad.oney@broadcom.com, philippe.reynes@softathome.com,
dan.beygelman@broadcom.com, samyon.furman@broadcom.com,
anand.gore@broadcom.com, florian.fainelli@broadcom.com,
William Zhang <william.zhang@broadcom.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 2/5] arm64: bcmbca: add arch bcmbca machine entry
Date: Wed, 1 Jun 2022 15:56:50 -0700 [thread overview]
Message-ID: <20220601225654.18519-3-william.zhang@broadcom.com> (raw)
In-Reply-To: <20220601225654.18519-1-william.zhang@broadcom.com>
[-- Attachment #1.1: Type: text/plain, Size: 885 bytes --]
Add ARCH_BCMBCA config for Broadcom Broadband SoC chipsets
Signed-off-by: William Zhang <william.zhang@broadcom.com>
---
(no changes since v1)
arch/arm64/Kconfig.platforms | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/arch/arm64/Kconfig.platforms b/arch/arm64/Kconfig.platforms
index 4e6d635a1731..88ddc2e5b152 100644
--- a/arch/arm64/Kconfig.platforms
+++ b/arch/arm64/Kconfig.platforms
@@ -63,6 +63,15 @@ config ARCH_BCM_IPROC
help
This enables support for Broadcom iProc based SoCs
+config ARCH_BCMBCA
+ bool "Broadcom Broadband SoC"
+ help
+ Say Y if you intend to run the kernel on a Broadcom Broadband ARM-based
+ BCA chipset.
+
+ This enables support for Broadcom BCA ARM-based broadband chipsets,
+ including the DSL, PON and Wireless family of chips.
+
config ARCH_BERLIN
bool "Marvell Berlin SoC Family"
select DW_APB_ICTL
--
2.36.1
[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4212 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-06-01 22:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 22:56 [PATCH v2 0/5] arm64: bcmbca: add bcm63158 soc support under bcmbca arch William Zhang
2022-06-01 22:56 ` [PATCH v2 1/5] dt-bindings: arm64: add bcm63158 SoC William Zhang
2022-06-02 11:50 ` Krzysztof Kozlowski
2022-06-08 8:14 ` Florian Fainelli
2022-06-01 22:56 ` William Zhang [this message]
2022-06-08 8:13 ` [PATCH v2 2/5] arm64: bcmbca: add arch bcmbca machine entry Florian Fainelli
2022-06-01 22:56 ` [PATCH v2 3/5] arm64: dts: add dts files for bcmbca soc 63158 William Zhang
2022-06-08 8:09 ` Florian Fainelli
2022-06-01 22:56 ` [PATCH v2 4/5] MAINTAINERS: add bcm63158 to bcmbca arch entry William Zhang
2022-06-08 8:14 ` Florian Fainelli
2022-06-01 22:56 ` [PATCH v2 5/5] arm64: defconfig: enable bcmbca soc support William Zhang
2022-06-08 8:14 ` 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=20220601225654.18519-3-william.zhang@broadcom.com \
--to=william.zhang@broadcom.com \
--cc=anand.gore@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=catalin.marinas@arm.com \
--cc=dan.beygelman@broadcom.com \
--cc=florian.fainelli@broadcom.com \
--cc=joel.peshkin@broadcom.com \
--cc=kursad.oney@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=philippe.reynes@softathome.com \
--cc=samyon.furman@broadcom.com \
--cc=tomer.yacoby@broadcom.com \
--cc=will@kernel.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).