[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <VI1PR0401MB22721D0D266207472B3C7829926B9@VI1PR0401MB2272.eurprd04.prod.outlook.com>
Date: Tue, 16 Mar 2021 13:42:40 +0000
From: Viorel Suman <viorel.suman@....com>
To: Mark Brown <broonie@...nel.org>,
"S.j. Wang" <shengjiu.wang@....com>
CC: "alsa-devel@...a-project.org" <alsa-devel@...a-project.org>,
"timur@...nel.org" <timur@...nel.org>,
"Xiubo.Lee@...il.com" <Xiubo.Lee@...il.com>,
"linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>,
"tiwai@...e.com" <tiwai@...e.com>,
"lgirdwood@...il.com" <lgirdwood@...il.com>,
"nicoleotsuka@...il.com" <nicoleotsuka@...il.com>,
"festevam@...il.com" <festevam@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] ASoC: fsl_sai: remove reset code from dai_probe
> On Tue, Mar 16, 2021 at 05:27:06PM +0800, Shengjiu Wang wrote:
> > From: Viorel Suman <viorel.suman@....com>
> >
> > SAI software reset is done in runtime resume, there is no need to do
> > it in fsl_sai_dai_probe.
>
> People can disable runtime PM in their configurations - do you not still need a
> reset on probe in case there's no runtime PM? It'd probably make sense to
> factor the rest code out itno a function though.
Hi Mark, Shengjiu,
To me it makes sense to manage the clocks and reset from the same place.
Currently we have the clocks management moved completely into runtime PM
fsl_sai_runtime_resume and fsl_sai_runtime_suspend callbacks.
/Viorel
Powered by blists - more mailing lists