linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bastien Nocera <hadess@hadess.net>
To: "Zheng, Lv" <lv.zheng@intel.com>,
	"Chen, Yu C" <yu.c.chen@intel.com>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"rjw@rjwysocki.net" <rjw@rjwysocki.net>,
	"lenb@kernel.org" <lenb@kernel.org>,
	"Zhang, Rui" <rui.zhang@intel.com>,
	"cwhuang@android-x86.org" <cwhuang@android-x86.org>
Subject: Re: [PATCH] ACPI / button: Avoid using broken _LID on Surface tablet
Date: Mon, 07 Mar 2016 17:19:28 +0100	[thread overview]
Message-ID: <1457367568.2648.72.camel@hadess.net> (raw)
In-Reply-To: <1AE640813FDE7649BE1B193DEA596E883BB60425@SHSMSX101.ccr.corp.intel.com>

On Fri, 2016-03-04 at 03:37 +0000, Zheng, Lv wrote:
<snip>
> 
> > I'm not happy about the "fix" for this problem either, but blaming
> > user-space for this is harsh, given the API exported by the kernel
> > and
> > how pretty much every laptop worked.
> > 
> [Lv Zheng] 
> It worked for so many years on top of traditional x86 laptops where
> the LID open event is handled by the BIOS to trigger a wake GPE.
> Now we are talking about runtime idle systems where resuming from the
> s2idle invokes no BIOS code.
> The new case is still working on Windows.
> Which forces us to re-consider the kernel API of the ACPI LID.

The current kernel API works on 99% of machines up until now, user-
space could not have been expected to know that the Lid status might be
incorrect on some machines, it had no way to know that, there was no
documentation saying "don't use the Lid status outside of Lid status
change events".

We either need to extend the current API to export the fact that we
should ignore the LID status outside of events, or we need a new API.

(We could fix this without any kernel changes, but we really need the
kernel to document that fact, and export it to user-space)

This is something you should have said at the start of the mail,
instead of repeatedly saying that user-space was broken. User-space
behaviour hasn't changed there for more than 10 years, and I'm fairly
certain it's worked the same way as APM (on x86) and PMU (on Mac PPC
machines) did.

Cheers
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2016-03-07 16:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-03 11:04 [PATCH] ACPI / button: Avoid using broken _LID on Surface tablet Chen Yu
2016-02-15  3:34 ` Zheng, Lv
2016-02-15  5:39   ` Chen, Yu C
2016-02-22  7:24     ` Zheng, Lv
2016-02-22 14:14       ` Bastien Nocera
2016-03-04  3:37         ` Zheng, Lv
2016-03-07 16:19           ` Bastien Nocera [this message]
2016-03-22  7:04             ` Zheng, Lv

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=1457367568.2648.72.camel@hadess.net \
    --to=hadess@hadess.net \
    --cc=cwhuang@android-x86.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lv.zheng@intel.com \
    --cc=rjw@rjwysocki.net \
    --cc=rui.zhang@intel.com \
    --cc=yu.c.chen@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).