public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Michael Brown" <mcb30@ipxe.org>
To: devel@edk2.groups.io, patrick.henz@hpe.com
Subject: Re: [edk2-devel] [PATCH] MdeModulePkg/XhciDxe: Use Performance Timer for XHCI Timeouts
Date: Thu, 6 Jul 2023 15:47:13 +0000	[thread overview]
Message-ID: <010201892be2d5e6-35273df4-44c0-4ead-8898-1c94cbc6713d-000000@eu-west-1.amazonses.com> (raw)
In-Reply-To: <PH0PR84MB14786A4B6A788AA05F8246B1892CA@PH0PR84MB1478.NAMPRD84.PROD.OUTLOOK.COM>

On 06/07/2023 15:19, Henz, Patrick wrote:
> I agree that XhcGetElapsedTime() would be better off in TimerLib, but I wasn't sure how the community would feel about adding to the interface.

My understanding is that the TimerLib API is not prescribed by any 
standards document, and that this change would add a new function 
without changing any existing functions and so would not break any 
existing users of TimerLib.  On that basis, I would be firmly in favour 
of extending TimerLib to include this functionality.

I will defer to actual EDK2 maintainers on this, however.  :)

Thanks,

Michael


  reply	other threads:[~2023-07-06 15:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-05 20:15 [PATCH] MdeModulePkg/XhciDxe: Use Performance Timer for XHCI Timeouts Henz, Patrick
2023-07-06 13:02 ` [edk2-devel] " Michael Brown
2023-07-06 14:19   ` Henz, Patrick
2023-07-06 15:47     ` Michael Brown [this message]
2023-07-06 18:01       ` Michael D Kinney
2023-07-31  2:57 ` Wu, Hao A
2023-08-10 22:44   ` Henz, Patrick
2023-08-11  1:43     ` Wu, Hao A
2023-10-30 20:36       ` Henz, Patrick
2023-10-31  1:41         ` Wu, Hao A
2023-10-31 12:14           ` Laszlo Ersek
2023-10-31 12:16           ` Laszlo Ersek
2023-10-31 13:38             ` Henz, Patrick

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=010201892be2d5e6-35273df4-44c0-4ead-8898-1c94cbc6713d-000000@eu-west-1.amazonses.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