From: Richard Acayan <mailingradian@gmail.com>
To: krzysztof.kozlowski@linaro.org
Cc: linux-arm-msm@vger.kernel.org, andersson@kernel.org,
agross@kernel.org, konrad.dybcio@somainline.org,
mturquette@baylibre.com, sboyd@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, tdas@codeaurora.org,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht, caleb@connolly.tech,
jo@jsfamily.in, Richard Acayan <mailingradian@gmail.com>
Subject: Re: [PATCH v2 3/3] clk: qcom: gcc-sdm845: add sdm670 global clock data
Date: Thu, 8 Sep 2022 19:02:43 -0400 [thread overview]
Message-ID: <20220908230243.207783-1-mailingradian@gmail.com> (raw)
In-Reply-To: <8233a19a-9b0b-6962-6f36-381c8f380ad3@linaro.org>
> > @@ -3515,6 +3881,7 @@ static const struct qcom_reset_map gcc_sdm845_resets[] = {
> > [GCC_QUPV3_WRAPPER_1_BCR] = { 0x18000 },
> > [GCC_QUSB2PHY_PRIM_BCR] = { 0x12000 },
> > [GCC_QUSB2PHY_SEC_BCR] = { 0x12004 },
> > + [GCC_SDCC1_BCR] = { 0x26000 },
>
> You are changing existing SDM845, so this should be separate patch with
> its own explanation.
I only added this reset for the sake of completeness. It is not used in my
initial dtsi so I will drop it from this series. It can be added later if
it is needed for a specific device.
prev parent reply other threads:[~2022-09-08 23:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 22:39 [PATCH v2 0/3] SDM670 Global Clocks Richard Acayan
2022-09-07 22:39 ` [PATCH v2 1/3] dt-bindings: clock: gcc-sdm845: add sdm670 global clocks Richard Acayan
2022-09-08 11:07 ` Krzysztof Kozlowski
2022-09-08 23:01 ` Richard Acayan
2022-09-09 7:14 ` Krzysztof Kozlowski
2022-09-07 22:39 ` [PATCH v2 2/3] clk: qcom: gcc-sdm845: use device tree match data Richard Acayan
2022-09-08 11:08 ` Krzysztof Kozlowski
2022-09-07 22:39 ` [PATCH v2 3/3] clk: qcom: gcc-sdm845: add sdm670 global clock data Richard Acayan
2022-09-08 11:10 ` Krzysztof Kozlowski
2022-09-08 23:02 ` Richard Acayan [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=20220908230243.207783-1-mailingradian@gmail.com \
--to=mailingradian@gmail.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=caleb@connolly.tech \
--cc=devicetree@vger.kernel.org \
--cc=jo@jsfamily.in \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=tdas@codeaurora.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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).