linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: linux-hotplug@vger.kernel.org
Subject: RE: [PATCH] Explicitly disable BT radio using rfkill interface on
Date: Wed, 01 Jul 2009 15:03:36 +0000	[thread overview]
Message-ID: <1246460616.12994.151.camel@localhost.localdomain> (raw)
In-Reply-To: <4A4A8B6D.3060509@dell.com>

Hi Mario,

> > what are you trying to solve here. And why do you need to disable a
> > Bluetooth radio on suspend? Are you trying to hack around a bug?
> 
> The problem is that a reset-resume is being ran on the BT radio device
> as well as the two virtual HID devices.  So the OS thinks that the BT
> radio device is still there after resuming from S3, but it isn't as the
> hardware is then in a different state after S3.
> 
> The initial solution I proposed was in the dell_laptop kernel module to
> run turn off/on explicitly using the rfkill interface that dell_laptop
> creates, but that not a good solution so Alan proposed adding something
> to userspace to run when the BT radio disappears but that the rest of
> the virtual HID devices are still there.

you know that we re-wrote RFKILL completely. You can kill a Bluetooth
device from within the kernel. And this looks like a hardkill of the
Bluetooth interface.

The only think that you can't do is send input events around to trigger
RFKILL. That is broken and will be removed.

Regards

Marcel



  parent reply	other threads:[~2009-07-01 15:03 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 ` Marcel Holtmann [this message]
2009-07-01 17:12 ` [PATCH] Explicitly disable BT radio using rfkill interface on Mario Limonciello
2009-07-01 17:18 ` Matthew Garrett
2009-07-01 22:13 ` Marcel Holtmann
2009-07-01 22:16 ` Matthew Garrett
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=1246460616.12994.151.camel@localhost.localdomain \
    --to=marcel@holtmann.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).