public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Wu, Hao A" <hao.a.wu@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"zhoucheng@phytium.com.cn" <zhoucheng@phytium.com.cn>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>,
	Liming Gao <gaoliming@byosoft.com.cn>,
	"Liu, Zhiguang" <zhiguang.liu@intel.com>
Subject: Re: [edk2-devel] [PATCH v1 1/2] MdePkg:Update IndustryStandard/Nvme.h with Nvme amdin controller data
Date: Fri, 20 Aug 2021 05:32:41 +0000	[thread overview]
Message-ID: <BN8PR11MB366619C49BCDCFFAF0F8C913CAC19@BN8PR11MB3666.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20210819073056.3996-2-zhoucheng@phytium.com.cn>

> -----Original Message-----
> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of
> zhoucheng
> Sent: Thursday, August 19, 2021 3:31 PM
> To: devel@edk2.groups.io
> Cc: Kinney, Michael D <michael.d.kinney@intel.com>; Liming Gao
> <gaoliming@byosoft.com.cn>; Liu, Zhiguang <zhiguang.liu@intel.com>
> Subject: [edk2-devel] [PATCH v1 1/2] MdePkg:Update
> IndustryStandard/Nvme.h with Nvme amdin controller data
> 
> Update Nvme data structure
> 
> Signed-off-by: Cheng Zhou <zhoucheng@phytium.com.cn>
> Reviewed-by: Liming Gao <gaoliming@byosoft.com.cn>
> 
> Cc: Michael D Kinney <michael.d.kinney@intel.com>
> Cc: Liming Gao <gaoliming@byosoft.com.cn>
> Cc: Zhiguang Liu <zhiguang.liu@intel.com>
> ---
>  MdePkg/Include/IndustryStandard/Nvme.h | 11 ++++++++++-
>  1 file changed, 10 insertions(+), 1 deletion(-)
> 
> diff --git a/MdePkg/Include/IndustryStandard/Nvme.h
> b/MdePkg/Include/IndustryStandard/Nvme.h
> index 9b19a2074b0d..f7a1a9f6ca32 100644
> --- a/MdePkg/Include/IndustryStandard/Nvme.h
> +++ b/MdePkg/Include/IndustryStandard/Nvme.h
> @@ -353,7 +353,16 @@ typedef struct {
>    UINT8  Npss;                /* Number of Power States Support */
>    UINT8  Avscc;               /* Admin Vendor Specific Command Configuration */
>    UINT8  Apsta;               /* Autonomous Power State Transition Attributes */
> -  UINT8  Rsvd2[246];          /* Reserved as of Nvm Express 1.1 Spec */
> +  //
> +  // Below fields before Rsvd2 are defined in NVM Express 1.3 Spec  //
> +  UINT16 Wctemp;              /* Warning Composite Temperature Threshold */
> +  UINT16 Cctemp;              /* Critical Composite Temperature Threshold */
> +  UINT16 Mtfa;                /* Maximum Time for Firmware Activation */
> +  UINT32 Hmpre;               /* Host Memory Buffer Preferred Size */
> +  UINT32 Hmmin;               /* Host Memory Buffer Minimum Size */
> +  UINT8  Tnvmcap[16];         /* Total NVM Capacity */
> +  UINT8  Rsvd2[216];          /* Reserved as of NVM Express */


Reviewed-by: Hao A Wu <hao.a.wu@intel.com>

Best Regards,
Hao Wu


>    //
>    // NVM Command Set Attributes
>    //
> --
> 2.17.1
> 
> 
> 
> 
> 


  reply	other threads:[~2021-08-20  5:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-19  7:30 [PATCH v1 0/2] MdeModulePkg:Increase Nvme capacity display zhoucheng
2021-08-19  7:30 ` [PATCH v1 1/2] MdePkg:Update IndustryStandard/Nvme.h with Nvme amdin controller data zhoucheng
2021-08-20  5:32   ` Wu, Hao A [this message]
2021-08-19  7:30 ` [PATCH v1 2/2] MdeModulePkg:Increase Nvme capacity display zhoucheng
2021-08-20  5:32   ` Wu, Hao A
2021-08-30  3:46 ` [edk2-devel] [PATCH v1 0/2] " 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=BN8PR11MB366619C49BCDCFFAF0F8C913CAC19@BN8PR11MB3666.namprd11.prod.outlook.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