Thread (89 messages) 89 messages, 5 authors, 2011-10-25

[PATCH v2 3/5] regulator: helper routine to extract regulator_init_data

From: Shawn Guo <hidden>
Date: 2011-10-24 13:36:39
Also in: linux-devicetree, linux-omap, lkml

On Mon, Oct 24, 2011 at 02:43:58PM +0530, Rajendra Nayak wrote:
Case 2:
One device for all regulators:

DT nodes look something like this

regulators {
	reg1: reg at 1 {
			...
			...
	};

	reg2: reg at 2 {
			...
			...
	};
};

The regulator driver probes only one device and the dev->of_node
points to the "regulators" node above.
The mc13892 example I put in the reply to Grant demonstrates that
for some case, dev->of_node is NULL (devices are created by mfd core).
The regulator driver then based on compatible property extracts
and registers all the child nodes of "regulators" (for ex: reg1, reg2
above) with each call to regulator_register and passes the child nodes
as of_node to be associated with the regulator device.
I still think the discovery of all the child nodes of "regulators" does
not necessarily need to be done in regulator driver.  Instead, it can
be done in regulator core.

-- 
Regards,
Shawn
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help