From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: "Andy Gross" <agross@kernel.org>,
"Bjorn Andersson" <andersson@kernel.org>,
"Konrad Dybcio" <konrad.dybcio@somainline.org>,
"Rob Herring" <robh+dt@kernel.org>,
"Jingoo Han" <jingoohan1@gmail.com>,
"Gustavo Pimentel" <gustavo.pimentel@synopsys.com>,
"Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Bjorn Helgaas" <bhelgaas@google.com>
Cc: linux-arm-msm@vger.kernel.org, linux-pci@vger.kernel.org,
Johan Hovold <johan@kernel.org>
Subject: [PATCH 0/4] PCI: qcom: use clk_bulk API
Date: Thu, 20 Oct 2022 13:31:16 +0300 [thread overview]
Message-ID: <20221020103120.1541862-1-dmitry.baryshkov@linaro.org> (raw)
Replace open-coded clk iterations with clk_bulk_ API usage.
Dmitry Baryshkov (4):
PCI: qcom: Move 2_1_0 defines close to the struct definition
PCI: qcom: Use clk_bulk_ API for 1.0.0 clocks handling
PCI: qcom: Use clk_bulk_ API for 2.3.2 clocks handling
PCI: qcom: Use clk_bulk_ API for 2.3.3 clocks handling
drivers/pci/controller/dwc/pcie-qcom.c | 230 +++++--------------------
1 file changed, 45 insertions(+), 185 deletions(-)
--
2.35.1
next reply other threads:[~2022-10-20 10:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 10:31 Dmitry Baryshkov [this message]
2022-10-20 10:31 ` [PATCH 1/4] PCI: qcom: Move 2_1_0 defines close to the struct definition Dmitry Baryshkov
2022-10-20 10:31 ` [PATCH 2/4] PCI: qcom: Use clk_bulk_ API for 1.0.0 clocks handling Dmitry Baryshkov
2022-10-20 11:08 ` Johan Hovold
2022-10-20 11:22 ` Dmitry Baryshkov
2022-10-20 11:32 ` Johan Hovold
2022-10-20 11:45 ` Dmitry Baryshkov
2023-01-13 15:54 ` Lorenzo Pieralisi
2023-01-16 11:26 ` Johan Hovold
2022-10-20 10:31 ` [PATCH 3/4] PCI: qcom: Use clk_bulk_ API for 2.3.2 " Dmitry Baryshkov
2022-10-23 23:27 ` Han Jingoo
2022-10-20 10:31 ` [PATCH 4/4] PCI: qcom: Use clk_bulk_ API for 2.3.3 " Dmitry Baryshkov
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=20221020103120.1541862-1-dmitry.baryshkov@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=bhelgaas@google.com \
--cc=gustavo.pimentel@synopsys.com \
--cc=jingoohan1@gmail.com \
--cc=johan@kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=kw@linux.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=robh+dt@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