Hi Andrej,

Thanks for your quick reply!

As some default symbols are named freely (such as ARM_LIB_STACK*, SRAM_WATERMARK), partially assigned prefixes could not make the whole file neat.

If TFM_ prefix is regarded as a good practice - to tell these components are TFM specific, it is okay to keep this one, but at least other customized prefixes like ER_* should be cleaned up -- multiple prefixes leads to no direction.

Thanks,

Xinyu

From: Andrej Butok <andrey.butok@nxp.com>
Sent: Thursday, June 24, 2021 6:15 PM
To: Xinyu Zhang <Xinyu.Zhang@arm.com>
Cc: tf-m@lists.trustedfirmware.org
Subject: RE: [TF-M] Remove Customized Region Name Prefix in Linker Scripts

This is the “good practice” to add prefixes to global names.

From: TF-M <tf-m-bounces@lists.trustedfirmware.org> On Behalf Of Xinyu Zhang via TF-M
Sent: Thursday, June 24, 2021 12:00 PM
To: tf-m@lists.trustedfirmware.org
Cc: nd <nd@arm.com>
Subject: [TF-M] Remove Customized Region Name Prefix in Linker Scripts

Hi,

The existing linker definitions abuse prefixes such as ER_ and TFM_. Some names do not have a clear scope, which reduces the readability.

Here are some patches to address the problem:

• Patch 10383: TFM_UNPRIV_CODE  -->  UNPRIV_CODE
• Patch 10384: TFM_SP_LOAD_LIST  -->  SP_LOAD_LIST
• Patch 10385: TFM_SECURE_*  -->  SECURE_*

Please help to put comments and inform us if your platforms couple tightly with the symbols defined in LD.

Thanks,

Xinyu