[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20130613.024235.1657219452701408875.davem@davemloft.net>
Date: Thu, 13 Jun 2013 02:42:35 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: nsujir@...adcom.com
Cc: netdev@...r.kernel.org, stable@...r.kernel.org, mchan@...adcom.com
Subject: Re: [PATCH net] tg3: Wait for boot code to finish after power on
From: "Nithin Nayak Sujir" <nsujir@...adcom.com>
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: stable@...r.kernel.org
> Signed-off-by: Nithin Nayak Sujir <nsujir@...adcom.com>
> Signed-off-by: Michael Chan <mchan@...adcom.com>
Applied.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists