From: Johan Hedberg <johan.hedberg@gmail.com>
To: Hieu Le <hieu.le@veriksystems.com>
Cc: Steve Gladden <steve@michiganbroadband.com>,
Barry Byford <31baz66@gmail.com>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>
Subject: Re: How can you set Transmit power level in Bluetooth LE mode for an LE beacon?
Date: Wed, 12 Oct 2016 09:22:44 +0200 [thread overview]
Message-ID: <20161012072244.GA29209@x1c> (raw)
In-Reply-To: <CADEmUHMF3gRai_kUHcKwA5RMi3WevMsE00NL2_NqWZWgu27OuA@mail.gmail.com>
Hi,
On Wed, Oct 12, 2016, Hieu Le wrote:
> In my opinion, the only way I can find to increase the tx_power is to
> recompile the linux kernel. There may be a better way
>
> It seems that bluetooth stack within kernel separated into two classes:
> 1. Inquiry Tx_power.
> 2. Advertise Tx_power.
>
> And the default value is 0.
>
> You can take a look at:
> *hci_alloc_dev(void) function within net/bluetooth/hci_core.c file
> hdev->inq_tx_power = HCI_TX_POWER_INVALID;
> hdev->adv_tx_power = HCI_TX_POWER_INVALID;
The adv_tx_power is not used for changing the controller advertising TX
power. It's only used for reading the current controller setting and
storing it in this variable. The reason for all this is that currently
(as of Bluetooth 4.2) there is no standard HCI command for changing the
advertising TX power.
Johan
next prev parent reply other threads:[~2016-10-12 7:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-09 16:11 How can you set Transmit power level in Bluetooth LE mode for an LE beacon? Steve Gladden
2016-10-11 16:50 ` Steve Gladden
2016-10-11 17:38 ` Barry Byford
2016-10-11 17:52 ` Steve Gladden
2016-10-12 5:00 ` Hieu Le
2016-10-12 7:22 ` Johan Hedberg [this message]
2016-10-12 15:33 ` Steve Gladden
[not found] ` <CAHFy41_8FzDF-jATapn20Km8vbX6nt44DN9uPnazDMOJ_yD=Kw@mail.gmail.com>
2016-10-13 13:54 ` Steve Gladden
2016-10-16 21:56 ` Steve Gladden
2016-10-16 22:48 ` Jason Anderssen
2016-10-17 4:15 ` Steve Gladden
2016-10-19 7:22 ` Andrei Emeltchenko
[not found] ` <E870213FE4F9C248AE722569E8374C6A386A32B414@X2.michiganbb.local>
2016-10-24 21:24 ` Steve Gladden
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=20161012072244.GA29209@x1c \
--to=johan.hedberg@gmail.com \
--cc=31baz66@gmail.com \
--cc=hieu.le@veriksystems.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=steve@michiganbroadband.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 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).