All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felipe Contreras <felipe.contreras@gmail.com>
To: Aaron Lu <aaron.lwe@gmail.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	Kernel development list <linux-kernel@vger.kernel.org>,
	linux-acpi@vger.kernel.org, Len Brown <lenb@kernel.org>,
	Zhang Rui <rui.zhang@intel.com>
Subject: Re: [PATCH] acpi: video: improve quirk check
Date: Sun, 4 Aug 2013 01:54:21 -0500	[thread overview]
Message-ID: <CAMP44s2CnJ5O5wspeG3-hYOTKwBLHbaZ1AbfHQ=rYEQRpeJW2g@mail.gmail.com> (raw)
In-Reply-To: <CAOzJMDQwte=7VtfQzW9DyQpt+pbe48STDEGhLis62Y0tG78G1w@mail.gmail.com>

On Sat, Aug 3, 2013 at 8:47 PM, Aaron Lu <aaron.lwe@gmail.com> wrote:
> On Sun, Aug 4, 2013 at 6:20 AM, Felipe Contreras
> <felipe.contreras@gmail.com> wrote:
>> On Sat, Aug 3, 2013 at 4:40 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:

>>> Do we still need to revert commit efaa14c if this patch is applied?
>>
>> I guess not. At least in this machine changing the backlight works
>> correctly, whereas in v3.11-rc3 it was all weird, and v3.7-v3.10
>> didn't work at all. I cannot see how it would affect negatively other
>> machines.
>
> That commit makes hotkey emit notifications, and it's not the
> problem of "booting into a black screen", that problem is due to
> broken _BQC.

The broken _BQC has been there for quite some time, hasn't it?

Either way, without efaa14c, changing the backlight doesn't work at
all either way, so there's no black screen, because there cannot be.

> BTW, the efaa14c will also make screen off at level 0 according
> to Felipe, who consider this is a bug. But since it is required to
> let firmware emit notifications on hotkey press, I think user will
> want it.

With or without efaa14c, level 0 makes the screen off, or at least it
would, if the control worked at all. So efaa14c is one step forward,
but two back, my patch removes the two steps back, but we are still
not at the level of what my blacklisting patch does, for that we would
need to fix two issues:

1. Fix the retrieval of the last level at boot
2. Fix level 0 (yes, I consider that a regression)

But we cannot achieve either of those for v3.11, the only
possibilities seem to be either a) revert efaa14c, or b) keep it and
apply my patch. Anything else doesn't seem to be a possible or
sensible option, and I vote for b).

-- 
Felipe Contreras

  reply	other threads:[~2013-08-04  6:54 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-02 19:37 [PATCH] acpi: video: improve quirk check Felipe Contreras
2013-08-02 23:47 ` Rafael J. Wysocki
2013-08-03  1:04   ` Felipe Contreras
2013-08-03  1:16     ` Rafael J. Wysocki
2013-08-03  1:07       ` Felipe Contreras
2013-08-03  1:19         ` Rafael J. Wysocki
2013-08-03  1:30           ` Felipe Contreras
2013-08-03  8:14   ` Aaron Lu
2013-08-03 11:34     ` Rafael J. Wysocki
2013-08-03 20:24       ` Felipe Contreras
2013-08-03 21:40         ` Rafael J. Wysocki
2013-08-03 22:20           ` Felipe Contreras
2013-08-03 22:38             ` Rafael J. Wysocki
2013-08-03 22:37               ` Felipe Contreras
2013-08-04  1:47             ` Aaron Lu
2013-08-04  6:54               ` Felipe Contreras [this message]
2013-08-04 14:14                 ` Rafael J. Wysocki
2013-08-04 14:08                   ` Felipe Contreras
2013-08-04  1:18       ` Aaron Lu
2013-08-04  6:42         ` Felipe Contreras
2013-08-04 14:19           ` Rafael J. Wysocki
2013-08-04 14:19             ` Felipe Contreras
2013-08-05 14:04               ` Rafael J. Wysocki
2013-08-05 14:41                 ` Felipe Contreras
2013-08-07  4:35               ` Aaron Lu

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='CAMP44s2CnJ5O5wspeG3-hYOTKwBLHbaZ1AbfHQ=rYEQRpeJW2g@mail.gmail.com' \
    --to=felipe.contreras@gmail.com \
    --cc=aaron.lwe@gmail.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=rui.zhang@intel.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.