linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] Explicitly disable BT radio using rfkill interface on
Date: Wed, 01 Jul 2009 22:16:55 +0000	[thread overview]
Message-ID: <20090701221655.GA26629@srcf.ucam.org> (raw)
In-Reply-To: <4A4A8B6D.3060509@dell.com>

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

  parent reply	other threads:[~2009-07-01 22:16 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-30 22:02 [PATCH] Explicitly disable BT radio using rfkill interface on Mario Limonciello
2009-06-30 22:26 ` Kay Sievers
2009-07-01  3:53 ` [PATCH] Explicitly disable BT radio using rfkill interface on suspend Mario_Limonciello
2009-07-01 12:06 ` [PATCH] Explicitly disable BT radio using rfkill interface on Marcel Holtmann
2009-07-01 13:13 ` [PATCH] Explicitly disable BT radio using rfkill interface on suspend Mario_Limonciello
2009-07-01 15:03 ` [PATCH] Explicitly disable BT radio using rfkill interface on Marcel Holtmann
2009-07-01 17:12 ` Mario Limonciello
2009-07-01 17:18 ` Matthew Garrett
2009-07-01 22:13 ` Marcel Holtmann
2009-07-01 22:16 ` Matthew Garrett [this message]
2009-07-01 22:23 ` Mario Limonciello
2009-07-01 22:49 ` Marcel Holtmann
2009-07-01 22:52 ` Matthew Garrett
2009-07-02 14:02 ` Alan Stern
2009-07-10 14:46 ` Alan Stern
2009-07-14 16:40 ` Mario Limonciello
2009-07-14 16:51 ` Alan Stern
2009-07-14 16:52 ` Kay Sievers
2009-07-14 17:32 ` Mario Limonciello
2009-07-14 18:46 ` Marcel Holtmann
2009-07-14 19:12 ` Kay Sievers
2009-07-14 21:00 ` Mario Limonciello
2009-07-14 21:20 ` Marcel Holtmann
2009-07-14 21:24 ` Kay Sievers
2009-07-14 22:45 ` Kay Sievers
2009-07-15  2:07 ` Alan Stern
2009-07-15  2:26 ` Kay Sievers
2009-07-15 22:15 ` Mario Limonciello
2009-07-15 22:24 ` Mario Limonciello
2009-07-15 23:27 ` Kay Sievers

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=20090701221655.GA26629@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=linux-hotplug@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).