<Ajay.Kathat@xxxxxxxxxxxxx> writes: > On 1/19/24 14:51, David Mosberger-Tang wrote: >> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe >> >> The current version of the wilc1000 driver has a probe function that simply >> assumes the chip is present. It is only later, in wilc_spi_init(), that the >> driver verifies that it can actually communicate with the chip. The result of >> this is that the net device (typically wlan0) is created and remains in place as >> long as the wilc1000-spi driver is loaded, even if the WILC1000 chip is not >> present or not working. >> >> Is there any reason not to detect the chip's present in wilc_bus_probe()? The >> patch below (relative to 5.15.147) works for me, but perhaps I'm missing >> something? Would it make sense to merge something along these lines into >> mainline? >> > > I think it is the WILC driver design that the firmware/chip operations > are executed only when the netdev interface(wlan0) is up. Yeah, that's good design. I think that wlan0 is down wireless drivers should turn off the hardware to reduce power consumption as much as possible. Many drivers do start the firmware during probe() to query the capabilities and then turn it off immediately. -- https://patchwork.kernel.org/project/linux-wireless/list/ https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
