From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kailang Subject: Re: Support low power consumption for ALC3254 Date: Tue, 7 May 2019 09:23:25 +0000 Message-ID: <6FAB7C47BCF00940BB0999A99BE3547A1D765ABD@RTITMBSVM07.realtek.com.tw> References: <6FAB7C47BCF00940BB0999A99BE3547A1D765A46@RTITMBSVM07.realtek.com.tw> <6FAB7C47BCF00940BB0999A99BE3547A1D765A7C@RTITMBSVM07.realtek.com.tw> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from rtits2.realtek.com.tw (rtits2.realtek.com [211.75.126.72]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by alsa1.perex.cz (Postfix) with ESMTPS id B0B4BF807B5 for ; Tue, 7 May 2019 11:23:30 +0200 (CEST) In-Reply-To: Content-Language: zh-TW List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: alsa-devel-bounces@alsa-project.org Sender: "Alsa-devel" To: Takashi Iwai Cc: " (alsa-devel@alsa-project.org)" List-Id: alsa-devel@alsa-project.org > -----Original Message----- > From: Takashi Iwai > Sent: Tuesday, May 7, 2019 5:15 PM > To: Kailang > Cc: (alsa-devel@alsa-project.org) > Subject: Re: Support low power consumption for ALC3254 > > On Tue, 07 May 2019 11:07:14 +0200, > Kailang wrote: > > > > Hi Takashi, > > > > I had sent other patch before. > > Could it can apply? > > Which patch, specifically? I resent again. > > > > -----Original Message----- > > > From: Takashi Iwai > > > Sent: Tuesday, May 7, 2019 4:40 PM > > > To: Kailang > > > Cc: (alsa-devel@alsa-project.org) > > > Subject: Re: Support low power consumption for ALC3254 > > > > > > On Tue, 07 May 2019 09:53:24 +0200, > > > Kailang wrote: > > > > > > > > Hi Takashi, > > > > > > > > Chrome OS want to support low power consumption. > > > > This patch will support low consumption. > > > > > > Looks mostly OK, but one question: why hp_pin isn't set? > > > > If hp_pin not assigned, depop procedure must run. > > So, if system doesn't have HP. It must assigned default 0x21 pin to run depop > procedure. > > OK, point taken. So it's not a headphone pin but other output pin that > requires the same depop workaround. But machine without HP was very few. I don't find it until now. > > Now applied the patch. Thanks. > > > Takashi > > ------Please consider the environment before printing this e-mail.