[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <f3aaf5b7-d822-d5d6-eb7c-71ef1e9c9e73@linux.intel.com>
Date: Tue, 17 Jan 2023 06:36:19 -0600
From: Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>
To: Mark Brown <broonie@...nel.org>
Cc: "Mukunda,Vijendar" <vijendar.mukunda@....com>,
"Limonciello, Mario" <mario.limonciello@....com>, vkoul@...nel.org,
alsa-devel@...a-project.org, Mastan.Katragadda@....com,
Sunil-kumar.Dommati@....com, Basavaraj.Hiregoudar@....com,
Takashi Iwai <tiwai@...e.com>,
Liam Girdwood <lgirdwood@...il.com>,
open list <linux-kernel@...r.kernel.org>,
Syed Saba Kareem <Syed.SabaKareem@....com>,
arungopal.kondaveeti@....com
Subject: Re: [PATCH 19/19] ASoC: amd: ps: increase runtime suspend delay
On 1/17/23 06:16, Mark Brown wrote:
> On Tue, Jan 17, 2023 at 05:51:03AM -0600, Pierre-Louis Bossart wrote:
>> On 1/17/23 05:33, Mukunda,Vijendar wrote:
>
>> [ 2.758904] rt1316-sdca sdw:0:025d:1316:01:0: ASoC: error at
>> snd_soc_component_update_bits on sdw:0:025d:1316:01:0 for register:
>> [0x00003004] -110
>
>> The last one is clearly listed in the regmap list.
>
>> You probably want to reverse-engineer what causes these accesses.
>> I see this suspicious kcontrol definition that might be related:
>
>> SOC_SINGLE("Left I Tag Select", 0x3004, 4, 7, 0),
>
> Looks like a case for putting the CODEC in cache only mode...
Right, and I think we'd need to do this during the probe instead of the
hardware initialization (which could happen at a later time).
I started a PR to try and improve regmap handling, see
https://github.com/thesofproject/linux/pull/3941
I was trying to solve the case where codecs become unattached, but
apparently the problem is hardware-related. One of the suggested
improvements was to move the cache_only part earlier to prevent such
accesses. Unfortunately the work isn't complete so that PR is just a
draft at the moment.
Powered by blists - more mailing lists