Hi Joanna,
Apologies for the delay. I don't know if it's ADP/ELP licence, however this is the MIDR: 0x410fd440. Do you think that will be okay?
Using the above headerfiles as a guidance in a suitably named header file
containing suitable contents something might be upstreamable?
Thank you for the pointers to the header files. I'll follow up with CLs soon.
Best regards, Okash
On Mon, Apr 11, 2022 at 4:50 PM Joanna Farley Joanna.Farley@arm.com wrote:
Hi Okash,
The Cortex-X1 was never a generic licensed CPU with a common MIDR IIUC and was licenced under terms that each partner licensing it had their own MIDR as part of the licensing program (ADP/ELP) and at the time X1 was released TF-A was not supporting such CPU’s in the upstream.
However, with https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git/tree/include/lib... we have started supporting in the upstream an ELP licensed CPU’s with their own MIDR such as https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git/tree/include/lib...
So I guess if Google have a ADP/ELP licence and want to upstream support with their MIDR?
Using the above headerfiles as a guidance in a suitably named header file containing suitable contents something might be upstreamable?
Joanna
*From: *Okash Khawaja via TF-A tf-a@lists.trustedfirmware.org *Date: *Monday, 11 April 2022 at 12:14 *To: *tf-a@lists.trustedfirmware.org tf-a@lists.trustedfirmware.org *Subject: *[TF-A] Cortex-X1 support
Hello,
Are there any immediate plans to add support for Cortex-X1 in TF-A? If not then I'll be happy to submit CL for it. For start, it will cover a subset of errata workarounds. Then people can add more as needed. Let me know what you think.
Thanks, Okash -- TF-A mailing list -- tf-a@lists.trustedfirmware.org To unsubscribe send an email to tf-a-leave@lists.trustedfirmware.org