[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4F958D5E.9090003@wwwdotorg.org>
Date: Mon, 23 Apr 2012 11:11:58 -0600
From: Stephen Warren <swarren@...dotorg.org>
To: David Daney <ddaney.cavm@...il.com>
CC: Grant Likely <grant.likely@...retlab.ca>,
devicetree-discuss@...ts.ozlabs.org,
"Jean Delvare (PC drivers core)" <khali@...ux-fr.org>,
"Ben Dooks (embedded platforms)" <ben-linux@...ff.org>,
"Wolfram Sang (embedded platforms)" <w.sang@...gutronix.de>,
Peter Korsgaard <peter.korsgaard@...co.com>,
Guenter Roeck <guenter.roeck@...csson.com>,
linux-i2c@...r.kernel.org, Rob Herring <rob.herring@...xeda.com>,
Lars-Peter Clausen <lars@...afoo.de>,
linux-kernel@...r.kernel.org, David Daney <david.daney@...ium.com>
Subject: Re: [PATCH v3 2/2] i2c/of: Automatically populate i2c mux busses
from device tree data.
On 04/12/2012 03:14 PM, David Daney wrote:
> From: David Daney <david.daney@...ium.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.
>
> Signed-off-by: David Daney <david.daney@...ium.com>
> Cc: Lars-Peter Clausen <lars@...afoo.de>
Acked-by: Stephen Warren <swarren@...dotorg.org>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists