[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f140ae96-a1fd-e636-2b8b-d453fba5c6e2@amd.com>
Date: Fri, 16 Jun 2023 18:28:29 +0530
From: "kondaveeti, Arungopal" <arungopal.kondaveeti@....com>
To: Mark Brown <broonie@...nel.org>
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 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 .
Previous sequence as listed below which is incorrect.
enable sequence:
pm_runtime_set_autosuspend_delay(&pdev->dev, ACP_SUSPEND_DELAY_MS);
pm_runtime_use_autosuspend(&pdev->dev);
pm_runtime_enable(&pdev->dev);
pm_runtime_allow(&pdev->dev);
disable sequence:
pm_runtime_disable(&pdev->dev)
Replaced pm runtime enable sequence.
Powered by blists - more mailing lists