platforms: Add persist partition for QTEE secure storage on Talos

[jiaxli-QC]

Add a 30 MB persist partition on protected RW LUN5 for both the IQ-615-EVK and QCS615-RIDE boards to provide a dedicated file storage area for QTEE.

Qualcomm's QTEE leverages a GPFS (Generic Persistent File System) interface library to enable encrypted file storage and secure data retrieval. The persist partition and QTEE operate independently, so no specific QTEE version dependency is introduced.

LUN5 is already provisioned on Talos boards; no reprovisioning is required. For partition layout reference, see: https://artifacts.codelinaro.org/ui/native/codelinaro-le/Qualcomm_Linux/QCS615/

Changes:

• IQ-615-EVK: add 30 MB (30720 KB) persist partition on LUN5
• QCS615-RIDE: add 30 MB (30720 KB) persist partition on LUN5

The persist partition was discussed in Issue87 , and approved add persist partition as LUN5 for UFS device.

[lumag]

Is LUN5 a part of the default provisioning or do users need to reprovision the UFS?

[ricardosalveti]

I believe this will require users to reprovision the UFS.

[jiaxli-QC]

Is LUN5 a part of the default provisioning or do users need to reprovision the UFS?

LUN5 should be a partition defined and managed by Qualcomm. We aim to support persistent partitioning on Qualcomm's platform for storing encrypted security files.
Is there any issue with creating LUN5? This approach has also been used on qcs6490 and qcs9100.

[lumag]

Is LUN5 a part of the default provisioning or do users need to reprovision the UFS?

LUN5 should be a partition defined and managed by Qualcomm. We aim to support persistent partitioning on Qualcomm's platform for storing encrypted security files. Is there any issue with creating LUN5? This approach has also been used on qcs6490 and qcs9100.

You didn't answer the question, did you?

[harshaldev27]

@lumag and @ricardosalveti are correct. This didn't come up earlier in our discussion but a reprovisioning would definitely be required with a new LUN 5. Should we go ahead and work with storage folks to ask for this provisioning file here? I can see that the obvious impact will be that any customers which have started using Talos and refuse to reprovision will not be able to get any of our security features enabled. I'm wondering if defining the persist partition within LUN4 itself makes sense considering this scenario.

[lumag]

@harshaldev27 if we have enough space in existing LUN, from my opinion, it would be preferable to use it instead of forcing the reprovisioning (otherwise we'd need to document it here, in the meta-qcom, etc.).

[harshaldev27]

Hi @ricardosalveti, @lumag. I had a chat with storage folks and also checked the provisioning files for UFS for Talos. It appears that LUN5 is already available in the provisioning files with a size of 128 MB. So I think we should be good with this PR where @jiaxli-QC is defining partition in LUN5. I am waiting for him to validate this on target, he is having trouble getting his hands on a UFS device, so let's see.

[harshaldev27]

@shoudil can you help review these changes as well?

[jiaxli-QC]

Hi @ricardosalveti, @lumag. I had a chat with storage folks and also checked the provisioning files for UFS for Talos. It appears that LUN5 is already available in the provisioning files with a size of 128 MB. So I think we should be good with this PR where @jiaxli-QC is defining partition in LUN5. I am waiting for him to validate this on target, he is having trouble getting his hands on a UFS device, so let's see.

Hi @lumag , @harshaldev27 , I have updated the persist partition change for qcs615 platfrom, and successfully validated it on the device..

[harshaldev27]

I can see that the provision_default.xml available publicly here has the LUN5 defined for size 128 MB:
https://artifacts.codelinaro.org/ui/native/codelinaro-le/Qualcomm_Linux/QCS615/

<ufs LUNum="5" bLUEnable="1" bBootLunID="0" size_in_kb="131072"   bDataReliability="0" bLUWriteProtect="0" bMemoryType="0" bLogicalBlockSize="0x0c" bProvisioningType="2" wContextCapabilities="0" desc="LU 5 - Protected Read-write LUN-512MB" />

Thanks @shoudil for helping to confirm this.

[lumag]

PLease write commit message describing the reasons for the change rather than a bulleted summary of the patch contents. Mention that reprovisioning is not required.

[jiaxli-QC]

PLease write commit message describing the reasons for the change rather than a bulleted summary of the patch contents. Mention that reprovisioning is not required.

Updated. Many thanks for your support.

[lumag]

Changes:

Drop the section. Also please report it to your AI tool, if you are using anything, to stop inserting such summarys.

[ricardosalveti]

Please split this into 2 different commits.