diff options
| author | Johan Hedberg <johan.hedberg@intel.com> | 2012-11-08 04:22:59 +0400 |
|---|---|---|
| committer | Gustavo Padovan <gustavo.padovan@collabora.co.uk> | 2012-11-19 05:03:00 +0400 |
| commit | bbaf444a89dd7dd7effd8ed2f4e4ec64da3cc1da (patch) | |
| tree | cc265122c83264b509353adad12d6dfe917f27c5 /firmware/bnx2x | |
| parent | 57527f8d4d71b5167a02fb6713857f55d3974748 (diff) | |
| download | linux-bbaf444a89dd7dd7effd8ed2f4e4ec64da3cc1da.tar.xz | |
Bluetooth: Use proper invalid value for tx_power
The core specification defines 127 as the "not available" value (well,
"reserved" for BR/EDR and "not available" for LE - but essentially the
same). Therefore, instead of testing for 0 (which is in fact a valid
value) we should be using this invalid value to test if the tx_power is
available.
Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
Acked-by: Marcel Holtmann <marcel@holtmann.org>
Signed-off-by: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
Diffstat (limited to 'firmware/bnx2x')
0 files changed, 0 insertions, 0 deletions