[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <93cf47c7-612b-49b3-a2f7-d36525fce3ed@sirena.org.uk>
Date: Fri, 16 Jun 2023 14:11:15 +0100
From: Mark Brown <broonie@...nel.org>
To: "kondaveeti, Arungopal" <arungopal.kondaveeti@....com>
Cc: alsa-devel@...a-project.org, vsujithkumar.reddy@....com,
Vijendar.Mukunda@....com, Basavaraj.Hiregoudar@....com,
Sunil-kumar.Dommati@....com, syed.sabakareem@....com,
mastan.katragadda@....com, Liam Girdwood <lgirdwood@...il.com>,
Jaroslav Kysela <perex@...ex.cz>,
Takashi Iwai <tiwai@...e.com>,
Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>,
Mario Limonciello <mario.limonciello@....com>,
Nicolas Ferre <nicolas.ferre@...rochip.com>,
Charles Keepax <ckeepax@...nsource.cirrus.com>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] ASoC: amd: correct pm_runtime enable sequence
On Fri, Jun 16, 2023 at 06:28:29PM +0530, kondaveeti, Arungopal wrote:
> On 6/13/2023 7:39 PM, Mark Brown wrote:
> > On Wed, Jun 14, 2023 at 06:01:59AM +0530, Arun Gopal Kondaveeti wrote:
> > > Replace pm_runtime_allow() with pm_runtime_mark_last_busy()
> > > & pm_runtime_set_active() in pm_runtime enable sequence for
> > > dma drivers.
> > This says what the change does but it doesn't say why the old sequence
> > was a problem and the new one is better.
> pm_runtime_allow is not needed for child platform drivers .
If it's not needed that explains the removal but not the addition of
set_active()... This information should be in the changelog.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists