From: Stephen Boyd <sboyd@kernel.org>
To: JC Kuo <jckuo@nvidia.com>,
gregkh@linuxfoundation.org, jonathanh@nvidia.com, kishon@ti.com,
mturquette@baylibre.com, robh@kernel.org,
thierry.reding@gmail.com
Cc: linux-tegra@vger.kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
nkristam@nvidia.com, linux-clk@vger.kernel.org,
JC Kuo <jckuo@nvidia.com>, Thierry Reding <treding@nvidia.com>
Subject: Re: [PATCH v7 02/14] clk: tegra: Don't enable PLLE HW sequencer at init
Date: Mon, 08 Feb 2021 11:28:40 -0800 [thread overview]
Message-ID: <161281252000.76967.4881086496669699756@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <20210120073414.69208-3-jckuo@nvidia.com>
Quoting JC Kuo (2021-01-19 23:34:02)
> PLLE hardware power sequencer references PEX/SATA UPHY PLL hardware
> power sequencers' output to enable/disable PLLE. PLLE hardware power
> sequencer has to be enabled only after PEX/SATA UPHY PLL's sequencers
> are enabled.
>
> Signed-off-by: JC Kuo <jckuo@nvidia.com>
> Acked-by: Thierry Reding <treding@nvidia.com>
> ---
Acked-by: Stephen Boyd <sboyd@kernel.org>
next prev parent reply other threads:[~2021-02-08 19:31 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 7:34 [PATCH v7 00/14] Tegra XHCI controller ELPG support JC Kuo
2021-01-20 7:34 ` [PATCH v7 01/14] clk: tegra: Add PLLE HW power sequencer control JC Kuo
2021-02-08 19:28 ` Stephen Boyd
2021-01-20 7:34 ` [PATCH v7 02/14] clk: tegra: Don't enable PLLE HW sequencer at init JC Kuo
2021-02-08 19:28 ` Stephen Boyd [this message]
2021-01-20 7:34 ` [PATCH v7 03/14] phy: tegra: xusb: Move usb3 port init for Tegra210 JC Kuo
2021-01-20 7:34 ` [PATCH v7 04/14] phy: tegra: xusb: Rearrange UPHY init on Tegra210 JC Kuo
2021-01-20 7:34 ` [PATCH v7 05/14] phy: tegra: xusb: Add Tegra210 lane_iddq operation JC Kuo
2021-01-20 7:34 ` [PATCH v7 06/14] phy: tegra: xusb: Add sleepwalk and suspend/resume JC Kuo
2021-01-20 7:34 ` [PATCH v7 07/14] soc/tegra: pmc: Provide USB sleepwalk register map JC Kuo
2021-01-20 7:34 ` [PATCH v7 08/14] arm64: tegra210: XUSB PADCTL add "nvidia,pmc" prop JC Kuo
2021-01-20 17:35 ` Thierry Reding
2021-01-20 7:34 ` [PATCH v7 09/14] dt-bindings: phy: tegra-xusb: Add nvidia,pmc prop JC Kuo
2021-01-20 17:32 ` Thierry Reding
2021-01-20 7:34 ` [PATCH v7 10/14] phy: tegra: xusb: Add wake/sleepwalk for Tegra210 JC Kuo
2021-01-20 7:34 ` [PATCH v7 11/14] phy: tegra: xusb: Tegra210 host mode VBUS control JC Kuo
2021-01-20 7:34 ` [PATCH v7 12/14] phy: tegra: xusb: Add wake/sleepwalk for Tegra186 JC Kuo
2021-01-20 7:34 ` [PATCH v7 13/14] usb: host: xhci-tegra: Unlink power domain devices JC Kuo
2021-01-20 7:34 ` [PATCH v7 14/14] xhci: tegra: Enable ELPG for runtime/system PM JC Kuo
2021-02-05 16:15 ` [PATCH v7 00/14] Tegra XHCI controller ELPG support Thierry Reding
2021-02-05 16:22 ` Greg KH
2021-03-24 12:39 ` Thierry Reding
2021-03-24 13:32 ` Thierry Reding
2021-03-25 6:15 ` Vinod Koul
2021-03-25 14:00 ` Thierry Reding
2021-03-25 14:05 ` Vinod Koul
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=161281252000.76967.4881086496669699756@swboyd.mtv.corp.google.com \
--to=sboyd@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jckuo@nvidia.com \
--cc=jonathanh@nvidia.com \
--cc=kishon@ti.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=nkristam@nvidia.com \
--cc=robh@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=treding@nvidia.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).