Re: [PATCH v3 01/11] dt-bindings: nvmem: imx-ocotp: Add support for secure-enclave

On Thu, Jul 23, 2026 at 09:27:23AM +0200, Frieder Schrempf wrote:
> From: Frieder Schrempf <[email protected]>
> 
> The driver currently uses the limited MMIO (FSB) interface to access the
> OTPs. The intention is to support the firmware interface alongside the
> MMIO interface so the driver can pick the interface that is available
> (firmware might not be loaded) and fallback to MMIO.
> 
> Some SoCs like the i.MX9 family allow full access to the fuses only
> through the secure enclave firmware API. Add a property to reference
> the secure enclave node and let the driver use the API.
> 
> Signed-off-by: Frieder Schrempf <[email protected]>
> ---
>  Documentation/devicetree/bindings/nvmem/imx-ocotp.yaml | 14 ++++++++++++++
>  1 file changed, 14 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/nvmem/imx-ocotp.yaml b/Documentation/devicetree/bindings/nvmem/imx-ocotp.yaml
> index a8076d0e2737..38fe451f808f 100644
> --- a/Documentation/devicetree/bindings/nvmem/imx-ocotp.yaml
> +++ b/Documentation/devicetree/bindings/nvmem/imx-ocotp.yaml
> @@ -20,6 +20,16 @@ description: |
>  allOf:
>    - $ref: nvmem.yaml#
>    - $ref: nvmem-deprecated-cells.yaml#
> +  - if:
> +      not:
> +        properties:
> +          compatible:
> +            contains:
> +              enum:
> +                - fsl,imx93-ocotp
> +    then:
> +      properties:
> +        secure-enclave: false

Please move the entire allOf in such case after "required:" block (just
like in example-schema).

>  
>  properties:
>    compatible:
> @@ -56,6 +66,10 @@ properties:
>    clocks:
>      maxItems: 1
>  
> +  secure-enclave:
> +    $ref: /schemas/types.yaml#/definitions/phandle
> +    description: A phandle to the secure enclave node

"... for full access to the fuses through firmware API."


Reviewed-by: Krzysztof Kozlowski <[email protected]>

Best regards,
Krzysztof