From: Bjorn Andersson <andersson@kernel.org>
To: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Brian Masney <bmasney@redhat.com>,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Taniya Das <taniya.das@oss.qualcomm.com>
Cc: linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org,
Ajit Pandey <ajit.pandey@oss.qualcomm.com>,
Imran Shaik <imran.shaik@oss.qualcomm.com>,
Jagadeesh Kona <jagadeesh.kona@oss.qualcomm.com>
Subject: Re: [PATCH 0/2] clk: qcom: Mark the GPU CX GDSC as votable for Glymur and Kaanapali
Date: Mon, 31 Aug 2026 15:21:25 -0500 [thread overview]
Message-ID: <178820768665.1699313.7933731912668367148.b4-ty@kernel.org> (raw)
In-Reply-To: <20260801-kaanapali-gpu-voteable-v1-0-fe804d24d2e9@oss.qualcomm.com>
On Sat, 01 Aug 2026 23:01:16 +0530, Taniya Das wrote:
> The GPU CX GDSC on both Glymur and Kaanapali is a votable power
> domain, but it was configured with POLL_CFG_GDSCR instead of VOTABLE
> when the respective GPUCC drivers were added. Fix both drivers to set
> the VOTABLE flag so the GDSC driver correctly treats collapse requests
> as always successful, matching other platforms with a votable GPU CX
> GDSC (e.g. SM8750, Milos).
>
> [...]
Applied, thanks!
[1/2] clk: qcom: gpucc-glymur: Mark the GPU CX GDSC as votable
commit: 8f3f88309fa4e975ac27368ee945c2c202251a7c
[2/2] clk: qcom: gpucc-kaanapali: Mark the GPU CX GDSC as votable
commit: 55981579b27b6541aeeab81c768f248dba0491ac
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2026-08-31 20:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-01 17:31 Taniya Das
2026-08-01 17:31 ` [PATCH 1/2] clk: qcom: gpucc-glymur: Mark the GPU CX GDSC as votable Taniya Das
2026-08-05 10:47 ` Jagadeesh Kona
2026-08-01 17:31 ` [PATCH 2/2] clk: qcom: gpucc-kaanapali: " Taniya Das
2026-08-05 10:48 ` Jagadeesh Kona
2026-08-10 18:46 ` [PATCH 0/2] clk: qcom: Mark the GPU CX GDSC as votable for Glymur and Kaanapali 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=178820768665.1699313.7933731912668367148.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=ajit.pandey@oss.qualcomm.com \
--cc=bmasney@redhat.com \
--cc=imran.shaik@oss.qualcomm.com \
--cc=jagadeesh.kona@oss.qualcomm.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--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®