From: bgat@billgatliff.com (Bill Gatliff)
To: linux-arm-kernel@lists.infradead.org
Subject: AC97 audio broken on SAM9263EK?
Date: Wed, 24 Feb 2010 13:06:05 -0600 [thread overview]
Message-ID: <4B85789D.6000704@billgatliff.com> (raw)
Guys:
It looks like AC97 support for the SAM9263EK isn't in the current
mainline kernel. Or am I just missing something?
More specifically, it looks like the "atmel_ac97c" driver found in
sound/atmel/ac97c.c is what I need, based on my look at
at91_add_device_ac97(). But I see this in sound/atmel/Kconfig:
config SND_ATMEL_AC97C
tristate "Atmel AC97 Controller (AC97C) driver"
select SND_PCM
select SND_AC97_CODEC
depends on DW_DMAC && AVR32
And I see this in sound/atmel/Makefile:
snd-atmel-abdac-objs := abdac.o
snd-atmel-ac97c-objs := ac97c.o
obj-$(CONFIG_SND_ATMEL_ABDAC) += snd-atmel-abdac.o
obj-$(CONFIG_SND_ATMEL_AC97C) += snd-atmel-ac97c.o
In other words, the driver isn't built unless I'm on an AVR32 platform
and I have a DesignWare DMAC. Neither of those describe the AT91SAM9263EK.
Has anyone tested AC97 audio on the SAM9263EK lately? Has it ever worked?
Thanks!
--
Bill Gatliff
Embedded systems training and consulting
http://billgatliff.com
bgat at billgatliff.com
next reply other threads:[~2010-02-24 19:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-24 19:06 Bill Gatliff [this message]
2010-02-25 10:09 ` AC97 audio broken on SAM9263EK? 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
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=4B85789D.6000704@billgatliff.com \
--to=bgat@billgatliff.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.