All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Ross Burton <ross@linux.intel.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Persisting power state when set via rfkill directly
Date: Wed, 04 Nov 2009 01:52:18 +0900	[thread overview]
Message-ID: <1257267138.3420.114.camel@localhost.localdomain> (raw)
In-Reply-To: <1257263702.8893.101.camel@flashheart.burtonini.com>

Hi Ross,

> I see that bluez has support for saving the current power state to disk
> (in /var/lib/bluetooth/[id]/config) when the Powered adaptor property is
> toggled, so that the same state can be restored when restarted.
> However, this only works if the powered state is toggled via the Bluez
> DBus API, applications which directly touch rfkill (such as
> gnome-bluetooth) don't cause the current mode to be persisted.
> 
> From a quick look at the code I'd say that rfkill_event() shouldn't
> return early if the adaptor was powered down and instead get the adaptor
> pointer and write the new mode state.  Does this sound reasonable?

I explained a couple of times that gnome-bluetooth should not use RFKILL
as a way to toggle Powered state. Use the D-Bus interface to do so and
not go behind its back. RFKILL states are not persistent and we will not
take RFKILL as an input for this.

Regards

Marcel



  reply	other threads:[~2009-11-03 16:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-03 15:55 Persisting power state when set via rfkill directly Ross Burton
2009-11-03 16:52 ` Marcel Holtmann [this message]
2009-11-03 17:04   ` Bastien Nocera
2009-11-03 17:16     ` Marcel Holtmann
2009-11-05 12:37       ` Bastien Nocera
2009-11-05 16:54         ` Marcel Holtmann

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=1257267138.3420.114.camel@localhost.localdomain \
    --to=marcel@holtmann.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=ross@linux.intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.