[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZJW1zjWMUYXP1XpH@finisterre.sirena.org.uk>
Date: Fri, 23 Jun 2023 16:10:06 +0100
From: Mark Brown <broonie@...nel.org>
To: "Limonciello, Mario" <mario.limonciello@....com>
Cc: Arun Gopal Kondaveeti <arungopal.kondaveeti@....com>,
alsa-devel@...a-project.org, Vijendar.Mukunda@....com,
Basavaraj.Hiregoudar@....com, sunil-kumar.dommati@....com,
venkataprasad.potturu@....com, syed.sabakareem@....com,
Liam Girdwood <lgirdwood@...il.com>,
Jaroslav Kysela <perex@...ex.cz>,
Takashi Iwai <tiwai@...e.com>,
Nicolas Ferre <nicolas.ferre@...rochip.com>,
Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>,
Charles Keepax <ckeepax@...nsource.cirrus.com>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] ASoC: amd: update pm_runtime enable sequence
On Fri, Jun 23, 2023 at 08:40:15AM -0500, Limonciello, Mario wrote:
> On 6/23/2023 4:41 PM, Arun Gopal Kondaveeti wrote:
> > pm_runtime_allow() is not needed for ACP child platform devices.
> > Replace pm_runtime_allow() with pm_runtime_mark_last_busy()
> > & pm_runtime_set_active() in pm_runtime enable sequence for
> > ACP child platform drivers.
> Can you explain what prompted this?
> Does this fix a particular bug, or is it just to correct
> things? If it fixes a particular bug; I think it should be
> split up across 5 patches (one for each APU) and then
> appropriate Fixes tags applied for each on the code they're
> fixing.
I had already gone ahead and applied this before your mail - it seemed
better to get it into 6.5 than leave it waiting longer. If there's a
need for backports that can be handled through the stable process.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists