Hi Joanna,

The use case right now is to identify and log the firmware version. Eventually, this information will be used to ensure that the platform is using a feature/errata/bug fix.

-Varun

From: Joanna Farley <Joanna.Farley@arm.com>
Sent: Wednesday, 11 January 2023 3:03 PM
To: Varun Wadekar <vwadekar@nvidia.com>; Sandrine Bailleux <Sandrine.Bailleux@arm.com>
Cc: tfa-lts@lists.trustedfirmware.org; tf-a@lists.trustedfirmware.org
Subject: Re: [TF-A] Re: Query BL31 version from NWd

External email: Use caution opening links or attachments

Hi Varun,

Can you allude to the use case here you need this information for? Just so we can flush out any other information needed.  With the reference of LTS I was thinking the platform was trying to find out if a security fix is supported or a hardware erratum mitigation was available. Is that the type of use case we are talking about here? Anything else?

Thanks

Joanna

From: Varun Wadekar via TF-A <tf-a@lists.trustedfirmware.org>
Date: Wednesday, 11 January 2023 at 14:33
To: Sandrine Bailleux <Sandrine.Bailleux@arm.com>
Cc: tfa-lts@lists.trustedfirmware.org <tfa-lts@lists.trustedfirmware.org>, tf-a@lists.trustedfirmware.org <tf-a@lists.trustedfirmware.org>
Subject: [TF-A] Re: Query BL31 version from NWd

Hi Sandrine,

This is a good start. Can you help define the SMC FID and the return value for this use case?

Please consider the requirement to return a 3-digit value (x.y.z) to support LTS versions too.

Thanks.

-----Original Message-----
From: Sandrine Bailleux <sandrine.bailleux@arm.com>
Sent: Wednesday, 11 January 2023 8:50 AM
To: Varun Wadekar <vwadekar@nvidia.com>
Cc: tfa-lts@lists.trustedfirmware.org; tf-a@lists.trustedfirmware.org
Subject: Re: [TF-A] Query BL31 version from NWd

External email: Use caution opening links or attachments


Hello Varun,

Happy New Year to you too!

This sounds like a reasonable idea to me.

JFYI we introduced an interface to query TF-A semantic version in the following patch:


https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.trustedfirmware.org%2FTF-A%2Ftrusted-firmware-a.git%2Fcommit%2F%3Fid%3Ddddf4283b043ad0a81d27bd5bb2f0c647c511e11&data=05%7C01%7Cvwadekar%40nvidia.com%7Cc58d847c8e5645c4569a08daf3b0e57f%7C43083d15727340c1b7db39efd9ccc17a%7C0%7C0%7C638090238346510461%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=4q%2BhHaTtpL0AMGzc78UfTnygDnr0Jbj0sHn519uJd84%3D&reserved=0

This is available for any BLx image, not just BL31. At the time, it was just meant to be used internally within TF-A so it's missing the SMC handler to return this information to normal world.

Best regards,
Sandrine

On 1/10/23 23:42, Varun Wadekar via TF-A wrote:
> Hi,
>
> Happy new year!
>
> For NVIDIA Tegra platforms, we need the capability to query the BL31
> version (e.g. 2.7, 2.8, 2.8.x) from the NWd at runtime. I could not
> find an FID that returns this value.
>
> I propose we introduce a new runtime service in bl31 that returns the
> version_string to the NWd to support this requirement.
>
> Thoughts?
>
> -Varun
>
>
--
TF-A mailing list -- tf-a@lists.trustedfirmware.org
To unsubscribe send an email to tf-a-leave@lists.trustedfirmware.org