Michal Kazior <michal.kazior@xxxxxxxxx> writes: > On 20 October 2014 14:14, Michal Kazior <michal.kazior@xxxxxxxxx> wrote: >> One of the problems with warm reset I've found is >> that it must be guaranteed that copy engine >> registers are not being accessed while being >> reset. Otherwise in worst case scenario the host >> may lock up. >> >> Instead of using sleeps and hoping the device is >> operational in some arbitrary timeframes use >> firmware indication register. >> >> As a side effect this makes driver >> boot/stop/recovery faster. >> >> Signed-off-by: Michal Kazior <michal.kazior@xxxxxxxxx> >> --- >> >> Notes: >> v2: >> * fix kernel panic on early fw crash due to CE not being fully initialized [Janusz] > > Marek reported he sees a memory leak and git bisect blames this patch. > Please don't apply this patch yet. Ok, thanks for letting me know. What about rest of the patches in the patchset? I assume it's safe to apply them. -- Kalle Valo -- 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
