[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210316134915.GB4309@sirena.org.uk>
Date: Tue, 16 Mar 2021 13:49:15 +0000
From: Mark Brown <broonie@...nel.org>
To: Viorel Suman <viorel.suman@....com>
Cc: "S.j. Wang" <shengjiu.wang@....com>,
"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 01:42:40PM +0000, Viorel Suman wrote:
> 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.
Usually the pattern is to have probe() leave everything powered up then
let runtime PM power things down if it's enabled, you can often do the
power up by having an open coded call to the resume callback in probe().
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists