From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: "Zeng, Star" <star.zeng@intel.com>
Cc: "Ni, Ruiyu" <ruiyu.ni@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
"Wu, Hao A" <hao.a.wu@intel.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
"Tian, Feng" <feng.tian@intel.com>,
"leif.lindholm@linaro.org" <leif.lindholm@linaro.org>
Subject: Re: [PATCH v2 1/2] MdeModulePkg: introduce SD/MMC override protocol
Date: Tue, 5 Dec 2017 09:26:10 +0000 [thread overview]
Message-ID: <CAKv+Gu_RfHwAGSnahkvHkKpoA-jif9MR3KDgBu+yK-G0=nuaPQ@mail.gmail.com> (raw)
In-Reply-To: <0C09AFA07DD0434D9E2A0C6AEB0483103B9BFB70@shsmsx102.ccr.corp.intel.com>
On 5 December 2017 at 08:50, Zeng, Star <star.zeng@intel.com> wrote:
> Regardless the protocol name SdMmcOverride/SdMmcPlatform, so you mean the protocol should be produced by a DXE driver, but not a UEFI driver, right? I saw the example at https://lists.01.org/pipermail/edk2-devel/2017-November/017672.html shared by Ard installs the protocol in PlatformDxe that is a DXE driver.
>
> And you mean the SD/MMC host controller driver code should use LocateProtocol, but not HandleProtocol to find out the protocol instance, right?
>
I think this makes sense, yes. I will respin the second patch accordingly.
--
Ard.
next prev parent reply other threads:[~2017-12-05 9:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 10:11 [PATCH v2 0/2] quirks handling for SDHCI controllers Ard Biesheuvel
2017-11-30 10:11 ` [PATCH v2 1/2] MdeModulePkg: introduce SD/MMC override protocol Ard Biesheuvel
2017-12-05 7:08 ` Ni, Ruiyu
2017-12-05 7:20 ` Zeng, Star
2017-12-05 8:37 ` Ni, Ruiyu
2017-12-05 8:50 ` Zeng, Star
2017-12-05 9:26 ` Ard Biesheuvel [this message]
2017-12-05 10:12 ` Ni, Ruiyu
2017-12-05 10:24 ` Ard Biesheuvel
2017-12-05 10:33 ` Zeng, Star
2017-12-05 10:34 ` Ni, Ruiyu
2017-12-05 13:09 ` Wu, Hao A
2017-12-05 17:16 ` Ard Biesheuvel
2017-11-30 10:11 ` [PATCH v2 2/2] MdeModulePkg/SdMmcPciHcDxe: allow HC capabilities to be overridden Ard Biesheuvel
2017-12-05 12:46 ` Wu, Hao A
2017-12-04 14:53 ` [PATCH v2 0/2] quirks handling for SDHCI controllers Ard Biesheuvel
2017-12-05 2:08 ` Zeng, Star
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_RfHwAGSnahkvHkKpoA-jif9MR3KDgBu+yK-G0=nuaPQ@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