All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aaron Lu <aaron.lu@intel.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Ben Skeggs <bskeggs@redhat.com>,
	platform-driver-x86@vger.kernel.org,
	dri-devel@lists.freedesktop.org,
	Sylvain Pasche <sylvain.pasche@gmail.com>,
	linux-acpi@vger.kernel.org
Subject: Re: [PATCH v2] acpi-video: Add a parameter to not register the backlight sysfs interface
Date: Thu, 11 Jun 2015 09:43:15 +0800	[thread overview]
Message-ID: <20150611014315.GA26277@aaronlu.sh.intel.com> (raw)
In-Reply-To: <557760A5.9000404@redhat.com>

On Tue, Jun 09, 2015 at 11:54:45PM +0200, Hans de Goede wrote:
> Hi,
> 
> On 06/09/2015 11:10 AM, Aaron Lu wrote:
> >On Tue, Jun 09, 2015 at 10:32:25AM +0200, Hans de Goede wrote:
> >>On some systems acpi-video backlight is broken in the sense that it cannot
> >>control the brightness of the backlight, but it must still be called on
> >>resume to power-up the backlight after resume.
> >
> >All the video module does on resume is a backlight set operation, it
> >can't control backlight but can turn on the screen on resume? Hmm...
> >
> >I'll ask Sylvain to attach acpidump, let's see if there is anything
> >special there.
> 
> Ok, lets see what comes out of that. Note in the mean time Sylvain has
> attached his acpidump.

Thanks.
According to the discussion in the bugzilla place, it doesn't seem we
have any other way to handle this at the moment.

Acked-by: Aaron Lu <aaron.lu@intel.com>

Best wishes,
Aaron

  reply	other threads:[~2015-06-11  1:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-09  8:32 [PATCH v2] acpi-video: Add a parameter to not register the backlight sysfs interface Hans de Goede
2015-06-09  9:10 ` Aaron Lu
2015-06-09 21:54   ` Hans de Goede
2015-06-11  1:43     ` Aaron Lu [this message]
2015-06-11 10:13       ` Hans de Goede
2015-06-11 11:10         ` Jani Nikula
2015-06-11 12:13           ` Hans de Goede
2015-06-15 23:18             ` Rafael J. Wysocki
2015-06-09 14:03 ` Jani Nikula

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=20150611014315.GA26277@aaronlu.sh.intel.com \
    --to=aaron.lu@intel.com \
    --cc=bskeggs@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hdegoede@redhat.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=sylvain.pasche@gmail.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.