public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "MrChromebox" <matt.devillier@gmail.com>
To: Pedro Falcato <pedro.falcato@gmail.com>
Cc: devel@edk2.groups.io, Zhiguang Liu <zhiguang.liu@intel.com>,
	 "Ni, Ray" <ray.ni@intel.com>,
	gua.guo@intel.com
Subject: Re: [edk2-devel] [PATCH 1/3] MdeModulePkg: Add ClockRate field to SerialPortInfo
Date: Wed, 11 Oct 2023 16:21:52 -0700	[thread overview]
Message-ID: <CAFTm+6DWZue6sPez8=DdipzcZBdgpBRON1gc98+K5FxUh=toHQ@mail.gmail.com> (raw)
In-Reply-To: <CAKbZUD3r_j4tM=XgtY51W0cemDTMgjK7nwkeE=LNYGdSocDwtA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 4041 bytes --]

hi Pedro,

thanks for the input, I will adjust the patch to append for v2

On Wed, Oct 11, 2023 at 2:16 PM Pedro Falcato <pedro.falcato@gmail.com>
wrote:

> On Mon, Oct 9, 2023 at 4:54 PM Matt DeVillier <matt.devillier@gmail.com>
> wrote:
> >
> > On Thu, Oct 5, 2023 at 12:45 PM Pedro Falcato <pedro.falcato@gmail.com>
> wrote:
> >>
> >> On Wed, Oct 4, 2023 at 9:01 PM MrChromebox <matt.devillier@gmail.com>
> wrote:
> >> >
> >> > Add the ClockRate field to the UNIVERSAL_PAYLOAD_SERIAL_PORT_INFO
> >> > struct, so that the field can be used by UefiPayloadPkg to properly
> >> > set up the serial port on boards using a non-standard clock rate.
> >> >
> >> > Signed-off-by: Matt DeVillier <matt.devillier@gmail.com>
> >> > Change-Id: I9bcaf03ab63f6a45d2cf25a580f7a2eba388cbbd
> >>
> >> Series-generic-feedback: Remove Change-Id lines and CC the proper
> >> maintainers for each patch
> >
> >
> > ack
> >
> >>
> >> > ---
> >> >  MdeModulePkg/Include/UniversalPayload/SerialPortInfo.h | 1 +
> >> >  1 file changed, 1 insertion(+)
> >> >
> >> > diff --git a/MdeModulePkg/Include/UniversalPayload/SerialPortInfo.h
> b/MdeModulePkg/Include/UniversalPayload/SerialPortInfo.h
> >> > index 3c4459e2c0..e3c9f93654 100644
> >> > --- a/MdeModulePkg/Include/UniversalPayload/SerialPortInfo.h
> >> > +++ b/MdeModulePkg/Include/UniversalPayload/SerialPortInfo.h
> >> > @@ -19,6 +19,7 @@ typedef struct {
> >> >    BOOLEAN                             UseMmio;
> >> >    UINT8                               RegisterStride;
> >> >    UINT32                              BaudRate;
> >> > +  UINT32                              ClockRate;
> >>
> >> I don't think you can do this? UNIVERSAL_PAYLOAD_SERIAL_PORT_INFO is
> >> part of a spec (
> https://universalscalablefirmware.github.io/documentation/2_universal_payload.html
> )
> >> and it doesn't even seem to be versioned, so you'd just break ABI. Am
> >> I missing something?
> >
> >
> > The USF spec says that it is currently at version 0.7 and under
> development / not final. I don't see why adding a field to a hob is
> problematic provided it's properly documented. The alternatives are some
> really hacky workarounds to pass the necessary data, or the serial port not
> working.
>
> My 2 cents, as someone that neither maintains nor works on this code:
> 1) This sounds like something that needs to be discussed with the spec
> people (good luck! lol)
> 2) Changing the structure abruptly like this seems like it would break
> many current users. HOWEVER:
> The spec (
> https://universalscalablefirmware.github.io/documentation/2_universal_payload.html#common-payload-header
> )
> says that the common header's Revision (indeed, it's versioned and I
> missed that) should be incremented if current members are renamed or
> reinterpreted, but not if you just append members. So it seems that if
> you add ClockRate like this:
>
> --- a/MdeModulePkg/Include/UniversalPayload/SerialPortInfo.h
> +++ b/MdeModulePkg/Include/UniversalPayload/SerialPortInfo.h
> @@ -19,6 +19,7 @@ typedef struct {
>    BOOLEAN                             UseMmio;
>    UINT8                               RegisterStride;
>    UINT32                              BaudRate;
>    EFI_PHYSICAL_ADDRESS                RegisterBase;
> +  UINT32                              ClockRate;
> } UNIVERSAL_PAYLOAD_SERIAL_PORT_INFO;
>
> --
>
> this should be acceptable for the spec people and
> EDK2/coreboot/SlimBootloader/etc people, given all the current
> consuming code takes the generic header's Length into account (as
> specified by the spec).
>
> --
> Pedro
>


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#109535): https://edk2.groups.io/g/devel/message/109535
Mute This Topic: https://groups.io/mt/101763374/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



[-- Attachment #2: Type: text/html, Size: 5868 bytes --]

      reply	other threads:[~2023-10-11 23:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-04 20:01 [edk2-devel] [PATCH 1/3] MdeModulePkg: Add ClockRate field to SerialPortInfo MrChromebox
2023-10-04 20:01 ` [edk2-devel] [PATCH 2/3] UefiPayloadEntry: Set serial ClockRate from parsed SerialInfo MrChromebox
2023-10-04 20:01 ` [edk2-devel] [PATCH 3/3] PlatformHookLib: Set PcdSerialClockRate using HOB data MrChromebox
2024-04-03  7:53   ` Sean Rhodes
2023-10-05 19:45 ` [edk2-devel] [PATCH 1/3] MdeModulePkg: Add ClockRate field to SerialPortInfo Pedro Falcato
2023-10-09 15:54   ` MrChromebox
2023-10-11 21:15     ` Pedro Falcato
2023-10-11 23:21       ` MrChromebox [this message]

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='CAFTm+6DWZue6sPez8=DdipzcZBdgpBRON1gc98+K5FxUh=toHQ@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