From: Florian Fainelli <f.fainelli@gmail.com>
To: William Zhang <william.zhang@broadcom.com>,
U-Boot Mailing List <u-boot@lists.denx.de>
Cc: kursad.oney@broadcom.com, dan.beygelman@broadcom.com,
joel.peshkin@broadcom.com, philippe.reynes@softathome.com,
rafal@milecki.pl, anand.gore@broadcom.com,
Andre Przywara <andre.przywara@arm.com>,
Christian Hewitt <christianshewitt@gmail.com>,
Fabio Estevam <festevam@denx.de>, Marek Vasut <marex@denx.de>,
Samuel Holland <samuel@sholland.org>,
Simon Glass <sjg@chromium.org>, Tom Rini <trini@konsulko.com>,
Tomer Yacoby <tomer.yacoby@broadcom.com>,
"Ying-Chun Liu (PaulLiu)" <paul.liu@linaro.org>
Subject: Re: [PATCH 3/4] arm: bcmbca: add bcm6813 SoC support
Date: Mon, 8 Aug 2022 20:27:07 -0700 [thread overview]
Message-ID: <3588c56d-8af6-b7ed-3eee-cdd0a883e56b@gmail.com> (raw)
In-Reply-To: <20220805183208.3.Ied4f916adc644f754f8c78e574b6295cec250d52@changeid>
On 8/5/2022 6:34 PM, William Zhang wrote:
> BCM6813 is a Broadcom B53 based PON and WLAN AP router SoC. It is part
> of the BCA (Broadband Carrier Access origin) chipset family so it's
> added under ARCH_BCMBCA platform. This initial support includes a
> bare-bone implementation and dts with CPU subsystem, memory and ARM
> PL011 uart.
>
> This SoC is supported in the linux-next git repository so the dts and
> dtsi files are copied from linux.
>
> The u-boot image can be loaded from flash or network to the entry point
> address in the memory and boot from there to the console.
>
> Signed-off-by: William Zhang <william.zhang@broadcom.com>
> ---
>
> MAINTAINERS | 1 +
> arch/arm/dts/Makefile | 2 +
> arch/arm/dts/bcm6813.dtsi | 128 +++++++++++++++++++++++
> arch/arm/dts/bcm96813.dts | 30 ++++++
> arch/arm/mach-bcmbca/Kconfig | 8 ++
> arch/arm/mach-bcmbca/Makefile | 1 +
> arch/arm/mach-bcmbca/bcm6813/Kconfig | 17 +++
> arch/arm/mach-bcmbca/bcm6813/Makefile | 5 +
> arch/arm/mach-bcmbca/bcm6813/mmu_table.c | 32 ++++++
OK, so after seeing the same mmu_table.c 4 times, maybe we could share a
common implementation that is configurable enough, even if there may not
be any need for configuration other than the DRAM size.
Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
--
Florian
next prev parent reply other threads:[~2022-08-09 3:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-06 1:33 [PATCH 0/4] arm: bcmbca: add basic support for more Broadcom BCA SoCs William Zhang
2022-08-06 1:34 ` [PATCH 1/4] arm: bcmbca: add bcm63146 SoC support William Zhang
2022-08-09 3:24 ` Florian Fainelli
2022-10-31 14:45 ` Tom Rini
2022-08-06 1:34 ` [PATCH 2/4] arm: bcmbca: add bcm4912 " William Zhang
2022-08-09 3:25 ` Florian Fainelli
2022-08-06 1:34 ` [PATCH 3/4] arm: bcmbca: add bcm6813 " William Zhang
2022-08-09 3:27 ` Florian Fainelli [this message]
2022-08-06 1:34 ` [PATCH 4/4] arm: bcmbca: add bcm4908 " William Zhang
2022-08-09 3:27 ` Florian Fainelli
2022-08-09 3:29 ` [PATCH 0/4] arm: bcmbca: add basic support for more Broadcom BCA SoCs Florian Fainelli
2022-08-09 5:51 ` William Zhang
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=3588c56d-8af6-b7ed-3eee-cdd0a883e56b@gmail.com \
--to=f.fainelli@gmail.com \
--cc=anand.gore@broadcom.com \
--cc=andre.przywara@arm.com \
--cc=christianshewitt@gmail.com \
--cc=dan.beygelman@broadcom.com \
--cc=festevam@denx.de \
--cc=joel.peshkin@broadcom.com \
--cc=kursad.oney@broadcom.com \
--cc=marex@denx.de \
--cc=paul.liu@linaro.org \
--cc=philippe.reynes@softathome.com \
--cc=rafal@milecki.pl \
--cc=samuel@sholland.org \
--cc=sjg@chromium.org \
--cc=tomer.yacoby@broadcom.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=william.zhang@broadcom.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