From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dmitry Torokhov Subject: Re: [RFC] rfkill - Add support for input key to control wireless radio Date: Tue, 12 Dec 2006 00:12:25 -0500 Message-ID: <200612120012.28911.dtor@insightbb.com> References: <200612031936.34343.IvDoorn@gmail.com> <200612072253.14492.IvDoorn@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org, John Linville , Jiri Benc , Lennart Poettering , Johannes Berg , Larry Finger Return-path: Received: from gateway.insightbb.com ([74.128.0.19]:45257 "EHLO asav00.insightbb.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751158AbWLLFMd convert rfc822-to-8bit (ORCPT ); Tue, 12 Dec 2006 00:12:33 -0500 To: Ivo van Doorn In-Reply-To: <200612072253.14492.IvDoorn@gmail.com> Content-Disposition: inline Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org Hi Ivo, On Thursday 07 December 2006 16:53, Ivo van Doorn wrote: > Hi, >=20 > > > > > =A02 - 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 bu= tton that don't send anything to > > > userspace (unless the ACPI event is read) and does not directly c= ontrol the radio itself. > > > > >=20 > > So what does such a button do? I am confused here... >=20 > 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 sta= te 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 eve= nt. In this case the driver can make the button state available to userspac= e so thsi is really type 2) driver as far as I can see. The fact that the bu= tton is not reported to userspace yet should not get into our way of classif= ying it. --=20 Dmitry