Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Zoilo Gomez <zoilo@xs4all.nl>
Cc: alsa-devel@alsa-project.org
Subject: Re: [Alsa-user] Jetway j7f2 via82xx volume problem: sound suddenly stops when increasing volume: "SOLVED" (well ... sort of)
Date: Tue, 29 Apr 2008 15:36:31 +0200	[thread overview]
Message-ID: <s5hve20vl40.wl%tiwai@suse.de> (raw)
In-Reply-To: <481721E5.50608@xs4all.nl>

At Tue, 29 Apr 2008 15:25:57 +0200,
Zoilo Gomez wrote:
> 
> >> This is consistent with the apparent introduction of this bug in kernel
> >> 2.6.19 (includes alsa-driver version 1.0.12rc1): no such problem
> >> occurred until 2.6.18, but all kernels since 2.6.19 do suffer from this
> >> problem. The line of code above first shows up in linux-2.6.19.
> >>
> >> Unfortunately, since I do not have a datasheet for the VT1617A chip set,
> >> I cannot verify the exact semantics, or suggest an improvement.
> >>
> >> Can anyone with a datasheet please suggest a proper patch to this line
> >> of code?
> >>     
> >
> > The register 0x5c is the VIA specific one.  I have a VT1617 (without
> > A) datasheet, and it suggests that the bit corresponds to the
> > "headphone amplifier temperature sensing control".  And setting this
> > bit means to _disable_ the temperature sensing control.  This sounds
> > rather the correct to set.
> >
> > However, I don't know whether any difference exists betweeen VIA1617
> > and 1617A although the codec id of both are identical.
> >
> > Andrey, any comments about your patch?
> >
> >
> > In anyway, it'd be helpful if we can know which ac97 registers work
> > and wich not.  Please take /proc/asound/card0/codec97#*/ac97#*-regs
> > file in both working and non-working cases to compare.  Especially,
> > the registers 0x5a and 0x5c look interesting.
> >   
> 
> Code containing "snd_ac97_write_cache(a97, 0x5c, 0x20)":
> 0x5a = 8300
> 0x5c = 0000
> 
> Code with "snd_ac97_write_cache(a97, 0x5c, 0x20)" commented out:
> 0x5a = 8301
> 0x5c = 0020
> 
> Quite a surprise to me, I would have expected exactly the opposite .....!?

I would, too.  Could you double-check, e.g. by adding a printk?
Also, any difference in other registers?

The reg 0x5a bit 0 is a reserved bits, so no further information about
it on VT1617 datasheet.

> Can you explain this? /proc/asound/card0/codec97#0/ac97#0-0+regs does 
> dump current registers, correct? Or is it a toggling bit?

It reads the current register values.  So, it's the value right now.
And snd_ac97_write_cache() should overwrite, not toggle.  The behavior
is really puzzling.


thanks,

Takashi

  reply	other threads:[~2008-04-29 13:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <48063E0E.7010305@xs4all.nl>
     [not found] ` <48111B88.80700@xs4all.nl>
2008-04-28 21:39   ` [Alsa-user] Jetway j7f2 via82xx volume problem: sound suddenly stops when increasing volume: "SOLVED" (well ... sort of) Zoilo Gomez
2008-04-29 12:53     ` Takashi Iwai
2008-04-29 13:25       ` Zoilo Gomez
2008-04-29 13:36         ` Takashi Iwai [this message]
2008-04-30 16:49           ` Zoilo Gomez
2008-05-02 11:03             ` Takashi Iwai
2008-05-02 15:15               ` Zoilo Gomez
2008-05-02 15:23                 ` Takashi Iwai
2008-05-02 17:12                   ` Zoilo Gomez
2008-05-03 15:55                     ` Takashi Iwai

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=s5hve20vl40.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=zoilo@xs4all.nl \
    /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