public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Marcin Juszkiewicz" <marcin.juszkiewicz@linaro.org>
To: Leif Lindholm <quic_llindhol@quicinc.com>, devel@edk2.groups.io
Cc: Ard Biesheuvel <ardb+tianocore@kernel.org>,
	Graeme Gregory <graeme@xora.org.uk>
Subject: Re: [edk2-devel] [PATCH edk2-platforms 1/1] SbsaQemu: get cpu information from TF-A
Date: Mon, 15 Jan 2024 19:37:05 +0100	[thread overview]
Message-ID: <f1497109-6ad8-4159-94de-883f82acba77@linaro.org> (raw)
In-Reply-To: <a4d092bd-40d7-4bd3-9088-2a4e4d74ed04@quicinc.com>

W dniu 15.01.2024 o 19:02, Leif Lindholm pisze:
>> As part of removing DeviceTree use we moved cpu related parts to TF-A.
>> On EDK2 side we get values via SMC calls during platform initialization.
> 
> Could you split this into three patches?:
> - Adding new Library (Library name should have a Lib suffix.)
> - Using this library to check whether SMCs are supported, falling back
>    to FdtHelperLib if not.
> - Dropping FdtHelperLib and the fallback paths.
> 
> ?

Will do. Thanks for suggestion.


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



      reply	other threads:[~2024-01-16  5:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-15 15:11 [edk2-devel] [PATCH edk2-platforms 0/1] get rid of DeviceTree from SbsaQemu Marcin Juszkiewicz
2024-01-15 15:11 ` [edk2-devel] [PATCH edk2-platforms 1/1] SbsaQemu: get cpu information from TF-A Marcin Juszkiewicz
2024-01-15 18:02   ` Leif Lindholm
2024-01-15 18:37     ` Marcin Juszkiewicz [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=f1497109-6ad8-4159-94de-883f82acba77@linaro.org \
    --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