[PATCH 8/9] regulator: helper to extract regulator node based on supply name
From: Cousson, Benoit <hidden>
Date: 2011-09-28 08:09:30
Also in:
linux-devicetree, linux-omap
From: Cousson, Benoit <hidden>
Date: 2011-09-28 08:09:30
Also in:
linux-devicetree, linux-omap
On 9/27/2011 8:59 PM, Mark Brown wrote:
On Tue, Sep 27, 2011 at 08:19:37PM +0530, Rajendra Nayak wrote:quoted
On Tuesday 27 September 2011 05:51 PM, Mark Brown wrote:quoted
On Tue, Sep 27, 2011 at 03:42:51PM +0530, Rajendra Nayak wrote:quoted
quoted
quoted
+ if (!dev) + return NULL;quoted
quoted
So how do we handle CPUs? cpufreq is one of the most active users of regulators...quoted
Hmm, never thought of it :( Maybe I should associate a supply name with all regulators and then lookup from the global registered list.I'm not sure how this should work in a device tree world, I'd *hope* we'd get a device tree node for the CPU and could then just make this a regular consumer thing but then the cpufreq drivers would need to be updated to make use of it. The only reason we allow null devices right now is the fact that cpufreq doesn't have a struct device it can use.
That's why we do have a MPU node in OMAP dts, in order to build an omap_device that will be mainly used for the DVFS on the MPU. And even before DT migration, we used to build statically some omap_device to represent the various processors in the system (MPU, DSP, CortexM3...). Regards, Benoit