Dear Marek,
From: Marek Vasut marex@denx.de Sent: mardi 31 mars 2020 19:52
The AV96 is in fact an assembly of DH Electronics DHCOR SoM on top of an AV96 reference board. Split the DTs to reflect that and make sure to DHCOR SoM can be reused on other boards easily.
It is also highly recommended to configure the board for the DHCOM make stm32mp15_dhcom_basic_defconfig make DEVICE_TREE=stm32mp15xx-dhcor- avenger96 as that permits reusing the board code for the DH components, like accessing and reading out the ethernet MAC from EEPROM.
Signed-off-by: Marek Vasut marex@denx.de Cc: Manivannan Sadhasivam manivannan.sadhasivam@linaro.org Cc: Patrick Delaunay patrick.delaunay@st.com Cc: Patrice Chotard patrice.chotard@st.com
V2: No change V3: No change
Applied to u-boot-stm/master, with few modifications:
arch/arm/dts/stm32mp15xx-dhcor-u-boot.dtsi
- -&v3v3 { - regulator-always-on; -};
Not needed as already present in arch/arm/dts/stm32mp15xx-dhcor.dtsi
I solve rebase conflict on arch/arm/dts/stm32mp15xx-dhcor.dtsi
- reg = <0x58003000 0x1000>, <0x70000000 0x4000000>; + reg = <0x58003000 0x1000>, <0x70000000 0x200000>;
And issue after kernel device tree alignment :
arch/arm/dts/stm32mp15xx-dhcor-avenger96-u-boot.dtsi
&sdmmc1_b4_pins_a { u-boot,dm-spl; - pins { + pins1 { + u-boot,dm-spl; + }; + pins2 { u-boot,dm-spl; }; };
Regards
Patrick