From: "Wu, Hao A" <hao.a.wu@intel.com>
To: Marcin Wojtas <mw@semihalf.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "leif.lindholm@linaro.org" <leif.lindholm@linaro.org>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
"Gao, Liming" <liming.gao@intel.com>,
"ard.biesheuvel@linaro.org" <ard.biesheuvel@linaro.org>,
"nadavh@marvell.com" <nadavh@marvell.com>,
"jsd@semihalf.com" <jsd@semihalf.com>,
"tm@semihalf.com" <tm@semihalf.com>,
"jaz@semihalf.com" <jaz@semihalf.com>
Subject: Re: [PATCH v4 0/4] SdMmcOverride extension
Date: Tue, 13 Nov 2018 07:38:46 +0000 [thread overview]
Message-ID: <B80AF82E9BFB8E4FBD8C89DA810C6A093C84C662@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <1541804487-27458-1-git-send-email-mw@semihalf.com>
Hi Marcin,
The code changes look good to me.
Could you please grant me some time for some additional tests for these
patches?
I will inform you with the results sometime next week. Thanks in advance.
Best Regards,
Hao Wu
> -----Original Message-----
> From: Marcin Wojtas [mailto:mw@semihalf.com]
> Sent: Saturday, November 10, 2018 7:01 AM
> To: edk2-devel@lists.01.org
> Cc: leif.lindholm@linaro.org; Wu, Hao A; Kinney, Michael D; Gao, Liming;
> ard.biesheuvel@linaro.org; nadavh@marvell.com; mw@semihalf.com;
> jsd@semihalf.com; tm@semihalf.com; jaz@semihalf.com
> Subject: [PATCH v4 0/4] SdMmcOverride extension
>
> Hi,
>
> Although I could've waited for Hao's remarks, I think it may
> be better if he takes a look at much cleaner code, which
> addresses v3 review comments.
> The newest version of the patchset cleans-up significantly
> patches 2&3 by removing code duplication and other minor
> improvements.
>
> Patches are available in the github:
> https://github.com/MarvellEmbeddedProcessors/edk2-open-
> platform/commits/sdmmc-override-upstream-r20181109
>
> Please note that extending SdMmcOverride protocol was impacting
> so far the only user of it (Synquacer controller). In paralel
> edk2-platforms patchset, a patch can be found:
> ("Silicon/SynQuacer/PlatformDxe: adjust to updated SdMmcOverride")
> which adjust to the new API.
> https://github.com/MarvellEmbeddedProcessors/edk2-open-
> platform/commits/xenon-upstream-r20181109
>
> I'm looking forward to the comments and remarks.
>
> Best regards,
> Marcin
>
> Changelog:
> v3->v4
> * 2/4:
> - avoid duplication by calling SdMmcOverride callback in
> SdMmcHcUhsSignaling
>
> * 3/4:
> - avoid duplication by calling SdMmcOverride callback in
> EmmcSwitchClockFreq
>
> * 4/4:
> - add Ard's RB
>
> v2->v3
> * 1/4:
> - rename new parameter to PhaseData
> - add Ard's RB
>
> * 2/4:
> - s/Controler/Controller/
> - remove all references to MMC_SDR_50 mode
> - rename and reorder MMC bus modes
> - rename enum: s/SD_MMC_UHS_TIMING/SD_MMC_BUS_MODE/
> and move it to protocol header in order to drop including private one
> - fix if condition in EmmcSwitchToHighSpeed
> - call SdMmcHcUhsSignaling unconditionally before SdMmcOverride
> callback, so that protocol producer can optionally modify only quirky
> timing mode values.
>
> *4/4
> - bump protocol version to 2
> - remove redundant assert from SdMmcPciHcDriverBindingStart
> (BaseClkFreq is already checked in SdMmcHcInitClockFreq)
> - update comment in SdMmcHcInitClockFreq
> - restore original DumpCapabilityReg and append
>
> v1 -> v2
> * Rebase onto newest master
> * 1/4 [new patch] - preparation for extending NotifyPhase
> * 2/4 - UhsSignaling as a part of NotifyPhase
> * 3/4 - SwitchClockFreqPost as a part of NotifyPhase
> * 4/4 - Allow updating BaseClkFreq via Capability instead of the
> independent callback.
>
>
> Marcin Wojtas (2):
> MdeModulePkg/SdMmcPciHcDxe: Add an optional parameter in NotifyPhase
> MdeModulePkg/SdMmcPciHcDxe: Allow overriding base clock frequency
>
> Tomasz Michalec (2):
> MdeModulePkg/SdMmcPciHcDxe: Add UhsSignaling to SdMmcOverride
> protocol
> MdeModulePkg/SdMmcPciHcDxe: Add SwitchClockFreqPost to
> SdMmcOverride
>
> MdeModulePkg/Bus/Pci/SdMmcPciHcDxe/SdMmcPciHcDxe.h | 6 +
> MdeModulePkg/Bus/Pci/SdMmcPciHcDxe/SdMmcPciHci.h | 42 ++++++-
> MdeModulePkg/Include/Protocol/SdMmcOverride.h | 29 ++++-
> MdeModulePkg/Bus/Pci/SdMmcPciHcDxe/EmmcDevice.c | 121 ++++++++++-
> --------
> MdeModulePkg/Bus/Pci/SdMmcPciHcDxe/SdDevice.c | 35 ++++--
> MdeModulePkg/Bus/Pci/SdMmcPciHcDxe/SdMmcPciHcDxe.c | 13 +-
> MdeModulePkg/Bus/Pci/SdMmcPciHcDxe/SdMmcPciHci.c | 124
> +++++++++++++++++---
> 7 files changed, 280 insertions(+), 90 deletions(-)
>
> --
> 2.7.4
next prev parent reply other threads:[~2018-11-13 7:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-09 23:01 [PATCH v4 0/4] SdMmcOverride extension Marcin Wojtas
2018-11-09 23:01 ` [PATCH v4 1/4] MdeModulePkg/SdMmcPciHcDxe: Add an optional parameter in NotifyPhase Marcin Wojtas
2018-11-09 23:01 ` [PATCH v4 2/4] MdeModulePkg/SdMmcPciHcDxe: Add UhsSignaling to SdMmcOverride protocol Marcin Wojtas
2018-11-12 10:22 ` Ard Biesheuvel
2018-11-09 23:01 ` [PATCH v4 3/4] MdeModulePkg/SdMmcPciHcDxe: Add SwitchClockFreqPost to SdMmcOverride Marcin Wojtas
2018-11-12 10:23 ` Ard Biesheuvel
2018-11-09 23:01 ` [PATCH v4 4/4] MdeModulePkg/SdMmcPciHcDxe: Allow overriding base clock frequency Marcin Wojtas
2018-11-13 7:38 ` Wu, Hao A [this message]
2018-11-13 8:25 ` [PATCH v4 0/4] SdMmcOverride extension Marcin Wojtas
2018-11-13 8:29 ` Wu, Hao A
2018-11-20 5:58 ` Wu, Hao A
2018-11-20 7:22 ` Marcin Wojtas
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=B80AF82E9BFB8E4FBD8C89DA810C6A093C84C662@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