From mboxrd@z Thu Jan 1 00:00:00 1970 From: narmstrong@baylibre.com (Neil Armstrong) Date: Fri, 17 Nov 2017 14:05:50 +0100 Subject: [PATCH 3/5] ARM64: dts: meson-axg: add I2C DT info for Meson-AXG SoC In-Reply-To: <20171117080236.32504-4-yixun.lan@amlogic.com> References: <20171117080236.32504-1-yixun.lan@amlogic.com> <20171117080236.32504-4-yixun.lan@amlogic.com> Message-ID: <96dc68e3-c394-70c4-eabe-f59d4c36150e@baylibre.com> To: linus-amlogic@lists.infradead.org List-Id: linus-amlogic.lists.infradead.org Hi Yixun, Jian, On 17/11/2017 09:02, Yixun Lan wrote: > From: Jian Hu > > There are four I2C masters in EE domain, and one I2C Master in > AO domain, the DT info here should describe them all. > > Signed-off-by: Jian Hu > Signed-off-by: Yixun Lan > --- > arch/arm64/boot/dts/amlogic/meson-axg.dtsi | 59 ++++++++++++++++++++++++++++++ > 1 file changed, 59 insertions(+) > > diff --git a/arch/arm64/boot/dts/amlogic/meson-axg.dtsi b/arch/arm64/boot/dts/amlogic/meson-axg.dtsi > index 57faaa9d8013..99e967aff439 100644 > --- a/arch/arm64/boot/dts/amlogic/meson-axg.dtsi > +++ b/arch/arm64/boot/dts/amlogic/meson-axg.dtsi > @@ -129,6 +129,54 @@ > #reset-cells = <1>; > }; > > + i2c_m0: i2c at 1f000 { Can you use a more simple "i2c0" phandle naming instead ? or get back to the "i2c_A/B/C/D" naming like in meson_gx to keep consistency ? [...] > + }; > + > + i2c_m1: i2c at 1e000 { [...] > + }; > + > + i2c_m2: i2c at 1d000 { [...] > + }; > + > + i2c_m3: i2c at 1c000 { [...] > + }; > + > uart_A: serial at 24000 { > compatible = "amlogic,meson-gx-uart", "amlogic,meson-uart"; > reg = <0x0 0x24000 0x0 0x14>; > @@ -312,6 +360,17 @@ > }; > }; > > + i2c_ao: i2c at 5000 { Can you keep the same "i2c_AO" as in meson-gx ? [...] > + }; > + > uart_AO: serial at 3000 { > compatible = "amlogic,meson-gx-uart", "amlogic,meson-ao-uart"; > reg = <0x0 0x3000 0x0 0x18>; > Neil