From: Marc Zyngier <maz@kernel.org>
To: 陈亮 <cl@rock-chips.com>
Cc: heiko@sntech.de, robh+dt@kernel.org, jagan@amarulasolutions.com,
wens@csie.org, uwe@kleine-koenig.org, mail@david-bauer.net,
jbx6244@gmail.com, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
jensenhuang@friendlyarm.com, michael@amarulasolutions.com,
cnsztl@gmail.com, devicetree@vger.kernel.org,
ulf.hansson@linaro.org, linux-mmc@vger.kernel.org,
gregkh@linuxfoundation.org, linux-serial@vger.kernel.org,
linux-i2c@vger.kernel.org, jay.xu@rock-chips.com,
shawn.lin@rock-chips.com, david.wu@rock-chips.com,
zhangqing@rock-chips.com, huangtao@rock-chips.com,
wim@linux-watchdog.org, linux@roeck-us.net, jamie@jamieiles.com,
linux-watchdog@vger.kernel.org
Subject: Re: [PATCH v3 09/10] arm64: dts: rockchip: add core dtsi for RK3568 SoC
Date: Thu, 29 Apr 2021 08:40:43 +0100 [thread overview]
Message-ID: <87eeeto7wk.wl-maz@kernel.org> (raw)
In-Reply-To: <3401442c-24a1-e8f8-fc4a-fa44d94b903b@rock-chips.com>
On Thu, 29 Apr 2021 02:13:35 +0100,
陈亮 <cl@rock-chips.com> wrote:
>
> Hi Marc,
>
> 在 2021/4/28 下午11:06, Marc Zyngier 写道:
> > On Wed, 28 Apr 2021 14:50:02 +0100,
> > <cl@rock-chips.com> wrote:
> >> From: Liang Chen <cl@rock-chips.com>
> >>
> >> RK3568 is a high-performance and low power quad-core application processor
> >> designed for personal mobile internet device and AIoT equipment. This patch
> >> add basic core dtsi file for it.
> >>
> >> We use scmi_clk for cortex-a55 instead of standard ARMCLK, so that
> >> kernel/uboot/rtos can change cpu clk with the same code in ATF, and we will
> >> enalbe a special high-performance PLL when high frequency is required. The
> >> smci_clk code is in ATF, and clkid for cpu is 0, as below:
> >>
> >> cpu0: cpu@0 {
> >> device_type = "cpu";
> >> compatible = "arm,cortex-a55";
> >> reg = <0x0 0x0>;
> >> clocks = <&scmi_clk 0>;
> >> };
> >>
> >> Signed-off-by: Liang Chen <cl@rock-chips.com>
> >> ---
> >> .../boot/dts/rockchip/rk3568-pinctrl.dtsi | 3111 +++++++++++++++++
> >> arch/arm64/boot/dts/rockchip/rk3568.dtsi | 779 +++++
> >> 2 files changed, 3890 insertions(+)
> >> create mode 100644 arch/arm64/boot/dts/rockchip/rk3568-pinctrl.dtsi
> >> create mode 100644 arch/arm64/boot/dts/rockchip/rk3568.dtsi
> > [...]
> >
> >> + gic: interrupt-controller@fd400000 {
> >> + compatible = "arm,gic-v3";
> >> + reg = <0x0 0xfd400000 0 0x10000>, /* GICD */
> >> + <0x0 0xfd460000 0 0xc0000>; /* GICR */
> > If this SoC has 4 CPUs, that's 4 redistributors. Given that GIC600
> > doesn't implement VLPIs, that's 128kB per redistributors. Why is GICR
> > large enough for 6 CPUs here? Is that copy-pasted from another SoC?
> Copy from rk3399, sorry.
> >> + interrupts = <GIC_PPI 9 IRQ_TYPE_LEVEL_HIGH>;
> >> + interrupt-controller;
> >> + #interrupt-cells = <3>;
> >> + mbi-alias = <0x0 0xfd400000>;
> >> + mbi-ranges = <296 24>;
> >> + msi-controller;
> >> + };
> > Glad to see that you found some spare SPIs to get MSIs going
> >
> > However, the whole point of mbi-alias (aka GICA in GIC600) is to be
> > different from GICD and provide some isolation via an IOMMU. If I
> > trust the TRM, if should be at 0xfd10000 in your implementation.
>
> But in the ./devicetree/bindings/interrupt-controller/arm,gic-v3.yaml, say:
>
> mbi-alias:
> description:
> Address property. Base address of an alias of the *GICD* region
> containing
> only the {SET,CLR}SPI registers to be used if isolation is required,
> and if supported by the HW.
[recurring theme: I happen to know about this section of the binding,
having written the original myself]
How does that contradict my comment? GIC600's GICA page only contains
the four {SET,CLR}_SPI registers, as expected (see section 4.3 in the
TRM[1]), and the address is computed using table 4-1 "Register map
pages" of the same document.
Please either fix the DT or explain why the GICA distributor alias
isn't usable.
M.
[1] https://documentation-service.arm.com/static/5e7ddddacbfe76649ba53034
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2021-04-29 7:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-28 13:47 [PATCH v3 00/10] arm64: dts: rockchip: add basic dtsi/dts files for RK3568 SoC cl
2021-04-28 13:47 ` [PATCH v3 01/10] dt-bindings: i2c: i2c-rk3x: add description for rk3568 cl
2021-04-28 13:47 ` [PATCH v3 02/10] dt-bindings: serial: snps-dw-apb-uart: " cl
2021-04-28 13:47 ` [PATCH v3 03/10] dt-bindings: mmc: rockchip-dw-mshc: " cl
2021-04-28 13:47 ` [PATCH v3 04/10] dt-bindings: watchdog: dw-wdt: " cl
2021-04-28 13:49 ` [PATCH v3 05/10] dt-bindings: pwm: rockchip: " cl
2021-04-28 13:49 ` [PATCH v3 06/10] dt-bindings: gpio: change items restriction of clock for rockchip,gpio-bank cl
2021-04-28 13:49 ` [PATCH v3 07/10] dt-bindings: soc: rockchip: Convert grf.txt to YAML cl
2021-04-28 16:56 ` Johan Jonker
2021-04-28 22:15 ` Rob Herring
2021-04-28 13:49 ` [PATCH v3 08/10] arm64: dts: rockchip: add generic pinconfig settings used by most Rockchip socs cl
2021-04-28 13:50 ` [PATCH v3 09/10] arm64: dts: rockchip: add core dtsi for RK3568 SoC cl
2021-04-28 15:06 ` Marc Zyngier
[not found] ` <3401442c-24a1-e8f8-fc4a-fa44d94b903b@rock-chips.com>
2021-04-29 7:40 ` Marc Zyngier [this message]
2021-04-28 18:25 ` Johan Jonker
2021-04-28 13:50 ` [PATCH v3 10/10] arm64: dts: rockchip: add basic dts for RK3568 EVB cl
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=87eeeto7wk.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=cl@rock-chips.com \
--cc=cnsztl@gmail.com \
--cc=david.wu@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=heiko@sntech.de \
--cc=huangtao@rock-chips.com \
--cc=jagan@amarulasolutions.com \
--cc=jamie@jamieiles.com \
--cc=jay.xu@rock-chips.com \
--cc=jbx6244@gmail.com \
--cc=jensenhuang@friendlyarm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mail@david-bauer.net \
--cc=michael@amarulasolutions.com \
--cc=robh+dt@kernel.org \
--cc=shawn.lin@rock-chips.com \
--cc=ulf.hansson@linaro.org \
--cc=uwe@kleine-koenig.org \
--cc=wens@csie.org \
--cc=wim@linux-watchdog.org \
--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).