From: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
To: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: avorontsov-hkdhdckH98+B+jHODAdFcQ@public.gmane.org,
ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org,
wg-ynQEQJNshbs@public.gmane.org
Subject: [PATCH 0/3] Automatically register i2c devices from the device tree
Date: Thu, 24 Jun 2010 14:11:44 -0600 [thread overview]
Message-ID: <20100624200509.10527.513.stgit@angua> (raw)
The following series adds automatic registration of i2c devices from
OF device tree data. If the i2c bus has the of_node pointer set, then
it will use that node pointer as the parent for a set of i2c devices and
automatically register the child nodes as new i2c devices.
When CONFIG_OF is not set, the of i2c hooks become empty stubs.
---
Grant Likely (3):
of/i2c: Generalize OF support
i2c: Add OF-style registration and binding
of: refactor of_modalias_node() and remove explicit match table.
arch/powerpc/platforms/83xx/mcu_mpc8349emitx.c | 6 ++
drivers/i2c/busses/i2c-cpm.c | 6 --
drivers/i2c/busses/i2c-ibm_iic.c | 4 --
drivers/i2c/busses/i2c-mpc.c | 2 -
drivers/i2c/i2c-core.c | 9 +++
drivers/mmc/host/mmc_spi.c | 8 +++
drivers/of/Kconfig | 2 -
drivers/of/base.c | 64 +++---------------------
drivers/of/of_i2c.c | 50 +++++++++++--------
include/linux/of_i2c.h | 13 ++++-
10 files changed, 75 insertions(+), 89 deletions(-)
next reply other threads:[~2010-06-24 20:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-24 20:11 Grant Likely [this message]
2010-06-24 20:11 ` [PATCH 1/3] of/i2c: Generalize OF support Grant Likely
2010-06-24 20:11 ` [PATCH 2/3] i2c: Add OF-style registration and binding Grant Likely
2010-06-24 20:12 ` [PATCH 3/3] of: refactor of_modalias_node() and remove explicit match table Grant Likely
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=20100624200509.10527.513.stgit@angua \
--to=grant.likely-s3s/wqlpoipyb63q8fvjnq@public.gmane.org \
--cc=avorontsov-hkdhdckH98+B+jHODAdFcQ@public.gmane.org \
--cc=ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=wg-ynQEQJNshbs@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