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: Mon, 14 Feb 2005 16:05:19 +0100	[thread overview]
Message-ID: <s5hr7jjchcg.wl@alsa2.suse.de> (raw)
In-Reply-To: <420CDDB9.6040805@request.com>

At Fri, 11 Feb 2005 11:30:49 -0500,
Ron Cococcia wrote:
> 
> [1  <text/plain; ISO-8859-1 (7bit)>]
> Takashi Iwai wrote:
> > At Thu, 10 Feb 2005 14:16:12 -0500,
> > Ron Cococcia wrote:
> > 
> >>I had been looking through that block of code, and had made some of my 
> >>own "tweaks".  What I did was make "reg_ok" an array (size 4, all 
> >>initialized to 0).  I used the codec index (cidx) to index into that 
> >>array.  The idea is that there would be a reg_ok for each codec, instead 
> >>of just 1 for all codecs.  This correctly set the output on all codecs 
> >>after making the change.
> > 
> > 
> > Yeah, that's better than my last hack.  Could you create a patch?
> 
> Attached.  I had a backup copy of the file that I diff'd against.  This 
> is also based off of 1.0.8 files, but from what I could see the 
> ac97_pcm.c file hasn't changed.  You'll also see a few snd_printk's in 
> there that I had for testing/debugging purposes.  You can get rid of 
> them if you want.

Thanks, applied to CVS (yes I removed printks :)

> I'm not sure what the implications of changing the rates on all of the 
> codecs are.  Is it possible that, in a multiple codec configuration, 
> there would be a situation where they would want to be handling 
> different rates?

Well, the current ac97 codec driver doesn't consider the multi stream
case.  And, AFAIK, no controller supports different sample rates for
each codec.  (Different rates can be used for different slots,
though.)


Takashi


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

  reply	other threads:[~2005-02-14 15:05 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
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 [this message]
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=s5hr7jjchcg.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.