From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753028AbbFHMbQ (ORCPT ); Mon, 8 Jun 2015 08:31:16 -0400 Received: from mail-yh0-f50.google.com ([209.85.213.50]:33606 "EHLO mail-yh0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751754AbbFHMbH (ORCPT ); Mon, 8 Jun 2015 08:31:07 -0400 MIME-Version: 1.0 In-Reply-To: <1433761837.31929.3.camel@mtksdaap41> References: <1433164107-26568-1-git-send-email-eddie.huang@mediatek.com> <1433164107-26568-3-git-send-email-eddie.huang@mediatek.com> <20150608072725.GJ6325@pengutronix.de> <1433761837.31929.3.camel@mtksdaap41> Date: Mon, 8 Jun 2015 14:31:07 +0200 Message-ID: Subject: Re: [PATCH v2 2/2] arm64: dts: mt8173: Add I2C device node From: Matthias Brugger To: Eddie Huang Cc: Sascha Hauer , "devicetree@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" , "moderated list:ARM/Mediatek SoC..." Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 2015-06-08 13:10 GMT+02:00 Eddie Huang : > Hi Sascha, > > On Mon, 2015-06-08 at 09:27 +0200, Sascha Hauer wrote: >> Hi Eddie, >> >> On Mon, Jun 01, 2015 at 09:08:27PM +0800, Eddie Huang wrote: >> > Add MT8173 I2C device nodes, include I2C controllers and pins. >> > MT8173 has six I2C controllers, from i2c0 to i2c6, exclude i2c5. >> > The 6th I2C controller register base doesn't next to 5th I2C, >> > and there is a hardware between 5th and 6th I2C controller. So >> > SoC designer name 6th controller as "i2c6", not "i2c5". >> > >> > Signed-off-by: Eddie Huang >> > --- >> > arch/arm64/boot/dts/mediatek/mt8173.dtsi | 119 +++++++++++++++++++++++++++++++ >> > 1 file changed, 119 insertions(+) >> > >> > diff --git a/arch/arm64/boot/dts/mediatek/mt8173.dtsi b/arch/arm64/boot/dts/mediatek/mt8173.dtsi >> > index b52ec43..7003ed2 100644 >> > --- a/arch/arm64/boot/dts/mediatek/mt8173.dtsi >> > +++ b/arch/arm64/boot/dts/mediatek/mt8173.dtsi >> > @@ -158,6 +158,53 @@ >> > interrupts = , >> > , >> > ; >> > + i2c0_pins_a: i2c0@0 { >> > + pins1 { >> > + pinmux = , >> > + ; >> > + bias-disable; >> > + }; >> > + }; >> >> The pinmux nodes should be in the board dts, not in the SoC dtsi. >> > > These pins are fixed, and all boards using MT8173 SoC I2C controller > should use these pins. To reduce spread these to many board dts files, > so I put i2c pins in SoC dtsi. There might be boards with MT8173 which don't use the I2C controller, right? So this should not go into the SoC dtsi. For now, we just have one board dts file for MT8173, so I think we can put it in there. If in the future more boards get added, we can evaluate if it makes sense to share the I2C controller pins config between them. Thanks, Matthias -- motzblog.wordpress.com From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthias Brugger Subject: Re: [PATCH v2 2/2] arm64: dts: mt8173: Add I2C device node Date: Mon, 8 Jun 2015 14:31:07 +0200 Message-ID: References: <1433164107-26568-1-git-send-email-eddie.huang@mediatek.com> <1433164107-26568-3-git-send-email-eddie.huang@mediatek.com> <20150608072725.GJ6325@pengutronix.de> <1433761837.31929.3.camel@mtksdaap41> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: In-Reply-To: <1433761837.31929.3.camel@mtksdaap41> Sender: linux-kernel-owner@vger.kernel.org To: Eddie Huang Cc: Sascha Hauer , "devicetree@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" , "moderated list:ARM/Mediatek SoC..." List-Id: devicetree@vger.kernel.org 2015-06-08 13:10 GMT+02:00 Eddie Huang : > Hi Sascha, > > On Mon, 2015-06-08 at 09:27 +0200, Sascha Hauer wrote: >> Hi Eddie, >> >> On Mon, Jun 01, 2015 at 09:08:27PM +0800, Eddie Huang wrote: >> > Add MT8173 I2C device nodes, include I2C controllers and pins. >> > MT8173 has six I2C controllers, from i2c0 to i2c6, exclude i2c5. >> > The 6th I2C controller register base doesn't next to 5th I2C, >> > and there is a hardware between 5th and 6th I2C controller. So >> > SoC designer name 6th controller as "i2c6", not "i2c5". >> > >> > Signed-off-by: Eddie Huang >> > --- >> > arch/arm64/boot/dts/mediatek/mt8173.dtsi | 119 +++++++++++++++++++++++++++++++ >> > 1 file changed, 119 insertions(+) >> > >> > diff --git a/arch/arm64/boot/dts/mediatek/mt8173.dtsi b/arch/arm64/boot/dts/mediatek/mt8173.dtsi >> > index b52ec43..7003ed2 100644 >> > --- a/arch/arm64/boot/dts/mediatek/mt8173.dtsi >> > +++ b/arch/arm64/boot/dts/mediatek/mt8173.dtsi >> > @@ -158,6 +158,53 @@ >> > interrupts = , >> > , >> > ; >> > + i2c0_pins_a: i2c0@0 { >> > + pins1 { >> > + pinmux = , >> > + ; >> > + bias-disable; >> > + }; >> > + }; >> >> The pinmux nodes should be in the board dts, not in the SoC dtsi. >> > > These pins are fixed, and all boards using MT8173 SoC I2C controller > should use these pins. To reduce spread these to many board dts files, > so I put i2c pins in SoC dtsi. There might be boards with MT8173 which don't use the I2C controller, right? So this should not go into the SoC dtsi. For now, we just have one board dts file for MT8173, so I think we can put it in there. If in the future more boards get added, we can evaluate if it makes sense to share the I2C controller pins config between them. Thanks, Matthias -- motzblog.wordpress.com From mboxrd@z Thu Jan 1 00:00:00 1970 From: matthias.bgg@gmail.com (Matthias Brugger) Date: Mon, 8 Jun 2015 14:31:07 +0200 Subject: [PATCH v2 2/2] arm64: dts: mt8173: Add I2C device node In-Reply-To: <1433761837.31929.3.camel@mtksdaap41> References: <1433164107-26568-1-git-send-email-eddie.huang@mediatek.com> <1433164107-26568-3-git-send-email-eddie.huang@mediatek.com> <20150608072725.GJ6325@pengutronix.de> <1433761837.31929.3.camel@mtksdaap41> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org 2015-06-08 13:10 GMT+02:00 Eddie Huang : > Hi Sascha, > > On Mon, 2015-06-08 at 09:27 +0200, Sascha Hauer wrote: >> Hi Eddie, >> >> On Mon, Jun 01, 2015 at 09:08:27PM +0800, Eddie Huang wrote: >> > Add MT8173 I2C device nodes, include I2C controllers and pins. >> > MT8173 has six I2C controllers, from i2c0 to i2c6, exclude i2c5. >> > The 6th I2C controller register base doesn't next to 5th I2C, >> > and there is a hardware between 5th and 6th I2C controller. So >> > SoC designer name 6th controller as "i2c6", not "i2c5". >> > >> > Signed-off-by: Eddie Huang >> > --- >> > arch/arm64/boot/dts/mediatek/mt8173.dtsi | 119 +++++++++++++++++++++++++++++++ >> > 1 file changed, 119 insertions(+) >> > >> > diff --git a/arch/arm64/boot/dts/mediatek/mt8173.dtsi b/arch/arm64/boot/dts/mediatek/mt8173.dtsi >> > index b52ec43..7003ed2 100644 >> > --- a/arch/arm64/boot/dts/mediatek/mt8173.dtsi >> > +++ b/arch/arm64/boot/dts/mediatek/mt8173.dtsi >> > @@ -158,6 +158,53 @@ >> > interrupts = , >> > , >> > ; >> > + i2c0_pins_a: i2c0 at 0 { >> > + pins1 { >> > + pinmux = , >> > + ; >> > + bias-disable; >> > + }; >> > + }; >> >> The pinmux nodes should be in the board dts, not in the SoC dtsi. >> > > These pins are fixed, and all boards using MT8173 SoC I2C controller > should use these pins. To reduce spread these to many board dts files, > so I put i2c pins in SoC dtsi. There might be boards with MT8173 which don't use the I2C controller, right? So this should not go into the SoC dtsi. For now, we just have one board dts file for MT8173, so I think we can put it in there. If in the future more boards get added, we can evaluate if it makes sense to share the I2C controller pins config between them. Thanks, Matthias -- motzblog.wordpress.com