From: Taniya Das <taniya.das@oss.qualcomm.com>
To: Dongfang Zhao <dongfang.zhao@oss.qualcomm.com>,
sboyd@kernel.org, andersson@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, robh@kernel.org, mturquette@baylibre.com
Cc: mike.tipton@oss.qualcomm.com, linux-clk@vger.kernel.org,
konrad.dybcio@oss.qualcomm.com, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 2/2] clk: qcom: Add support for Hawi GPUCC
Date: Mon, 27 Jul 2026 11:23:33 +0530 [thread overview]
Message-ID: <511dfd42-f0e8-48e5-b02c-8429db1a74b1@oss.qualcomm.com> (raw)
In-Reply-To: <20260726-gpucc-hawi-v1-2-224e7884cf9a@oss.qualcomm.com>
On 7/27/2026 11:19 AM, Dongfang Zhao wrote:
> Add the graphics clock controller driver for Hawi. This provides the
> clocks, resets and power domains required by the GPU driver to enable the
> graphics subsystem.
>
> Reuse the existing gxclkctl-kaanapali driver for GX clock controller
> support and build it with the Hawi GPUCC driver.
>
> Signed-off-by: Dongfang Zhao <dongfang.zhao@oss.qualcomm.com>
> Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
> ---
> drivers/clk/qcom/Kconfig | 12 ++
> drivers/clk/qcom/Makefile | 1 +
> drivers/clk/qcom/gpucc-hawi.c | 461 ++++++++++++++++++++++++++++++++++++++++++
> 3 files changed, 474 insertions(+)
Reviewed-by: Taniya Das <taniya.das@oss.qualcomm.com>
--
Thanks,
Taniya Das
prev parent reply other threads:[~2026-07-27 5:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 5:49 [PATCH 0/2] clk: qcom: Add GPUCC and GXCLK support for Hawi Dongfang Zhao
2026-07-27 5:49 ` [PATCH 1/2] dt-bindings: clock: qcom: Add Hawi GPU clock controllers Dongfang Zhao
2026-07-30 8:34 ` Krzysztof Kozlowski
2026-07-27 5:49 ` [PATCH 2/2] clk: qcom: Add support for Hawi GPUCC Dongfang Zhao
2026-07-27 5:53 ` Taniya Das [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=511dfd42-f0e8-48e5-b02c-8429db1a74b1@oss.qualcomm.com \
--to=taniya.das@oss.qualcomm.com \
--cc=andersson@kernel.org \
--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=mike.tipton@oss.qualcomm.com \
--cc=mturquette@baylibre.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
all inboxes | Powered by JetHome®