From: Takashi Iwai <tiwai@suse.de>
To: Kailang <kailang@realtek.com>
Cc: George Gugulea <gugulea@gmail.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: No sound after suspend-to-ram
Date: Mon, 26 Oct 2015 12:39:44 +0100 [thread overview]
Message-ID: <s5hmvv5g8ov.wl-tiwai@suse.de> (raw)
In-Reply-To: <6FAB7C47BCF00940BB0999A99BE3547A17A237D4@RTITMBSV09.realtek.com.tw>
On Mon, 26 Oct 2015 08:45:02 +0100,
Kailang wrote:
>
>
> Attach is the patch.
Looks good to me.
I'm going to queue it once when George confirms that it works indeed.
thanks,
Takashi
>
> > -----Original Message-----
> > From: Takashi Iwai [mailto:tiwai@suse.de]
> > Sent: Monday, October 26, 2015 3:13 PM
> > To: Kailang
> > Cc: George Gugulea; alsa-devel@alsa-project.org
> > Subject: Re: [alsa-devel] No sound after suspend-to-ram
> >
> > On Mon, 26 Oct 2015 08:00:20 +0100,
> > Kailang wrote:
> > >
> > > Hi Takashi,
> > >
> > > [ALC275_FIXUP_DELL_XPS] = {
> > > .type = HDA_FIXUP_VERBS,
> > > .v.verbs = (const struct hda_verb[]) {
> > > /* Enables internal speaker */
> > > {0x20, AC_VERB_SET_COEF_INDEX, 0x1f},
> > > {0x20, AC_VERB_SET_PROC_COEF, 0x00c0},
> > > {0x20, AC_VERB_SET_COEF_INDEX, 0x30},
> > > {0x20, AC_VERB_SET_PROC_COEF, 0x00b1},
> > > {}
> > > }
> > > },
> > >
> > > Could I put code as upper? Was it enter to initial state?
> > > I think it should be execute atfter resume back. Right?
> >
> > Yes, these are performed at resume. But the COEF stuff needs
> > a bit care since it's written in multiple places. If you can
> > cook up the patch, I can check it hda-emu, too.
> >
> >
> > thanks,
> >
> > Takashi
> >
> > ------Please consider the environment before printing this e-mail.
> >
> [2 0000-dell-xps-speaker-no-sound.patch <application/octet-stream (base64)>]
>
next prev parent reply other threads:[~2015-10-26 11:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 8:38 No sound after suspend-to-ram George Gugulea
2015-10-22 15:15 ` Takashi Iwai
2015-10-22 21:23 ` George Gugulea
2015-10-23 7:30 ` Takashi Iwai
2015-10-23 7:34 ` Takashi Iwai
2015-10-23 8:28 ` Kailang
2015-10-23 22:01 ` George Gugulea
2015-10-24 7:38 ` Takashi Iwai
2015-10-26 3:20 ` Kailang
2015-10-26 7:00 ` Kailang
2015-10-26 7:13 ` Takashi Iwai
[not found] ` <6FAB7C47BCF00940BB0999A99BE3547A17A237D4@RTITMBSV09.realtek.com.tw>
2015-10-26 9:00 ` George Gugulea
2015-10-26 11:39 ` Takashi Iwai [this message]
2015-10-26 21:51 ` George Gugulea
2015-10-27 6:50 ` Takashi Iwai
-- strict thread matches above, loose matches on Subject: below --
2015-10-21 17:29 George Gugulea
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=s5hmvv5g8ov.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=gugulea@gmail.com \
--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 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.