From: Ilikara Zheng <ilikara@aosc.io>
To: Keith Busch <kbusch@kernel.org>
Cc: linux-kernel@vger.kernel.org, Wu Haotian <rigoligo03@gmail.com>,
Mingcong Bai <jeffbai@aosc.io>,
Kexy Biscuit <kexybiscuit@aosc.io>,
stable@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
"open list:NVM EXPRESS DRIVER" <linux-nvme@lists.infradead.org>
Subject: Re: [PATCH] nvme-pci: add quirk for Wodposit WPBSNM8-256GTP to disable secondary temp thresholds
Date: Tue, 16 Dec 2025 21:47:48 +0800 [thread overview]
Message-ID: <84cb474d-c41e-40dd-9a75-704b9ebaaf45@aosc.io> (raw)
In-Reply-To: <aUAqGO7GXRrTk4Vq@kbusch-mbp>
Hi Keith,
On 12/15/2025 11:32 PM, Keith Busch wrote:
> I'm not finding vendor 1FA0 registered on the public pci-ids, nor in the
> pcisig.com members list.
When I run command lspci -vvnnk, I got outputs below:
01:00.0 Non-Volatile memory controller [0108]: Device [1fa0:2283]
(prog-if 02 [NVM Express])
Subsystem: Device [1fa0:2283]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast
>TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 37
NUMA node: 0
Region 0: Memory at 40110000 (64-bit, non-prefetchable)
[size=16K]
Expansion ROM at 40000000 [disabled] [size=64K]
Capabilities: <access denied>
Kernel driver in use: nvme
> I just want to make sure the identifier is officially registered.
I have no idea why they didn't use their PCI Vendor ID, see
https://pcisig.com/membership/member-companies where they used a
different Vendor ID (0x2094).
prev parent reply other threads:[~2025-12-16 13:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-08 13:23 [PATCH] nvme-pci: add quirk for Wodposit WPBSNM8-256GTP to disable secondary temp thresholds Ilikara Zheng
2025-12-08 13:27 ` RigoLigo
2025-12-15 13:52 ` Ilikara Zheng
2025-12-15 15:32 ` Keith Busch
2025-12-16 13:47 ` Ilikara Zheng [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=84cb474d-c41e-40dd-9a75-704b9ebaaf45@aosc.io \
--to=ilikara@aosc.io \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=jeffbai@aosc.io \
--cc=kbusch@kernel.org \
--cc=kexybiscuit@aosc.io \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=rigoligo03@gmail.com \
--cc=sagi@grimberg.me \
--cc=stable@vger.kernel.org \
/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