From: Lars-Peter Clausen <lars@metafoo.de>
To: Shawn Guo <shawn.guo@linaro.org>
Cc: alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH v4 2/5] ASoC: Move standard kcontrol helpers to the component level
Date: Fri, 09 May 2014 17:17:03 +0200 [thread overview]
Message-ID: <536CF16F.8010807@metafoo.de> (raw)
In-Reply-To: <20140509150034.GH2870@dragon>
On 05/09/2014 05:00 PM, Shawn Guo wrote:
> Hi Lars,
>
> On Tue, Apr 22, 2014 at 01:23:14PM +0200, Lars-Peter Clausen wrote:
>> After moving the IO layer inside ASoC to the component level we can now easily
>> move the standard control helpers also to the component level. This allows to
>> reuse the same standard helper control implementations for other components.
>>
>> Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
>
> I'm running next-20140508 on imx6q-sabresd board and seeing repeated
> 'amixer: Mixer hw:0 load error: Device or resource busy' message with
> Debian wheezy rootfs. The git bisect points me to this patch.
>
> == message output before this patch ==
>
> [....] Setting up ALSA...warning: 'alsactl restore' failed with error message 'Found hardware: "wm8962-audio" "" "" "" ""
> Hardware is initialized using a generic method
> [ ok tl: set_control:1328: failed to obtain info for control #117 (No such file or directory)'...done.
>
> == message output after this patch ==
>
> [....] Setting up ALSA...warning: 'alsactl restore' failed with error message 'Found hardware: "wm8962-audio" "" "" "" ""
> Hardware is initialized using a generic method
> alsactl: set_control:1328: failed to obtain info for control #117 (No such file or directory)'...amixer: Mixer hw:0 load error: Device or resource busy
> amixer: Mixer hw:0 load error: Device or resource busy
> amixer: Mixer hw:0 load error: Device or resource busy
> amixer: Mixer hw:0 load error: Device or resource busy
> amixer: Mixer hw:0 load error: Device or resource busy
> amixer: Mixer hw:0 load error: Device or resource busy
> amixer: Mixer hw:0 load error: Device or resource busy
> amixer: Mixer hw:0 load error: Device or resource busy
> amixer: Mixer hw:0 load error: Device or resource busy
> amixer: Mixer hw:0 load error: Device or resource busy
> amixer: Mixer hw:0 load error: Device or resource busy
> amixer: Mixer hw:0 load error: Device or resource busy
> amixer: Mixer hw:0 load error: Device or resource busy
> amixer: Mixer hw:0 load error: Device or resource busy
> amixer: Mixer hw:0 load error: Device or resource busy
> amixer: Mixer hw:0 load error: Device or resource busy
> amixer: Mixer hw:0 load error: Device or resource busy
> amixer: Mixer hw:0 load error: Device or resource busy
> amixer: Mixer hw:0 load error: Device or resource busy
> amixer: Mixer hw:0 load error: Device or resource busy
> amixer: Mixer hw:0 load error: Device or resource busy
> amixer: Mixer hw:0 load error: Device or resource busy
> amixer: Mixer hw:0 load error: Device or resource busy
> amixer: Mixer hw:0 load error: Device or resource busy
> amixer: Mixer hw:0 load error: Device or resource busy
> amixer: Mixer hw:0 load error: Device or resource busy
> amixer: Mixer hw:0 load error: Device or resource busy
> amixer: Mixer hw:0 load error: Device or resource busy
> amixer: Mixer hw:0 load error: Device or resource busy
> amixer: Mixer hw:0 load error: Device or resource busy
> amixer: Mixer hw:0 load error: Device or resource busy
> amixer: Mixer hw:0 load error: Device or resource busy
> amixer: Mixer hw:0 load error: Device or resource busy
> amixer: Mixer hw:0 load error: Device or resource busy
> amixer: Mixer hw:0 load error: Device or resource busy
> amixer: Mixer hw:0 load error: Device or resource busy
> amixer: Mixer hw:0 load error: Device or resource busy
> done.
>
> Why do we start seeing such error message with your patch? Is this
> a problem of rootfs or kernel?
The changes in the patch should mostly be transparent. But what changed is
how error reporting is handled. If there is a error reading/writing a
register in the kcontrol callbacks that error is passed on to userspace
whereas previously it was silently ignored.
There is also the possibility that there is a bug somewhere in the patch
causing this.
Does the board otherwise work fine?
I actually have the board here, if you tell me which devictree/defconfig I
can use with an upstream kernel I can give things a try.
- Lars
next prev parent reply other threads:[~2014-05-09 15:17 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 [this message]
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
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=536CF16F.8010807@metafoo.de \
--to=lars@metafoo.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.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