public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v5 0/2] i2c: sunxi: Support every i2c controller on each supported platform
Date: Wed, 15 Apr 2015 16:37:13 +0200	[thread overview]
Message-ID: <552E7799.1080004@redhat.com> (raw)
In-Reply-To: <1428700192-17784-1-git-send-email-contact@paulk.fr>

Hi,

On 10-04-15 23:09, Paul Kocialkowski wrote:
> Changes since v4:
> * Got rid of Kconfig after all
> * Only build mvtwsi when at least one controller is enabled on sunxi
> * Controller 0 doesn't have to be enabled in particular
>
> Changes since v3:
> * Kconfig support for MVTWSI
> * Only enable twsi0 by default for platforms that always use it for the AXP
> * Remove enabling other I2C busses by default on boards that expose them on pin
>    headers since those might be used for some other functionalities
>
> Changes since v2:
> * I2C/TWI busses enable for Cubietruck as well
>
> Changes since v1:
> * Kconfig option to enable I2C/TWI controllers 1-4 (when applicable)
> * Following patch to enable exposed busses on a few community-supported
>    single-board-computers
>
> This series adds support for every i2c controller found on
> sun4i/sun5i/sun6i/sun7i/sun8i platforms and shouldn't break support for Marvell
> platforms (orion5x, kirkwood, armada xp) the driver was originally written for.
>
> Regarding sunxi, I double-checked that this doesn't conflict with
> VIDEO_LCD_PANEL_I2C.
>
> I would be interested in having this tested on sun8i (A23), since I changed TWI0
> muxing (to PH2-PH3 instead of PB0-PB1), according to the user manual and what
> is being done on the upstream Linux kernel. I2C was either not working before,
> or it was being muxed correctly by the bootrom, probably to communicate with the
> AXP, which luckily made it work in U-Boot too, since the I/O base address was
> already correct.
>
> My use case here is that I'm writing a slave-side bitbang i2c implementation
> (with an Arduino) for a school project, using a Cubieboard2 as master and
> U-Boot as POC. However, only TWI1 was available through the expansion pins,
> hence the need for this series.
>

Thanks, merged into u-boot-sunxi/next with Heiko's ack for the first patch,

Regards,

Hans

      parent reply	other threads:[~2015-04-15 14:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-10 21:09 [U-Boot] [PATCH v5 0/2] i2c: sunxi: Support every i2c controller on each supported platform Paul Kocialkowski
2015-04-10 21:09 ` [U-Boot] [PATCH v5 1/2] i2c: mvtwsi: Support for up to 4 different controllers Paul Kocialkowski
2015-04-10 21:09 ` [U-Boot] [PATCH v5 2/2] sunxi: Complete i2c support for each supported platform Paul Kocialkowski
2015-04-14 14:36 ` [U-Boot] [PATCH v5 0/2] i2c: sunxi: Support every i2c controller on " Paul Kocialkowski
2015-04-15 14:37 ` Hans de Goede [this message]

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=552E7799.1080004@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=u-boot@lists.denx.de \
    /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