Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Kailang <kailang@realtek.com>
Cc: " (alsa-devel@alsa-project.org)" <alsa-devel@alsa-project.org>
Subject: Re: ALC1150 COEF
Date: Wed, 12 Nov 2014 11:32:59 +0100	[thread overview]
Message-ID: <s5hlhngn1yc.wl-tiwai@suse.de> (raw)
In-Reply-To: <6FAB7C47BCF00940BB0999A99BE3547A179FB052@RTITMBSV09.realtek.com.tw>

At Wed, 12 Nov 2014 10:02:33 +0000,
Kailang wrote:
> 
> 
> I merge all codec into alc_fill_eapd_coef().
> Please see attach.
> Many Thanks. ^^

Thanks, I applied the patch with a few additional notes about the
problem.

Unfortunately, this can't go to stable kernel cleanly because it
requires the recent COEF accessor changes.


Takashi

> 
> > -----Original Message-----
> > From: Takashi Iwai [mailto:tiwai@suse.de] 
> > Sent: Wednesday, November 12, 2014 4:39 PM
> > To: Kailang
> > Subject: Re: ALC1150 COEF
> > 
> > At Wed, 12 Nov 2014 08:27:56 +0000,
> > Kailang wrote:
> > > 
> > > Hi Takashi,
> > > 
> > > I cooked a patch for this issue as attach. 
> > > It is not include ALC26x ALC28x ALC29x.
> > > If you agree this patch,
> > > could it merge into one patch?
> > 
> > Yes, it looks good.  Could you submit it with proper 
> > changelog etc as usual to alsa-devel ML?  Then I'll queue it 
> > for 3.18-rc5.
> > 
> > 
> > thanks,
> > 
> > Takashi
> > 
> > > 
> > > BR,
> > > Kailang
> > > 
> > > > -----Original Message-----
> > > > From: Takashi Iwai [mailto:tiwai@suse.de]
> > > > Sent: Wednesday, November 12, 2014 4:08 AM
> > > > To: Kailang
> > > > Subject: ALC1150 COEF
> > > > 
> > > > Hi Kailang,
> > > > 
> > > > we've got bug reports about the silent output on mobos 
> > with ALC1150 
> > > > after Windows reboot.  It seems that COEF 0x07 bit
> > > > 0x02 plays some role.  Could you check it?
> > > > 	https://bugzilla.kernel.org/show_bug.cgi?id=87771
> > > > 
> > > > thanks,
> > > > 
> > > > Takashi
> > > > 
> > > > ------Please consider the environment before printing this e-mail.
> > > > 
> > > [2 0000-reset-eapd-control.patch <application/octet-stream 
> > (base64)>]
> > > 
> > 
> [2 0000-change-eapd-to-verb-control.patch <application/octet-stream (base64)>]
> 

  reply	other threads:[~2014-11-12 10:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <s5hr3x9qz5j.wl-tiwai@suse.de>
     [not found] ` <6FAB7C47BCF00940BB0999A99BE3547A179FB004@RTITMBSV09.realtek.com.tw>
     [not found]   ` <s5h8ujgrext.wl-tiwai@suse.de>
2014-11-12 10:02     ` ALC1150 COEF Kailang
2014-11-12 10:32       ` Takashi Iwai [this message]
2014-11-19  7:13     ` HP mute led for ALC286 Kailang
2014-11-19 11:27       ` Takashi Iwai
2014-11-20  7:04         ` Kailang
2014-11-20 10:05           ` Takashi Iwai
2014-11-21  7:56             ` Kailang
2014-11-21  9:59               ` 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=s5hlhngn1yc.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