Hi Reinhard,

We had a discussion in the TSC last week about coding standard. The general consensus was that there multiple possible standards that we can aim for but we need to decide our goal in order to decide the coding standard for the project. I believe Mark G is planning to look at the work ongoing in Zephyr project and provide some details to help us take the discussion forward for TF.org.

The input below is helpful, we should take this into the unified effort for coding standard and tooling to enforce it.

Thanks, Abhishek

-----Original Message----- From: TF-M tf-m-bounces@lists.trustedfirmware.org On Behalf Of Reinhard Keil via TF-M Sent: 22 November 2019 07:59 To: tf-m@lists.trustedfirmware.org Subject: Re: [TF-M] Coding guideline

Hi all,

I suggest to use industry standard coding rules. Here are the CMSIS coding rules:

https://arm-software.github.io/CMSIS_5/General/html/index.html#CodingRules

Simple, as we use MISRA.

MISRA is an accepted set of coding standards, why invent something new?

For wide acceptance of TF-M in automotive/industrial projects, you should publish also deviations like here: https://arm-software.github.io/CMSIS_5/RTOS2/html/misraCompliance5.html

Reinhard

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.