Hi Simon, On 1/23/23 12:42, Simon Glass wrote: > HI Samuel, > > On Sun, 22 Jan 2023 at 14:16, Samuel Holland <sam...@sholland.org> wrote: >> >> This is easier to read than the #ifdef staircase, provides better >> visibility into the memory map (alongside the other Kconfig >> definitions), and allows these addresses to be reused from code. >> >> Signed-off-by: Samuel Holland <sam...@sholland.org> >> --- >> >> Changes in v2: >> - New patch for v2, split from the .dtsi changes >> >> arch/arm/dts/sunxi-u-boot.dtsi | 24 +++++++----------------- >> arch/arm/mach-sunxi/Kconfig | 17 +++++++++++++++++ >> 2 files changed, 24 insertions(+), 17 deletions(-) > > Reviewed-by: Simon Glass <s...@chromium.org> > > Is this info not in the device tree?
It is not. These values do not correspond to any hardware property. For example, on A64/H5/H6, BL31 and SCP share a single "SRAM A2" region. The division of the SRAM between them was chosen arbitrarily (though now it is ABI). How would you represent this in the devicetree? Regards, Samuel
