All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jaroslaw Sobierski <fycio@gucio.com>
To: alsa-devel@lists.sourceforge.net
Subject: S/PDIF on AD1980 patch
Date: Thu, 13 Feb 2003 03:19:02 -0800	[thread overview]
Message-ID: <1045135142.3e4b7f26649c8@webmail3.namezero.com> (raw)


Hi all,

I recently installed an Asus P4PE with built in AD1980 audio codec
(accessible through the ICH4 south bridge). The latest ALSA drivers
detected the chip and AC97 audio correctly even setting up the 
IEC958 controls. The problem is I still got no output on the external
S/PDIF module. 

I downloaded the specs from Analog Devices and found the register
responsible for this, modified the AC97 codec drivers to add a
control for the 3 flags specific to this chip (ie. outside of the ac97
specification) concerning the digital interface and managed to turn
it on. 

I would like to submit this modification so that others who may have
a similar setup can use it. So my question is : what's next? Who can
merge such patches to the CVS tree and what is the validation and/or
testing procedure? Or do I just mail the code to 'perex' and he takes
care of it?

I found similar patches for different chips with controls specific to
them, so I assume this is the accepted solution, although it would
also be possible simply initialize this register to the "on" value on
startup - since this is a dedicated digital output, not shared with 
lfe/center like on Creative's sound cards.

Jaroslaw Sobierski


--------------
Fycio (J.Sobierski)
 fycio@gucio.com


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

             reply	other threads:[~2003-02-13 11:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-13 11:19 Jaroslaw Sobierski [this message]
2003-02-13 11:40 ` S/PDIF on AD1980 patch Takashi Iwai
  -- strict thread matches above, loose matches on Subject: below --
2003-02-14 23:32 Jaroslaw Sobierski
2003-02-16 12:39 ` Jaroslav Kysela
2003-02-17 16:01 Jaroslaw Sobierski
2003-02-18 16:59 ` Takashi Iwai
2003-02-20  9:01   ` Jaroslaw Sobierski
2003-02-20 11:13     ` Takashi Iwai
2003-02-20 21:29       ` Jaroslaw Sobierski
2003-02-17 19:36 Jaroslaw Sobierski
2003-02-18 16:50 ` Takashi Iwai
2003-02-19 10:48   ` Jaroslaw Sobierski
2003-02-20  8:37   ` Jaroslaw Sobierski

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=1045135142.3e4b7f26649c8@webmail3.namezero.com \
    --to=fycio@gucio.com \
    --cc=alsa-devel@lists.sourceforge.net \
    /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.