[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200905130422.36e230df@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Date: Sat, 5 Sep 2020 13:04:22 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Shannon Nelson <snelson@...sando.io>
Cc: netdev@...r.kernel.org, davem@...emloft.net
Subject: Re: [PATCH v2 net-next 2/2] ionic: add devlink firmware update
On Thu, 3 Sep 2020 17:05:34 -0700 Shannon Nelson wrote:
> +/* The worst case wait for the install activity is about 25 minutes when
> + * installing a new CPLD, which is very seldom. Normal is about 30-35
> + * seconds. Since the driver can't tell if a CPLD update will happen we
> + * set the timeout for the ugly case.
25 minutes is really quite scary. And user will see no notification
other than "Installing 50%" for 25 minutes? And will most likely not
be able to do anything that'd involve talking to the FW, like setting
port info/speed?
Is it possible for the FW to inform that it's updating the CPLD?
Can you release the dev_cmd_lock periodically to allow other commands
to be executed while waiting?
Powered by blists - more mailing lists