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>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: Marcin Wojtas <mw@semihalf.com>,
	"Gao, Zhichao" <zhichao.gao@intel.com>,
	"Gao, Liming" <liming.gao@intel.com>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: Re: [PATCH 0/2] MdeModulePkg/SdMmcPciHcDxe: Send the EdkiiSdMmcSwitchClockFreq notification before sending CMD13
Date: Tue, 24 Dec 2019 02:51:51 +0000	[thread overview]
Message-ID: <B80AF82E9BFB8E4FBD8C89DA810C6A093C974BE7@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <20191220171312.3120-1-mateusz.albecki@intel.com>

> -----Original Message-----
> From: Albecki, Mateusz
> Sent: Saturday, December 21, 2019 1:13 AM
> To: devel@edk2.groups.io
> Cc: Albecki, Mateusz; Wu, Hao A; Marcin Wojtas; Gao, Zhichao; Gao, Liming
> Subject: [PATCH 0/2] MdeModulePkg/SdMmcPciHcDxe: Send the
> EdkiiSdMmcSwitchClockFreq notification before sending CMD13
> 
> The first patch refactors the SdMmcClockSupply function with a goal
> of sending the EdkiiSdMmcSwitchClockFreq notification before we send the
> CMD13 to check the switch status in eMMC init flow. This is required to
> avoid sending the CMD13 on link that still has not been fixed by platform.
> 
> To avoid changing the driver behavior we avoid sending notifications
> when the clock is setup for the first time or when we setup the clock
> after the voltage switch procedure(adressed in second patch).
> 
> The second patch in the series optimizes the SD card detection routine
> to stop it from going through the process of internal clock setup
> after switching the voltage. According to SD HC specification there
> is no need to setup internal clock all over again.
> 
> Tests performed:
> - Booted eMMC in HS400 mode on platform which required post clock freq
> fixes
> 
> I wasn't able to test SD card yet due to the lack of setup with working SD.


I performed a quick verification on the eMMC device and SD card on my side.
They work properly after the series.

So for the series,
Tested-by: Hao A Wu <hao.a.wu@intel.com>


> 
> The patch series is available on github here:
> https://github.com/malbecki/edk2/tree/sdmmc_post_freq_notify


Add Ard to the loop to see if there is additional comment.

Best Regards,
Hao Wu


> 
> Cc: Hao A Wu <hao.a.wu@intel.com>
> Cc: Marcin Wojtas <mw@semihalf.com>
> Cc: Zhichao Gao <zhichao.gao@intel.com>
> Cc: Liming Gao <liming.gao@intel.com>
> 
> Mateusz Albecki (2):
>   SdMmcPciHcDxe: Send EdkiiSdMmcSwitchClockFreq after SD clock start
>   MdeModulePkg/SdMmcPciHcDxe: Add function to start SD clock
> 
>  MdeModulePkg/Bus/Pci/SdMmcPciHcDxe/EmmcDevice.c    |  20 +--
>  MdeModulePkg/Bus/Pci/SdMmcPciHcDxe/SdDevice.c      |  25 +---
>  MdeModulePkg/Bus/Pci/SdMmcPciHcDxe/SdMmcPciHcDxe.h |  24 ++++
>  MdeModulePkg/Bus/Pci/SdMmcPciHcDxe/SdMmcPciHci.c   | 136
> +++++++++++----------
>  MdeModulePkg/Bus/Pci/SdMmcPciHcDxe/SdMmcPciHci.h   |  45 ++-----
>  5 files changed, 112 insertions(+), 138 deletions(-)
> 
> --
> 2.14.1.windows.1


  parent reply	other threads:[~2019-12-24  2:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-20 17:13 [PATCH 0/2] MdeModulePkg/SdMmcPciHcDxe: Send the EdkiiSdMmcSwitchClockFreq notification before sending CMD13 Albecki, Mateusz
2019-12-20 17:13 ` [PATCH 1/2] SdMmcPciHcDxe: Send EdkiiSdMmcSwitchClockFreq after SD clock start Albecki, Mateusz
2019-12-24  2:52   ` Wu, Hao A
2019-12-24  9:54     ` Ard Biesheuvel
2019-12-30  8:44       ` Marcin Wojtas
2019-12-31 14:49     ` Albecki, Mateusz
2019-12-20 17:13 ` [PATCH 2/2] MdeModulePkg/SdMmcPciHcDxe: Add function to start SD clock Albecki, Mateusz
2019-12-24  2:52   ` Wu, Hao A
2019-12-24  2:51 ` Wu, Hao A [this message]
2020-01-03 11:04   ` [PATCH 0/2] MdeModulePkg/SdMmcPciHcDxe: Send the EdkiiSdMmcSwitchClockFreq notification before sending CMD13 Marcin Wojtas
2020-01-06  5:18     ` Wu, Hao A
2020-01-06  6:10       ` [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=B80AF82E9BFB8E4FBD8C89DA810C6A093C974BE7@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