Thread (32 messages) 32 messages, 5 authors, 2025-11-05

Re: [PATCH v6 4/6] arm64: dts: aspeed: Add initial AST2700 SoC device tree

From: Andrew Lunn <andrew@lunn.ch>
Date: 2025-10-27 12:02:03
Also in: linux-aspeed, linux-devicetree, lkml

On Mon, Oct 27, 2025 at 02:42:01AM +0000, Ryan Chen wrote:
quoted
Subject: Re: [PATCH v6 4/6] arm64: dts: aspeed: Add initial AST2700 SoC device
tree
quoted
SoC0, referred to as the CPU die, contains a dual-core Cortex-A35
cluster and two Cortex-M4 cores, along with its own clock/reset
domains and high-speed peripheral set.
quoted
SoC1, referred to as the I/O die, contains the Boot MCU and its own
clock/reset domains and low-speed peripheral set, and is responsible
for system boot and control functions.
So is the same .dtsi file shared by both systems? 
This .dtsi represents the Cortex-A35 view only and is not shared
with the Cortex-M4 or the Boot MCU side, since they are separate
32-bit and 64-bit systems running independent firmware.
DT describes the hardware. The .dtsi file could be shared, you just
need different status = <>; lines in the dtb blob.
quoted
How do you partition devices
so each CPU cluster knows it has exclusive access to which peripherals?
Before the system is fully brought up, Boot MCU configure hardware 
controllers handle the resource partitioning to ensure exclusive access.
Are you saying it modifies the .dtb blob and changes some status =
"okay"; to "disabled";?

	Andrew
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help