From: Heiko Stuebner <[email protected]>

i2c@0 on i2cmux2 does already have a phandle i2c_lvds_blc defined.

Use this one instead of replicating the hirarchy again, as this might
result in strange errors if the lion dtsi is change at some point
in the future.

Signed-off-by: Heiko Stuebner <[email protected]>
---
 .../boot/dts/rockchip/rk3368-lion-haikou.dts   | 18 ++++++++----------
 1 file changed, 8 insertions(+), 10 deletions(-)

diff --git a/arch/arm64/boot/dts/rockchip/rk3368-lion-haikou.dts 
b/arch/arm64/boot/dts/rockchip/rk3368-lion-haikou.dts
index ab70ee5f561a..abd1af97456a 100644
--- a/arch/arm64/boot/dts/rockchip/rk3368-lion-haikou.dts
+++ b/arch/arm64/boot/dts/rockchip/rk3368-lion-haikou.dts
@@ -18,16 +18,6 @@ chosen {
                stdout-path = "serial0:115200n8";
        };
 
-       i2cmux2 {
-               i2c@0 {
-                       eeprom: eeprom@50 {
-                               compatible = "atmel,24c01";
-                               pagesize = <8>;
-                               reg = <0x50>;
-                       };
-               };
-       };
-
        leds {
                pinctrl-0 = <&module_led_pins>, <&sd_card_led_pin>;
 
@@ -68,6 +58,14 @@ vcc5v0_otg: regulator-vcc5v0-otg {
        };
 };
 
+&i2c_lvds_blc {
+       eeprom: eeprom@50 {
+               compatible = "atmel,24c01";
+               pagesize = <8>;
+               reg = <0x50>;
+       };
+};
+
 &sdmmc {
        bus-width = <4>;
        cap-mmc-highspeed;
-- 
2.47.2

Reply via email to