public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson-VXdhtT5mjnY@public.gmane.org>
To: "Yu, Luming" <luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Borislav Deianov
	<borislav-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
	Karol Kozimor <sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>,
	Hiroshi Miura <miura-yiisDzvROlQdnm+yROfE0A@public.gmane.org>,
	Julien Lerouge <julien.lerouge-GANU6spQydw@public.gmane.org>,
	"Brown, Len" <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	acpi-devel
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [RFC][PATCH] Generic Hotkey driver interface
Date: Tue, 09 Nov 2004 09:13:04 -0700	[thread overview]
Message-ID: <1100016784.12984.7.camel@tdi> (raw)
In-Reply-To: <3ACA40606221794F80A5670F0AF15F84041AC040@pdsmsx403>

Luming,

   Have you considered trying to implement this as a userspace daemon on
top of dev_acpi?  I believe I'm exporting all the of the ACPI interfaces
you'd need to do this.  The acpivideo tool (available along w/ the
latest dev_acpi) does something similar in setting up a notify handler
on the graphics device, and receiving hotkey events.  The hooks are
already there to allow userspace to generate an ACPI event as well.  I'd
be interested in any feedback you have on dev_acpi should you
investigate this approach.  Thanks,

	Alex

On Tue, 2004-11-09 at 23:25 +0800, Yu, Luming wrote:
>   To consolidate the hotkey implementation in ACPI subsystem, 
> I tried to implement a generic hotkey driver under ACPI.
> I hope you can give it a review. Thanks in advances for any
> comments.
> 
>   The basic idea is to supply configurable interface
> to userspace, thus user can configure the generic
> hotkey driver to work for their specific laptop model.
> 
>   Please note, the code is trying to prove the concept
> is feasible. So there are large room to improve, including
> bugs need to be fixed, redundant code need to be clean up,
> critical section need to be protected by lock or semaphore,
> memory leak need to be fix up, interfaces need to be revised.
> 
>   The code is inspired by Karol Kozimor, Borislav Deianov,
> Hiroshi Miura, Julien Lerouge, Alex Williamson,  and Len.
> 
> Thanks,
> Luming

-- 
Alex Williamson                             HP Linux & Open Source Lab



-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click

  reply	other threads:[~2004-11-09 16:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-09 15:25 [RFC][PATCH] Generic Hotkey driver interface Yu, Luming
2004-11-09 16:13 ` Alex Williamson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-11-10  9:18 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=1100016784.12984.7.camel@tdi \
    --to=alex.williamson-vxdhtt5mjny@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=borislav-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=julien.lerouge-GANU6spQydw@public.gmane.org \
    --cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=miura-yiisDzvROlQdnm+yROfE0A@public.gmane.org \
    --cc=sziwan-DETuoxkZsSqrDJvtcaxF/A@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