From: Wolfram Sang <w.sang@pengutronix.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>,
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>,
Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: [PATCH v3 2/2] i2c/of: Automatically populate i2c mux busses from device tree data.
Date: Sun, 22 Apr 2012 18:20:08 +0200 [thread overview]
Message-ID: <20120422162008.GA4201@pengutronix.de> (raw)
In-Reply-To: <1334265263-13549-3-git-send-email-ddaney.cavm@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1373 bytes --]
On Thu, Apr 12, 2012 at 02:14:23PM -0700, David Daney wrote:
> From: David Daney <david.daney@cavium.com>
>
> For 'normal' i2c bus drivers, we can call of_i2c_register_devices()
> and have the device tree framework automatically populate the bus with
> the devices specified in the device tree.
>
> This patch adds a common code to the i2c mux framework to have the mux
> sub-busses be populated by the of_i2c_register_devices() too. If the
> mux device has an of_node, we populate the sub-bus' of_node so that
> the subsequent call to of_i2c_register_devices() will find the
> corresponding devices.
>
> It seemed better to put this logic in i2c_add_mux_adapter() rather
> than the individual mux drivers, as they will all probably want to do
> the same thing.
Both patches looking mostly good, two things here:
> + /*
> + * Try to get populate the mux adapter's of_node, expands to
"get populate"? I'd think you mean "populate" only, but am not sure
enough to fix it myself.
> + * nothing if !CONFIG_OF.
> + */
> + if (mux_dev->of_node) {
> + struct device_node *child;
> + u32 reg;
> + int ret;
We have a "ret" already in this function.
Regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-04-22 16:20 UTC|newest]
Thread overview: 10+ 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 ` [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
2012-04-22 16:20 ` Wolfram Sang [this message]
2012-04-23 16:48 ` David Daney
2012-04-23 16:58 ` Wolfram Sang
2012-04-23 17:04 ` David Daney
2012-04-23 17:11 ` Stephen Warren
2012-04-13 11:09 ` [PATCH v3 0/2] i2c/of: Populate multiplexed i2c busses from the device tree Lars-Peter Clausen
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=20120422162008.GA4201@pengutronix.de \
--to=w.sang@pengutronix.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=lars@metafoo.de \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.korsgaard@barco.com \
--cc=rob.herring@calxeda.com \
/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