From: Kailang <kailang@realtek.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: " (alsa-devel@alsa-project.org)" <alsa-devel@alsa-project.org>,
"linux-sound@vger.kernel.org" <linux-sound@vger.kernel.org>
Subject: RE: update ALC222 depop optimize
Date: Wed, 5 Mar 2025 07:56:41 +0000 [thread overview]
Message-ID: <f7fba6fc8d9e4abfb0c89e487e1d5d89@realtek.com> (raw)
In-Reply-To: <87zfhzud4s.wl-tiwai@suse.de>
> -----Original Message-----
> From: Takashi Iwai <tiwai@suse.de>
> Sent: Wednesday, March 5, 2025 3:54 PM
> To: Kailang <kailang@realtek.com>
> Cc: (alsa-devel@alsa-project.org) <alsa-devel@alsa-project.org>;
> linux-sound@vger.kernel.org
> Subject: Re: update ALC222 depop optimize
>
>
> External mail : This email originated from outside the organization. Do not
> reply, click links, or open attachments unless you recognize the sender and
> know the content is safe.
>
>
>
> On Wed, 05 Mar 2025 07:32:00 +0100,
> Kailang wrote:
> >
> > Hi Takashi,
> >
> > Update ALC222 depop optimize as attach.
>
> Could you give a bit more background info why this change is needed?
> Is it a mandatory change to fix something, or it improves something?
>
This codec has two headphone design.
The HP2 was nid 0x14.
>
> thanks,
>
> Takashi
next prev parent reply other threads:[~2025-03-05 7:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 6:32 update ALC222 depop optimize Kailang
2025-03-05 7:53 ` Takashi Iwai
2025-03-05 7:56 ` Kailang [this message]
2025-03-05 8:16 ` Takashi Iwai
2025-03-05 8:22 ` Kailang
2025-03-05 8:50 ` Takashi Iwai
2025-03-05 9:22 ` Kailang
2025-03-05 9:29 ` Takashi Iwai
2025-03-05 9:33 ` Kailang
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=f7fba6fc8d9e4abfb0c89e487e1d5d89@realtek.com \
--to=kailang@realtek.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-sound@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox