From: "Cássio Gabriel Monteiro Pires" <cassiogabrielcontato@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Takashi Iwai <tiwai@suse.com>, Jaroslav Kysela <perex@perex.cz>,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: ac97: drop stale CMI9738 PCM-volume quirk
Date: Wed, 29 Apr 2026 10:04:38 -0300 [thread overview]
Message-ID: <f2636cc2-4e49-4a20-bc68-54c6ed830ecd@gmail.com> (raw)
In-Reply-To: <87h5ouos8m.wl-tiwai@suse.de>
[-- Attachment #1.1: Type: text/plain, Size: 972 bytes --]
On 4/29/26 09:39, Takashi Iwai wrote:
> On Wed, 29 Apr 2026 14:05:31 +0200,
> Cássio Gabriel wrote:
>>
>> patch_cm9738() still carries an old comment claiming that CMI9738
>> has no PCM volume although AC97_PCM reacts, and then forces
>> AC97_HAS_NO_PCM_VOL.
>>
>> The CMI9738 datasheet documents register 0x18 as "PCM Out Vol"
>> with mute and left/right volume fields, so that old assumption is
>> not justified.
>
> Well, that's actually the part the FIXME points to. Although the spec
> shows the register is available and the chip reads out, the volume
> didn't seem reacting properly on the real hardware, as far as I
> remember correctly.
>
> So, it's really doubtful whether it's safe to cut off this workaround
> just by reading the data sheet.
Yes, that matches what I suspected at first glance; I wanted to confirm
whether the datasheet was enough to revisit the old workaround.
> thanks,
>
> Takashi
--
Thanks,
Cássio
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
prev parent reply other threads:[~2026-04-29 13:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-29 12:05 [PATCH] ALSA: ac97: drop stale CMI9738 PCM-volume quirk Cássio Gabriel
2026-04-29 12:39 ` Takashi Iwai
2026-04-29 13:04 ` Cássio Gabriel Monteiro Pires [this message]
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=f2636cc2-4e49-4a20-bc68-54c6ed830ecd@gmail.com \
--to=cassiogabrielcontato@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--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.