From: Takashi Iwai <tiwai@suse.de>
To: Kailang <kailang@realtek.com>
Cc: " (alsa-devel@alsa-project.org)" <alsa-devel@alsa-project.org>
Subject: Re: ALC256 speaker noise issue
Date: Mon, 30 May 2016 14:12:29 +0200 [thread overview]
Message-ID: <s5hwpmbd9si.wl-tiwai@suse.de> (raw)
In-Reply-To: <s5hzir7d9y4.wl-tiwai@suse.de>
On Mon, 30 May 2016 14:09:07 +0200,
Takashi Iwai wrote:
>
> On Mon, 30 May 2016 10:13:13 +0200,
> Kailang wrote:
> >
> > Hi Takashi,
> >
> > ALC256 had speaker noise issue.
> > Attach patch will solve it.
> >
> > This issue is cause from LDO output voltage control.
> > This patch is updated the right LDO register value.
>
> Applied, thanks.
Oh, I forgot to mention that there was a typo in the original patch
(alc255fw[] vs alc256fw[]), so I fixed it manually.
Takashi
next prev parent reply other threads:[~2016-05-30 12:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6FAB7C47BCF00940BB0999A99BE3547A17A3E4E9@RTITMBSV09.realtek.com.tw>
2016-05-30 12:09 ` ALC256 speaker noise issue Takashi Iwai
2016-05-30 12:12 ` Takashi Iwai [this message]
2016-05-31 3:16 ` Kailang
[not found] ` <6FAB7C47BCF00940BB0999A99BE3547A17A3E514@RTITMBSV09.realtek.com.tw>
2016-05-30 12:12 ` Add support for new codecs ALC700/ALC701/ALC703 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=s5hwpmbd9si.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=kailang@realtek.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox