From: Enzo Adriano <enzo.adriano.code@gmail.com>
To: alex@sverdlin.org
Cc: andre.przywara@arm.com, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, wens@kernel.org, jernej.skrabec@gmail.com,
samuel@sholland.org, Maxime Ripard <mripard@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org,
Junhui Liu <junhui.liu@pigmoral.tech>,
Jerome Brunet <jbrunet@baylibre.com>,
Pablo Mazzini <pmazzini@gmail.com>,
Vinicius Pedrosa <vinicius.eduardo.pedrosa@gmail.com>,
Jun Yan <jerrysteve1101@gmail.com>,
Lukas Schmid <lukas.schmid@netcube.li>
Subject: Re: [PATCH v3 2/3] arm64: dts: allwinner: add A733 SoC description
Date: Thu, 19 Nov 2026 13:06:53 -0500 [thread overview]
Message-ID: <20261118-a733-dt-v3-2-reply@gmail.com> (raw)
In-Reply-To: <18a78cddfc3c28c011bb5d0c566c2f307773b235.camel@sverdlin.org>
Hi Alexander,
> Shall parts of this go below "---" as history/changelog?
Yes. In v4 I will move the dated test results below "---" and keep
the hardware rationale in the commit message.
> Do we need capacity-dmips-mhz, cpu-map and two PMUs here, similar
> to rk3588-base.dtsi? This in turn would mean ppi-partitions with
> #interrupt-cells = <4> in GIC?
The A733 manual shows one DynamIQ cluster with six Cortex-A55 cores
(0-5) and two Cortex-A76 cores (6-7) sharing L3 (section 5.1.2,
figure 5-1). Every core's PMU interrupt is PPI 7 (section 12.2.3,
table 12-1).
In v4 I will add a single-cluster cpu-map and separate
arm,cortex-a55-pmu and arm,cortex-a76-pmu nodes on PPI 7 with
ppi-partitions, and switch the GIC to #interrupt-cells = <4>, as
MT8186 does for the same six-plus-two layout.
I will leave capacity-dmips-mhz out until measured on A733. Radxa's
BSP uses 430/1024 without a stated method. In the November 18
RAM boot on Cubie A7S with the v4 DT, CPUs 0-7 were in one cluster,
with the A55 PMU on CPUs 0-5 and the A76 PMU on CPUs 6-7 counting
and receiving PPI 7 overflow interrupts on each CPU.
Thanks,
Enzo
next prev parent reply other threads:[~2026-11-19 18:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 4:45 [PATCH v3 0/3] arm64: dts: allwinner: add A733/Cubie A7S support Enzo Adriano
2026-11-10 4:45 ` [PATCH v3 1/3] dt-bindings: arm: sunxi: document Radxa Cubie A7S Enzo Adriano
2026-11-17 23:24 ` Alexander Sverdlin
2026-11-10 4:45 ` [PATCH v3 2/3] arm64: dts: allwinner: add A733 SoC description Enzo Adriano
2026-11-10 23:45 ` sashiko-bot
2026-11-11 12:02 ` Vinicius Pedrosa
2026-11-18 16:47 ` Alexander Sverdlin
2026-11-19 18:06 ` Enzo Adriano [this message]
2026-11-10 4:45 ` [PATCH v3 3/3] arm64: dts: allwinner: add Radxa Cubie A7S board Enzo Adriano
2026-11-11 0:00 ` sashiko-bot
2026-11-18 18:03 ` Alexander Sverdlin
2026-11-19 18:08 ` Enzo Adriano
2026-11-11 12:09 ` [PATCH v3 0/3] arm64: dts: allwinner: add A733/Cubie A7S support Enzo Adriano
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=20261118-a733-dt-v3-2-reply@gmail.com \
--to=enzo.adriano.code@gmail.com \
--cc=alex@sverdlin.org \
--cc=andre.przywara@arm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=jernej.skrabec@gmail.com \
--cc=jerrysteve1101@gmail.com \
--cc=junhui.liu@pigmoral.tech \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=lukas.schmid@netcube.li \
--cc=mripard@kernel.org \
--cc=pmazzini@gmail.com \
--cc=robh@kernel.org \
--cc=samuel@sholland.org \
--cc=vinicius.eduardo.pedrosa@gmail.com \
--cc=wens@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.