From: "Rhodes, David" <drhodes@opensource.cirrus.com>
To: "Nícolas F. R. A. Prado" <nfraprado@collabora.com>,
"Stefan Binding" <sbinding@opensource.cirrus.com>,
"David Rhodes" <david.rhodes@cirrus.com>,
"Richard Fitzgerald" <rf@opensource.cirrus.com>,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Mark Brown" <broonie@kernel.org>,
"Jaroslav Kysela" <perex@perex.cz>,
"Takashi Iwai" <tiwai@suse.com>,
pgriffais@valvesoftware.com
Cc: kernel@collabora.com, linux-sound@vger.kernel.org,
patches@opensource.cirrus.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: cs35l41: Restore register state after system sleep
Date: Thu, 23 Jul 2026 12:27:57 -0500 [thread overview]
Message-ID: <53147854-3d08-425e-8589-ca39a7b6d2bd@opensource.cirrus.com> (raw)
In-Reply-To: <55cecbcf049d3e95d3a6d0cd33004fbf6c7d01e1.camel@collabora.com>
On 7/21/26 3:08 PM, Nícolas F. R. A. Prado wrote:
> Also, since on my system the DSP is not used, the early return in the
> runtime suspend/resume `if (!cs35l41->dsp.preloaded || !cs35l41-
>> dsp.cs_dsp.running)` means that the runtime suspend/resume callbacks
> are no-ops on my system.
>
The Steam Deck LCD should be using the DSP firmware. Valve distributed
this initially but it was added to linux-firmware early last year.
See 'cirrus/cs35l41-dsp1-spk-prot-vlv1776.bin'.
> Nonetheless, I tried simply marking the regcache dirty and syncing it
> upon system resume, mimicking the runtime suspend/resume, as follows:
>
>
> Given that my patch that fully reinitializes the hardware works, while
> this doesn't, I'm inclined to believe that the chip loses power during
> S4 indeed, at which point just restoring the register state is no
> longer enough. But perhaps you could shed more light into this since
> you're much more familiar with this hardware than I am.
>
> Thanks,
> Nícolas
Thank you for looking into this. I agree with your conclusion that the
chip is fully losing power. With that in mind, your implementation makes
sense.
Given the above comments about disabling the DSP on your system, I have
to ask: Are you working on a 'standard' Steam Deck, or have you made
other changes to the power management that aren't present on a typical
device? Has this always been an issue affecting the Steam Deck LCD?
The Steam Deck is the primary use for this ASoC driver. Valve is
regularly updating the kernel in their OS releases, so I don't want to
make any changes that affect the out-of-box behavior. Of course if you
are in touch with Valve and submitting this on their behalf, no worries
and I'd love to see an Ack from someone on their side.
Thanks,
David
prev parent reply other threads:[~2026-07-23 17:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-15 14:54 Nícolas F. R. A. Prado
2026-06-15 17:42 ` Mark Brown
2026-06-16 16:31 ` Stefan Binding
2026-06-17 17:40 ` Rhodes, David
2026-07-21 20:08 ` Nícolas F. R. A. Prado
2026-07-23 17:27 ` Rhodes, David [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=53147854-3d08-425e-8589-ca39a7b6d2bd@opensource.cirrus.com \
--to=drhodes@opensource.cirrus.com \
--cc=broonie@kernel.org \
--cc=david.rhodes@cirrus.com \
--cc=kernel@collabora.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=nfraprado@collabora.com \
--cc=patches@opensource.cirrus.com \
--cc=perex@perex.cz \
--cc=pgriffais@valvesoftware.com \
--cc=rf@opensource.cirrus.com \
--cc=sbinding@opensource.cirrus.com \
--cc=tiwai@suse.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®