public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Zhang Rui <rui.zhang@intel.com>
Cc: linux-acpi <linux-acpi@vger.kernel.org>,
	Len Brown <lenb@kernel.org>, Thomas Renninger <trenn@suse.de>
Subject: Re: [RFC PATCH 4/5] ACPI video: support reversed _BCL method
Date: Wed, 11 Mar 2009 01:45:10 +0000	[thread overview]
Message-ID: <20090311014510.GA13760@srcf.ucam.org> (raw)
In-Reply-To: <1236735775.2820.160.camel@rzhang-dt>

On Wed, Mar 11, 2009 at 09:42:55AM +0800, Zhang Rui wrote:

> The index value returned by _BQC is the index in the PCTG package.
> if the _BCL package is in a reversed order, we can not use this index to
> get the value in device->brightness->levels[].
> For example, if the current brightness is 0x64, _BQC returns 0 in this
> case, but we can not translate this to value 0x14, we need a flag to
> tell us that _BCL is reversed.
> 
> But in the non-indexed case, _BQC always returns a percentage that can
> be used directly by ACPI video driver, i.e. we don't need to parse
> device->brightness->levels to get the real value. so we don't need to
> check the device->brightness->flags._BCL_reversed bit.

Ah, of course. Sorry, I should have got that. Thanks for the 
explanation!

Acked-by: Matthew Garrett <mjg@redhat.com>

-- 
Matthew Garrett | mjg59@srcf.ucam.org
--
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:[~2009-03-11  1:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-10  8:03 [RFC PATCH 4/5] ACPI video: support reversed _BCL method Zhang Rui
2009-03-10 17:08 ` Matthew Garrett
2009-03-10 17:11 ` Matthew Garrett
2009-03-11  1:42   ` Zhang Rui
2009-03-11  1:45     ` Matthew Garrett [this message]

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=20090311014510.GA13760@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=rui.zhang@intel.com \
    --cc=trenn@suse.de \
    /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