From: Leif Lindholm <leif.lindholm@linaro.org>
To: "Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: "Tian, Feng" <feng.tian@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
"Zeng, Star" <star.zeng@intel.com>
Subject: Re: [patch] MdeModulePkg/Xhci: add 1ms delay before access MMIO reg during reset
Date: Thu, 15 Sep 2016 11:19:58 +0100 [thread overview]
Message-ID: <20160915101958.GG16080@bivouac.eciton.net> (raw)
In-Reply-To: <E92EE9817A31E24EB0585FDF735412F564814D03@ORSMSX113.amr.corp.intel.com>
On Wed, Sep 14, 2016 at 05:14:19PM +0000, Kinney, Michael D wrote:
> MdePkg/Include/Library/UefiLib.h does have some helper macros for
> setting timer events periods that are in 100 nS units:
>
> #define EFI_TIMER_PERIOD_MICROSECONDS(Microseconds) MultU64x32((UINT64)(Microseconds), 10)
> #define EFI_TIMER_PERIOD_MILLISECONDS(Milliseconds) MultU64x32((UINT64)(Milliseconds), 10000)
> #define EFI_TIMER_PERIOD_SECONDS(Seconds) MultU64x32((UINT64)(Seconds), 10000000)
>
> I believe the examples you show are for use with the gBS->Stall()
> service which is in 1 uS units.
Correct.
> Maybe we should consider some additional macros in UefiLib.h
>
> #define EFI_STALL_PERIOD_MICROSECONDS(Microseconds) (Microseconds)
> #define EFI_STALL_PERIOD_MILLISECONDS(Milliseconds) ((Milliseconds) * 1000)
> #define EFI_STALL_PERIOD_SECONDS(Seconds) ((Seconds) * 1000000)
>
> Or maybe some macros that actually do the call to gBS->Stall() too.
>
> #define EFI_STALL_MICROSECONDS(Microseconds) gBS->Stall (Microseconds)
> #define EFI_STALL_MILLISECONDS(Milliseconds) gBS->Stall ((Milliseconds) * 1000)
> #define EFI_STALL_SECONDS(Seconds) gBS->Stall ((Seconds) * 1000000)
>
Either (or both) of those two look good to me. The latter has the
benefit of a smaller call site, at the cost of perhaps obscuring the
dependency on UefiRuntimeServicesTableLib.
> The other method of generating timed delays for PEI/DXE/SMM modules
> is using the Services in MdePkg/Include/Library/TimerLib.h:
>
> UINTN
> EFIAPI
> NanoSecondDelay (
> IN UINTN NanoSeconds
> );
>
> UINTN
> EFIAPI
> MicroSecondDelay (
> IN UINTN MicroSeconds
> );
>
> If we wanted macros helper to use these services to match UEFI ones, maybe
> add the following to TimerLib.h:
>
> #define DELAY_NANOSECONDS(Nanoseconds) NanoSecondDelay (Nanoseconds)
> #define DELAY_MICROSECONDS(Microseconds) MicroSecondDelay (Microseconds)
> #define DELAY_MILLISECONDS(Milliseconds) MicroSecondDelay ((Microseconds) * 1000)
> #define DELAY_SECONDS(Seconds) MicroSecondDelay ((Microseconds) * 1000000)
I'm less concerned about those, but it could make sense for
completeness.
> Do you think it would improve the maintenance of the code if macros
> like these were used consistently?
It would certainly be good to reduce duplication, and consistency
would help with the readability of the code. (Which is good for
reviewing.)
Regards,
Leif
next prev parent reply other threads:[~2016-09-15 10:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 1:37 [patch] MdeModulePkg/Xhci: add 1ms delay before access MMIO reg during reset Feng Tian
2016-09-14 2:58 ` Zeng, Star
2016-09-14 2:59 ` Tian, Feng
2016-09-14 13:08 ` Leif Lindholm
2016-09-14 17:14 ` Kinney, Michael D
2016-09-14 17:37 ` Andrew Fish
2016-09-14 18:07 ` Kinney, Michael D
2016-09-15 10:19 ` Leif Lindholm [this message]
2016-09-20 2:01 ` Tian, Feng
2016-09-20 1:39 ` Tian, Feng
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=20160915101958.GG16080@bivouac.eciton.net \
--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