[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20111024081706.GC8708@ponder.secretlab.ca>
Date: Mon, 24 Oct 2011 10:17:06 +0200
From: Grant Likely <grant.likely@...retlab.ca>
To: Rajendra Nayak <rnayak@...com>
Cc: Shawn Guo <shawn.guo@...escale.com>,
broonie@...nsource.wolfsonmicro.com, patches@...aro.org,
tony@...mide.com, devicetree-discuss@...ts.ozlabs.org,
linux-kernel@...r.kernel.org, linux-omap@...r.kernel.org,
lrg@...com, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v2 3/5] regulator: helper routine to extract
regulator_init_data
On Mon, Oct 24, 2011 at 11:32:19AM +0530, Rajendra Nayak wrote:
> On Friday 21 October 2011 05:28 PM, Shawn Guo wrote:
> >On Fri, Oct 21, 2011 at 02:11:55PM +0530, Rajendra Nayak wrote:
> >[...]
> >>>+ /* find device_node and attach it */
> >>>+ rdev->dev.of_node = of_find_node_by_name(NULL, regulator_desc->name);
> >>
> >>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.
> >
> >>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.
--
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