On Friday 16 September 2011 02:31 PM, Mark Brown wrote:
On Fri, Sep 16, 2011 at 12:49:17PM +0530, Rajendra Nayak wrote:
On Thursday 15 September 2011 07:20 PM, Mark Brown wrote:
On Thu, Sep 15, 2011 at 04:52:02PM +0530, Rajendra Nayak wrote:
+# For fixed voltage regulators
+- supply-name: Name of the regulator supply
+- microvolts: Output voltage of regulator
+- gpio: gpio to use for enable control
+- startup-delay: startup time in microseconds
+- enable-high: Polarity of enable GPIO, 1 = Active High, 0 = Active low
+- enabled-at-boot: 1 = yes, 0 = no
Much of this is specific to the Linux fixed voltage regulator driver
rather than a generic regulator with a fixed voltage.
So how should these non-generic things be handled through device
tree? Should they never be part of dt or should the bindings just be
defined such that its clear they are linux specific?
Having them be part of the fixed voltage regulator bindings would be
fine, the problem is that you're adding this in framework code not in a
driver.
agree, will make the bindings fixed voltage regulator specific.
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
