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.
, but this arch has 32 bit "fields". Should I just stick
with 8 bit "fields" and have 4 times as many? Or have I missed the point of
"fields"?
Thank you!
>-Original Message-
>From: Tim Hardisty
>Sent: Tuesday, April 25, 2023 7:33 PM
>To: dev@nut
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
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
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 the relatively straightforward management of
