From: Antony Pavlov <antonynpavlov@gmail.com>
To: barebox@lists.infradead.org
Subject: [RFC 0/2] add multiplexed I2C bus support
Date: Wed, 18 Nov 2015 16:00:02 +0300 [thread overview]
Message-ID: <1447851604-18072-1-git-send-email-antonynpavlov@gmail.com> (raw)
This patchseries adds multiplexed I2C bus support to barebox
and a driver for pca954x bus multiplexer.
This series has the "RFC" status mostly because of these
adapter numbering hack in drivers/i2c/i2c-mux.c:
/* FIXME */
// priv->adap.nr = mux_dev->id;
priv->adap.nr = -1;
ret = i2c_add_numbered_adapter(&priv->adap);
Antony Pavlov (2):
i2c: import multiplexed I2C bus core support from linux kernel
i2c: add pca954x bus multiplexer driver
drivers/i2c/Kconfig | 9 ++
drivers/i2c/Makefile | 3 +-
drivers/i2c/i2c-mux.c | 118 ++++++++++++++++++++
drivers/i2c/muxes/Kconfig | 15 +++
drivers/i2c/muxes/Makefile | 4 +
drivers/i2c/muxes/pca954x.c | 254 ++++++++++++++++++++++++++++++++++++++++++++
include/i2c/i2c-mux.h | 40 +++++++
include/i2c/i2c.h | 19 +++-
8 files changed, 460 insertions(+), 2 deletions(-)
create mode 100644 drivers/i2c/i2c-mux.c
create mode 100644 drivers/i2c/muxes/Kconfig
create mode 100644 drivers/i2c/muxes/Makefile
create mode 100644 drivers/i2c/muxes/pca954x.c
create mode 100644 include/i2c/i2c-mux.h
--
2.6.2
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2015-11-18 13:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 13:00 Antony Pavlov [this message]
2015-11-18 13:00 ` [RFC 1/2] i2c: import multiplexed I2C bus core support from linux kernel Antony Pavlov
2015-11-18 13:00 ` [RFC 2/2] i2c: add pca954x bus multiplexer driver Antony Pavlov
2015-11-19 7:41 ` [RFC 0/2] add multiplexed I2C bus support Sascha Hauer
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=1447851604-18072-1-git-send-email-antonynpavlov@gmail.com \
--to=antonynpavlov@gmail.com \
--cc=barebox@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