All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric <ejaouen@ponctey.fr>
To: alsa-devel@alsa-project.org
Subject: Re: intel DP35DP adat supported (STAC927x codec) ?
Date: Sat, 31 Jan 2009 13:06:46 +0100	[thread overview]
Message-ID: <49843ED6.5050703@ponctey.fr> (raw)
In-Reply-To: <s5h63jv25pn.wl%tiwai@suse.de>

Their has never been an ADAT input advertised on the STAC927x codec.
What is needed for this codec to work is a switch to change between
SPDIF and ADAT mode OUTPUT (on the backpanel toslink).
As shown in the codec datasheet :
When choosing ADAT mode : node 1Fh ADATout (instead of node 1Eh spdif)
goes to node 21h Digout.

I think I have to buy the DP35DP so we can make and test the driver
modifications for it to work... I am really interested in the intel ADAT
output capable motherboard line.
Thanks

> I think that mux list is reather "the input source" of SPDIF output,
> not the output target.  i.e. if you choose ADAT there, it means that
> the input from ADAT will go to SPDIF output.
> Takashi

  reply	other threads:[~2009-01-31 12:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-11 14:01 idt STAC927x adat supported (sigmatel HDA codec) ? Eric
2009-01-12 11:34 ` Takashi Iwai
2009-01-12 12:46   ` intel DP35DP adat supported (STAC927x " Eric
2009-01-15  0:14     ` Matthew Ranostay
2009-01-30 22:41       ` Tellman, Steven
2009-01-31  9:19         ` Takashi Iwai
2009-01-31 12:06           ` Eric [this message]
2009-02-04 23:03         ` Eric
2009-03-31  1:53           ` Eric
2009-04-04 22:19             ` to support STAC927x ADATout (intel hda mobo) Eric
2009-04-06  1:37             ` modify the 0x21 pin config for ADATout (STAC927x hda codec) ? Eric
2009-04-14 13:33               ` Takashi Iwai
2010-10-04 12:23           ` [STAC927x HDA codec] 0x1F function not supported by driver ? Eric
2011-03-03 11:59             ` [STAC927x HDA codec] 0x1F function not supported bydriver ? Eric

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=49843ED6.5050703@ponctey.fr \
    --to=ejaouen@ponctey.fr \
    --cc=alsa-devel@alsa-project.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.