On Saturday 23 June 2012 04:44 AM, Stephen Warren wrote:
From: Stephen Warren<[email protected]>
Seaboard uses a TPS6586x regulator. Instantiate this, and hook up a
couple of fixed GPIO-controlled regulators too.
The regulator configurations were mostly taken from the ChromeOS 3.2
kernel. Exceptions are:
* The schematic lists a fixed voltage for each rail, whereas the ChromeOS
kernel lists a range for many rails. I used the values from the ChromeOS
kernel in all cases, since I know the board file there is the most
complete available for this hardware.
* The vdd_1v2 fixed regulator is present only in the schematic. So, I added
this based on the schematic.
* A 3.3v fixed regulator using GPIO3 of the TPS6586x is present in the
ChromeOS kernel, but not in the schematic. So, I dropped this based on
the schematic.
Signed-off-by: Stephen Warren<[email protected]>
---
Acked-by: Laxman Dewangan <[email protected]>
I think this series very much depends on the series
[PATCH V3 0/3] regulator: dt: add policy to match regulator with prop
"regulator-compatible"
+ regulator@3 {
+ reg =<3>;
+ regulator-compatible = "ldo0";
+ regulator-name = "vdd_ldo0";
+ regulator-min-microvolt =<1250000>;
+ regulator-max-microvolt =<3300000>;
+ vin-supply =<&sm2_reg>;
I think support for vin-supply is still not there for this regulator in
driver.
--
To unsubscribe from this list: send the line "unsubscribe linux-tegra" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
