From: Clemens Ladisch <clemens@ladisch.de>
To: "Couch, Kelly J" <kelly.j.couch@intel.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: How to Tx/Rx data via TDM/I2S interface of Intel HD Audio controller without a CODEC attached?
Date: Fri, 30 Mar 2012 09:40:16 +0200 [thread overview]
Message-ID: <4F756360.6020407@ladisch.de> (raw)
In-Reply-To: <934D8D6A4B048048942509C4D57C8A400A845BA6@ORSMSX103.amr.corp.intel.com>
Couch, Kelly J wrote:
> I'm designing software for a specific test application that will
> utilize an Intel HD audio controller. I must verify the functionality
> of several sets of TDM audio signals (CK, FS, TXD, RXD) from the Intel
> HD Audio controller. In this scenario, the Intel HD Audio controller
> is NOT connected directly to a CODEC, but to a header. My proposal
> is to connect these signals directly to an FPGA, using it to loopback
> the data (in various permutations of loopback to channels) to verify
> each of the signals.
Let's see what the spec says:
| SDO – Serial Data Out: [...] Data is double pumped – i.e., the
| controller drives data onto SDO, and codecs sample data present on
| SDO with respect to every edge of BCLK. [...]
| SDI – Serial Data In: [...] Data is single pumped; codecs drive SDI
| and the controller samples SDI with respect to the rising edge of
| BCLK.
Oh, and outbound and inbound frames use a different format.
I guess this why you're using an FPGA instead of a wire? :)
> Because the FPGA will be in place of a real CODEC device, I'm
> concerned with how the software side of this approach will work?
The ALSA driver tries to detect the capabilities of the codec(s).
You would have to replace all codec read accesses with hardcoded values
that describe a virtual codec with a suitable widget topology.
Regards,
Clemens
prev parent reply other threads:[~2012-03-30 7:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 20:12 How to Tx/Rx data via TDM/I2S interface of Intel HD Audio controller without a CODEC attached? Couch, Kelly J
2012-03-30 7:40 ` Clemens Ladisch [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=4F756360.6020407@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=kelly.j.couch@intel.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 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.