diff options
| author | Johan Hovold <johan+linaro@kernel.org> | 2024-04-30 20:07:41 +0300 |
|---|---|---|
| committer | Luiz Augusto von Dentz <luiz.von.dentz@intel.com> | 2024-05-03 20:05:31 +0300 |
| commit | dd336649ba89789c845618dcbc09867010aec673 (patch) | |
| tree | e7ef76ed85ff719f8a04eea320151f7bcac6ba70 /tools/perf/util/scripting-engines | |
| parent | a112d3c72a227f2edbb6d8094472cc6e503e52af (diff) | |
| download | linux-dd336649ba89789c845618dcbc09867010aec673.tar.xz | |
Bluetooth: qca: generalise device address check
The default device address apparently comes from the NVM configuration
file and can differ quite a bit between controllers.
Store the default address when parsing the configuration file and use it
to determine whether the controller has been provisioned with an
address.
This makes sure that devices without a unique address start as
unconfigured unless a valid address has been provided in the devicetree.
Fixes: 32868e126c78 ("Bluetooth: qca: fix invalid device address check")
Cc: stable@vger.kernel.org # 6.5
Cc: Doug Anderson <dianders@chromium.org>
Cc: Janaki Ramaiah Thota <quic_janathot@quicinc.com>
Signed-off-by: Johan Hovold <johan+linaro@kernel.org>
Tested-by: Douglas Anderson <dianders@chromium.org>
Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Diffstat (limited to 'tools/perf/util/scripting-engines')
0 files changed, 0 insertions, 0 deletions