Received-SPF: pass (google.com: domain of linux-bluetooth+bounces-4193-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) client-ip=147.75.199.223;
From: Johan Hovold <johan+linaro@kernel.org>
To: Marcel Holtmann <marcel@holtmann.org>,
	Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: Doug Anderson <dianders@chromium.org>,
	Janaki Ramaiah Thota <quic_janathot@quicinc.com>,
	linux-bluetooth@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Johan Hovold <johan+linaro@kernel.org>
Subject: [PATCH v2 0/3] Bluetooth: qca: generalise device address check
Date: Tue, 30 Apr 2024 19:07:38 +0200
Message-ID: <20240430170741.15742-1-johan+linaro@kernel.org>
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit

The QCA default device address apparently comes from the NVM
configuration file and can differ quite a bit between controllers.

This series adds support for storing the default address when parsing
the configuration file and using 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.

Included in v2 are two preparatory but otherwise independent fixes that
adds the missing sanity checks when parsing the firmware files and makes
sure that the parser can handle configuration files for WCN3xxx.

Johan


Changes in v2:
 - add missing firmware sanity checks (new patch)
 - fix nvm configuration parsing (new patch)
 - make sure to set the BD_ADDR quirk flag also when the controller
   returns BDADDR_ANY


Johan Hovold (3):
  Bluetooth: qca: add missing firmware sanity checks
  Bluetooth: qca: fix NVM configuration parsing
  Bluetooth: qca: generalise device address check

 drivers/bluetooth/btqca.c | 83 +++++++++++++++++++++++++++++++--------
 drivers/bluetooth/btqca.h |  2 +
 2 files changed, 68 insertions(+), 17 deletions(-)

-- 
2.43.2