From: Dirk Behme <dirk.behme@googlemail.com>
To: "Rajashekara, Suresh" <suresh.r@ti.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: ALSA on OMAP?
Date: Fri, 23 Feb 2007 07:31:19 +0100 [thread overview]
Message-ID: <45DE8A37.2000504@googlemail.com> (raw)
In-Reply-To: <7EAD1AEEA7621C45899FE99123E124A0B12DD9@dbde01.ent.ti.com>
Rajashekara, Suresh wrote:
> Has anyone successfully tried ALSA on OMAP development boards?
Yes.
> If yes, on which board and which kernel version?
ALSA in recent OMAP git (and most older versions since
2.6.16 (?)) works on OMAP5912 OSK.
Regards
Dirk
P.S.: My ALSA config for OSK:
#
# Sound
#
CONFIG_SOUND=m
#
# Advanced Linux Sound Architecture
#
CONFIG_SND=m
CONFIG_SND_TIMER=m
CONFIG_SND_PCM=m
# CONFIG_SND_SEQUENCER is not set
CONFIG_SND_OSSEMUL=y
# CONFIG_SND_MIXER_OSS is not set
CONFIG_SND_PCM_OSS=m
CONFIG_SND_PCM_OSS_PLUGINS=y
# CONFIG_SND_DYNAMIC_MINORS is not set
# CONFIG_SND_SUPPORT_OLD_API is not set
CONFIG_SND_VERBOSE_PROCFS=y
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set
...
#
# ALSA ARM devices
#
CONFIG_SND_OMAP_AIC23=m
# CONFIG_SND_OMAP_TSC2101 is not set
# CONFIG_SND_SX1 is not set
# CONFIG_SND_OMAP_TSC2102 is not set
#
# I2C support
#
CONFIG_I2C=y
CONFIG_I2C_CHARDEV=y
...
#
# I2C Hardware Bus support
#
# CONFIG_I2C_OCORES is not set
CONFIG_I2C_OMAP=y
# CONFIG_I2C_PARPORT_LIGHT is not set
# CONFIG_I2C_STUB is not set
# CONFIG_I2C_PCA_ISA is not set
#
# Miscellaneous I2C Chip support
#
...
# CONFIG_ISP1301_OMAP is not set
CONFIG_TPS65010=y
CONFIG_SENSORS_TLV320AIC23=y
# CONFIG_GPIOEXPANDER_OMAP is not set
...
#
# OMAP Feature Selections
#
...
# CONFIG_OMAP_STI is not set
CONFIG_OMAP_MCBSP=y
# CONFIG_OMAP_MPU_TIMER is not set
...
prev parent reply other threads:[~2007-02-23 6:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-23 5:34 ALSA on OMAP? Rajashekara, Suresh
2007-02-23 6:31 ` Dirk Behme [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=45DE8A37.2000504@googlemail.com \
--to=dirk.behme@googlemail.com \
--cc=linux-omap-open-source@linux.omap.com \
--cc=suresh.r@ti.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