Messages in this thread | | | Date | Tue, 12 Dec 2006 08:47:07 +0100 | From | "Ivo Van Doorn" <> | Subject | Re: [RFC] rfkill - Add support for input key to control wireless radio |
| |
Hi,
> > > > > > 2 - Hardware key that does not control the hardware radio and does not report anything to userspace > > > > > > > > > > Kind of uninteresting button ;) > > > > > > > > And this is the button that rfkill was originally designed for. > > > > Laptops with integrated WiFi cards from Ralink have a hardware button that don't send anything to > > > > userspace (unless the ACPI event is read) and does not directly control the radio itself. > > > > > > > > > > So what does such a button do? I am confused here... > > > > Without a handler like rfkill, it does nothing besides toggling a bit in a register. > > The Ralink chipsets have a couple of registers that represent the state of that key. > > Besides that, there are no notifications to the userspace nor does it directly control the > > radio. > > That is where rfkill came in with the toggle handler that will listen to the register > > to check if the key has been pressed and properly process the key event. > > In this case the driver can make the button state available to userspace so > thsi is really type 2) driver as far as I can see. The fact that the button > is not reported to userspace yet should not get into our way of classifying > it.
I was indeed considering it as a type 2) device. I am currently working on revising the rfkill driver to work as you suggested, so I hope to have a new patch ready for you soon.
Ivo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |