From: "Nithin Nayak Sujir" <[email protected]> Date: Wed, 12 Jun 2013 11:08:59 -0700
> Some systems that don't need wake-on-lan may choose to power down the > chip on system standby. Upon resume, the power on causes the boot code > to startup and initialize the hardware. On one new platform, this is > causing the device to go into a bad state due to a race between the > driver and boot code, once every several hundred resumes. The same race > exists on open since we come up from a power on. > > This patch adds a wait for boot code signature at the beginning of > tg3_init_hw() which is common to both cases. If there has not been a > power-off or the boot code has already completed, the signature will be > present and poll_fw() returns immediately. Also return immediately if > the device does not have firmware. > > Cc: [email protected] > Signed-off-by: Nithin Nayak Sujir <[email protected]> > Signed-off-by: Michael Chan <[email protected]> Applied. -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
