From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: "Wu, Hao A" <hao.a.wu@intel.com>,
"Zeng, Star" <star.zeng@intel.com>,
"Ni, Ruiyu" <ruiyu.ni@intel.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
"leif.lindholm@linaro.org" <leif.lindholm@linaro.org>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
"Tian, Feng" <feng.tian@intel.com>
Subject: Re: [PATCH v4 0/2] quirks handling for SDHCI controllers
Date: Mon, 29 Jan 2018 08:25:43 +0000 [thread overview]
Message-ID: <CAKv+Gu_hMH_BLkTfvHPFPUjv-oQsDEccTO4iZ1Gv-AqaKHQc=Q@mail.gmail.com> (raw)
In-Reply-To: <B80AF82E9BFB8E4FBD8C89DA810C6A0931D449E3@SHSMSX104.ccr.corp.intel.com>
On 29 January 2018 at 05:13, Wu, Hao A <hao.a.wu@intel.com> wrote:
> One minor comment, please help to remove the line (around line 1067):
> @param[in] Capability The capability of the slot.
>
> within function description comment for SdMmcHcInitHost() in file:
> MdeModulePkg\Bus\Pci\SdMmcPciHcDxe\SdMmcPciHci.c
>
> Other than that, the series is good to me:
> Reviewed-by: Hao Wu <hao.a.wu@intel.com>
>
Thank you very much!
> Really sorry for the delay.
>
No worries. Star, Ray, any more comments from your side?
>
>> -----Original Message-----
>> From: Ard Biesheuvel [mailto:ard.biesheuvel@linaro.org]
>> Sent: Friday, December 08, 2017 6:43 AM
>> To: edk2-devel@lists.01.org
>> Cc: leif.lindholm@linaro.org; Kinney, Michael D; Zeng, Star; Tian, Feng; Ni,
>> Ruiyu; Wu, Hao A; Ard Biesheuvel
>> Subject: [PATCH v4 0/2] quirks handling for SDHCI controllers
>>
>> Many SDHCI implementations exist that are almost spec complicant, and
>> could be driven by the generic SD/MMC host controller driver except
>> for some minimal necessary init time tweaks.
>>
>> Adding such tweaks to the generic driver is undesirable. On the other
>> hand, forking the driver for every platform that has such a SDHCI
>> controller is problematic when it comes to upstreaming and ongoing
>> maintenance (which is arguably the point of upstreaming in the first
>> place).
>>
>> So these patches propose a workaround that is minimally invasive on the
>> EDK2 side, but gives platforms a lot of leeway when it comes to applying
>> SDHCI quirks.
>>
>> Changes since v3:
>> - remove PassThru argument from protocol members: it is unclear whether the
>> protocol is available when the override protocol is invoked, and my
>> example use case does not need it
>> - replace incorrect HandleProtocol with LocateProtocol, given that the override
>> protocol is now a singleton instance
>> - merge notifier calls into SdMmcHcReset() and SdMmcHcInitHost (), this
>> required changing the prototype to take a SD_MMC_HC_PRIVATE_DATA*
>> argument
>> and so the prototypes no longer belong in SdMmcPciHci.h and have been
>> moved
>> to SdMmcPciHcDxe.h
>> - use VOID* type for capability not UINT64* since we don't know its alignment
>>
>> Changes since v2:
>> - use a singleton instance of the SD/MMC protocol rather than one per
>> controller; this is needed to support 'reconnect -r', as pointed out
>> by Ray
>> - use EDKII prefixes for all types defined by the protocol
>> - replace 'hook' with 'notify', and tweak some other identifiers
>> - add missing function comment headers for factored out functions
>>
>> Changes since RFC/v1:
>> - add EFI_SD_MMC_PASS_THRU_PROTOCOL* member to override methods
>> - use UINT64* not VOID* to pass capability structure (which is always 64 bits
>> in size)
>>
>> Ard Biesheuvel (2):
>> MdeModulePkg: introduce SD/MMC override protocol
>> MdeModulePkg/SdMmcPciHcDxe: allow HC capabilities to be overridden
>>
>> MdeModulePkg/Bus/Pci/SdMmcPciHcDxe/SdMmcPciHcDxe.c | 35 ++++++-
>> MdeModulePkg/Bus/Pci/SdMmcPciHcDxe/SdMmcPciHcDxe.h | 36 ++++++++
>> MdeModulePkg/Bus/Pci/SdMmcPciHcDxe/SdMmcPciHcDxe.inf | 2 +
>> MdeModulePkg/Bus/Pci/SdMmcPciHcDxe/SdMmcPciHci.c | 95
>> +++++++++++++++++--
>> MdeModulePkg/Bus/Pci/SdMmcPciHcDxe/SdMmcPciHci.h | 35 -------
>> MdeModulePkg/Include/Protocol/SdMmcOverride.h | 97
>> ++++++++++++++++++++
>> MdeModulePkg/MdeModulePkg.dec | 3 +
>> 7 files changed, 257 insertions(+), 46 deletions(-)
>> create mode 100644 MdeModulePkg/Include/Protocol/SdMmcOverride.h
>>
>> --
>> 2.11.0
>
next prev parent reply other threads:[~2018-01-29 8:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-07 22:43 [PATCH v4 0/2] quirks handling for SDHCI controllers Ard Biesheuvel
2017-12-07 22:43 ` [PATCH v4 1/2] MdeModulePkg: introduce SD/MMC override protocol Ard Biesheuvel
2017-12-07 22:43 ` [PATCH v4 2/2] MdeModulePkg/SdMmcPciHcDxe: allow HC capabilities to be overridden Ard Biesheuvel
2017-12-12 7:00 ` [PATCH v4 0/2] quirks handling for SDHCI controllers Ard Biesheuvel
2017-12-12 10:56 ` Wu, Hao A
2017-12-12 10:57 ` Ard Biesheuvel
2018-01-08 19:41 ` Ard Biesheuvel
2018-01-29 5:13 ` Wu, Hao A
2018-01-29 8:25 ` Ard Biesheuvel [this message]
2018-01-30 1:24 ` Zeng, Star
2018-01-30 9:52 ` Ard Biesheuvel
2018-03-06 5:14 ` Meenakshi Aggarwal
2018-03-06 11:10 ` Ard Biesheuvel
2018-03-06 11:18 ` Meenakshi Aggarwal
2018-01-30 9:07 ` Ni, Ruiyu
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='CAKv+Gu_hMH_BLkTfvHPFPUjv-oQsDEccTO4iZ1Gv-AqaKHQc=Q@mail.gmail.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