From: "Yu, Luming" <luming.yu@intel.com>
To: "Jaya Kumar" <jayakumar.acpi@gmail.com>
Cc: <linux-acpi@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH 2.6.15.3 1/1] ACPI: Atlas ACPI driver
Date: Mon, 13 Mar 2006 21:16:53 +0800 [thread overview]
Message-ID: <3ACA40606221794F80A5670F0AF15F84041AC262@pdsmsx403> (raw)
>On 3/8/06, Yu, Luming <luming.yu@intel.com> wrote:
>> I suggest LCD support in hotkey.c like:
>> http://bugzilla.kernel.org/attachment.cgi?id=6843&action=view
>>
>> Config userspace acpi daemon to respond events by evoking
>> LCD._BCM with command:
>> echo -n xx > /sys/hotkey/brightness.
>>
>
>A quick question here. I took a look at your patch adding hotkeylib. I
>see brightness_show/store callbacks and I think they end up calling
>write_acpi_int to do the actual method eval.
Yes. But there are some restricts with write_acpi_int that only
takes single integer parameter, and write_acpi_int2 that fits aml
method of taking Package as argument.
>
>So I assume my action_method has got to be "_BCM". I don't have a poll
>method but it looks like I'll need to put something in there since you
>check for it. Atlas has a _BCL. I guess I'll just use that.
Yes. poll_method is for query the status/current value.
For example, to query current brightness value.
>
>+ if(!poll_handle || !poll_method || !action_handle ||
>!action_method)
>+ goto do_fail;
>
>From what I can tell, it looks like I have to use ACPILCD00 as my HID
>in this hotkey code. Right? So basically, it'd be something like:
> {
> .ids = "ACPILCD00",
> .name = "brightness",
> .poll_method = "_BCL",
> .action_method = "_BCM",
> .min = 1,
> .max = 31,
> .id = 10001,
> },
I think this is ok.
>
>So if I get that working, is that what you are saying is the right way
>to do brightness support for limited devices like Atlas? I guess it
>feels kind of odd to me because it's an LCD device rather than a
>hotkey device. But afaict it looks like doing that will work fine and
>have the added benefit of not creating any new /proc entries. So let
>me know if I understood you correctly.
Yes. You are right.
>
>By the way, I just applied your sequence of patches from
>http://bugzilla.kernel.org/show_bug.cgi?id=5749 to my tree. You know,
>if it's okay with you, I'll post the full diff from below to your bug
>report so that the next person doesn't have to cherrypick.
Thanks for doing that.
>
>wget "http://bugzilla.kernel.org/attachment.cgi?id=6839&action=view"
>wget "http://bugzilla.kernel.org/attachment.cgi?id=6840&action=view"
>wget "http://bugzilla.kernel.org/attachment.cgi?id=6841&action=view"
>wget "http://bugzilla.kernel.org/attachment.cgi?id=6842&action=view"
>wget "http://bugzilla.kernel.org/attachment.cgi?id=6843&action=view"
>wget "http://bugzilla.kernel.org/attachment.cgi?id=7061&action=view"
>wget "http://bugzilla.kernel.org/attachment.cgi?id=7060&action=view"
>
>Thanks,
>jayakumar
next reply other threads:[~2006-03-13 13:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-13 13:16 Yu, Luming [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-08 7:44 Yu, Luming
2006-03-08 8:53 ` Jaya Kumar
2006-03-13 6:38 ` Jaya Kumar
2006-03-08 6:17 Yu, Luming
2006-03-08 7:11 ` Jaya Kumar
2006-03-07 8:52 Yu, Luming
2006-03-07 16:09 ` Jaya Kumar
2006-03-06 13:50 Yu, Luming
2006-03-07 1:50 ` Jaya Kumar
[not found] <AcY1+QTZumb9d6e3RHms9ocp4LswwgAtmORQ>
2006-02-21 6:34 ` Yu, Luming
2006-03-03 8:16 ` Jaya Kumar
2006-02-20 8:26 Yu, Luming
2006-02-20 8:37 ` Jaya Kumar
2006-02-20 2:13 jayakumar.acpi
2006-02-20 10:26 ` Matthew Garrett
2006-02-20 10:49 ` Jaya Kumar
2006-02-20 11:01 ` Matthew Garrett
2006-02-20 11:25 ` Jaya Kumar
2006-02-20 11:28 ` 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=3ACA40606221794F80A5670F0AF15F84041AC262@pdsmsx403 \
--to=luming.yu@intel.com \
--cc=jayakumar.acpi@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®