RE: [PATCH v4 01/19] dt-bindings: crypto: add Rambus CryptoManager Hub

On Thu, Aug 27, 2026 at 06:14:21PM +0100, Conor Dooley wrote:
> With the correct syntax, which I think the sifive example I copied from
> doesn't have, but
> Documentation/devicetree/bindings/crypto/inside-secure,safexcel-eip93.yaml
> does, fake compatibles won't be permitted (and we would probably object
> to seeing them too). What we want is the binding to force people to use
> a soc-specific one to pass validation. Unfortunately this does mean you
> can't have an example because it won't pass the validation, which is
> annoying!

Thanks, I'll follow the eip93 model. For v5 the compatible becomes:

    compatible:
      items:
        - not: {}
          description: SoC-specific compatible, e.g. vendor,soc-cmh
        - const: rambus,cmh-v1030

and grows a oneOf branch for the concrete "vendor,soc-cmh" once the first
integrating platform is upstreamed. I'll drop the examples block for now,
as you say.

> > So I'd keep clocks (and reset-gpios) optional.  I can add a one-line,
> > hardware-framed note to the description if you'd like that rationale on
> > record.
>
> Please do, yeah.

Will do; I'll add to the description:

    Clock and reset are owned by the CMH management host; a node
    describing a non-management host has no clock or reset provider of its
    own, so clocks and reset-gpios are optional.

Thanks,
Alex

_______________________________________________
linux-riscv mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-riscv