From: Rayyan Ansari <rayyan@ansari.sh>
To: linux-arm-msm@vger.kernel.org
Cc: ~postmarketos/upstreaming@lists.sr.ht,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
devicetree@vger.kernel.org,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
Michael Turquette <mturquette@baylibre.com>,
Rob Herring <robh+dt@kernel.org>, Stephen Boyd <sboyd@kernel.org>
Subject: Re: [PATCH v3 0/3] Add XO clocks for MSM8226/MSM8974
Date: Sat, 21 Jan 2023 19:23:41 +0000 [thread overview]
Message-ID: <f2266be7-b0b8-8b10-8b0f-e8bae4196917@ansari.sh> (raw)
In-Reply-To: <20230121175838.755636-1-rayyan@ansari.sh>
On 21/01/2023 17:58, Rayyan Ansari wrote:
> Changes since v2:
> - Base off linux-next
> - Add correct XO clock to MSM8974 as well
>
> Rayyan Ansari (3):
> clk: qcom: smd: Add XO RPM clocks for MSM8226/MSM8974
> ARM: dts: qcom: msm8226: add clocks and clock-names to GCC node
I've just noticed that rpmcc.h has somehow been missed in this commit. I
will send v4 to address this.
> ARM: dts: qcom: msm8974: add correct XO clock source to GCC node
>
> arch/arm/boot/dts/qcom-msm8226.dtsi | 5 +++++
> arch/arm/boot/dts/qcom-msm8974.dtsi | 2 +-
> drivers/clk/qcom/clk-smd-rpm.c | 2 ++
> 3 files changed, 8 insertions(+), 1 deletion(-)
>
--
Rayyan Ansari
https://ansari.sh
prev parent reply other threads:[~2023-01-21 19:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-21 17:58 [PATCH v3 0/3] Add XO clocks for MSM8226/MSM8974 Rayyan Ansari
2023-01-21 17:58 ` [PATCH v3 1/3] clk: qcom: smd: Add XO RPM " Rayyan Ansari
2023-01-21 17:58 ` [PATCH v3 2/3] ARM: dts: qcom: msm8226: add clocks and clock-names to GCC node Rayyan Ansari
2023-01-21 17:58 ` [PATCH v3 3/3] ARM: dts: qcom: msm8974: add correct XO clock source " Rayyan Ansari
2023-01-21 19:23 ` Rayyan Ansari [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=f2266be7-b0b8-8b10-8b0f-e8bae4196917@ansari.sh \
--to=rayyan@ansari.sh \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@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=~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).