From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: "Andy Gross" <agross@kernel.org>,
"Bjorn Andersson" <bjorn.andersson@linaro.org>,
"Stanimir Varbanov" <svarbanov@mm-sol.com>,
"Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Michael Turquette" <mturquette@baylibre.com>,
"Stephen Boyd" <swboyd@chromium.org>,
"Johan Hovold" <johan+linaro@kernel.org>,
"Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>
Cc: Prasad Malisetty <pmaliset@codeaurora.org>,
Vinod Koul <vkoul@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-pci@vger.kernel.org,
linux-clk@vger.kernel.org
Subject: [PATCH v5 0/5] PCI: qcom: Rework pipe_clk/pipe_clk_src handling
Date: Thu, 12 May 2022 20:29:04 +0300 [thread overview]
Message-ID: <20220512172909.2436302-1-dmitry.baryshkov@linaro.org> (raw)
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.
PCIe part depends on [1].
Changes since v4:
- Renamed the clock to clk-regmap-pipe-src,
- Added mention of PCIe2 PHY to the commit message,
- Expanded commit messages to mention additional pipe clock details.
Changes since v3:
- Replaced the clock multiplexer implementation with branch-like clock.
Changes since v2:
- Added is_enabled() callback
- Added default parent to the pipe clock configuration
Changes since v1:
- Rebased on top of [1].
- Removed erroneous Fixes tag from the patch 4.
Changes since RFC:
- Rework clk-regmap-mux fields. Specify safe parent as P_* value rather
than specifying the register value directly
- Expand commit message to the first patch to specially mention that
it is required only on newer generations of Qualcomm chipsets.
[1]: https://lore.kernel.org/all/20220401133351.10113-1-johan+linaro@kernel.org/
Dmitry Baryshkov (5):
PCI: qcom: Remove unnecessary pipe_clk handling
clk: qcom: regmap: add PHY clock source implementation
clk: qcom: gcc-sm8450: use new clk_regmap_pipe_src_ops for PCIe pipe
clocks
clk: qcom: gcc-sc7280: use new clk_regmap_pipe_src_ops for PCIe pipe
clocks
PCI: qcom: Drop manual pipe_clk_src handling
drivers/clk/qcom/Makefile | 1 +
drivers/clk/qcom/clk-regmap-pipe-src.c | 62 ++++++++++++++++++++
drivers/clk/qcom/clk-regmap-pipe-src.h | 24 ++++++++
drivers/clk/qcom/gcc-sc7280.c | 49 ++++++----------
drivers/clk/qcom/gcc-sm8450.c | 51 ++++++----------
drivers/pci/controller/dwc/pcie-qcom.c | 81 +-------------------------
6 files changed, 128 insertions(+), 140 deletions(-)
create mode 100644 drivers/clk/qcom/clk-regmap-pipe-src.c
create mode 100644 drivers/clk/qcom/clk-regmap-pipe-src.h
base-commit: 3123109284176b1532874591f7c81f3837bbdc17
prerequisite-patch-id: 71e4b5b7ff5d87f2407735cc6a3074812cde3697
--
2.35.1
next reply other threads:[~2022-05-12 17:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-12 17:29 Dmitry Baryshkov [this message]
2022-05-12 17:29 ` [PATCH v5 1/5] PCI: qcom: Remove unnecessary pipe_clk handling Dmitry Baryshkov
2022-05-13 7:45 ` Johan Hovold
2022-05-12 17:29 ` [PATCH v5 2/5] clk: qcom: regmap: add PHY clock source implementation Dmitry Baryshkov
2022-05-13 8:16 ` Johan Hovold
2022-05-13 9:50 ` Dmitry Baryshkov
2022-05-12 17:29 ` [PATCH v5 3/5] clk: qcom: gcc-sm8450: use new clk_regmap_pipe_src_ops for PCIe pipe clocks Dmitry Baryshkov
2022-05-12 17:29 ` [PATCH v5 4/5] clk: qcom: gcc-sc7280: " Dmitry Baryshkov
2022-05-12 17:29 ` [PATCH v5 5/5] PCI: qcom: Drop manual pipe_clk_src handling Dmitry Baryshkov
2022-05-13 8:19 ` Johan Hovold
2022-05-13 7:41 ` [PATCH v5 0/5] PCI: qcom: Rework pipe_clk/pipe_clk_src handling Johan Hovold
2022-05-13 9:31 ` Dmitry Baryshkov
2022-05-13 9:43 ` Johan Hovold
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=20220512172909.2436302-1-dmitry.baryshkov@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=agross@kernel.org \
--cc=bhelgaas@google.com \
--cc=bjorn.andersson@linaro.org \
--cc=johan+linaro@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=manivannan.sadhasivam@linaro.org \
--cc=mturquette@baylibre.com \
--cc=pmaliset@codeaurora.org \
--cc=robh@kernel.org \
--cc=svarbanov@mm-sol.com \
--cc=swboyd@chromium.org \
--cc=vkoul@kernel.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).