[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <86253ac7-ef06-974e-9b2d-6575ad5b7195@linaro.org>
Date: Thu, 24 Feb 2022 16:13:50 +0000
From: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>,
broonie@...nel.org
Cc: lgirdwood@...il.com, perex@...ex.cz, tiwai@...e.com,
alsa-devel@...a-project.org, linux-kernel@...r.kernel.org,
quic_srivasam@...cinc.com
Subject: Re: [PATCH v2 14/16] ASoC: codecs: wsa881x: add runtime pm support
On 24/02/2022 15:29, Pierre-Louis Bossart wrote:
>
>
> On 2/24/22 05:17, Srinivas Kandagatla wrote:
>> WSA881x codecs can not cope up with clk stop and requires a full reset after suspend.
>> WSA SoundWire Controller connected to this instances do a full soft reset on suspend.
>
> is it the manager or peripheral that cannot cope with clock stop?
>
>> @@ -1124,6 +1136,7 @@ static int wsa881x_probe(struct sdw_slave *pdev,
>> pdev->prop.sink_ports = GENMASK(WSA881X_MAX_SWR_PORTS, 0);
>> pdev->prop.sink_dpn_prop = wsa_sink_dpn_prop;
>> pdev->prop.scp_int1_mask = SDW_SCP_INT1_BUS_CLASH | SDW_SCP_INT1_PARITY;
>> + pdev->prop.simple_clk_stop_capable = true;
>
> here it's pretty clear the peripheral is capable of supporting clock
> stop, no?
>
> Something's not clear between the commit message and the code.
True, This should be removed along with attempting to call clock stop
functions from WSA SoundWire controller suspend that does not support
clock stop.
--srini
Powered by blists - more mailing lists