From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: fabricioakio@gmail.com, Bjorn Andersson <andersson@kernel.org>,
Abel Vesa <abelvesa@kernel.org>, Stephen Boyd <sboyd@kernel.org>,
Brian Masney <bmasney+clk@redhat.com>,
Jerome Brunet <jbrunet+clk@baylibre.com>,
Konrad Dybcio <konradybcio@kernel.org>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@somainline.org>,
Martin Botka <martin.botka@somainline.org>
Cc: linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] clk: qcom: gcc-sdm660: Keep the USB GDSC in retention
Date: Wed, 30 Sep 2026 10:58:42 +0200 [thread overview]
Message-ID: <9b4eb301-5bb6-45c4-94eb-a6a3a2540309@oss.qualcomm.com> (raw)
In-Reply-To: <20260928-sdm660-clk-fixes-v1-1-5d5bb84e3258@gmail.com>
On 9/28/26 7:41 PM, Fabricio Akio via B4 Relay wrote:
> From: Fabricio Akio <fabricioakio@gmail.com>
>
> The DWC3 glue writes its QSCRATCH configuration only at probe. When
> system suspend switches usb_30_gdsc off, that configuration is lost
> and on resume the core fails to enable endpoint 0. Keep the GDSC in
> retention, as is already done on:
>
> commit 78a2f2a04fb5 ("clk: qcom: gcc-msm8996: Update the .pwrsts for
> usb gdsc")
> commit 83fddbcc8337 ("clk: qcom: gcc-msm8998: Update the .pwrsts for
> usb gdsc")
>
> This change should be reverted when a proper suspend sequence is
> implemented in the USB drivers.
>
> Signed-off-by: Fabricio Akio <fabricioakio@gmail.com>
> ---
Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Konrad
next prev parent reply other threads:[~2026-09-30 8:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 17:41 [PATCH 0/2] clk: qcom: sdm660: keep USB across suspend, give mdss_axi_clk its parent Fabricio Akio via B4 Relay
2026-09-28 17:41 ` [PATCH 1/2] clk: qcom: gcc-sdm660: Keep the USB GDSC in retention Fabricio Akio via B4 Relay
2026-09-30 8:58 ` Konrad Dybcio [this message]
2026-09-28 17:41 ` [PATCH 2/2] clk: qcom: mmcc-sdm660: set num_parents on mdss_axi_clk Fabricio Akio via B4 Relay
2026-09-30 8:58 ` Konrad Dybcio
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=9b4eb301-5bb6-45c4-94eb-a6a3a2540309@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=abelvesa@kernel.org \
--cc=andersson@kernel.org \
--cc=angelogioacchino.delregno@somainline.org \
--cc=bmasney+clk@redhat.com \
--cc=fabricioakio@gmail.com \
--cc=jbrunet+clk@baylibre.com \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.botka@somainline.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®