From: Nishanth Menon <menon.nishanth@gmail.com>
To: Raghunandan Dhongadi <dk.raghu@gmail.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: Sample AIC33 loopback test
Date: Sun, 07 Jan 2007 21:59:45 -0600 [thread overview]
Message-ID: <45A1C1B1.3010704@gmail.com> (raw)
In-Reply-To: <7d8fdf6f0701071950l54a35c9ncaa13895a433691a@mail.gmail.com>
Raghunandan Dhongadi stated on 1/7/2007 9:50 PM:
> Referring the e-mail on the "davinci" mailing list, I wanted to have
> some advice on the following approach.
>
?? can u put in the thread link?
> I have a OMAP2430 application and, I am trying to have the Audio Codec
> AIC31B driver for I2S ( Data channel ) interface on the DSP core side,
> and teh AIC31B driver for I2C ( control channel ) on the ARM code
> side.
I2S on 2430 is supported on McBSP. you can configure it pretty easily,
two options:
1. handle all configuration of mcbsp and data dump to mcbsp from DSP and
handle only the codec configuration from ARM
2. handle configuration of mcbsp and codec from ARM and data dump only
from DSP.
The decision of which depends on the options you do have in your s/w
stack. if u make mcbsp on omap as slave, then you have more flexibility
in configuration.
McBSP configuration wise: depending on the amt of work u'd want to do.
the simple soln, do a arm side playback (if u already have access to the
working drivers), and break it on a ICD, dump the registers... ;)
S/w perspective is interesting, since default oss and alsa assume that
data flows on arm side.. guess u'd have to redirect configuration
commands and data flow seperately... this is another interesting thing
for all of us to solve someday... with multiprocessors on a single die
sharing differing responsibilities on the same external peripheral..
dont think we have a ready made architecture to use at the moment..
Regards,
Nishanth Menon
prev parent reply other threads:[~2007-01-08 3:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-08 3:50 Sample AIC33 loopback test Raghunandan Dhongadi
2007-01-08 3:59 ` Nishanth Menon [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=45A1C1B1.3010704@gmail.com \
--to=menon.nishanth@gmail.com \
--cc=dk.raghu@gmail.com \
--cc=linux-omap-open-source@linux.omap.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