From: Hiroshi Miura <miura-yiisDzvROlQdnm+yROfE0A@public.gmane.org>
To: "Yu, Luming" <luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
"Brown, Len" <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: generic hotkey driver
Date: Fri, 03 Sep 2004 20:16:55 +0900 [thread overview]
Message-ID: <87fz5zppp4.wl%miura@da-cha.org> (raw)
In-Reply-To: <3ACA40606221794F80A5670F0AF15F84055D6C10@pdsmsx403>
Hi,
I think hotkey drivers are so differ that it is enough to decide
event format. ie) 'ibm KEY 00001 00001' or 'hotkey/pcc HKEY 000003 000001'
Lcd brightness control is defined in ACPI spec apendix.
I'm starting implement that.
I want to make generic lcd driver that is configurable for each extra drivers.
Bluetooth, dock, and other device settings are not common.
So these may be implement in each extra drivers. eg) ibm_acpi.c has these functions.
At Wed, 1 Sep 2004 18:32:53 +0800,
Yu, Luming wrote:
>
> I'm thinking if we need a generic hotkey driver that is configurable
> to any specific machine.
> There already have two specific hotkey driver: asus_acpi.c and
> toshiba_acpi.c. And there
> are two upcoming driver : ibm_acpi.c and panasonic_acpi.c. I don't know
> how many
> hotkey driver will be invented in the future. But I know it will mess up
> the code structure.
> So, I'm considering a generic hotkey driver that will export
> configurable interface to
> accommodate the difference.
>
> a. Configure interface:
> 1. register mapping of event number to internal hotkey number.
> 2. register expected acpi_handle which is needed to install
> notify handler, which will generate event for acpid.
> 3. register the AML methods that should be executed , with
> respect to the hotkey get pressed.
> b. Expose interface:
> 1. Expose the event action interface through /proc/acpi/action,
> the interface will receive argument which
> will be passed into AML method, as well as AML method
> should be executed.
> c. Use interface:
> 1. When user space acpid get a event, it can call related AML
> methods related to this hotkey.
--
Hiroshi Miura --- http://www.da-cha.org/ --- miura-yiisDzvROlQdnm+yROfE0A@public.gmane.org
NTTDATA Corp. OpenSource Software Center. --- miurahr-3MafRgGXt7BL9jVzuh4AOg@public.gmane.org
NTTDATA Intellilink Corp. OpenSource Engineering Dev. -- miurahr-w0OK63jvRlAuJ+9fw/WgBHgSJqDPrsil@public.gmane.org
Key fingerprint = 9117 9407 5684 FBF1 4063 15B4 401D D077 04AB 8617
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
next prev parent reply other threads:[~2004-09-03 11:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-01 10:32 generic hotkey driver Yu, Luming
2004-09-03 11:16 ` Hiroshi Miura [this message]
2004-09-04 8:45 ` John Belmonte
-- strict thread matches above, loose matches on Subject: below --
2004-09-07 7:54 Yu, Luming
2004-09-07 13:13 ` John Belmonte
2004-09-07 8:14 Yu, Luming
2004-09-07 8:49 ` Karol Kozimor
2004-09-14 20:42 ` Pavel Machek
2004-09-08 15:42 Yu, Luming
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=87fz5zppp4.wl%miura@da-cha.org \
--to=miura-yiisdzvrolqdnm+yrofe0a@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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