linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: l.stach@pengutronix.de (Lucas Stach)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 3/3] ARM: tegra: correct Colibri T20 regulator settings
Date: Wed, 04 Dec 2013 12:52:45 +0100	[thread overview]
Message-ID: <1386157965.4066.1.camel@weser.hi.pengutronix.de> (raw)
In-Reply-To: <fc7440a2f4bf9ab95e47a911c0e0b3b6a2250356.1386108712.git.stefan@agner.ch>

Am Dienstag, den 03.12.2013, 23:18 +0100 schrieb Stefan Agner:
> Set the parent of the regulators LDO2 to LDO9 according to the
> schematic. Set the base voltage to 3.3V, there is only 3.3V on the
> module itself.
> 
> Set the Core and CPU voltage to the specified voltages of 1.2V and
> 1.0V respectivly.
> 
> LDO6 should deliver 2.85V. The attached peripherals were not in
> use so far.
> 
> Signed-off-by: Stefan Agner <stefan@agner.ch>
Reviewed-by: Lucas Stach <l.stach@pengutronix.de>

> ---
>  arch/arm/boot/dts/tegra20-colibri-512.dtsi | 30 +++++++++++++++---------------
>  1 file changed, 15 insertions(+), 15 deletions(-)
> 
> diff --git a/arch/arm/boot/dts/tegra20-colibri-512.dtsi b/arch/arm/boot/dts/tegra20-colibri-512.dtsi
> index cbe89ff..51e0880 100644
> --- a/arch/arm/boot/dts/tegra20-colibri-512.dtsi
> +++ b/arch/arm/boot/dts/tegra20-colibri-512.dtsi
> @@ -225,15 +225,15 @@
>  			#gpio-cells = <2>;
>  			gpio-controller;
>  
> -			sys-supply = <&vdd_5v0_reg>;
> +			sys-supply = <&vdd_3v3_reg>;
>  			vin-sm0-supply = <&sys_reg>;
>  			vin-sm1-supply = <&sys_reg>;
>  			vin-sm2-supply = <&sys_reg>;
>  			vinldo01-supply = <&sm2_reg>;
> -			vinldo23-supply = <&sm2_reg>;
> -			vinldo4-supply = <&sm2_reg>;
> -			vinldo678-supply = <&sm2_reg>;
> -			vinldo9-supply = <&sm2_reg>;
> +			vinldo23-supply = <&vdd_3v3_reg>;
> +			vinldo4-supply = <&vdd_3v3_reg>;
> +			vinldo678-supply = <&vdd_3v3_reg>;
> +			vinldo9-supply = <&vdd_3v3_reg>;
>  
>  			regulators {
>  				#address-cells = <1>;
> @@ -250,8 +250,8 @@
>  					reg = <1>;
>  					regulator-compatible = "sm0";
>  					regulator-name = "vdd_sm0,vdd_core";
> -					regulator-min-microvolt = <1275000>;
> -					regulator-max-microvolt = <1275000>;
> +					regulator-min-microvolt = <1200000>;
> +					regulator-max-microvolt = <1200000>;
>  					regulator-always-on;
>  				};
>  
> @@ -259,8 +259,8 @@
>  					reg = <2>;
>  					regulator-compatible = "sm1";
>  					regulator-name = "vdd_sm1,vdd_cpu";
> -					regulator-min-microvolt = <1100000>;
> -					regulator-max-microvolt = <1100000>;
> +					regulator-min-microvolt = <1000000>;
> +					regulator-max-microvolt = <1000000>;
>  					regulator-always-on;
>  				};
>  
> @@ -316,8 +316,8 @@
>  					reg = <10>;
>  					regulator-compatible = "ldo6";
>  					regulator-name = "vdd_ldo6,avdd_vdac,vddio_vi,vddio_cam";
> -					regulator-min-microvolt = <1800000>;
> -					regulator-max-microvolt = <1800000>;
> +					regulator-min-microvolt = <2850000>;
> +					regulator-max-microvolt = <2850000>;
>  				};
>  
>  				hdmi_vdd_reg: regulator at 11 {
> @@ -504,12 +504,12 @@
>  		#address-cells = <1>;
>  		#size-cells = <0>;
>  
> -		vdd_5v0_reg: regulator at 100 {
> +		vdd_3v3_reg: regulator at 100 {
>  			compatible = "regulator-fixed";
>  			reg = <100>;
> -			regulator-name = "vdd_5v0";
> -			regulator-min-microvolt = <5000000>;
> -			regulator-max-microvolt = <5000000>;
> +			regulator-name = "vdd_3v3";
> +			regulator-min-microvolt = <3300000>;
> +			regulator-max-microvolt = <3300000>;
>  			regulator-always-on;
>  		};
>  

-- 
Pengutronix e.K.                           | Lucas Stach                 |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-5076 |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  reply	other threads:[~2013-12-04 11:52 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-03 22:18 [PATCH v4 0/3] regulator: tps6586x: add version detection and voltage tables Stefan Agner
2013-12-03 22:18 ` [PATCH v4 1/3] mfd: tps6586x: add version detection Stefan Agner
2013-12-04  8:10   ` Lee Jones
2013-12-04  8:40     ` Stefan Agner
2013-12-04 10:07       ` Lee Jones
2013-12-04 11:38         ` Stefan Agner
2013-12-04 11:48           ` Lee Jones
2013-12-04 11:49         ` Mark Brown
2013-12-04 11:58           ` Lee Jones
2013-12-05 17:06   ` Stephen Warren
2013-12-05 17:43     ` Stefan Agner
2013-12-05 17:40       ` Stephen Warren
2013-12-05 22:56         ` Stefan Agner
2013-12-06  8:44           ` Lee Jones
2013-12-03 22:18 ` [PATCH v4 2/3] regulator: tps6586x: add and use correct voltage table Stefan Agner
2013-12-04  9:48   ` Thierry Reding
2013-12-04 12:14   ` Mark Brown
2013-12-04 14:17     ` Stefan Agner
2013-12-04 14:29       ` Mark Brown
2013-12-04 14:40         ` Lee Jones
2013-12-05 17:10   ` Stephen Warren
2013-12-03 22:18 ` [PATCH v4 3/3] ARM: tegra: correct Colibri T20 regulator settings Stefan Agner
2013-12-04 11:52   ` Lucas Stach [this message]
2013-12-05 17:12   ` Stephen Warren
2013-12-05 17:33     ` Stefan Agner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1386157965.4066.1.camel@weser.hi.pengutronix.de \
    --to=l.stach@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).