[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <847f4512-7118-e087-1004-685e476e11d8@gmail.com>
Date: Fri, 7 Feb 2020 21:22:51 +0300
From: Dmitry Osipenko <digetx@...il.com>
To: Sameer Pujar <spujar@...dia.com>
Cc: perex@...ex.cz, tiwai@...e.com, robh+dt@...nel.org,
broonie@...nel.org, lgirdwood@...il.com, thierry.reding@...il.com,
jonathanh@...dia.com, alsa-devel@...a-project.org,
devicetree@...r.kernel.org, linux-tegra@...r.kernel.org,
linux-kernel@...r.kernel.org, sharadg@...dia.com,
mkumard@...dia.com, viswanathl@...dia.com, rlokhande@...dia.com,
dramesh@...dia.com, atalambedu@...dia.com
Subject: Re: [PATCH v2 6/9] ASoC: tegra: add Tegra186 based DSPK driver
07.02.2020 14:26, Sameer Pujar пишет:
>
>
> On 2/6/2020 10:45 PM, Dmitry Osipenko wrote:
>> External email: Use caution opening links or attachments
>>
>>
>> 30.01.2020 13:33, Sameer Pujar пишет:
>>> +static const struct dev_pm_ops tegra186_dspk_pm_ops = {
>>> + SET_RUNTIME_PM_OPS(tegra186_dspk_runtime_suspend,
>>> + tegra186_dspk_runtime_resume, NULL)
>>> + SET_LATE_SYSTEM_SLEEP_PM_OPS(pm_runtime_force_suspend,
>>> + pm_runtime_force_resume)
>>> +};
>> Could you please explain why drivers need the "late" system sleep?
>
> It was done to ensure core drivers are suspended first and defer the
> codec driver suspend
Suspend order is opposite to the drivers registration order. If there is
no real problem with that, then you should use the default suspend
level. Please don't try to fix a non-existent problems.
Powered by blists - more mailing lists