From: Nishanth Menon <nm@ti.com>
To: "Tony Lindgren" <tony@atomide.com>,
"Benoît Cousson" <bcousson@baylibre.com>
Cc: <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-omap@vger.kernel.org>,
Tomi Valkeinen <tomi.valkeinen@ti.com>
Subject: Re: [PATCH] ARM: dts: am57xx-beagle-x15: Update Phy supplies
Date: Wed, 16 Sep 2015 10:11:12 -0500 [thread overview]
Message-ID: <55F98690.6070601@ti.com> (raw)
In-Reply-To: <1441308226-26690-1-git-send-email-nm@ti.com>
Hi Tony,
On 09/03/2015 02:23 PM, Nishanth Menon wrote:
> Originally, all the SoC PHY rails were supplied by LDO3. However, as a
> result of characterization, it was determined that this posed a risk in
> extreme load conditions. Hence the PHY rails are split between two
> different LDOs. Update the related node as a result
>
> LDO3/VDDA_1V8_PHYA supplies vdda_usb1, vdda_usb2, vdda_sata, vdda_usb3
> LDO4/VDDA_1V8_PHYB supplies vdda_pcie1, vdda_pcie0, vdda_hdmi, vdda_pcie
>
> NOTE: We break compatibility with pre-production boards with this change
> since, the PMIC LDO4 is disabled at OTP level.
>
> The new configuration is the plan of record and all pre-production
> boards are supposed to be replaced with the latest boards matching the
> mentioned configuration.
>
> Signed-off-by: Nishanth Menon <nm@ti.com>
> ---
Gentle ping. Some very few 10 something boards have been created and
stopped production till the latest modifications were done (PMIC USB
interrupt, LDO4 etc) - and all of those boards are now getting
scrapped.. If there are any (as per tracking information, there should
not be any), TI should be contacted to have them replaced.
Is it possible for us to consider this patch in 4.3 cycle - given that
we are this close, might have been great to see 4.3 vanilla function on
the production platform.
> arch/arm/boot/dts/am57xx-beagle-x15.dts | 13 +++++++++++--
> 1 file changed, 11 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/boot/dts/am57xx-beagle-x15.dts b/arch/arm/boot/dts/am57xx-beagle-x15.dts
> index 3a05b94f59ed..ede7fb73c717 100644
> --- a/arch/arm/boot/dts/am57xx-beagle-x15.dts
> +++ b/arch/arm/boot/dts/am57xx-beagle-x15.dts
> @@ -432,7 +432,7 @@
> };
>
> ldo3_reg: ldo3 {
> - /* VDDA_1V8_PHY */
> + /* VDDA_1V8_PHYA */
> regulator-name = "ldo3";
> regulator-min-microvolt = <1800000>;
> regulator-max-microvolt = <1800000>;
> @@ -440,6 +440,15 @@
> regulator-boot-on;
> };
>
> + ldo4_reg: ldo4 {
> + /* VDDA_1V8_PHYB */
> + regulator-name = "ldo4";
> + regulator-min-microvolt = <1800000>;
> + regulator-max-microvolt = <1800000>;
> + regulator-always-on;
> + regulator-boot-on;
> + };
> +
> ldo9_reg: ldo9 {
> /* VDD_RTC */
> regulator-name = "ldo9";
> @@ -681,7 +690,7 @@
>
> &hdmi {
> status = "ok";
> - vdda-supply = <&ldo3_reg>;
> + vdda-supply = <&ldo4_reg>;
>
> pinctrl-names = "default";
> pinctrl-0 = <&hdmi_pins>;
>
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2015-09-16 15:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 19:23 [PATCH] ARM: dts: am57xx-beagle-x15: Update Phy supplies Nishanth Menon
2015-09-16 15:11 ` Nishanth Menon [this message]
2015-09-16 23:57 ` Tony Lindgren
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=55F98690.6070601@ti.com \
--to=nm@ti.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tomi.valkeinen@ti.com \
--cc=tony@atomide.com \
/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