From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: "Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Taniya Das" <quic_tdas@quicinc.com>,
"Dmitry Baryshkov" <dmitry.baryshkov@linaro.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Andy Gross" <agross@kernel.org>,
"Michael Turquette" <mturquette@baylibre.com>,
"Stephen Boyd" <swboyd@chromium.org>
Cc: linux-arm-msm@vger.kernel.org, Johan Hovold <johan@kernel.org>,
Johan Hovold <johan+linaro@kernel.org>,
linux-pci@vger.kernel.org, linux-clk@vger.kernel.org
Subject: Re: (subset) [PATCH v11 0/5] PCI: qcom: Rework pipe_clk/pipe_clk_src handling
Date: Mon, 27 Jun 2022 15:02:46 -0500 [thread overview]
Message-ID: <165636016349.3080661.11515834835284657733.b4-ty@linaro.org> (raw)
In-Reply-To: <20220608105238.2973600-1-dmitry.baryshkov@linaro.org>
On Wed, 8 Jun 2022 13:52:33 +0300, Dmitry Baryshkov wrote:
> PCIe pipe clk (and some other clocks) must be parked to the "safe"
> source (bi_tcxo) when corresponding GDSC is turned off and on again.
> Currently this is handcoded in the PCIe driver by reparenting the
> gcc_pipe_N_clk_src clock.
>
> Instead of doing it manually, follow the approach used by
> clk_rcg2_shared_ops and implement this parking in the enable() and
> disable() clock operations for respective pipe clocks.
>
> [...]
Applied, thanks!
[1/5] clk: qcom: regmap: add PHY clock source implementation
commit: 74e4190cdebe5a4aa099185edb4db418fc9883e3
[2/5] clk: qcom: gcc-sm8450: use new clk_regmap_phy_mux_ops for PCIe pipe clocks
commit: 7ee9d2e8b9c9f4a829cd2d77c8cba36c514f24ba
[3/5] clk: qcom: gcc-sc7280: use new clk_regmap_phy_mux_ops for PCIe pipe clocks
commit: 553d12b20c10953617cc195f9e447a177c776f9d
Best regards,
--
Bjorn Andersson <bjorn.andersson@linaro.org>
prev parent reply other threads:[~2022-06-27 20:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 10:52 [PATCH v11 0/5] PCI: qcom: Rework pipe_clk/pipe_clk_src handling Dmitry Baryshkov
2022-06-08 10:52 ` [PATCH v11 1/5] clk: qcom: regmap: add PHY clock source implementation Dmitry Baryshkov
2022-06-08 19:22 ` Bjorn Helgaas
2022-06-27 20:02 ` Bjorn Andersson
2022-06-15 19:46 ` Stephen Boyd
2022-06-16 18:25 ` Bjorn Helgaas
2022-06-08 10:52 ` [PATCH v11 2/5] clk: qcom: gcc-sm8450: use new clk_regmap_phy_mux_ops for PCIe pipe clocks Dmitry Baryshkov
2022-06-15 19:47 ` Stephen Boyd
2022-06-08 10:52 ` [PATCH v11 3/5] clk: qcom: gcc-sc7280: " Dmitry Baryshkov
2022-06-15 19:49 ` Stephen Boyd
2022-06-08 10:52 ` [PATCH v11 4/5] PCI: qcom: Remove unnecessary pipe_clk handling Dmitry Baryshkov
2022-06-15 19:50 ` Stephen Boyd
2022-07-14 1:07 ` Stanimir Varbanov
2022-06-08 10:52 ` [PATCH v11 5/5] PCI: qcom: Drop manual pipe_clk_src handling Dmitry Baryshkov
2022-06-15 19:51 ` Stephen Boyd
2022-07-14 1:08 ` Stanimir Varbanov
2022-07-14 16:56 ` Bjorn Helgaas
2022-06-16 18:21 ` [PATCH v11 0/5] PCI: qcom: Rework pipe_clk/pipe_clk_src handling Bjorn Helgaas
2022-07-07 14:03 ` Dmitry Baryshkov
2022-07-07 15:40 ` Bjorn Helgaas
2022-07-07 17:09 ` Dmitry Baryshkov
2022-07-07 20:04 ` Bjorn Helgaas
2022-06-27 20:02 ` Bjorn Andersson [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=165636016349.3080661.11515834835284657733.b4-ty@linaro.org \
--to=bjorn.andersson@linaro.org \
--cc=agross@kernel.org \
--cc=bhelgaas@google.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=johan+linaro@kernel.org \
--cc=johan@kernel.org \
--cc=kw@linux.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mturquette@baylibre.com \
--cc=quic_tdas@quicinc.com \
--cc=swboyd@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.