Thread (45 messages) 45 messages, 7 authors, 2012-10-03

Re: [PATCH v6 0/4] Runtime Interpreted Power Sequences

From: Alex Courbot <acourbot@nvidia.com>
Date: 2012-09-13 06:40:20
Also in: linux-devicetree, linux-tegra, lkml

On Thursday 13 September 2012 14:25:53 Mark Brown wrote:
On Thu, Sep 13, 2012 at 03:23:06PM +0900, Alex Courbot wrote:
quoted
I understand the logic behind handling powering sequences in the device
driver, but as we discussed for some classes of devices this might just
not
scale. I don't know how many different panels (each with different
powering
It would be sensible to make sure that the framework is done in such a
way that drivers can use it - there will be drivers (perhaps not display
ones) that have a known power sequence and which could benefit from the
ability to use library code to implement it based on the user simply
supplying named resources.
Not sure I understand what you mean, but things should be working this way 
already - regulators and PWMs are acquired by name using the standard 
regulator_get() and pwm_get() functions. GPIOs do not, AFAIK, have a way to be 
referenced by name so their number is used instead.

Alex.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help