All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Ron Cococcia <ron.cococcia@request.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: intel8x0 dual codec issue
Date: Thu, 10 Feb 2005 18:27:08 +0100	[thread overview]
Message-ID: <s5h8y5w1g2b.wl@alsa2.suse.de> (raw)
In-Reply-To: <4208437B.3080207@request.com>

[-- Attachment #1: Type: text/plain, Size: 1430 bytes --]

At Mon, 07 Feb 2005 23:43:39 -0500,
Ron Cococcia wrote:
> 
> Hello,
> 
> I'm having a little trouble with a dual codec setup that I am using. 
> The motherboard has an Intel 815 chip (82801BAICH2).  The motherboard 
> has the primary (00) codec, which is an AD1885.  A secondary (01) codec 
> has been added over a CNR connector.  This one is a CS4299.  The 
> secondary codec uses the timing values generated by the primary.
> 
> I had been hearing some distortion in the audio.  It was quite 
> noticeable.  Using a wav file of sine waves that has different 
> frequencies (440, 880, 1760, 3520) at 44100Hz, I could see that there 
> was some jitter on a scope.  As the frequencies went up, it got worse. 
> I then created another test file with the same frequencies, but sampled 
> at 48000Hz.  Playback of that audio was extremely clean on the scope.
> 
> Looking into it more, I noticed that the PCM front DAC (ac97#1-1) was 
> not adjusting itself to the appropriate frequency.  The DAC on the 
> primary codec was switching between 44100Hz and 48000Hz when I played 
> the different samples.
> 
> I'd like to have the secondary codec reflect the output rate that is 
> being sent to it.  How might I get it to do this?  Is it a bug (should 
> the codec front DAC on the secondary codec reflect the appropriate 
> frequency?), or how is it intended to work?

I guess it's a bug.  Could you try the attached patch?


Takashi

[-- Attachment #2: Type: text/plain, Size: 701 bytes --]

Index: alsa-kernel/pci/ac97/ac97_pcm.c
===================================================================
RCS file: /suse/tiwai/cvs/alsa/alsa-kernel/pci/ac97/ac97_pcm.c,v
retrieving revision 1.19
diff -u -r1.19 ac97_pcm.c
--- alsa-kernel/pci/ac97/ac97_pcm.c	27 Dec 2004 13:19:32 -0000	1.19
+++ alsa-kernel/pci/ac97/ac97_pcm.c	10 Feb 2005 17:19:45 -0000
@@ -602,8 +602,10 @@
 					snd_printk(KERN_ERR "invalid AC97 slot %i?\n", i);
 					continue;
 				}
+#if 0
 				if (reg_ok & (1 << (reg - AC97_PCM_FRONT_DAC_RATE)))
 					continue;
+#endif
 				//printk(KERN_DEBUG "setting ac97 reg 0x%x to rate %d\n", reg, rate);
 				err = snd_ac97_set_rate(pcm->r[r].codec[cidx], reg, rate);
 				if (err < 0)

  reply	other threads:[~2005-02-10 17:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-08  4:43 intel8x0 dual codec issue Ron Cococcia
2005-02-10 17:27 ` Takashi Iwai [this message]
2005-02-10 19:16   ` Ron Cococcia
2005-02-11 10:19     ` Takashi Iwai
2005-02-11 16:30       ` Ron Cococcia
2005-02-14 15:05         ` Takashi Iwai
2005-02-24 22:10       ` Ron Cococcia

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=s5h8y5w1g2b.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=ron.cococcia@request.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.