summaryrefslogtreecommitdiffstats
path: root/net/ipv4
diff options
context:
space:
mode:
authorNithin Sujir <nsujir@broadcom.com>2013-06-12 11:08:59 -0700
committerDavid S. Miller <davem@davemloft.net>2013-06-13 02:41:51 -0700
commitdf465abfe06f7dc4f33f4a96d17f096e9e8ac917 (patch)
treea6ed8d59f635bf3337c9f4295a15fd59188294f4 /net/ipv4
parenta6f79d0f26704214b5b702bbac525cb72997f984 (diff)
downloadop-kernel-dev-df465abfe06f7dc4f33f4a96d17f096e9e8ac917.zip
op-kernel-dev-df465abfe06f7dc4f33f4a96d17f096e9e8ac917.tar.gz
tg3: Wait for boot code to finish after power on
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: stable@vger.kernel.org Signed-off-by: Nithin Nayak Sujir <nsujir@broadcom.com> Signed-off-by: Michael Chan <mchan@broadcom.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/ipv4')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud