Hi Dhruva,
Am 27.01.25 um 13:22 schrieb Dhruva Gole:
Hi Wadim,
On Jan 27, 2025 at 05:16:10 +0100, Wadim Egorov wrote:
Add bootph-all properties to I2C0 nodes to ensure the bus and EEPROM are accessible across all stages. This enables reading the SoM configuration at any point during the boot process.
Signed-off-by: Wadim Egorov w.egorov@phytec.de
arch/arm/dts/k3-am642-phyboard-electra-rdk-u-boot.dtsi | 8 ++++++++ 1 file changed, 8 insertions(+)
diff --git a/arch/arm/dts/k3-am642-phyboard-electra-rdk-u-boot.dtsi b/arch/arm/dts/k3-am642-phyboard-electra-rdk-u-boot.dtsi index 8f3c3a185ae..c68a48678a2 100644 --- a/arch/arm/dts/k3-am642-phyboard-electra-rdk-u-boot.dtsi +++ b/arch/arm/dts/k3-am642-phyboard-electra-rdk-u-boot.dtsi @@ -72,6 +72,14 @@ bootph-all; };
+&main_i2c0 {
- bootph-all;
+};
+&main_i2c0_pins_default {
- bootph-all;
+};
Can we not add the bootph-all property in the kernel DT nodes for this?
Yes, adding bootph-props to the Kernel device tree is on my todo.
Also, I don't see main_i2c0 in the kernel DTS file for this[1] platform. Is there a particular reason to not put it there?
It is defined in the som.dtsi file
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch...
Regards, Wadim
[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch...