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 0/4] arm: bcmbca: add basic support for more Broadcom BCA SoCs
Date: Mon, 8 Aug 2022 20:29:26 -0700 [thread overview]
Message-ID: <3ec9470f-3cfb-dd16-7180-287c6b176df2@gmail.com> (raw)
In-Reply-To: <20220806013403.1344-1-william.zhang@broadcom.com>
On 8/5/2022 6:33 PM, William Zhang wrote:
> Broadcom BCA (Broadband Carrier Access origin) chipset family includes
> DSL, PON and WLAN access point and gateway SoC. Now that the ARCH_BCMBCA
> architecture and its first SoC BCM47622 are supported in u-boot 2022.07,
> this patch series add the basic support for following BCA chips under
> ARCH_BCMBCA: BCM4908, BCM4912, BCM63146 and BCM6813.
>
> This patch series applies on top of the my previous patch [1].
>
> [1] https://lists.denx.de/pipermail/u-boot/2022-August/491060.html
Looks good to me, thanks William! On the mmu_table.c implementation
maybe just a few nits:
- should not we do an early parsing of the memory node for the given
board(s) to ensure that we map no more than the amount of available DRAM?
- the exact same file is currently being re-used, so it would make sense
to make it a common object
- you could create a memory mapping for the AXI bus region right away to
avoid forgetting about it later if you start bringing up drivers that
make use of that peripheral region
Thanks!
--
Florian
next prev parent reply other threads:[~2022-08-09 3:29 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
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 ` Florian Fainelli [this message]
2022-08-09 5:51 ` [PATCH 0/4] arm: bcmbca: add basic support for more Broadcom BCA SoCs 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=3ec9470f-3cfb-dd16-7180-287c6b176df2@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