devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sebastian Reichel <sebastian.reichel@collabora.com>
To: Marc Zyngier <maz@kernel.org>
Cc: Heiko Stuebner <heiko@sntech.de>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	Christopher Obbard <chris.obbard@collabora.com>,
	Benjamin Gaignard <benjamin.gaignard@collabora.com>,
	linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Kever Yang <kever.yang@rock-chips.com>,
	kernel@collabora.com, Yifeng Zhao <yifeng.zhao@rock-chips.com>,
	Elaine Zhang <zhangqing@rock-chips.com>,
	Sugar Zhang <sugar.zhang@rock-chips.com>
Subject: Re: [PATCHv6 3/7] arm64: dts: rockchip: Add base DT for rk3588 SoC
Date: Thu, 15 Dec 2022 15:00:58 +0100	[thread overview]
Message-ID: <20221215140058.ef4z5k6bg4tob44k@mercury.elektranox.org> (raw)
In-Reply-To: <861qp1qawb.wl-maz@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 2464 bytes --]

Hi,

On Thu, Dec 15, 2022 at 09:22:28AM +0000, Marc Zyngier wrote:
> On Wed, 14 Dec 2022 18:22:43 +0000,
> Sebastian Reichel <sebastian.reichel@collabora.com> wrote:
> > 
> > From: Kever Yang <kever.yang@rock-chips.com>
> > 
> > This initial version supports (single core) CPU, dma, interrupts, timers,
> > UART and SDHCI. In short - everything necessary to boot Linux on this
> > system on chip.
> 
> Single core? The DT indicates otherwise.

oops, that's a still from v0 (missing from the changelog since that
was a big rk3588 series also containing the required driver changes).
I will update the commit message in PATCHv7.

> 
> > 
> > The DT is split into rk3588 and rk3588s, which is a reduced version
> > (i.e. with less peripherals) of the former.
> > 
> > Signed-off-by: Yifeng Zhao <yifeng.zhao@rock-chips.com>
> > Signed-off-by: Elaine Zhang <zhangqing@rock-chips.com>
> > Signed-off-by: Sugar Zhang <sugar.zhang@rock-chips.com>
> > Signed-off-by: Kever Yang <kever.yang@rock-chips.com>
> > [rebase, squash and reword commit message]
> > Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.com>
> > ---
> >  arch/arm64/boot/dts/rockchip/rk3588.dtsi  |   58 +
> >  arch/arm64/boot/dts/rockchip/rk3588s.dtsi | 1703 +++++++++++++++++++++
> >  2 files changed, 1761 insertions(+)
> >  create mode 100644 arch/arm64/boot/dts/rockchip/rk3588.dtsi
> >  create mode 100644 arch/arm64/boot/dts/rockchip/rk3588s.dtsi
> > 
> 
> [...]
> 
> > +	gic: interrupt-controller@fe600000 {
> > +		compatible = "arm,gic-v3";
> > +		reg = <0x0 0xfe600000 0 0x10000>, /* GICD */
> > +		      <0x0 0xfe680000 0 0x100000>; /* GICR */
> > +		interrupts = <GIC_PPI 9 IRQ_TYPE_LEVEL_HIGH 0>;
> > +		interrupt-controller;
> > +		mbi-alias = <0x0 0xfe610000>;
> > +		mbi-ranges = <424 56>;
> > +		msi-controller;
> > +		#interrupt-cells = <4>;
> > +
> > +		ppi-partitions {
> > +			ppi_cluster0: interrupt-partition-0 {
> > +				affinity = <&cpu_l0 &cpu_l1 &cpu_l2 &cpu_l3>;
> > +			};
> > +
> > +			ppi_cluster1: interrupt-partition-1 {
> > +				affinity = <&cpu_b0 &cpu_b1 &cpu_b2 &cpu_b3>;
> 
> The use of the word "cluster" is pretty misleading, specially as the
> actual CPU clusters don't align with this partitioning (you seem to
> have 2 independent A76 clusters). Consider using the word "partition",
> which was chosen exactly to avoid this confusion.

Ack.

Thanks for the review,

-- Sebastian

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-12-15 14:01 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-14 18:22 [PATCHv6 0/7] Initial rk3588 DT Sebastian Reichel
2022-12-14 18:22 ` [PATCHv6 1/7] dt-bindings: soc: rockchip: add initial rk3588 syscon compatibles Sebastian Reichel
2022-12-14 18:22 ` [PATCHv6 2/7] arm64: dts: rockchip: Add rk3588 pinctrl data Sebastian Reichel
2022-12-14 18:22 ` [PATCHv6 3/7] arm64: dts: rockchip: Add base DT for rk3588 SoC Sebastian Reichel
2022-12-15  9:22   ` Marc Zyngier
2022-12-15 14:00     ` Sebastian Reichel [this message]
2022-12-15 10:45   ` Jagan Teki
2022-12-15 10:50     ` Marc Zyngier
2022-12-15 10:55       ` Jagan Teki
2022-12-14 18:22 ` [PATCHv6 4/7] dt-bindings: arm: rockchip: add initial rk3588 boards Sebastian Reichel
2023-01-05 19:20   ` Christopher Obbard
2023-01-07  0:28     ` Sebastian Reichel
2023-01-09 14:27       ` Christopher Obbard
2022-12-14 18:22 ` [PATCHv6 5/7] arm64: dts: rockchip: Add rk3588-evb1 board Sebastian Reichel
2022-12-15 13:07   ` Jagan Teki
2022-12-15 13:56     ` Sebastian Reichel
2022-12-14 18:22 ` [PATCHv6 6/7] arm64: dts: rockchip: Add rock-5a board Sebastian Reichel
2022-12-14 18:22 ` [PATCHv6 7/7] arm64: dts: rockchip: Add rock-5b board Sebastian Reichel
2022-12-15 17:18 ` [PATCHv6 0/7] Initial rk3588 DT Rob Herring
2022-12-15 18:17   ` Sebastian Reichel

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=20221215140058.ef4z5k6bg4tob44k@mercury.elektranox.org \
    --to=sebastian.reichel@collabora.com \
    --cc=benjamin.gaignard@collabora.com \
    --cc=chris.obbard@collabora.com \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=kernel@collabora.com \
    --cc=kever.yang@rock-chips.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=maz@kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=sugar.zhang@rock-chips.com \
    --cc=yifeng.zhao@rock-chips.com \
    --cc=zhangqing@rock-chips.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).