From: Jens Axboe <axboe@kernel.dk>
To: Sagi Grimberg <sagi@grimberg.me>,
Mario Limonciello <mario.limonciello@dell.com>,
Keith Busch <kbusch@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>,
linux-nvme@lists.infradead.org,
LKML <linux-kernel@vger.kernel.org>,
Ryan Hong <Ryan.Hong@Dell.com>, Crag Wang <Crag.Wang@dell.com>,
sjg@google.com, Charles Hyde <charles.hyde@dellteam.com>,
Jared Dominguez <jared.dominguez@dell.com>
Subject: Re: [PATCH v3] nvme: Add quirk for LiteON CL1 devices running FW 22301111
Date: Mon, 19 Aug 2019 13:02:08 -0600 [thread overview]
Message-ID: <3d01da80-be78-5ca6-6ef2-c0e44840118f@kernel.dk> (raw)
In-Reply-To: <b4456ee7-6f5d-5968-2167-9900f049e5c6@grimberg.me>
On 8/19/19 12:57 PM, Sagi Grimberg wrote:
>
>
> On 8/16/19 1:16 PM, Mario Limonciello wrote:
>> One of the components in LiteON CL1 device has limitations that
>> can be encountered based upon boundary race conditions using the
>> nvme bus specific suspend to idle flow.
>>
>> When this situation occurs the drive doesn't resume properly from
>> suspend-to-idle.
>>
>> LiteON has confirmed this problem and fixed in the next firmware
>> version. As this firmware is already in the field, avoid running
>> nvme specific suspend to idle flow.
>>
>> Fixes: d916b1be94b6 ("nvme-pci: use host managed power state for suspend")
>> Link: http://lists.infradead.org/pipermail/linux-nvme/2019-July/thread.html
>> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
>> Signed-off-by: Charles Hyde <charles.hyde@dellteam.com>
>> ---
>
> Jens, can you please rebase for-linus so we have the needed dependency:
> 4eaefe8c621c6195c91044396ed8060c179f7aae
I just did as part of adding a new patch, being pushed out shortly.
--
Jens Axboe
next prev parent reply other threads:[~2019-08-19 19:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-16 20:16 Mario Limonciello
2019-08-19 18:57 ` Sagi Grimberg
2019-08-19 19:02 ` Jens Axboe [this message]
2019-08-19 21:23 ` Sagi Grimberg
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=3d01da80-be78-5ca6-6ef2-c0e44840118f@kernel.dk \
--to=axboe@kernel.dk \
--cc=Crag.Wang@dell.com \
--cc=Ryan.Hong@Dell.com \
--cc=charles.hyde@dellteam.com \
--cc=hch@lst.de \
--cc=jared.dominguez@dell.com \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=mario.limonciello@dell.com \
--cc=sagi@grimberg.me \
--cc=sjg@google.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
all inboxes | Powered by JetHome®