From: Lars-Peter Clausen <lars@metafoo.de>
To: Shawn Guo <shawn.guo@linaro.org>
Cc: Dimitris Papastamos <dp@opensource.wolfsonmicro.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
patches@opensource.wolfsonmicro.com,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Charles Keepax <ckeepax@opensource.wolfsonmicro.com>,
Fabio Estevam <festevam@gmail.com>
Subject: Re: [PATCH v4 2/5] ASoC: Move standard kcontrol helpers to the component level
Date: Sat, 10 May 2014 11:28:59 +0200 [thread overview]
Message-ID: <536DF15B.50409@metafoo.de> (raw)
In-Reply-To: <20140510091209.GM2870@dragon>
On 05/10/2014 11:12 AM, Shawn Guo wrote:
> On Sat, May 10, 2014 at 10:37:28AM +0200, Lars-Peter Clausen wrote:
>> On 05/10/2014 10:31 AM, Shawn Guo wrote:
>>> On Sat, May 10, 2014 at 09:11:04AM +0200, Lars-Peter Clausen wrote:
>>>> On 05/10/2014 09:04 AM, Lars-Peter Clausen wrote:
>>>> [..]
>>>>>> The error message only shows up with Debian wheezy and does not with
>>>>>> yocto rootfs. And even when the error message shows, the audio still
>>>>>> functions well on Debian wheezy. So it's just a noisy error message
>>>>>> for me which is only seen after your kernel patch.
>>>>>
>>>>> The keyword here is "seen". The error quite likely predated the commit, but
>>>>> it was silently discarded.
>>>>>
>>>>> regmap_read() returns -EBUSY when there is no cached register value and
>>>>> cache_only is set to true. But I'm not sure why that would happen, try to
>>>>> add some printks to _regmap_read() to see if this is the source and if it is
>>>>> why it is.
>>>>
>>>> Both SGTL5000_CHIP_ANA_ADC_CTRL and SGTL5000_CHIP_MIC_CTRL don't
>>>> have an entry in sgtl5000_reg_defaults. So if cache_only is true,
>>>> controls which use these registers will return -EBUSY when you try
>>>> to read or write them.
>>>
>>> Hmm, it's a wm8962 than sgtl5000 on board imx6q-sabresd.
>>
>> Ok, misread the boardname. But the issue will be the same.
>> cache_only = true and trying to read/update a register that is not
>> in the cache.
>
> Yea, you're right. When the error message shows up, _regmap_read()
> returns -EBUSY for reg WM8962_CLASS_D_CONTROL_1. But how do I find out
> why the reg is not in the cache?
The register is marked as volatile in the driver and volatile registers are
never cached. I don't know what the right fix is in this case though.
- Lars
next prev parent reply other threads:[~2014-05-10 9:29 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 11:23 [PATCH v4 0/5] ASoC: Move IO and kcontrols to the component level Lars-Peter Clausen
2014-04-22 11:23 ` [PATCH v4 1/5] ASoC: Move IO abstraction " Lars-Peter Clausen
2014-04-22 12:24 ` Mark Brown
2014-04-22 11:23 ` [PATCH v4 2/5] ASoC: Move standard kcontrol helpers " Lars-Peter Clausen
2014-04-22 12:38 ` Mark Brown
2014-05-09 15:00 ` Shawn Guo
2014-05-09 15:17 ` Lars-Peter Clausen
2014-05-09 15:34 ` Fabio Estevam
2014-05-09 16:01 ` Lars-Peter Clausen
2014-05-09 16:11 ` Fabio Estevam
2014-05-10 5:07 ` Shawn Guo
2014-05-10 7:04 ` Lars-Peter Clausen
2014-05-10 7:11 ` Lars-Peter Clausen
2014-05-10 8:31 ` Shawn Guo
2014-05-10 8:37 ` Lars-Peter Clausen
2014-05-10 9:12 ` Shawn Guo
2014-05-10 9:28 ` Lars-Peter Clausen [this message]
2014-05-12 10:42 ` Charles Keepax
2014-05-12 11:03 ` Mark Brown
2014-05-12 14:09 ` Charles Keepax
2014-05-12 10:52 ` Charles Keepax
2014-05-13 3:19 ` Shawn Guo
2014-04-22 11:23 ` [PATCH v4 3/5] ASoC: Remove snd_soc_update_bits_locked() Lars-Peter Clausen
2014-04-22 12:25 ` Mark Brown
2014-04-22 11:23 ` [PATCH v4 4/5] ASoC: dapm: Rename soc_widget_update_bits_locked() to soc_widget_update_bits() Lars-Peter Clausen
2014-04-22 12:25 ` Mark Brown
2014-04-22 11:23 ` [PATCH v4 5/5] ASoC: Remove ASoC level IO tracing Lars-Peter Clausen
2014-04-22 12:25 ` Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=536DF15B.50409@metafoo.de \
--to=lars@metafoo.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=dp@opensource.wolfsonmicro.com \
--cc=festevam@gmail.com \
--cc=lgirdwood@gmail.com \
--cc=patches@opensource.wolfsonmicro.com \
--cc=shawn.guo@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox