From: "Zeng, Star" <star.zeng@intel.com>
To: "Wu, Hao A" <hao.a.wu@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Zeng, Star" <star.zeng@intel.com>
Subject: Re: [PATCH 0/2] Implementation of UFS Device Config Protocol
Date: Wed, 2 Aug 2017 08:08:44 +0000 [thread overview]
Message-ID: <0C09AFA07DD0434D9E2A0C6AEB0483103B8F8B0A@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <20170720021835.10808-1-hao.a.wu@intel.com>
Reviewed-by: Star Zeng <star.zeng@intel.com>
-----Original Message-----
From: Wu, Hao A
Sent: Thursday, July 20, 2017 10:19 AM
To: edk2-devel@lists.01.org
Cc: Wu, Hao A <hao.a.wu@intel.com>; Zeng, Star <star.zeng@intel.com>
Subject: [PATCH 0/2] Implementation of UFS Device Config Protocol
The series adds the implementation of UFS Device Config Protocol in the UfsPassThruDxe driver.
Also, the series resolves a 'Write Descriptor' operation failure issue in the UFS drivers.
Cc: Star Zeng <star.zeng@intel.com>
Hao Wu (2):
MdeModulePkg/UfsPassThruDxe: Add impl of UFS Device Config Protocol
MdeModulePkg/Ufs: Set 'Data Segment Length' field for Write Descriptor
MdeModulePkg/Bus/Ufs/UfsBlockIoPei/UfsHci.c | 3 +
MdeModulePkg/Bus/Ufs/UfsPassThruDxe/UfsDevConfigProtocol.c | 196 ++++++++++++++++++++
MdeModulePkg/Bus/Ufs/UfsPassThruDxe/UfsPassThru.c | 24 ++-
MdeModulePkg/Bus/Ufs/UfsPassThruDxe/UfsPassThru.h | 133 ++++++++++++-
MdeModulePkg/Bus/Ufs/UfsPassThruDxe/UfsPassThruDxe.inf | 4 +-
MdeModulePkg/Bus/Ufs/UfsPassThruDxe/UfsPassThruHci.c | 43 ++++-
6 files changed, 389 insertions(+), 14 deletions(-) create mode 100644 MdeModulePkg/Bus/Ufs/UfsPassThruDxe/UfsDevConfigProtocol.c
--
2.12.0.windows.1
prev parent reply other threads:[~2017-08-02 8:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-20 2:18 [PATCH 0/2] Implementation of UFS Device Config Protocol Hao Wu
2017-07-20 2:18 ` [PATCH 1/2] MdeModulePkg/UfsPassThruDxe: Add impl " Hao Wu
2017-07-20 2:18 ` [PATCH 2/2] MdeModulePkg/Ufs: Set 'Data Segment Length' field for Write Descriptor Hao Wu
2017-08-02 8:08 ` Zeng, Star [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-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=0C09AFA07DD0434D9E2A0C6AEB0483103B8F8B0A@shsmsx102.ccr.corp.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