Alsa-Devel Archive on 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: Tue, 31 Mar 2009 03:53:28 +0200	[thread overview]
Message-ID: <49D17798.6040205@ponctey.fr> (raw)
In-Reply-To: <498A1EBC.9060203@ponctey.fr>

Hi all, I bought motherboards intel DP35DP and DG33TL and just tried
ADAT output in Alsa (ADAT output on them is proven to work under windows).
I wrote the command (thanks to the work of Matthew for the 'IEC958
Playback Source' control.28 setting) :
amixer sset 'IEC958 Playback Source' ADAT

Here is my resulting alsainfo:
www.alsa-project.org/db/?f=cb01bf4f7bc62fe69f36bc1a4bbc0dbcace20605

It still does not work
I think the reason is that contrary to the windows driver the
Node 0x21 is still unchanged :
Pin Default 0x01452150: [Jack] SPDIF Out
whereas it should be better with :
		0x01552150

How can I change my computer from the Pin default config to this
alternative Pin config ?

Anybody has any other idea to help ?
Thanks a lot, Eric

> Hi Steven,
> I have studied the hd audio documents :
> Please make sure the pin default is actually 015521xx when in ADAT mode
> (instead of config default 014521xx ) .
> 
> Please copy me your alsainfo script if it still does not work.
> Matthew Ranostay is right : really not much is missing or wrong for ADAT
> to work.
> Thanks everybody for future help, Eric
> Tellman, Steven a écrit :
>> It doesn't work. The option comes up, but no dice. Doesn't lock to the
>> receiver that has ADAT support.

>> Hello Eric,
>> You should run the latest ALSA from the git tree because I added a codec
>> specific SPDIF output control control for that chipset.
>> ....
>>  417 static const char *stac927x_spdif_labels[5] = {
>>  418     "Digital Playback", "ADAT", "Analog Mux 1",
>>  419     "Analog Mux 2", "Analog Mux 3"
>>  420 };
>> ....
>> I haven't tested ADAT output though but I have no reason to
>> think it wouldn't work.
>> Thanks,
>> Matt Ranostay
>>
>>
>> Eric wrote:
>>> In their handbook, motherboard intel DP35DP and others with STAC927x
>> (in
>>> the codec datasheet also ADAT output is featured on older sigmatel
>>> STAC9271 and now IDT STAC9274 only) advertise ADAT output possible on
>>> their toslink.
>>> DP35DP and other intel boards are proven to have the ADAT output
>> working
>>> under windows.
>>> Is it working in Alsa ?>>>
>>> Anybody from intel or IDT/sigmatel to confirm (by checking the
>> sigmatel
>>> STAC927x hda codec driver) that it will work ?
>>> I want these intel motherboards only for this ADAT output feature and
>> I
>>> am a linux only user so I would like to know before buying...
>>> I want to be sure someone would make the necessary changes to the hda
>>> sigmatel codec alsa driver so it would work.

  reply	other threads:[~2009-03-31  1:54 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
2009-02-04 23:03         ` Eric
2009-03-31  1:53           ` Eric [this message]
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=49D17798.6040205@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox