> IMO, the driver probing path is allowed to sleep, so looks request firmware > should be allowed inside .probe().
I'm not convinced about that. It can sleep but its holding various locks in most cases, and it looks like that can end up in a complete heap. By all means *request* the firmware asynchronously in the probe, but there needs to be a seperate method somewhere after the probe to finish the job once the firmware appears. Alan -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
