Re: SAMA5 secure fuse controller driver

2023-04-28 Thread Gregory Nutt
struct efuse_param Also .. does not follow the naming standard for structures.   The coding standard requires that all structure names end with _s so, if this is needed, it must be efuse_param_s If it is not needed, then it should be removed.

RE: SAMA5 secure fuse controller driver

2023-04-28 Thread Tim Hardisty
I am trying to make use of the template/skeleton in include/nuttx/efuse.h It defines: struct efuse_param { FAR const efuse_desc_t **field; size_t size; FAR uint8_t *data; }; With the explanation: /* The efuse_param is used by the application to inform which field(s) * will be passed to

Re: SAMA5 secure fuse controller driver

2023-04-25 Thread Tomek CEDRO
On Tue, Apr 25, 2023 at 9:17 PM Gregory Nutt wrote: > Searching for C files with "fuse" in the number under arch/, I find > drivers for the ESP32, ESP32S2, ESP32S3, ESP32C3, BL602, and RTL8720C > > Other MCUs have have fuse header files, but no C drivers. > > There are alias like OTP (i.MXRT). PI

Re: SAMA5 secure fuse controller driver

2023-04-25 Thread Gregory Nutt
On 4/25/2023 12:32 PM, Tim Hardisty wrote: The SAMA5 support has no driver for the secure fuse peripheral. Kconfig allows you to “enable” it but there’s no underlying code. Before I go ahead and create a character driver for this, is the omission for a “good” reason? The driver would handle t