All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>, Aaron Lu <aaron.lwe@gmail.com>,
	linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
	Len Brown <lenb@kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [REGRESSION/PATCH] acpi: blacklist win8 OSI for ASUS Zenbok Prime UX31A
Date: Wed, 31 Jul 2013 18:52:32 +0100	[thread overview]
Message-ID: <20130731175232.GA29987@srcf.ucam.org> (raw)
In-Reply-To: <CAMP44s1cLou9TMfLS+FHwPM_b3bG5HN1-hzgvhz0fVRCZ8XqWw@mail.gmail.com>

On Wed, Jul 31, 2013 at 12:46:04PM -0500, Felipe Contreras wrote:

> That doesn't change the fact that you were wrong, and there *is*
> actually a way. The fact that you don't want to go there doesn't mean
> it's not there.

A quirk list will be incomplete, and as such there's no way to guarantee 
whether or not a value of 0 will turn off the backlight. This is why the 
interface doesn't make that guarantee, and why any userspace that 
depends upon that behaviour is behaving incorrectly.

> Here's another: device tree.

There's no functional distinction between device tree and a quirk list 
on x86 - they're both static data sources provided by something other 
than the system firmware. As a result, they will both be incomplete.

> There are ways to provide a consistent backlight interface to user-space.

No, there aren't. What you *can* do is propose to change the ABI 
description for the sysfs backlight interface such that any system where 
0 turns off the backlight is considered buggy, but that won't make those 
systems vanish. A good interface doesn't promise things it can't 
guarantee, so I'd expect that any such proposal would be rejected.

-- 
Matthew Garrett | mjg59@srcf.ucam.org

  reply	other threads:[~2013-07-31 17:52 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-29 19:20 [REGRESSION/PATCH] acpi: blacklist win8 OSI for ASUS Zenbok Prime UX31A Felipe Contreras
2013-07-29 20:17 ` Rafael J. Wysocki
2013-07-29 20:22   ` Felipe Contreras
2013-07-29 20:47     ` Rafael J. Wysocki
2013-07-29 21:04       ` Felipe Contreras
2013-07-30  3:11 ` Aaron Lu
2013-07-30  3:44   ` Felipe Contreras
2013-07-30  5:51     ` Aaron Lu
2013-07-30  5:57       ` Aaron Lu
2013-07-30 13:42         ` Rafael J. Wysocki
2013-07-30 20:59           ` Felipe Contreras
2013-07-30 23:13             ` Rafael J. Wysocki
2013-07-31  0:11               ` Felipe Contreras
2013-07-31  1:36                 ` Aaron Lu
2013-07-31  2:07                   ` Felipe Contreras
2013-07-31  2:22                     ` Aaron Lu
2013-08-01 18:50                       ` Felipe Contreras
2013-07-31  5:14                 ` Matthew Garrett
2013-07-31 11:32                   ` Felipe Contreras
2013-07-31 14:00                     ` Matthew Garrett
2013-07-31 17:46                       ` Felipe Contreras
2013-07-31 17:52                         ` Matthew Garrett [this message]
2013-07-31 18:07                           ` Felipe Contreras
2013-07-31 18:47                             ` Matthew Garrett
2013-08-01 17:37                               ` Felipe Contreras
2013-08-01 17:42                                 ` Matthew Garrett
2013-08-01 17:50                                   ` Felipe Contreras
2013-08-01 18:01                                     ` Matthew Garrett
2013-08-01 18:11                                       ` Felipe Contreras
2013-08-01 23:40                 ` Felipe Contreras
2013-07-31  1:59             ` Aaron Lu
2013-07-31  2:09               ` Felipe Contreras
  -- strict thread matches above, loose matches on Subject: below --
2013-10-20 22:16 Vincent Blut
2013-10-21  1:53 ` Aaron Lu
2013-10-21 21:21   ` Vincent Blut
2013-10-22  2:16     ` Aaron Lu
2013-10-22  2:12 ` Felipe Contreras
2013-10-23 15:31   ` Matthew Garrett
2013-10-23 19:39     ` Felipe Contreras
2013-10-24  0:53       ` Matthew Garrett

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=20130731175232.GA29987@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=aaron.lwe@gmail.com \
    --cc=felipe.contreras@gmail.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=torvalds@linux-foundation.org \
    /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.