From: Lars-Peter Clausen <lars@metafoo.de>
To: David Daney <ddaney.cavm@gmail.com>
Cc: Grant Likely <grant.likely@secretlab.ca>,
devicetree-discuss@lists.ozlabs.org,
"Jean Delvare (PC drivers core)" <khali@linux-fr.org>,
"Ben Dooks (embedded platforms)" <ben-linux@fluff.org>,
Wolfram Sang <w.sang@pengutronix.de>,
Peter Korsgaard <peter.korsgaard@barco.com>,
Guenter Roeck <guenter.roeck@ericsson.com>,
linux-i2c@vger.kernel.org, Rob Herring <rob.herring@calxeda.com>,
linux-kernel@vger.kernel.org,
David Daney <david.daney@cavium.com>
Subject: Re: [PATCH v3 0/2] i2c/of: Populate multiplexed i2c busses from the device tree.
Date: Fri, 13 Apr 2012 13:09:20 +0200 [thread overview]
Message-ID: <4F880960.8010803@metafoo.de> (raw)
In-Reply-To: <1334265263-13549-1-git-send-email-ddaney.cavm@gmail.com>
On 04/12/2012 11:14 PM, David Daney wrote:
> From: David Daney <david.daney@cavium.com>
>
> v3: Integrate changes from Lars-Peter Clausen to make better use of
> the of_*() infrastructure. Get rid of ugly #ifdefs.
>
> v2: Update bindings to use "reg" insutead of "cell-index"
>
> v1: Unchanged from the original RFC where I said:
>
> 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.
>
> This is now tested against 3.4-rc2 and is still working well.
>
I've been using these patches with a pca9548 and a pca9546 for a while now.
Both:
Tested-by: Lars-Peter Clausen <lars@metafoo.de>
next prev parent reply other threads:[~2012-04-13 11:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-12 21:14 [PATCH v3 0/2] i2c/of: Populate multiplexed i2c busses from the device tree David Daney
2012-04-12 21:14 ` David Daney
2012-04-12 21:14 ` [PATCH v3 1/2] i2c: Add a struct device * parameter to i2c_add_mux_adapter() David Daney
2012-04-12 21:14 ` [PATCH v3 2/2] i2c/of: Automatically populate i2c mux busses from device tree data David Daney
[not found] ` <1334265263-13549-3-git-send-email-ddaney.cavm-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-04-22 16:20 ` Wolfram Sang
2012-04-22 16:20 ` Wolfram Sang
[not found] ` <20120422162008.GA4201-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2012-04-23 16:48 ` David Daney
2012-04-23 16:48 ` David Daney
[not found] ` <4F9587E8.1050702-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-04-23 16:58 ` Wolfram Sang
2012-04-23 16:58 ` Wolfram Sang
[not found] ` <20120423165847.GF27321-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2012-04-23 17:04 ` David Daney
2012-04-23 17:04 ` David Daney
2012-04-23 17:11 ` Stephen Warren
2012-04-23 17:11 ` Stephen Warren
2012-04-13 11:09 ` Lars-Peter Clausen [this message]
[not found] ` <4F880960.8010803-Qo5EllUWu/uELgA04lAiVw@public.gmane.org>
2012-04-23 17:58 ` [PATCH v3 0/2] i2c/of: Populate multiplexed i2c busses from the device tree Wolfram Sang
2012-04-23 17:58 ` Wolfram Sang
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=4F880960.8010803@metafoo.de \
--to=lars@metafoo.de \
--cc=ben-linux@fluff.org \
--cc=david.daney@cavium.com \
--cc=ddaney.cavm@gmail.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=guenter.roeck@ericsson.com \
--cc=khali@linux-fr.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.korsgaard@barco.com \
--cc=rob.herring@calxeda.com \
--cc=w.sang@pengutronix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.