[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9d254e18-2e2f-49ce-b785-ef0f16117550@tuxon.dev>
Date: Wed, 29 Oct 2025 17:29:15 +0200
From: claudiu beznea <claudiu.beznea@...on.dev>
To: Mark Brown <broonie@...nel.org>
Cc: support.opensource@...semi.com, lgirdwood@...il.com, perex@...ex.cz,
 tiwai@...e.com, biju.das.jz@...renesas.com,
 prabhakar.mahadev-lad.rj@...renesas.com, linux-sound@...r.kernel.org,
 linux-kernel@...r.kernel.org, linux-renesas-soc@...r.kernel.org,
 Claudiu Beznea <claudiu.beznea.uj@...renesas.com>, stable@...r.kernel.org
Subject: Re: [PATCH 1/2] ASoC: codecs: Use component driver suspend/resume
On 10/29/25 16:37, Mark Brown wrote:
> On Wed, Oct 29, 2025 at 04:11:33PM +0200, Claudiu wrote:
>> From: Claudiu Beznea <claudiu.beznea.uj@...renesas.com>
>>
>> Since snd_soc_suspend() is invoked through snd_soc_pm_ops->suspend(),
>> and snd_soc_pm_ops is associated with the soc_driver (defined in
>> sound/soc/soc-core.c), and there is no parent-child relationship between
>> the soc_driver and the DA7213 codec driver, the power management subsystem
>> does not enforce a specific suspend/resume order between the DA7213 driver
>> and the soc_driver.
> 
> Oh, also:
> 
> Please submit patches using subject lines reflecting the style for the
> subsystem, this makes it easier for people to identify relevant patches.
> Look at what existing commits in the area you're changing are doing and
> make sure your subject lines visually resemble what they're doing.
> There's no need to resubmit to fix this alone.
I messed this up. I'll be more careful next time.
Thank you,
Claudiu
Powered by blists - more mailing lists
 
