From: Bjorn Andersson <andersson@kernel.org>
To: mturquette@baylibre.com, robh@kernel.org, conor+dt@kernel.org,
sboyd@kernel.org, krzk+dt@kernel.org,
Dongfang Zhao <dongfang.zhao@oss.qualcomm.com>
Cc: linux-kernel@vger.kernel.org, konrad.dybcio@oss.qualcomm.com,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-clk@vger.kernel.org, taniya.das@oss.qualcomm.com,
bmasney@redhat.com
Subject: Re: (subset) [PATCH v2 0/2] clk: qcom: Add GPUCC and GXCLK support for Hawi
Date: Mon, 31 Aug 2026 15:21:14 -0500 [thread overview]
Message-ID: <178820768660.1699313.17347540515197728651.b4-ty@kernel.org> (raw)
In-Reply-To: <20260730-gpucc-hawi-v2-0-7bf618ab8a34@oss.qualcomm.com>
On Thu, 30 Jul 2026 22:53:47 -0700, Dongfang Zhao wrote:
> Add GPU clock controller (GPUCC) and GX clock controller (GXCLKCTL)
> support for the Qualcomm Hawi SoC.
>
> The GPUCC provides clocks, resets and power domains for the GPU
> subsystem. The GXCLKCTL manages only the GX GDSC; remaining resources
> are handled by firmware. Hawi's GX clock controller reuses the existing
> gxclkctl-kaanapali driver via a fallback compatible
> ("qcom,hawi-gxclkctl", "qcom,kaanapali-gxclkctl"), so no driver change
> is needed unless Hawi-specific behaviour is required later.
>
> [...]
Applied, thanks!
[2/2] clk: qcom: Add support for Hawi GPUCC
commit: 1450a68f30a163d5cc2b1f1009797b357bec33e3
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2026-08-31 20:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 5:53 Dongfang Zhao
2026-07-31 5:53 ` [PATCH v2 1/2] dt-bindings: clock: qcom: Add Hawi GPU clock controllers Dongfang Zhao
2026-08-03 9:26 ` Krzysztof Kozlowski
2026-07-31 5:53 ` [PATCH v2 2/2] clk: qcom: Add support for Hawi GPUCC Dongfang Zhao
2026-08-10 18:45 ` [PATCH v2 0/2] clk: qcom: Add GPUCC and GXCLK support for Hawi Bjorn Andersson
2026-08-31 20:21 ` 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=178820768660.1699313.17347540515197728651.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=bmasney@redhat.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dongfang.zhao@oss.qualcomm.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--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=mturquette@baylibre.com \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=taniya.das@oss.qualcomm.com \
/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
all inboxes | Powered by JetHome®