linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: yegor_sub1@visionsystems.de (Yegor Yefremov)
To: linux-arm-kernel@lists.infradead.org
Subject: AC97 audio broken on SAM9263EK?
Date: Thu, 03 Jun 2010 16:02:59 +0200	[thread overview]
Message-ID: <4C07B613.2040201@visionsystems.de> (raw)
In-Reply-To: <4C07A422.5070505@atmel.com>

Hi Sedji,

> It is an error indeed, it should be a debug message.

here is a patch:

atmel: set "channel A event" output to debug

Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>

Index: b/sound/atmel/ac97c.c
===================================================================
--- a/sound/atmel/ac97c.c	2010-06-01 15:28:23.000000000 +0200
+++ b/sound/atmel/ac97c.c	2010-06-03 15:20:43.000000000 +0200
@@ -657,7 +657,7 @@
 	if (sr & AC97C_SR_CAEVT) {
 		struct snd_pcm_runtime *runtime;
 		int offset, next_period, block_size;
-		dev_info(&chip->pdev->dev, "channel A event%s%s%s%s%s%s\n",
+		dev_dbg(&chip->pdev->dev, "channel A event%s%s%s%s%s%s\n",
 				casr & AC97C_CSR_OVRUN   ? " OVRUN"   : "",
 				casr & AC97C_CSR_RXRDY   ? " RXRDY"   : "",
 				casr & AC97C_CSR_UNRUN   ? " UNRUN"   : "",

      reply	other threads:[~2010-06-03 14:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-24 19:06 AC97 audio broken on SAM9263EK? Bill Gatliff
2010-02-25 10:09 ` Sedji Gaouaou
2010-02-25 12:46   ` Bill Gatliff
2010-02-25 16:49     ` Sedji Gaouaou
2010-02-28  3:23       ` Bill Gatliff
2010-03-01 10:34         ` Sedji Gaouaou
2010-03-09 14:11           ` Yegor Yefremov
2010-03-09 15:17             ` Sedji Gaouaou
2010-03-10  8:47               ` Yegor Yefremov
2010-03-10  9:02                 ` Sedji Gaouaou
2010-03-10 15:41                   ` Yegor Yefremov
2010-03-10 15:53                     ` Sedji Gaouaou
2010-06-01 13:39                       ` Yegor Yefremov
2010-06-03 12:46                         ` Sedji Gaouaou
2010-06-03 14:02                           ` Yegor Yefremov [this message]

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=4C07B613.2040201@visionsystems.de \
    --to=yegor_sub1@visionsystems.de \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).