From: Enzo Matsumiya <ematsumiya@suse.de>
To: Chaitanya Kulkarni <chaitanyak@nvidia.com>
Cc: "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@fb.com>,
Sagi Grimberg <sagi@grimberg.me>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [RFC PATCH] nvme: add NO APST quirk for Kioxia device
Date: Wed, 10 Nov 2021 12:23:52 -0300 [thread overview]
Message-ID: <20211110152352.44l43fe5gg66mjna@cyberdelia> (raw)
In-Reply-To: <e37edd78-a390-25a6-874b-8b69d2b80182@nvidia.com>
Hi Chaitanya,
On 11/10, Chaitanya Kulkarni wrote:
>Enzo,
>
>> I didn't, had to google. I see it listed on Kioxia's website as
>> CD6-V Series (6.4T model), but since customer was running on an
>> DL380 Gen10, I suspect it could also be HPE PE8030 (PN P19837-B21).
>>
>
>You can get more information about this controller using nvme-cli
>id-ctrl command.
I'm aware.
I don't have access to the system, but id-ctrl output was shared with
us.
AFAICS these are the only identifying fields, which all indicate to be
Kioxia's:
NVME Identify Controller:
vid : 0x1e0f
ssvid : 0x1e0f
sn : [redacted]
mn : KCD6XVUL6T40
fr : GPK1
rab : 2
ieee : 8ce38e
...
Now something that I'm not aware. Would these change even if another
brand was using this Kioxia's chipset?
Is it crucial to have the product information (vs only chipset information)
for quirks? I'm already querying the customer for this anyway.
Cheers,
Enzo
next prev parent reply other threads:[~2021-11-10 15:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-06 2:08 Enzo Matsumiya
2021-11-09 8:06 ` Christoph Hellwig
2021-11-09 15:04 ` Enzo Matsumiya
2021-11-10 6:08 ` Chaitanya Kulkarni
2021-11-10 15:23 ` Enzo Matsumiya [this message]
2021-11-11 10:01 ` Christoph Hellwig
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=20211110152352.44l43fe5gg66mjna@cyberdelia \
--to=ematsumiya@suse.de \
--cc=axboe@fb.com \
--cc=chaitanyak@nvidia.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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®