From: yegor_sub1@visionsystems•de (Yegor Yefremov)
To: linux-arm-kernel@lists•infradead.org
Subject: AC97 audio broken on SAM9263EK?
Date: Tue, 01 Jun 2010 15:39:35 +0200 [thread overview]
Message-ID: <4C050D97.4000404@visionsystems.de> (raw)
In-Reply-To: <4B97C086.2080404@atmel.com>
Hi,
>> When do you think the driver could hit the mainline kernel? Till
>> 2.6.35 open window?
>
> It has been acked, but I don't know when it will be in the mainline kernel.
have just tested 2.6.35-rc1 with mainline ac97 driver and found this issue. During playback I see following output on the console:
...
atmel_ac97c atmel_ac97c.0: channel A event
atmel_ac97c atmel_ac97c.0: channel A event
atmel_ac97c atmel_ac97c.0: channel A event
...
If I see it right these, lines come from sound/atmel/ac97c.c->atmel_ac97c_interrupt():
dev_info(&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" : "",
casr & AC97C_CSR_TXEMPTY ? " TXEMPTY" : "",
casr & AC97C_CSR_TXRDY ? " TXRDY" : "",
!casr ? " NONE" : "");
It is necessary to output this message in normal mode or is it a debug message?
Regards,
Yegor
next prev parent reply other threads:[~2010-06-01 13:39 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 [this message]
2010-06-03 12:46 ` Sedji Gaouaou
2010-06-03 14:02 ` Yegor Yefremov
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=4C050D97.4000404@visionsystems.de \
--to=yegor_sub1@visionsystems$(echo .)de \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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