From: <harald-95f8Dae0BrPYtjvyW6yDsg@public.gmane.org> To: Stefan Wahren <stefan.wahren-eS4NqCHxEME@public.gmane.org> Cc: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Sascha Hauer <kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>, Shawn Guo <shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>, Fabio.Estevam-KZfg59tc24xl57MIdRCFDg@public.gmane.org, linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org Subject: Re: [PATCH] ARM: dts: imx23-olinuxino: Add i2c support Date: Thu, 09 Apr 2015 15:03:40 +0200 [thread overview] Message-ID: <d8d27c22eb78aed693a977b88ebcc327@imap.cosmopool.net> (raw) In-Reply-To: <5526444A.3060805-eS4NqCHxEME@public.gmane.org> Hi Stefan! On Thu, 09 Apr 2015 11:20:10 +0200, Stefan Wahren <stefan.wahren-eS4NqCHxEME@public.gmane.org> wrote: > Hi Harald, > >>>> This patch provides the necessary devicetree code. >>>> Tested with MOD-LCD1x9 from Olimex. >>>> >>>> This patch is based on work by Fadil Berisha with his permission. >> However >>>> all bugs are mine. >>>> >>>> Signed-off-by: Harald Geyer <harald-95f8Dae0BrPYtjvyW6yDsg@public.gmane.org> >>>> --- >>>> arch/arm/boot/dts/imx23-olinuxino.dts | 6 +++++ >>>> arch/arm/boot/dts/imx23.dtsi | 40 ++++++++++++++++++++++++++++++++- >>>> 2 files changed, 45 insertions(+), 1 deletion(-) >>>> >>>> [...] >>>> --- a/arch/arm/boot/dts/imx23.dtsi >>>> +++ b/arch/arm/boot/dts/imx23.dtsi >>>> @@ -308,6 +308,39 @@ >>>> fsl,voltage = <MXS_VOLTAGE_HIGH>; >>>> fsl,pull-up = <MXS_PULL_ENABLE>; >>>> }; >>>> + >>>> + i2c_pins_a: i2c@0 { >>>> + reg = <0>; >>>> + fsl,pinmux-ids = < >>>> + MX23_PAD_I2C_SCL__I2C_SCL >>>> + MX23_PAD_I2C_SDA__I2C_SDA >>>> + >; >>>> + fsl,drive-strength = <MXS_DRIVE_8mA>; >>>> + fsl,voltage = <MXS_VOLTAGE_HIGH>; >>>> + fsl,pull-up = <MXS_PULL_ENABLE>; >>>> + }; >>>> + >>>> + i2c_pins_b: i2c@1 { >>>> + reg = <1>; >>>> + fsl,pinmux-ids = < >>>> + MX23_PAD_LCD_ENABLE__I2C_SCL >>>> + MX23_PAD_LCD_HSYNC__I2C_SDA >>>> + >; >>>> + fsl,drive-strength = <MXS_DRIVE_8mA>; >>>> + fsl,voltage = <MXS_VOLTAGE_HIGH>; >>>> + fsl,pull-up = <MXS_PULL_ENABLE>; >>>> + }; >>>> + >>>> + i2c_pins_c: i2c@2 { >>>> + reg = <2>; >>>> + fsl,pinmux-ids = < >>>> + MX23_PAD_SSP1_DATA1__I2C_SCL >>>> + MX23_PAD_SSP1_DATA2__I2C_SDA >>>> + >; >>>> + fsl,drive-strength = <MXS_DRIVE_8mA>; >>>> + fsl,voltage = <MXS_VOLTAGE_HIGH>; >>>> + fsl,pull-up = <MXS_PULL_ENABLE>; >>>> + }; >>> Please add only i2c_pins_b because this pin muxing is the only used one. >> I disagree: Having all possible i2c pin groups documented in devicetree >> is >> a good thing. Also imx23.dtsi is more general then olinuxino - somebody >> might produce a imx23 based board where one of the other pin groups makes >> more sense to use. Well, even on olinuxino somebody might use i2c_pins_a >> if they don't need an UART, but use an LCD. > > Sure. But this 2 additional muxes have nothing to do with adding i2c > support to olinuxino and should be a separate patch. In case of a revert > of this patch the other i.MX23 boards are also affected. So i think it > should be a separate patch. If it is prefered, I will split the changes to imx23.dtsi and imx23-olinuxino.dts into two patches. > Btw i read that Shawn only want used muxes [1]. > > [1] - > http://lists.infradead.org/pipermail/linux-arm-kernel/2012-August/115779.html If that is an issue, then I'll just test all three pin groups on my olinuxino board. After all it would be really awkward to have only one pin group and that one is labeled "i2c_pins_b" ... Thanks, Harald -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: harald@ccbib.org (harald at ccbib.org) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH] ARM: dts: imx23-olinuxino: Add i2c support Date: Thu, 09 Apr 2015 15:03:40 +0200 [thread overview] Message-ID: <d8d27c22eb78aed693a977b88ebcc327@imap.cosmopool.net> (raw) In-Reply-To: <5526444A.3060805@i2se.com> Hi Stefan! On Thu, 09 Apr 2015 11:20:10 +0200, Stefan Wahren <stefan.wahren@i2se.com> wrote: > Hi Harald, > >>>> This patch provides the necessary devicetree code. >>>> Tested with MOD-LCD1x9 from Olimex. >>>> >>>> This patch is based on work by Fadil Berisha with his permission. >> However >>>> all bugs are mine. >>>> >>>> Signed-off-by: Harald Geyer <harald@ccbib.org> >>>> --- >>>> arch/arm/boot/dts/imx23-olinuxino.dts | 6 +++++ >>>> arch/arm/boot/dts/imx23.dtsi | 40 ++++++++++++++++++++++++++++++++- >>>> 2 files changed, 45 insertions(+), 1 deletion(-) >>>> >>>> [...] >>>> --- a/arch/arm/boot/dts/imx23.dtsi >>>> +++ b/arch/arm/boot/dts/imx23.dtsi >>>> @@ -308,6 +308,39 @@ >>>> fsl,voltage = <MXS_VOLTAGE_HIGH>; >>>> fsl,pull-up = <MXS_PULL_ENABLE>; >>>> }; >>>> + >>>> + i2c_pins_a: i2c at 0 { >>>> + reg = <0>; >>>> + fsl,pinmux-ids = < >>>> + MX23_PAD_I2C_SCL__I2C_SCL >>>> + MX23_PAD_I2C_SDA__I2C_SDA >>>> + >; >>>> + fsl,drive-strength = <MXS_DRIVE_8mA>; >>>> + fsl,voltage = <MXS_VOLTAGE_HIGH>; >>>> + fsl,pull-up = <MXS_PULL_ENABLE>; >>>> + }; >>>> + >>>> + i2c_pins_b: i2c at 1 { >>>> + reg = <1>; >>>> + fsl,pinmux-ids = < >>>> + MX23_PAD_LCD_ENABLE__I2C_SCL >>>> + MX23_PAD_LCD_HSYNC__I2C_SDA >>>> + >; >>>> + fsl,drive-strength = <MXS_DRIVE_8mA>; >>>> + fsl,voltage = <MXS_VOLTAGE_HIGH>; >>>> + fsl,pull-up = <MXS_PULL_ENABLE>; >>>> + }; >>>> + >>>> + i2c_pins_c: i2c at 2 { >>>> + reg = <2>; >>>> + fsl,pinmux-ids = < >>>> + MX23_PAD_SSP1_DATA1__I2C_SCL >>>> + MX23_PAD_SSP1_DATA2__I2C_SDA >>>> + >; >>>> + fsl,drive-strength = <MXS_DRIVE_8mA>; >>>> + fsl,voltage = <MXS_VOLTAGE_HIGH>; >>>> + fsl,pull-up = <MXS_PULL_ENABLE>; >>>> + }; >>> Please add only i2c_pins_b because this pin muxing is the only used one. >> I disagree: Having all possible i2c pin groups documented in devicetree >> is >> a good thing. Also imx23.dtsi is more general then olinuxino - somebody >> might produce a imx23 based board where one of the other pin groups makes >> more sense to use. Well, even on olinuxino somebody might use i2c_pins_a >> if they don't need an UART, but use an LCD. > > Sure. But this 2 additional muxes have nothing to do with adding i2c > support to olinuxino and should be a separate patch. In case of a revert > of this patch the other i.MX23 boards are also affected. So i think it > should be a separate patch. If it is prefered, I will split the changes to imx23.dtsi and imx23-olinuxino.dts into two patches. > Btw i read that Shawn only want used muxes [1]. > > [1] - > http://lists.infradead.org/pipermail/linux-arm-kernel/2012-August/115779.html If that is an issue, then I'll just test all three pin groups on my olinuxino board. After all it would be really awkward to have only one pin group and that one is labeled "i2c_pins_b" ... Thanks, Harald
next prev parent reply other threads:[~2015-04-09 13:03 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-04-08 17:45 [PATCH] ARM: dts: imx23-olinuxino: Add i2c support Harald Geyer [not found] ` <1428515100-1496-1-git-send-email-harald-95f8Dae0BrPYtjvyW6yDsg@public.gmane.org> 2015-04-08 22:12 ` Stefan Wahren 2015-04-08 22:12 ` Stefan Wahren 2015-04-08 22:43 ` harald 2015-04-08 22:43 ` harald at ccbib.org [not found] ` <3f0efa88b69ea2e8eb22909b6fbe6f91-VlVdRp1qTtWC18heOpxMWqxOck334EZe@public.gmane.org> 2015-04-09 9:20 ` Stefan Wahren 2015-04-09 9:20 ` Stefan Wahren [not found] ` <5526444A.3060805-eS4NqCHxEME@public.gmane.org> 2015-04-09 13:03 ` harald-95f8Dae0BrPYtjvyW6yDsg [this message] 2015-04-09 13:03 ` harald at ccbib.org [not found] ` <d8d27c22eb78aed693a977b88ebcc327-VlVdRp1qTtWC18heOpxMWqxOck334EZe@public.gmane.org> 2015-04-09 16:34 ` Stefan Wahren 2015-04-09 16:34 ` Stefan Wahren [not found] ` <1893593729.135182.1428597263856.JavaMail.open-xchange-h4m1HHXQYNFuz1KIG1bTI8gmgJlYmuWJ@public.gmane.org> 2015-04-10 17:37 ` Harald Geyer 2015-04-10 17:37 ` Harald Geyer [not found] ` <1158701263.68321.1428531175931.JavaMail.open-xchange-h4m1HHXQYNGvCDav5jC2oMgmgJlYmuWJ@public.gmane.org> 2015-04-08 22:52 ` Fabio Estevam 2015-04-08 22:52 ` Fabio Estevam
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=d8d27c22eb78aed693a977b88ebcc327@imap.cosmopool.net \ --to=harald-95f8dae0brpytjvyw6ydsg@public.gmane.org \ --cc=Fabio.Estevam-KZfg59tc24xl57MIdRCFDg@public.gmane.org \ --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \ --cc=kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \ --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \ --cc=shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \ --cc=stefan.wahren-eS4NqCHxEME@public.gmane.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.