From: David Daney <david.daney-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org>
To: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: David Daney <david.daney-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org>
Subject: [RFC PATCH 0/2] i2c/of: Populate multiplexed i2c busses from the device tree.
Date: Wed, 24 Aug 2011 17:25:54 -0700 [thread overview]
Message-ID: <1314231956-21115-1-git-send-email-david.daney@cavium.com> (raw)
We need to populate our I2C devices from the device tree, but some of
our systems have multiplexers which currently break this process.
The basic idea is to have the generic i2c-mux framework propagate the
device_node for the child bus into the corresponding i2c_adapter, and
then call of_i2c_register_devices(). This means that the device tree
bindings for *all* i2c muxes must have some common properties. I try
to document these in mux.txt.
At this point it is an RFC because the patches are against an old
kernel. Once we agree on how this should look, I will test them
against a current kernel.
Any feedback on the approach and/or specific bindings is most welcome.
David Daney (2):
i2c: Add a struct device * parameter to i2c_add_mux_adapter()
i2c/of: Automatically populate i2c mux busses from device tree data.
Documentation/devicetree/bindings/i2c/mux.txt | 54 +++++++++++++++++++++++++
drivers/i2c/i2c-mux.c | 44 ++++++++++++++++----
drivers/i2c/muxes/gpio-i2cmux.c | 3 +-
drivers/i2c/muxes/pca9541.c | 3 +-
drivers/i2c/muxes/pca954x.c | 2 +-
include/linux/i2c-mux.h | 3 +-
6 files changed, 96 insertions(+), 13 deletions(-)
create mode 100644 Documentation/devicetree/bindings/i2c/mux.txt
--
1.7.2.3
next reply other threads:[~2011-08-25 0:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-25 0:25 David Daney [this message]
2011-08-25 0:25 ` [RFC PATCH 1/2] i2c: Add a struct device * parameter to i2c_add_mux_adapter() David Daney
2011-08-25 0:25 ` [RFC PATCH 2/2] i2c/of: Automatically populate i2c mux busses from device tree data David Daney
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=1314231956-21115-1-git-send-email-david.daney@cavium.com \
--to=david.daney-ygcgfspz5w/qt0dzr+alfa@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@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: 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).