From: Tom Rini <trini@konsulko.com>
To: William Zhang <william.zhang@broadcom.com>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
dan.beygelman@broadcom.com, anand.gore@broadcom.com,
kursad.oney@broadcom.com, philippe.reynes@softathome.com,
joel.peshkin@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>,
Tomer Yacoby <tomer.yacoby@broadcom.com>,
"Ying-Chun Liu (PaulLiu)" <paul.liu@linaro.org>
Subject: Re: [PATCH 1/5] arm: bcmbca: add bcm63178 SoC support
Date: Mon, 1 Aug 2022 10:02:14 -0400 [thread overview]
Message-ID: <20220801140214.GD1146598@bill-the-cat> (raw)
In-Reply-To: <20220729124534.1.I49e41e791b038a159729c535e9dcfc4a7d59e95c@changeid>
[-- Attachment #1: Type: text/plain, Size: 1465 bytes --]
On Fri, Jul 29, 2022 at 12:48:43PM -0700, William Zhang wrote:
> BCM63178 is an ARM A7 based DSL Broadband 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 with minor fix-up that needs to be
> upstreamed to linux as well.
>
> The u-boot image can be loaded from flash or network to the entry
> point address in the memory and boot from there.
>
> Signed-off-by: William Zhang <william.zhang@broadcom.com>
[snip]
> diff --git a/include/configs/bcm963178.h b/include/configs/bcm963178.h
> new file mode 100644
> index 000000000000..3ee2011b3a2d
> --- /dev/null
> +++ b/include/configs/bcm963178.h
> @@ -0,0 +1,12 @@
> +/* SPDX-License-Identifier: GPL-2.0+ */
> +/*
> + * (C) Copyright 2022 Broadcom Ltd.
> + */
> +
> +#ifndef __BCM963178_H
> +#define __BCM963178_H
> +
> +#define CONFIG_SYS_SDRAM_BASE 0x00000000
> +#define COUNTER_FREQUENCY 50000000
> +
> +#endif
The one problem I have is that we need to put COUNTER_FREQUENCY
somewhere else, if it needs to be defined. I see the top-level README
has outdated information about COUNTER_FREQUENCY, which is most often
CONFIG_COUNTER_FREQUENCY instead, as well.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2022-08-01 14:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 19:48 [PATCH 0/5] arm: bcmbca: add basic support for Broadcom BCA SoCs William Zhang
2022-07-29 19:48 ` [PATCH 1/5] arm: bcmbca: add bcm63178 SoC support William Zhang
2022-08-01 14:02 ` Tom Rini [this message]
2022-08-01 17:28 ` William Zhang
2022-07-29 19:48 ` [PATCH 2/5] arm: bcmbca: add bcm6846 " William Zhang
2022-07-29 19:48 ` [PATCH 3/5] arm: bcmbca: add bcm6878 " William Zhang
2022-07-29 19:48 ` [PATCH 4/5] arm: bcmbca: add bcm6756 " William Zhang
2022-07-29 19:48 ` [PATCH 5/5] arm: bcmbca: add bcm63148 " 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=20220801140214.GD1146598@bill-the-cat \
--to=trini@konsulko.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=samuel@sholland.org \
--cc=sjg@chromium.org \
--cc=tomer.yacoby@broadcom.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