From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Zhang Rui <rui.zhang@intel.com>
Cc: Len Brown <lenb@kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH] ACPI video: Be more liberal in validating _BQC behaviour
Date: Mon, 22 Feb 2010 02:06:47 +0000 [thread overview]
Message-ID: <20100222020647.GA30278@srcf.ucam.org> (raw)
In-Reply-To: <1266803479.2608.1484.camel@rzhang1-desktop>
On Mon, Feb 22, 2010 at 09:51:19AM +0800, Zhang Rui wrote:
> On Fri, 2010-02-19 at 21:54 +0800, Matthew Garrett wrote:
> > My system statically initialises the variable containing the current
> > brightness to 100, but doesn't include 100 in the list of valid
> > brightnesses.
>
> sorry, I don't understand.
> does the video driver set the backlight to 100, which is not a valid
> value in the _BCL package?
No, the firmware does.
> > Right now this causes us to stop believing _BQC. However,
> > the enxt thing we do is set the brightness to maximum anyway - at this
> > point _BQC will now return a correct value.
>
> hmmm, could you attach the acpidump please?
The relevant bits are:
Name (BRIG, 0x64)
Method (_BQC, 0, Serialized)
{
Store (BRIG, Local0)
Return (Local0)
}
Method (_BCM, 1, Serialized)
{
...
Store (Arg0, BRIG)
0x64 is an invalid value as far as _BCL goes. So, _BQC will give an
invalid response until we set a value - after that, it'll be correct.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2010-02-22 2:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-16 21:53 [PATCH] ACPI video: Be more liberal in validating _BQC behaviour Matthew Garrett
2010-02-19 6:40 ` Len Brown
2010-02-19 13:54 ` Matthew Garrett
2010-02-22 1:51 ` Zhang Rui
2010-02-22 2:06 ` Matthew Garrett [this message]
2010-02-23 6:29 ` Zhang Rui
2010-02-22 17:24 ` Thomas Renninger
2010-02-22 17:38 ` 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=20100222020647.GA30278@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox