Re: [PATCH v2 3/5] regulator: helper routine to extract regulator_init_data
From: Rajendra Nayak <hidden>
Date: 2011-10-24 08:54:00
Also in:
linux-arm-kernel, linux-omap, lkml
From: Rajendra Nayak <hidden>
Date: 2011-10-24 08:54:00
Also in:
linux-arm-kernel, linux-omap, lkml
On Monday 24 October 2011 01:47 PM, Grant Likely wrote:
On Mon, Oct 24, 2011 at 11:32:19AM +0530, Rajendra Nayak wrote:quoted
On Friday 21 October 2011 05:28 PM, Shawn Guo wrote:quoted
On Fri, Oct 21, 2011 at 02:11:55PM +0530, Rajendra Nayak wrote: [...]quoted
quoted
+ /* find device_node and attach it */ + rdev->dev.of_node = of_find_node_by_name(NULL, regulator_desc->name);
Shawn/Mark, How about the driver passing the of_node to be associated with the regulator, as part of regulator_desc, to the regulator core, instead of this complete DT search and the restriction of having to match DT node names with names in regulator_desc. regards, Rajendra
quoted
quoted
quoted
so would this do a complete dt search for every regulator?Yes, with the first param being NULL, tthe entire device tree will be searched.quoted
we would also need the driver names and dt names to match for this to work, right?Driver name does not matter. The key for this search to work is having regulator's name (regulator_desc->name) match device tree node's name, case ignored.Mark, whats your take on this? I am somehow not quite sure if we should have this limitation put in to match DT node names with whats in the driver structs (regulator_desc).This looks wrong to me. Matching based on node /name/, particularly when searching the entire tree, will cause problems. g.