From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Henningsson Subject: Re: [RFC PATCH] ALSA: hda - Keep power link on for PantherPoint HDMI Date: Mon, 19 Nov 2012 15:14:45 +0100 Message-ID: <50AA3ED5.5070809@canonical.com> References: <1352276553-26044-1-git-send-email-david.henningsson@canonical.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: Received: from youngberry.canonical.com (youngberry.canonical.com [91.189.89.112]) by alsa0.perex.cz (Postfix) with ESMTP id 1AB0A2616E3 for ; Mon, 19 Nov 2012 15:14:44 +0100 (CET) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: alsa-devel-bounces@alsa-project.org Sender: alsa-devel-bounces@alsa-project.org To: Takashi Iwai Cc: alsa-devel@alsa-project.org, fengguang.wu@intel.com, "jesse.sung" , 1075882@bugs.launchpad.net List-Id: alsa-devel@alsa-project.org On 11/07/2012 09:36 AM, Takashi Iwai wrote: > At Wed, 7 Nov 2012 09:22:33 +0100, > David Henningsson wrote: >> >> On some of the PantherPoint HDMI machines we currently enable, we're seeing >> trouble with unsol events, i e detecting monitor presence, especially when >> on battery and after suspend/resume. >> >> BugLink: https://bugs.launchpad.net/bugs/1075882 >> Tested-by: Cyrus Lien >> Signed-off-by: David Henningsson >> --- >> sound/pci/hda/patch_hdmi.c | 8 ++++++-- >> 1 file changed, 6 insertions(+), 2 deletions(-) >> >> So far this is the workaround we have found to be working. Sometimes, it also >> seems that "cat /proc/asound/cardx/codec#x" can also make the HDMI unsol event >> trigger, so that the problem fixes itself. >> >> We have not run any battery life tests to see if this causes more power consumption. > > Looks safe at least, so I applied to for-next branch to give more > testing. If you find a better solution, let me know. Jesse has now done a battery life test, both for idle machine and S3 machine, and both with HDMI connected and HDMI unconnected. All differences in power consumption were within error margins. Given that, should we consider sending this patch to stable? -- David Henningsson, Canonical Ltd. https://launchpad.net/~diwic