Received: by 2002:a05:6a10:1a4d:0:0:0:0 with SMTP id nk13csp1828553pxb; Wed, 9 Feb 2022 05:28:32 -0800 (PST) X-Google-Smtp-Source: ABdhPJwwuIZxsbbPfhUh4VwV7YOgXUMED5CjzCplVZ3nW7+FdXFisOOUb8tH4M/zT/dypR4KdnjR X-Received: by 2002:a17:906:794c:: with SMTP id l12mr2087909ejo.116.1644413311895; Wed, 09 Feb 2022 05:28:31 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1644413311; cv=none; d=google.com; s=arc-20160816; b=Hna+l+Tt2Ov4Uz/4BxwWiU6sZd/IkZ2So9y5ljARM7BLD/cCjOWjnai6CUgOXTiV5K AJABoQzLX7s3hnUaCv8kUWDicZne3QycO+OzVrI2Kcu52+pPXHJRNwFzW2GGaqzH4Lt9 1tj6HJaz2ld2WTvMDvuTKSF6LkACW7uXtR0bb3uCXxfLWWAfvBIjciR+JJtlcCNo4W9j a7reTaGgOUGV2DKW0GNRu9kR76vjmTClKPAdLygkhZPIQ82vzMsIr9DZtSp8pZR/k3JW M4YNODmZ+lolISIqvrSmfMFy0IBw4+t6dCuC1UqOzeQtVl09zyBZrzXOKh4MpREHT8Nb BsRw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from; bh=SDOa1OXASuBWQlpkG37XFJUeX+/6NIZleooTtRkH2A8=; b=AjeTSBZgJoVBLHVbqFGD9EkY4cDwBbuy9yU5id0oc82sDveYDnHAJQwWnTupdOlVvh S4lR6sQj+FeCHWwG5TYj63coEFbuoKLpExZ4Y/w7/bz63IyWlpXioteO5d+deO/FVZ8R 7OjYdrpc41dryVGyANulRX209lr3zYdnZv0qMSa0dczUZ0TV84UGjnUgipn3UbadzVPl vlNmyHA2qvijku9fOucyHVTFa5BIq+kH8pVyt2ijOP9zkFEKGcmofTqO0Bb8RA1nxRzj g0rM2Azsh/+hrRp1S01Fcc5zYhi69TDQh0Kb7WNR6l/1ChDmFE10NSyD1Nq73vrwBuUj uJDw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id gb7si4719006ejc.722.2022.02.09.05.28.06; Wed, 09 Feb 2022 05:28:31 -0800 (PST) Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233692AbiBIMwu (ORCPT + 99 others); Wed, 9 Feb 2022 07:52:50 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56954 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229922AbiBIMwt (ORCPT ); Wed, 9 Feb 2022 07:52:49 -0500 Received: from gloria.sntech.de (gloria.sntech.de [185.11.138.130]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 920D5C0613CA; Wed, 9 Feb 2022 04:52:51 -0800 (PST) Received: from ip5b412258.dynamic.kabel-deutschland.de ([91.65.34.88] helo=diego.localnet) by gloria.sntech.de with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nHmSj-0001ci-RZ; Wed, 09 Feb 2022 13:52:45 +0100 From: Heiko =?ISO-8859-1?Q?St=FCbner?= To: davem@davemloft.net, herbert@gondor.apana.org.au, krzysztof.kozlowski@canonical.com, robh+dt@kernel.org, Corentin Labbe Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org, Corentin Labbe Subject: Re: [PATCH] dt-bindings: crypto: convert rockchip-crypto to yaml Date: Wed, 09 Feb 2022 13:52:45 +0100 Message-ID: <2571349.qrhAyUUNuM@diego> In-Reply-To: <20220209124725.2080986-1-clabbe@baylibre.com> References: <20220209124725.2080986-1-clabbe@baylibre.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_NONE, T_SCC_BODY_TEXT_LINE,T_SPF_HELO_TEMPERROR autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org Am Mittwoch, 9. Februar 2022, 13:47:25 CET schrieb Corentin Labbe: > Convert rockchip-crypto to yaml. > > Signed-off-by: Corentin Labbe > --- > .../bindings/crypto/rockchip-crypto.txt | 28 -------- > .../bindings/crypto/rockchip-crypto.yaml | 64 +++++++++++++++++++ > 2 files changed, 64 insertions(+), 28 deletions(-) > delete mode 100644 Documentation/devicetree/bindings/crypto/rockchip-crypto.txt > create mode 100644 Documentation/devicetree/bindings/crypto/rockchip-crypto.yaml > > diff --git a/Documentation/devicetree/bindings/crypto/rockchip-crypto.txt b/Documentation/devicetree/bindings/crypto/rockchip-crypto.txt > deleted file mode 100644 > index 5e2ba385b8c9..000000000000 > --- a/Documentation/devicetree/bindings/crypto/rockchip-crypto.txt > +++ /dev/null > @@ -1,28 +0,0 @@ > -Rockchip Electronics And Security Accelerator > - > -Required properties: > -- compatible: Should be "rockchip,rk3288-crypto" > -- reg: Base physical address of the engine and length of memory mapped > - region > -- interrupts: Interrupt number > -- clocks: Reference to the clocks about crypto > -- clock-names: "aclk" used to clock data > - "hclk" used to clock data > - "sclk" used to clock crypto accelerator > - "apb_pclk" used to clock dma > -- resets: Must contain an entry for each entry in reset-names. > - See ../reset/reset.txt for details. > -- reset-names: Must include the name "crypto-rst". > - > -Examples: > - > - crypto: cypto-controller@ff8a0000 { > - compatible = "rockchip,rk3288-crypto"; > - reg = <0xff8a0000 0x4000>; > - interrupts = ; > - clocks = <&cru ACLK_CRYPTO>, <&cru HCLK_CRYPTO>, > - <&cru SCLK_CRYPTO>, <&cru ACLK_DMAC1>; > - clock-names = "aclk", "hclk", "sclk", "apb_pclk"; > - resets = <&cru SRST_CRYPTO>; > - reset-names = "crypto-rst"; > - }; > diff --git a/Documentation/devicetree/bindings/crypto/rockchip-crypto.yaml b/Documentation/devicetree/bindings/crypto/rockchip-crypto.yaml > new file mode 100644 > index 000000000000..392d89055398 > --- /dev/null > +++ b/Documentation/devicetree/bindings/crypto/rockchip-crypto.yaml > @@ -0,0 +1,64 @@ > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/crypto/rockchip-crypto.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: Rockchip Electronics And Security Accelerator > + > +maintainers: > + - Heiko Stuebner > + > +properties: > + compatible: > + const: rockchip,rk3288-crypto > + > + reg: > + maxItems: 1 > + > + interrupts: > + maxItems: 1 > + > + clocks: > + items: > + - description: clock data > + - description: clock data > + - description: clock crypto accelerator > + - description: clock dma > + > + clock-names: > + items: > + - const: aclk > + - const: hclk > + - const: sclk > + - const: apb_pclk > + > + resets: > + minItems: 1 > + > + reset-names: > + const: crypto-rst > + > +required: > + - compatible > + - reg > + - interrupts > + - clocks > + - clock-names > + - resets > + - reset-names > + > +additionalProperties: false > + > +examples: > + - | Binding itself looks good. But the constants below will probably trigger a compiler-error and therefore Rob's bot. You will need something like #include #include here. A "make ..... dt_binding_check" should show the issue and also it going away with the right includes ;-) Heiko > + crypto: crypto@ff8a0000 { > + compatible = "rockchip,rk3288-crypto"; > + reg = <0xff8a0000 0x4000>; > + interrupts = ; > + clocks = <&cru ACLK_CRYPTO>, <&cru HCLK_CRYPTO>, > + <&cru SCLK_CRYPTO>, <&cru ACLK_DMAC1>; > + clock-names = "aclk", "hclk", "sclk", "apb_pclk"; > + resets = <&cru SRST_CRYPTO>; > + reset-names = "crypto-rst"; > + }; >