From: Bjorn Andersson <andersson@kernel.org>
To: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Rajendra Nayak <quic_rjendra@quicinc.com>,
Konrad Dybcio <konradybcio@kernel.org>
Cc: Marijn Suijten <marijn.suijten@somainline.org>,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Subject: Re: (subset) [PATCH 0/3] X1P42100 clock changes
Date: Thu, 26 Dec 2024 12:26:40 -0600 [thread overview]
Message-ID: <173523761374.1412574.6777541539264789462.b4-ty@kernel.org> (raw)
In-Reply-To: <20241221-topic-x1p4_clk-v1-0-dbaeccb74884@oss.qualcomm.com>
On Sat, 21 Dec 2024 13:24:08 +0100, Konrad Dybcio wrote:
> X1P42100 is heavily based upon X1E80100, but ultimately it's a
> separate design.
>
> From the clocks POV, we need a new GPUCC driver (though for ease of DT
> integration the bindings part is reused from X1E - perhaps that's
> something to look into on a broader scale, but that's not for today).
>
> [...]
Applied, thanks!
[1/3] dt-bindings: clock: qcom,x1e80100-gcc: Add X1P42100
commit: 089c09ee12317def57ab6a5159269315743083e3
[3/3] clk: qcom: Add X1P42100 GPUCC driver
commit: 99c21c7ca6423913783ea50e2c16be3cc097f17b
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2024-12-26 18:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-21 12:24 [PATCH 0/3] X1P42100 clock changes Konrad Dybcio
2024-12-21 12:24 ` [PATCH 1/3] dt-bindings: clock: qcom,x1e80100-gcc: Add X1P42100 Konrad Dybcio
2024-12-21 12:24 ` [PATCH 2/3] dt-bindings: clock: qcom,x1e80100-gpucc: Extend for X1P42100 Konrad Dybcio
2024-12-21 12:24 ` [PATCH 3/3] clk: qcom: Add X1P42100 GPUCC driver Konrad Dybcio
2024-12-26 18:26 ` 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=173523761374.1412574.6777541539264789462.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=mturquette@baylibre.com \
--cc=quic_rjendra@quicinc.com \
--cc=robh@kernel.org \
--cc=sboyd@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