Return-path: Received: from out1.smtp.messagingengine.com ([66.111.4.25]:51861 "EHLO out1.smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755946AbYF1N5a (ORCPT ); Sat, 28 Jun 2008 09:57:30 -0400 Date: Sat, 28 Jun 2008 10:57:25 -0300 From: Henrique de Moraes Holschuh To: drago01 Cc: Linux Wireless , "Zhu, Yi" , Dan Williams , Tomas Winkler , Ivo van Doorn , "John W. Linville" Subject: Re: [PATCHv2] iwlwifi: add support for RFKILL_STATE_HARD_BLOCKED Message-ID: <20080628135725.GC871@khazad-dum.debian.net> (sfid-20080628_155820_391165_53662CFB) References: <20080628131439.GA871@khazad-dum.debian.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: Sender: linux-wireless-owner@vger.kernel.org List-ID: On Sat, 28 Jun 2008, drago01 wrote: > On Sat, Jun 28, 2008 at 3:14 PM, Henrique de Moraes Holschuh > wrote: > > On Sat, 28 Jun 2008, drago01 wrote: > >> This patch fixes the rfkill states to set RFKILL_STATE_HARD_BLOCKED when the > >> radio is disabled by a hardware killswitch. > >> It does not allow setting the sw state while the device is blocked by > >> a hardware rfkill switch. > > > > It should. In fact, you should do it in a way that it is possible to > > double-block the radio (i.e. in SW while it is blocked in HW), so that if > > the HW block goes away, the radio remains blocked. > > > > Read the docs and examples again, please. There even is special code in the > > rfkill_toggle_radio private function to allow for it, we want drivers to be > > able to double-block. > > OK, v2 attached it allows double-block. Looks good at first glance (I just looked over the patch, I have never looked at the iwlwifi code, though. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh