Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Subject: Re: Firmware version read error on Intel AX210
To:     "K, Kiran" <kiran.k@intel.com>, Kiran K <kiraank@gmail.com>
Cc:     BlueZ development <linux-bluetooth@vger.kernel.org>,
        "Srivatsa, Ravishankar" <ravishankar.srivatsa@intel.com>,
        "Tumkur Narayan, Chethan" <chethan.tumkur.narayan@intel.com>,
        Marcel Holtmann <marcel@holtmann.org>
References: <89a134d0-c6f6-c685-2aeb-7dc5eee1966f@gmail.com>
 <44820333-3e09-5405-a1aa-19f64087f164@gmail.com>
 <DM6PR11MB314662E82730EF100538531DF5FD0@DM6PR11MB3146.namprd11.prod.outlook.com>
From:   Heiner Kallweit <hkallweit1@gmail.com>
Message-ID: <65ed6733-6dd2-41fa-7757-55fe5b91f290@gmail.com>
Date:   Sun, 22 Nov 2020 18:41:51 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
 Thunderbird/78.5.0
MIME-Version: 1.0
In-Reply-To: <DM6PR11MB314662E82730EF100538531DF5FD0@DM6PR11MB3146.namprd11.prod.outlook.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Precedence: bulk

Am 22.11.2020 um 09:35 schrieb K, Kiran:
> Hi Heiner Kallweit,
> 
> The patches to support  Intel AX210  are not fully upstreamed into bluetooth-next.  Final patch set review is in progress - https://patchwork.kernel.org/project/bluetooth/list/?series=387475
> 
Good to hear and thanks for the link to the patch series.
How about firmware, is it submitted to linux-firmware in parallel?


Following is unrelated, however I hope you're the right addressee too.

In btusb.c we have the following code. I interpret this in a way
that once firmware was loaded the driver will never check for
updated firmware.
Shouldn't the driver always read the firmware file available on
the system and check its version against the firmware version
the device has (and apply it if it's newer)?
But maybe I miss something ..

bt_dev_info(hdev, "read Intel version: %02x%02x%02x%02x%02x%02x%02x%02x%02x",
	    ver.hw_platform, ver.hw_variant, ver.hw_revision,
	    ver.fw_variant,  ver.fw_revision, ver.fw_build_num,
	    ver.fw_build_ww, ver.fw_build_yy, ver.fw_patch_num);

/* fw_patch_num indicates the version of patch the device currently
 * have. If there is no patch data in the device, it is always 0x00.
 * So, if it is other than 0x00, no need to patch the device again.
 */
if (ver.fw_patch_num) {
	bt_dev_info(hdev, "Intel device is already patched. "
		    "patch num: %02x", ver.fw_patch_num);
	goto complete;
}


> Regards,
> Kiran
> 
Thank you, Heiner

>> -----Original Message-----
>> From: Heiner Kallweit <hkallweit1@gmail.com>
>> Sent: Sunday, November 22, 2020 4:30 AM
>> To: Kiran K <kiraank@gmail.com>; K, Kiran <kiran.k@intel.com>
>> Cc: BlueZ development <linux-bluetooth@vger.kernel.org>
>> Subject: Re: Firmware version read error on Intel AX210
>>
>> Am 21.11.2020 um 23:12 schrieb Heiner Kallweit:
>>> I have a new AX210 WiFi/Bluetooth card and btintel_read_version()
>>> fails with error -22 (EINVAL). Underlying error is that the firmware
>>> version read command returns with hdev->req_result = 18 (0x12).
>>> (req_status = 0)
>>> >From what I've read this means invalid command parameters.
>>> Did something change with AX210 and command 0xfc05 requires specific
>>> parameters now? Or what else may cause this issue?
>>>
>> Seems AX210 uses the new TLV infrastructure. btintel_read_version_tlv()
>> returns valid data. Will TLV/AX210 support be added for 5.11?