From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Garrett Date: Wed, 01 Jul 2009 22:16:55 +0000 Subject: Re: [PATCH] Explicitly disable BT radio using rfkill interface on Message-Id: <20090701221655.GA26629@srcf.ucam.org> List-Id: References: <4A4A8B6D.3060509@dell.com> In-Reply-To: <4A4A8B6D.3060509@dell.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Wed, Jul 01, 2009 at 03:13:33PM -0700, Marcel Holtmann wrote: > Hi Matthew, > > I disliked this for a couple of reasons. The first is that it forces an > > rfkill even on hardware that doens't have this behaviour. The second is > > that it's working around a quirk on hardware that this driver really > > isn't reponsible for. > > I don't agree with how the patch is done, but in theory it is what > RFKILL is all about (after the re-write). However it has to be hardkill > and not a softkill. The softkill is a userspace decision while the > hardkill comes from actually hardware or firmware in this case. > > Seems the Dell hardware/firmware is kinda stupid and inconsistent here > and I have no problem solution. However adding a special HID driver with > this quirk might be better anyway. I'm really still not quite clear on what the issue here is. At boot, there are hid devices that need to be quirked into hci mode. Over suspend these devices return to their original state. So something needs to be done to quirk them back on resume. Why is this a kernel issue at all? -- Matthew Garrett | mjg59@srcf.ucam.org