lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b5696361-3b62-deb4-61d6-a9b64bb6f9c3@seznam.cz>
Date:   Tue, 21 Jan 2020 10:11:50 +0100
From:   Michal Simek <monstr@...nam.cz>
To:     Kalyani Akula <kalyani.akula@...inx.com>,
        linux-crypto@...r.kernel.org, linux-kernel@...r.kernel.org
Cc:     git <git@...inx.com>, Harsh Jain <harshj@...inx.com>,
        Sarat Chand Savitala <saratcha@...inx.com>,
        Mohan <mohand@...inx.com>, Kalyani Akul <kalyania@...inx.com>
Subject: Re: [PATCH V4 1/4] dt-bindings: crypto: Add bindings for ZynqMP AES
 driver

On 20. 11. 19 8:43, Kalyani Akula wrote:
> Add documentation to describe Xilinx ZynqMP AES driver bindings.
> 
> Signed-off-by: Kalyani Akula <kalyani.akula@...inx.com>
> ---
>  Documentation/devicetree/bindings/crypto/xlnx,zynqmp-aes.txt | 12 ++++++++++++
>  1 file changed, 12 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/crypto/xlnx,zynqmp-aes.txt
> 
> diff --git a/Documentation/devicetree/bindings/crypto/xlnx,zynqmp-aes.txt b/Documentation/devicetree/bindings/crypto/xlnx,zynqmp-aes.txt
> new file mode 100644
> index 0000000..226bfb9
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/crypto/xlnx,zynqmp-aes.txt
> @@ -0,0 +1,12 @@
> +Xilinx ZynqMP AES hw acceleration support
> +
> +The ZynqMP PS-AES hw accelerator is used to encrypt/decrypt
> +the given user data.
> +
> +Required properties:
> +- compatible: should contain "xlnx,zynqmp-aes"
> +
> +Example:
> +	zynqmp_aes {
> +		compatible = "xlnx,zynqmp-aes";
> +	};
> 

Ok. This should be converted to yaml and it should be placed to
zynqmp_firmware node as is done for clk, pcap, nvmem, power, reset and
genpd.

Thanks,
Michal

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ