From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755677AbbJ1KqF (ORCPT ); Wed, 28 Oct 2015 06:46:05 -0400 Received: from youngberry.canonical.com ([91.189.89.112]:42124 "EHLO youngberry.canonical.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754169AbbJ1KqD (ORCPT ); Wed, 28 Oct 2015 06:46:03 -0400 Date: Wed, 28 Oct 2015 10:45:59 +0000 From: Luis Henriques To: Michel =?iso-8859-1?Q?D=E4nzer?= Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org, kernel-team@lists.ubuntu.com, Alex Deucher Subject: Re: [PATCH 3.16.y-ckt 072/104] drm/radeon: Restore LCD backlight level on resume (>= R5xx) Message-ID: <20151028104559.GB2792@ares> References: <1445867006-18048-1-git-send-email-luis.henriques@canonical.com> <1445867006-18048-73-git-send-email-luis.henriques@canonical.com> <562EDD15.8030205@daenzer.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <562EDD15.8030205@daenzer.net> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Oct 27, 2015 at 11:10:29AM +0900, Michel Dänzer wrote: > On 26.10.2015 22:42, Luis Henriques wrote: > > 3.16.7-ckt19 -stable review patch. If anyone has any objections, please let me know. > > > > ------------------ > > > > From: =TF-8?q?Michel Dänzer?= > > > > commit 4281f46ef839050d2ef60348f661eb463c21cc2e upstream. > > > > Instead of only enabling the backlight (which seems to set it to max > > brightness), just re-set the current backlight level, which also takes > > care of enabling the backlight if necessary. > > > > Only the radeon_atom_encoder_dpms_dig part tested on a Kaveri laptop, > > the radeon_atom_encoder_dpms_avivo part is only compile tested. > > > > Signed-off-by: Michel Dänzer > > Signed-off-by: Alex Deucher > > Signed-off-by: Luis Henriques > > We're currently investigating a regression which was bisected to this > change. Please hold off on backporting this change until we have a > solution for that. Thanks, I'll drop this patch for this 3.16 release, and will wait for a fix to be available. Cheers, -- Luís