linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: stefan.wahren@i2se.com (Stefan Wahren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: imx23-olinuxino: Add i2c support
Date: Thu, 09 Apr 2015 11:20:10 +0200	[thread overview]
Message-ID: <5526444A.3060805@i2se.com> (raw)
In-Reply-To: <3f0efa88b69ea2e8eb22909b6fbe6f91@imap.cosmopool.net>

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.

Btw i read that Shawn only want used muxes [1].

[1] -
http://lists.infradead.org/pipermail/linux-arm-kernel/2012-August/115779.html

> Thanks,
> Harald

  reply	other threads:[~2015-04-09  9:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-08 17:45 [PATCH] ARM: dts: imx23-olinuxino: Add i2c support Harald Geyer
2015-04-08 22:12 ` Stefan Wahren
2015-04-08 22:43   ` harald at ccbib.org
2015-04-09  9:20     ` Stefan Wahren [this message]
2015-04-09 13:03       ` harald at ccbib.org
2015-04-09 16:34         ` Stefan Wahren
2015-04-10 17:37           ` Harald Geyer
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=5526444A.3060805@i2se.com \
    --to=stefan.wahren@i2se.com \
    --cc=linux-arm-kernel@lists.infradead.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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).