Convert Atmel AES, TDES and SHA documentation to yaml format. There is one binding defined per file. Keeping all bindings under the same yaml does not make sense, as these are individual IPs. With the conversion the clock and clock-names properties are made mandatory, to reflect how the drivers treat them: when these properties are not provided, the drivers return error. v2: - use generic "crypto" node name - drop redundant status = "okay" - it's the default state anyway - introduce empty line for readability - be specific and rename the bindings to let room for future possible lines of architectures. Tudor Ambarus (3): dt-bindings: crypto: Convert Atmel AES to yaml dt-bindings: crypto: Convert Atmel TDES to yaml dt-bindings: crypto: Convert Atmel SHA to yaml .../crypto/atmel,at91sam9g46-aes.yaml | 65 ++++++++++++++++++ .../crypto/atmel,at91sam9g46-sha.yaml | 59 ++++++++++++++++ .../crypto/atmel,at91sam9g46-tdes.yaml | 63 +++++++++++++++++ .../bindings/crypto/atmel-crypto.txt | 68 ------------------- 4 files changed, 187 insertions(+), 68 deletions(-) create mode 100644 Documentation/devicetree/bindings/crypto/atmel,at91sam9g46-aes.yaml create mode 100644 Documentation/devicetree/bindings/crypto/atmel,at91sam9g46-sha.yaml create mode 100644 Documentation/devicetree/bindings/crypto/atmel,at91sam9g46-tdes.yaml delete mode 100644 Documentation/devicetree/bindings/crypto/atmel-crypto.txt -- 2.25.1
