From: Krzysztof Kozlowski <krzk@kernel.org>
To: Alexandru Chimac <alex@chimac.ro>,
Alim Akhtar <alim.akhtar@samsung.com>,
Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Kees Cook <kees@kernel.org>, Tony Luck <tony.luck@intel.com>,
"Guilherme G. Piccoli" <gpiccoli@igalia.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH 2/3] arm64: dts: exynos: Add initial support for the Exynos9610 SoC
Date: Mon, 15 Sep 2025 06:36:16 +0200 [thread overview]
Message-ID: <ede52fd2-fe20-4648-be7b-de10b14d7e3f@kernel.org> (raw)
In-Reply-To: <20250914-exynos9610-devicetree-v1-2-2000fc3bbe0b@chimac.ro>
On 14/09/2025 22:44, Alexandru Chimac wrote:
> +
> + arm-a53-pmu {
> + compatible = "arm,cortex-a53-pmu";
> + interrupts = <0 82 4>,
> + <0 83 4>,
> + <0 84 4>,
> + <0 85 4>;
> + interrupt-affinity = <&cpu0>,
> + <&cpu1>,
> + <&cpu2>,
> + <&cpu3>;
> + };
> +
> + arm-a73-pmu {
> + compatible = "arm,cortex-a73-pmu";
> + interrupts = <0 96 4>,
> + <0 97 4>,
> + <0 98 4>,
> + <0 99 4>;
You need to use proper defines.
> + interrupt-affinity = <&cpu100>,
> + <&cpu101>,
> + <&cpu102>,
> + <&cpu103>;
> + };
> +
> + oscclk: clock-osc {
> + compatible = "fixed-clock";
> + #clock-cells = <0>;
> + clock-output-names = "oscclk";
> + clock-frequency = <26000000>;
clock-frequency is board property.
...
> +
> + timer {
> + compatible = "arm,armv8-timer";
> + interrupts = <GIC_PPI 13 (GIC_CPU_MASK_SIMPLE(8) | IRQ_TYPE_LEVEL_LOW)>,
> + <GIC_PPI 14 (GIC_CPU_MASK_SIMPLE(8) | IRQ_TYPE_LEVEL_LOW)>,
> + <GIC_PPI 11 (GIC_CPU_MASK_SIMPLE(8) | IRQ_TYPE_LEVEL_LOW)>,
> + <GIC_PPI 10 (GIC_CPU_MASK_SIMPLE(8) | IRQ_TYPE_LEVEL_LOW)>;
> +
> + /* Stock Samsung bootloader doesn't configure CNTFRQ_EL0 */
> + clock-frequency = <26000000>;
> + };
> +
> + reserved-memory {
> + #address-cells = <2>;
> + #size-cells = <1>;
> + ranges;
> +
> + abox_rmem: abox@e9400000 {
What is abox?
> + compatible = "reserved-memory";
> + reg = <0x0 0xe9400000 0x2800000>;
> + no-map;
> + };
> +
> + ramoops@f9d10000 {
This belongs to the the board.
> + compatible = "ramoops";
> + reg = <0x0 0xf9d10000 0x200000>;
> + record-size = <0x80000>;
> + console-size = <0x80000>;
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-09-15 4:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-14 20:43 [PATCH 0/3] arm64: dts: exynos: Add initial support for Exynos9610 Alexandru Chimac
2025-09-14 20:43 ` [PATCH 1/3] dt-bindings: arm: samsung: Document gta4xl board binding Alexandru Chimac
2025-09-15 13:21 ` Rob Herring (Arm)
2025-09-14 20:44 ` [PATCH 2/3] arm64: dts: exynos: Add initial support for the Exynos9610 SoC Alexandru Chimac
2025-09-15 4:36 ` Krzysztof Kozlowski [this message]
2025-09-14 20:44 ` [PATCH 3/3] arm64: dts: exynos: Add initial support for Samsung Galaxy Tab S6 Lite (gta4xl) Alexandru Chimac
2025-09-15 4:32 ` Krzysztof Kozlowski
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=ede52fd2-fe20-4648-be7b-de10b14d7e3f@kernel.org \
--to=krzk@kernel.org \
--cc=alex@chimac.ro \
--cc=alim.akhtar@samsung.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gpiccoli@igalia.com \
--cc=kees@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=robh@kernel.org \
--cc=tony.luck@intel.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