linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: ipaton0@gmail.com (Iain Paton)
To: linux-arm-kernel@lists.infradead.org
Subject: [linux-sunxi] [PATCH 3/3] sunxi: A20-OLinuXino-LIME2: Add i2c2 bus in DTS
Date: Sat, 26 Mar 2016 00:48:44 +0000	[thread overview]
Message-ID: <56F5DC6C.4070005@gmail.com> (raw)
In-Reply-To: <1458932647-24268-3-git-send-email-haas@computerlinguist.org>

On 25/03/16 19:04, Michael Haas wrote:
> The A20 processor provides a third I2C bus on pins PB20 and PB21.
> The A20-OLinuXino-LIME2 exposes this bus via its GPIO1 port.
> 
> Olimex also provide a breakout board called the
> A20-OLinuXino-LIME2-UEXT. This change is required to properly
> support I2C on the UEXT connector found there.
> 
> Signed-off-by: Michael Haas <haas@computerlinguist.org>

Acked-by: Iain Paton <ipaton0@gmail.com>

This didn't go in originally simply because not everyone will have 
the breakout and they may want to use those pins for other things.

  reply	other threads:[~2016-03-26  0:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-25 19:04 [PATCH 1/3] sunxi: A20-OLinuXino-LIME2: Fix ldo3/ldo4 in DTS Michael Haas
2016-03-25 19:04 ` [PATCH 2/3] sunxi: A20-OLinuXino-LIME2: Add usb-power-supply Michael Haas
2016-03-26  0:48   ` [linux-sunxi] " Iain Paton
2016-04-02 10:36   ` Maxime Ripard
2016-05-01  6:46     ` [linux-sunxi] " Michael Haas
2016-05-02 11:07       ` Maxime Ripard
2016-03-25 19:04 ` [PATCH 3/3] sunxi: A20-OLinuXino-LIME2: Add i2c2 bus in DTS Michael Haas
2016-03-26  0:48   ` Iain Paton [this message]
2016-04-02 10:34   ` Maxime Ripard
2016-04-02 14:42     ` [linux-sunxi] " Priit Laes
2016-04-02 16:21     ` Michael Haas
2016-04-10 10:32       ` Maxime Ripard
2016-03-26  0:58 ` [linux-sunxi] [PATCH 1/3] sunxi: A20-OLinuXino-LIME2: Fix ldo3/ldo4 " Iain Paton
2016-03-26  8:56   ` Iain Paton
2016-03-27  8:08     ` Michael Haas
2016-03-28 13:01       ` Hans de Goede
2016-03-29 12:03         ` Maxime Ripard

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=56F5DC6C.4070005@gmail.com \
    --to=ipaton0@gmail.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).