public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Wu, Hao A" <hao.a.wu@intel.com>
To: "Albecki, Mateusz" <mateusz.albecki@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [PATCH 0/3] Implement UFS info protocol to pass additional UIC programming data from platform/silicon specific driver
Date: Mon, 1 Apr 2019 06:53:25 +0000	[thread overview]
Message-ID: <B80AF82E9BFB8E4FBD8C89DA810C6A093C8BA00B@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <cover.1553774396.git.mateusz.albecki@intel.com>

> -----Original Message-----
> From: Albecki, Mateusz
> Sent: Thursday, March 28, 2019 9:49 PM
> To: edk2-devel@lists.01.org
> Cc: Albecki, Mateusz; Wu; Wu, Hao A
> Subject: [PATCH 0/3] Implement UFS info protocol to pass additional UIC
> programming data from platform/silicon specific driver
> 
> UFS specification allows for additional, implementation specific, programming
> to be done during host controller initialization. Since some hosts
> might require it to allow for device detection we add a way for platform/silicon
> specific code to pass required attributes and their values to
> generic UFS driver. Please see UFS 2.0 specification for details of the host
> controller initialization sequence(JESD223B section 7.1.1 step 4).
> Patchset consists of 3 patches to achieve this. The first one is a bugfix for data
> transfers that are not aligned to DWORD boundary such as SCSI SENSE
> command. The second one is code refactoring for device presence detection
> that cleans up the function that sends UIC commands. Final patch defines
> UFS info protocol and implements driver logic for servicing it.
> 
> Tests performed:
> -Test UFS LU enumeration with UFS 2.0 card with 3 enabled LUs
> -Test that no unaligned data transfers are performed during enumeration
> -Test that UIC is programmed according to platform table

Hello Mateusz,

For the additional UIC during HC initialization change, could you help to
verify a 'reconnect -r' under Shell to see whether the UFS devices work
fine in such case? Thanks.

Best Regards,
Hao Wu


> -Test that driver operation is not impacted when no UFS info protocol is
> installed
> 
> CC: Wu, Hao A <hao.a.wu@intel.com>
> 
> Albecki, Mateusz (3):
>   MdeModulePkg/UfsPassThruDxe: Fix unaligned data transfer handling
>   MdeModulePkg/UfsPassThruDxe: Refactor UFS device presence detection
>   MdeModulePkg/UfsPassThruDxe: Add UFS info protocol
> 
>  MdeModulePkg/Bus/Ufs/UfsPassThruDxe/UfsPassThru.c  |  62 +++++
>  MdeModulePkg/Bus/Ufs/UfsPassThruDxe/UfsPassThru.h  |   3 +
>  .../Bus/Ufs/UfsPassThruDxe/UfsPassThruDxe.inf      |   1 +
>  .../Bus/Ufs/UfsPassThruDxe/UfsPassThruHci.c        | 299 +++++++++++++++-----
> -
>  .../Include/Protocol/UfsHostControllerInfo.h       |  75 ++++++
>  MdeModulePkg/MdeModulePkg.dec                      |   3 +
>  6 files changed, 356 insertions(+), 87 deletions(-)
>  create mode 100644 MdeModulePkg/Include/Protocol/UfsHostControllerInfo.h
> 
> --
> 2.14.1.windows.1



      parent reply	other threads:[~2019-04-01  6:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-28 13:48 [PATCH 0/3] Implement UFS info protocol to pass additional UIC programming data from platform/silicon specific driver Albecki, Mateusz
2019-03-28 13:48 ` [PATCH 1/3] MdeModulePkg/UfsPassThruDxe: Fix unaligned data transfer handling Albecki, Mateusz
2019-03-28 13:56 ` [PATCH 2/3] MdeModulePkg/UfsPassThruDxe: Refactor UFS device presence detection Albecki, Mateusz
2019-04-01  6:53   ` Wu, Hao A
2019-03-28 13:56 ` [PATCH 3/3] MdeModulePkg/UfsPassThruDxe: Add UFS info protocol Albecki, Mateusz
2019-04-01  6:53   ` Wu, Hao A
     [not found]     ` <92CF190FF2351747A47C1708F0E09C0875DE7165@IRSMSX102.ger.corp.intel.com>
2019-04-12  6:35       ` Wu, Hao A
2019-04-12 23:22         ` Albecki, Mateusz
2019-04-15  5:56           ` Wu, Hao A
2019-04-01  6:53 ` Wu, Hao A [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=B80AF82E9BFB8E4FBD8C89DA810C6A093C8BA00B@SHSMSX104.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