From: Claudiu Beznea <claudiu.beznea@tuxon.dev>
To: Mark Brown <broonie@kernel.org>
Cc: support.opensource@diasemi.com, lgirdwood@gmail.com,
perex@perex.cz, tiwai@suse.com, biju.das.jz@bp.renesas.com,
prabhakar.mahadev-lad.rj@bp.renesas.com,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-renesas-soc@vger.kernel.org,
Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>,
stable@vger.kernel.org
Subject: Re: [PATCH 1/2] ASoC: codecs: Use component driver suspend/resume
Date: Tue, 4 Nov 2025 13:53:45 +0200 [thread overview]
Message-ID: <6296a8fd-bc2b-470a-a367-61c2d80fe8e1@tuxon.dev> (raw)
In-Reply-To: <56911e0e-0f25-4134-92fd-f89cb47fd9b6@sirena.org.uk>
Hi, Mark,
On 10/29/25 18:14, Mark Brown wrote:
>> Would keeping the regcache_cache_only() + regcache_sync() here along with
>> populating the struct snd_soc_component_driver::{suspend, resume} be an
>> acceptable solution for you? I think that will work as well.
> I'm not sure what you're intending to populate the component with there.
Sorry for the late reply, I took the chance and prepared a new version
showing what I intended to say here. v2 posted here:
https://lore.kernel.org/all/20251104114914.2060603-1-claudiu.beznea.uj@bp.renesas.com/
Thank you,
Claudiu
next prev parent reply other threads:[~2025-11-04 11:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 14:11 [PATCH 0/2] ASoC: renesas: Fix clip sounds Claudiu
2025-10-29 14:11 ` [PATCH 1/2] ASoC: codecs: Use component driver suspend/resume Claudiu
2025-10-29 14:37 ` Mark Brown
2025-10-29 15:22 ` claudiu beznea
2025-10-29 16:14 ` Mark Brown
2025-11-04 11:53 ` Claudiu Beznea [this message]
2025-10-29 14:37 ` Mark Brown
2025-10-29 15:29 ` claudiu beznea
2025-10-29 14:38 ` Richard Fitzgerald
2025-10-29 14:11 ` [PATCH 2/2] ASoC: renesas: rz-ssi: Use proper dma_buffer_pos after resume Claudiu
2025-10-30 11:09 ` (subset) [PATCH 0/2] ASoC: renesas: Fix clip sounds Mark Brown
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=6296a8fd-bc2b-470a-a367-61c2d80fe8e1@tuxon.dev \
--to=claudiu.beznea@tuxon.dev \
--cc=biju.das.jz@bp.renesas.com \
--cc=broonie@kernel.org \
--cc=claudiu.beznea.uj@bp.renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=stable@vger.kernel.org \
--cc=support.opensource@diasemi.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;
as well as URLs for NNTP newsgroup(s).