From: Jarkko Nikula <jarkko.nikula@nokia.com>
To: "ext Pharaoh ." <pharaoh137@gmail.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: Qeury regarding EAC driver for omap 24xx
Date: Wed, 6 Jun 2007 15:04:30 +0300 [thread overview]
Message-ID: <20070606150430.e4d55f5c.jarkko.nikula@nokia.com> (raw)
In-Reply-To: <61445c750706060402q34388d3fm7bf2c097b34f6346@mail.gmail.com>
On Wed, 6 Jun 2007 16:32:24 +0530
"ext Pharaoh ." <pharaoh137@gmail.com> wrote:
> I am referring the EAC driver for omap 24xx which is used by n800
> board. The EAC 24xx driver
> doesn't look complete since it has only hardware init sequences and
> very basic ALSA related
> functionalities i.e. register the sound card etc. Is omap 24xx eac
> driver still in intermediate stage?Or
> it is complete but not yet integrated in to omap git tree? In later
> case, where can I find the complete
> eac driver?
>
That's correct, it is mainly targeted for N800 where audio is coming
from DSP side and driver is only charge of configuring digital audio
interface and doing runtime clock and codec power management.
I agree that native EAC ALSA PCM support would be nice but unfortunately
we don't have any progress on that developing it.
> Also, omap 24xx driver doesn't seem to follow the framework/structure
> of other omap alsa
> drivers in sound/arm/omap/ , any particular reason? Please enlighten.
>
I think drivers in sound/arm/omap are somewhat "adrift". Codec drivers
are tightly coupled into OMAP, they implement same global functions so
that you cannot link them together, no clear separation between audio
controller and codec, etc.
Hopefully we see gradually those drivers ported into ASoC platform and
codec drivers in order to get some change to get them into mainline.
Jarkko
next prev parent reply other threads:[~2007-06-06 12:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-06 11:02 Qeury regarding EAC driver for omap 24xx Pharaoh .
2007-06-06 12:04 ` Jarkko Nikula [this message]
2007-06-06 12:33 ` Pharaoh .
2007-06-06 12:51 ` Dmitry Krivoschekov
2007-06-06 13:02 ` Jarkko Nikula
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=20070606150430.e4d55f5c.jarkko.nikula@nokia.com \
--to=jarkko.nikula@nokia.com \
--cc=linux-omap-open-source@linux.omap.com \
--cc=pharaoh137@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