From: Peter Heatwole <peter599@gotnet.net>
To: Benny Sjostrand <gorm@cucumelo.org>
Cc: Takashi Iwai <tiwai@suse.de>, alsa-devel@alsa-project.org
Subject: Re: More CS4630, secondary CODEC output.
Date: Fri, 2 Aug 2002 08:47:53 -0700 [thread overview]
Message-ID: <20020802154753.GA718@porky> (raw)
In-Reply-To: <3D4A1DDF.2090404@cucumelo.org>; from gorm@cucumelo.org on Thu, Aug 01, 2002 at 22:51:27 -0700
On 2002.08.01 22:51 Benny Sjostrand wrote:
> On the "Turtle Beach Santa Cruz" now i know that GPIO7/GPIO8 on sec.
> codec controls back speakers, that's not done yet,
> But I would like to know if current code at least detects the secondary
> CODEC successfully. In theory it should.
[...]
> Turtle Beach Santa Cruz
> dsp: cs4630
> primary codec: cs4294
> secondary codec: cs4297A
> GPIO7/GPIO8 on secondary codec controls back speakers support
Actually, the codecs are reversed. The CS4297A is the primary codec,
and
the CS4294 is the secondary. And yes, your driver detects them both just
fine and I can manipulate both with alsamixer and confirm the changes to
the CS4294 with the changes in the "ac97#0-1regs" file in
/proc/asound/card0.
-- Peter Heatwole
"Murphy was just a well known pessimist."
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2002-08-02 15:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-26 23:01 More CS4630, secondary CODEC output Benny Sjostrand
2002-07-27 0:36 ` Peter Heatwole
2002-07-27 7:02 ` Benny Sjostrand
2002-07-27 15:13 ` Frank van de Pol
2002-07-27 16:13 ` Peter Heatwole
2002-08-01 1:14 ` Peter Heatwole
2002-08-01 9:40 ` Takashi Iwai
2002-08-01 9:39 ` Benny Sjostrand
2002-08-01 10:57 ` Takashi Iwai
2002-08-01 12:42 ` Takashi Iwai
2002-08-01 12:57 ` Benny Sjostrand
2002-08-02 5:51 ` Benny Sjostrand
2002-08-02 10:14 ` Takashi Iwai
2002-08-02 15:47 ` Peter Heatwole [this message]
2002-08-02 18:16 ` Benny Sjostrand
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=20020802154753.GA718@porky \
--to=peter599@gotnet.net \
--cc=alsa-devel@alsa-project.org \
--cc=gorm@cucumelo.org \
--cc=tiwai@suse.de \
/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.