[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YyxGXXSp2JD9a6ah@google.com>
Date: Thu, 22 Sep 2022 19:26:21 +0800
From: Tzung-Bi Shih <tzungbi@...nel.org>
To: AngeloGioacchino Del Regno
<angelogioacchino.delregno@...labora.com>
Cc: broonie@...nel.org, alsa-devel@...a-project.org,
linux-kernel@...r.kernel.org, tiwai@...e.com, lgirdwood@...il.com,
linux-mediatek@...ts.infradead.org, trevor.wu@...iatek.com,
matthias.bgg@...il.com, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] ASoC: mediatek: mt8195-mt6359: Use snd_soc_pm_ops
instead of custom ops
On Thu, Sep 22, 2022 at 12:35:02PM +0200, AngeloGioacchino Del Regno wrote:
> -static const struct dev_pm_ops mt8195_mt6359_pm_ops = {
> - .poweroff = snd_soc_poweroff,
> - .restore = snd_soc_resume,
> -};
> -
> static struct platform_driver mt8195_mt6359_driver = {
> .driver = {
> .name = "mt8195_mt6359",
> .of_match_table = mt8195_mt6359_dt_match,
> - .pm = &mt8195_mt6359_pm_ops,
> + .pm = &snd_soc_pm_ops,
snd_soc_pm_ops[1] sets some more fields. I'm not quite sure whether
it would introduce any side effect or not. Perhaps Trevor could
provide some suggestions.
[1]: https://elixir.bootlin.com/linux/v5.19.10/source/sound/soc/soc-core.c#L2150
Powered by blists - more mailing lists