On Saturday 10 July 2021 00:25:36 Maximilian Luz wrote: > On 7/9/21 11:25 PM, Pali Rohár wrote: > > [...] > > > PCIe Function Level Reset should reset only one PCIe part of device. And > > seems that this type of reset does not work properly in some situations. > > > > Note that PCIe Function Level Reset is independent of running firmware. > > It is implement in hardware and (should) work also at early stage when > > firmware is not loaded yet. > > > > I'm starting to think more and more if quirk in this patch really needs > > to be behind DMI check and if rather it should not be called on other > > platforms too? > > Maybe? I'm not sure how well this behaves on other devices and if there > even are any devices outside of the MS Surface line that really require > or benefit from something like this. To me it seems safer to put it > behind quirks, at least until we know more. This is a good argument for DMI based quirk. But at the end, PCI people should look at this patch and say what do they thing about it, if it is better to enable it only for specific set of machines (Surface) or it is better to enable it for every 88W8xxx wifi or for none. > Also not sure if this is just my bias, but it feels like the Surface > line always had more problems with that driver (and firmware) than > others. Ehm, really? I see reports also from non-Surface users about bad quality of these 88W[89]xxx cards and repeating firmware issues. I have bad personal experience with 88W8997 SDIO firmware and lot of times I get advice about ex-Marvell/NXP wifi cards "do not touch and run away quickly". I think that more people if they get mPCIe/M.2 wifi card in laptop which does not work, they just replace it with some working one. And not spending infinite time in trying to fix it... So this may explain why there are more Surface users with these issues... > I'm honestly a bit surprised that MS stuck with them for this > long (they decided to go with Intel for 7th gen devices). AFAICT they > initially chose Marvell due to connected standby support, so maybe that > causes issue for us and others simply aren't using that feature? Just > guessing though. In my opinion that "Connected Standby" is just MS marketing term. 88W[89]xxx chips using full-mac firmware and drivers [*]. Full-mac lot of times causing more issues than soft-mac solution. Moreover this Marvell firmware implements also other "application" layers in firmware which OS drivers can use, e.g. there is fully working "wpa-supplicant" replacement and also AP part. Maybe windows drivers are using it and it cause less problems? Duno. mwifiex uses only "low level" commands and WPA state machine is implemented in userspace wpa-supplicant daemon. [*] - Small note: There are also soft-mac firmwares and drivers but apparently Marvell has never finished linux driver and firmware was not released to public... And there is also Laird Connectivity which offers their own proprietary linux kernel drivers with their own firmware for these 88W[89]xxx chips. Last time I checked it they released some parts of driver on github. Maybe somebody could contact Laird or check if their driver can be replaced by mwifiex? Or just replacing ex-Marvell/NXP firmware by their? But I'm not sure if they have something for 88W8897.
