From: keith.busch@intel.com (Keith Busch)
Subject: Firmware Activate without Reset
Date: Wed, 12 Oct 2016 16:25:24 -0400 [thread overview]
Message-ID: <20161012202523.GB12827@localhost.localdomain> (raw)
In-Reply-To: <B4627D7B-0736-4436-9901-EA9575105919@hgst.com>
On Wed, Oct 12, 2016@07:37:13PM +0000, David Darrington wrote:
> I?m trying to understand how firmware activate without reset would work. Is there a requirement for the driver to do something to support this? Should the driver be listening for Firmware Activation Notifications, and respond in some way?
>
I don't think there's anything the driver necessarily has to do. If
anything, we could have it observe the notify AER on firmware activation
started, quiesce IO, then poll CSTS.PP. Once cleared, it can restart IO.
But that shouldn't really be necessary since we expect all outstanding
commands to complete when the activation completes. If activation takes
longer than an IO timeout, it might be best to quiesce, but the driver
doesn't do that right now.
If new firmware brings new capabilities that you want the driver to use,
the driver won't discover these until after a controller reset.
prev parent reply other threads:[~2016-10-12 20:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 19:37 Firmware Activate without Reset David Darrington
2016-10-12 20:25 ` Keith Busch [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161012202523.GB12827@localhost.localdomain \
--to=keith.busch@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox