Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Shawn Guo <shawn.guo@linaro.org>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	Mark Brown <broonie@kernel.org>,
	Fabio Estevam <festevam@gmail.com>,
	Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH v4 2/5] ASoC: Move standard kcontrol helpers to the component level
Date: Sat, 10 May 2014 13:07:49 +0800	[thread overview]
Message-ID: <20140510050747.GI2870@dragon> (raw)
In-Reply-To: <536CFBE7.3070805@metafoo.de>

On Fri, May 09, 2014 at 06:01:43PM +0200, Lars-Peter Clausen wrote:
> On 05/09/2014 05:34 PM, Fabio Estevam wrote:
> >On Fri, May 9, 2014 at 12:17 PM, Lars-Peter Clausen <lars@metafoo.de> wrote:
> >
> >>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.
> >
> >make imx_v6_v7_defconfig
> >make imx6q-sabresd.dtb
> 
> I just tried 907fe36a2c, e2c330b9b5 and next/master. I get the same
> behavior with all 3, no errors when loading a state file and audio
> out on the headphones works.

For me, e2c330b9b5 is good while 907fe36a2c and next/master expose this
error message.

> I disabled DRM though since it
> deadlocked the system, maybe that makes a difference.

It does not make a difference.

> 
> Is it possible that the error is coming from the I2C driver? Can you
> build the I2C driver with #define DEBUG and take a look at the
> output?

I tried to turn on DEBUG in I2C driver, and did not notice any I2C
message when above error appears.

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.

Shawn

  parent reply	other threads:[~2014-05-10  5:08 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 [this message]
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=20140510050747.GI2870@dragon \
    --to=shawn.guo@linaro.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=festevam@gmail.com \
    --cc=lars@metafoo.de \
    --cc=lgirdwood@gmail.com \
    /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