On Thu, Apr 21, 2016 at 2:09 PM, Bjorn Andersson <bjorn.andersson@xxxxxxxxxx> wrote: > After booting the wireless subsystem and uploading the NV blob to the > WCNSS_CTRL service the remote continues to do things and will not start > servicing wlan-requests for another 2-5 seconds (measured). > > The downstream code does not have any special handling for this case, > but has a timeout of 10 seconds for the communication layer. By > extending the wcn36xx timeout to match this we follows the same flow for > the boot procedure and can successfully configure WiFi as wlan0 is > registered. > > Signed-off-by: Bjorn Andersson <bjorn.andersson@xxxxxxxxxx> I've been using this with my nexus7 tree, and its avoided issues I was seeing without it. Tested-by: John Stultz <john.stultz@xxxxxxxxxx> thanks -john -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html