Messages in this thread | | | Date | Mon, 22 Jul 2019 11:13:20 -0600 | From | Rob Herring <> | Subject | Re: [PATCH v4 2/3] dt-bindings: rng: add bindings for MediaTek ARMv8 SoCs |
| |
On Mon, Jun 24, 2019 at 03:24:11PM +0800, Neal Liu wrote: > Document the binding used by the MediaTek ARMv8 SoCs random > number generator with TrustZone enabled. > > Signed-off-by: Neal Liu <neal.liu@mediatek.com> > --- > .../devicetree/bindings/rng/mtk-sec-rng.txt | 10 ++++++++++ > 1 file changed, 10 insertions(+) > create mode 100644 Documentation/devicetree/bindings/rng/mtk-sec-rng.txt > > diff --git a/Documentation/devicetree/bindings/rng/mtk-sec-rng.txt b/Documentation/devicetree/bindings/rng/mtk-sec-rng.txt > new file mode 100644 > index 0000000..c04ce15 > --- /dev/null > +++ b/Documentation/devicetree/bindings/rng/mtk-sec-rng.txt > @@ -0,0 +1,10 @@ > +MediaTek random number generator with TrustZone enabled > + > +Required properties: > +- compatible : Should be "mediatek,mtk-sec-rng"
What's the interface to access this?
A node with a 'compatible' and nothing else is a sign of something that a parent device should instantiate and doesn't need to be in DT. IOW, what do complete bindings for firmware functions look like?
> + > +Example: > + > +hwrng: hwrng { > + compatible = "mediatek,mtk-sec-rng"; > +} > -- > 1.7.9.5 >
| |