Brian Norris <briannor...@chromium.org> wrote: > Depending on system factors (e.g., the PCIe link PM state), the first > read to wake up the Wifi firmware can take a long time. There is no > reason to use a (blocking, non-posted) read at this point, so let's just > use a write instead. Write vs. read doesn't matter functionality-wise -- > it's just a dummy operation. But let's make sure to re-write with the > correct "ready" signature, since we check for that in other parts of the > driver. > > This has been shown to decrease the time spent blocking in this function > on RK3399. > > Signed-off-by: Brian Norris <briannor...@chromium.org>
3 patches applied to wireless-drivers-next.git, thanks. 062e008a6e83 mwifiex: pcie: use posted write to wake up firmware 5d5ddb5e0d9b mwifiex: pcie: don't loop/retry interrupt status checks fe1167883939 mwifiex: pcie: read FROMDEVICE DMA-able memory with READ_ONCE() -- https://patchwork.kernel.org/patch/9516615/ Documentation about submitting wireless patches and checking status from patchwork: https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
