From: Rob Herring <robh@kernel.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Jon Hunter <jonathanh@nvidia.com>,
linux-tegra@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 1/8] dt-bindings: phy: tegra-xusb: List PLL power supplies
Date: Wed, 10 Apr 2019 09:13:31 -0500 [thread overview]
Message-ID: <20190410141331.GA28160@bogus> (raw)
In-Reply-To: <20190404112511.28118-1-thierry.reding@gmail.com>
On Thu, 4 Apr 2019 13:25:04 +0200, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
>
> These power supplies provide power for various PLLs that are set up and
> driven by the XUSB pad controller. These power supplies were previously
> improperly added to the PCIe and XUSB controllers, but depending on the
> driver probe order, power to the PLLs will not be supplied soon enough
> and cause initialization to fail.
>
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
> .../bindings/phy/nvidia,tegra124-xusb-padctl.txt | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
Reviewed-by: Rob Herring <robh@kernel.org>
prev parent reply other threads:[~2019-04-10 14:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-04 11:25 [PATCH 1/8] dt-bindings: phy: tegra-xusb: List PLL power supplies Thierry Reding
2019-04-04 11:25 ` [PATCH 2/8] ARM: tegra: apalis: Move PLL power supplies to XUSB pad controller Thierry Reding
2019-04-04 11:25 ` [PATCH 3/8] ARM: tegra: jetson-tk1: " Thierry Reding
2019-04-04 11:25 ` [PATCH 4/8] ARM: tegra: nyan: " Thierry Reding
2019-04-04 11:25 ` [PATCH 5/8] ARM: tegra: venice2: " Thierry Reding
2019-04-04 11:25 ` [PATCH 6/8] arm64: tegra: jetson-tx1: " Thierry Reding
2019-04-04 11:25 ` [PATCH 7/8] arm64: tegra: smaug: " Thierry Reding
2019-04-04 11:25 ` [PATCH v2 8/8] arm64: tegra: Add NVIDIA Jetson Nano Developer Kit support Thierry Reding
2019-04-04 14:47 ` Jon Hunter
2019-04-04 16:51 ` Vidya Sagar
2019-04-08 7:50 ` Nicolas Chauvet
2019-04-10 14:13 ` Rob Herring [this message]
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=20190410141331.GA28160@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@gmail.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;
as well as URLs for NNTP newsgroup(s).