From: "chenxia1" <xiao.x.chen@intel.com>
To: devel@edk2.groups.io
Cc: Xiao X Chen <xiao.x.chen@intel.com>
Subject: [PATCH v2 0/1] Use PCI_DEVICE_PPI to manage Nvme device
Date: Tue, 30 Aug 2022 13:46:47 +0800 [thread overview]
Message-ID: <cover.1661838204.git.xiao.x.chen@intel.com> (raw)
This change modifies NvmExpressPei library to allow usage EDKII_PCI_DEVICE_PPI to manage Nvme device.
For now, the part that performs the enumeration and creates EDKII_PCI_DEVICE_PPI will be implemented in the silicon code.
Sample code can be seen here: https://github.com/mczaj/edk2-platforms/commit/d443062e58f9fba228869b54f2546d9735b3b506
unit test:
- verified the origin EDKII_NVM_EXPRESS_HOST_CONTROLLER_PPI flow in platform project,
Nvme controller can successful initialize.
- merged https://github.com/mczaj/edk2-platforms/commit/d443062e58f9fba228869b54f2546d9735b3b506 to platform project
to enumerate pcie device and create the EDKII_PCI_DEVICE_PPI for Nvme,
Nvme controller also can successful initialize by EDKII_PCI_DEVICE_PPI.
v1: https://edk2.groups.io/g/devel/topic/93340344
v2 changes:
- add the unit test information for cover letter
- refine the BAR type check for no.1 commit
Xiao X Chen (1):
MdeModulePkg/NvmExpressPei: Use PCI_DEVICE_PPI to manage Nvme device
.../Bus/Pci/NvmExpressPei/DevicePath.c | 44 --
.../Bus/Pci/NvmExpressPei/NvmExpressPei.c | 639 ++++++++++++------
.../Bus/Pci/NvmExpressPei/NvmExpressPei.h | 54 ++
.../Bus/Pci/NvmExpressPei/NvmExpressPei.inf | 3 +-
4 files changed, 488 insertions(+), 252 deletions(-)
--
2.37.0.windows.1
next reply other threads:[~2022-08-30 5:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 5:46 chenxia1 [this message]
2022-08-30 5:46 ` [PATCH v2 1/1] MdeModulePkg/NvmExpressPei: Use PCI_DEVICE_PPI to manage Nvme device chenxia1
2022-08-30 6:27 ` Wu, Hao A
2022-09-01 5:33 ` [edk2-devel] " Wu, Hao A
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-list 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=cover.1661838204.git.xiao.x.chen@intel.com \
--to=devel@edk2.groups.io \
/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