Linux bluetooth development
 help / color / mirror / Atom feed
From: "Àlex Fiestas" <afiestas@kde.org>
To: BlueZ <linux-bluetooth@vger.kernel.org>
Subject: Adapters power management
Date: Sun, 23 Mar 2014 01:42:49 +0100	[thread overview]
Message-ID: <2963801.adpd6n3SPJ@minibad> (raw)

I'm finishing the port of KDE's bluez interface to BlueZ5 and I am wondering a 
few things about power management.

First thing is, why is Adapter::powered not hook into rfkill? Is there any 
difference power consumption-wise whether the power state is true or false?
I look  into the source code and only saw code to monitor the rfkill state but 
not for modifying it.

In the case that Adapter::powered has an impact on power consumption, then the 
ideal state is to have it to false as much as possible. Are there any plans to 
make that easy for frontend developers? In a sense this is very similar to 
Inhibitions in systemd[1] so I was thinking 

             reply	other threads:[~2014-03-23  0:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-23  0:42 Àlex Fiestas [this message]
2014-03-23  0:45 ` Adapters power management Àlex Fiestas
2014-03-23 15:08   ` Johan Hedberg
2014-03-24 13:46     ` Àlex Fiestas

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=2963801.adpd6n3SPJ@minibad \
    --to=afiestas@kde.org \
    --cc=linux-bluetooth@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