Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp11406340ybi; Thu, 25 Jul 2019 15:56:30 -0700 (PDT) X-Google-Smtp-Source: APXvYqx2TYWBZV44OKauRG6t0bImdBnGb1WhHPhtjtU6ccJGcv0z6LHMr6oIEW/haz1gmSSU47aK X-Received: by 2002:a63:db45:: with SMTP id x5mr75843012pgi.293.1564095390148; Thu, 25 Jul 2019 15:56:30 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1564095390; cv=none; d=google.com; s=arc-20160816; b=wzAY17xo3/Yr6EczNxbv4Ce/o63G8yuH8yoG+bLovtKJiKtrAu0igMFVChyZSWur4+ SuX97MZn574ScVlmw1uiIUNwUPpCgkNiB2ozoGcGflJyJwNM6/3yK7KtPXrp/5k49kib kpEEO1GpmH4t/dQBczeM/8lnW4nn6brD2MxHEEkZxNjWUXS7r7lbOC/FS0brafdN+rhf 4AiyZGN0qOodUTwmxD6gjmIODyhsFYbL3EZ5JOxpZukIYzVLWh5jKuPTfJRNd0PSedaM AlWWqKYIn6jotliPgZx0WmJpA1BBBa2JqK0l+nN+83WI/IinJBBeE2FoX1ilSQGLVl25 Lo5A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=nF07bsxksmkPeqTM6qbdQ8WZoZ2mE8Eup98RTVnnfEo=; b=vOHeQ4Yl3OiVGozpoQuDLuwNxy+N7dHfWbcx1NllPKNK0aAXNelqOyQIPS0azeLBfb J/sMjfSE5JF8OrHzeIx5r1DtWN2Jr4CyarnJ0n/mnUPn9k44rqfo4qwM+5gwQF8Xnt5s rzE15wY8Q+N2Y3d6EReP0xQapv480nWYOctdRS4rDxhT/mLcjEbkK7aVtG30+wGMloCF L/xQ+byu0ag7KH4HnSxbPmIJ4/shbSOCLSgo3Wd9LkpS8huOnRnpVN5x0HqdJZbrTCmf YHwpEOlNGLOiyiA11dsE8rSaN6OumsjNjuGo/lRSpvBZ+Ch1l7gbjRd/hvF01EZ3v+nc ER9w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=Dz09u9S+; spf=pass (google.com: best guess record for domain of linux-crypto-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id u3si17151354plz.201.2019.07.25.15.56.07; Thu, 25 Jul 2019 15:56:30 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-crypto-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=Dz09u9S+; spf=pass (google.com: best guess record for domain of linux-crypto-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726829AbfGYWzo (ORCPT + 99 others); Thu, 25 Jul 2019 18:55:44 -0400 Received: from mail.kernel.org ([198.145.29.99]:58260 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726823AbfGYWzo (ORCPT ); Thu, 25 Jul 2019 18:55:44 -0400 Received: from mail-qt1-f172.google.com (mail-qt1-f172.google.com [209.85.160.172]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 6D58222C7C; Thu, 25 Jul 2019 22:55:42 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1564095342; bh=g812QekVhk9YTdEBM9x7cM1JCaC9kZOURpxH8pDFoBY=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=Dz09u9S+Y3r70TocpuCA7IhoTLlYKdq7e+lwmbq167Zr4gqovWvCkIFvioJzQc30E UExAFN0EUnJRkGN7juvvECfcyT/2dxBkDeevZjvKHHIjF+P3AGjXUkTgj812rRiWOK Eqxe4SYbimo13thxamdtxgOCzguesjyhhx+fJq8w= Received: by mail-qt1-f172.google.com with SMTP id h18so50763315qtm.9; Thu, 25 Jul 2019 15:55:42 -0700 (PDT) X-Gm-Message-State: APjAAAULM5dbKVfmFz8HHWJU32uUu7JoGoERmWGE3E4mjiQffKlxmz1X 5akBSq8CsoxPFEkfIJGKaZiV0Kl2rKw+f0Dt9w== X-Received: by 2002:a0c:b786:: with SMTP id l6mr65611308qve.148.1564095341588; Thu, 25 Jul 2019 15:55:41 -0700 (PDT) MIME-Version: 1.0 References: <1564083776-20540-1-git-send-email-clabbe@baylibre.com> <1564083776-20540-2-git-send-email-clabbe@baylibre.com> In-Reply-To: <1564083776-20540-2-git-send-email-clabbe@baylibre.com> From: Rob Herring Date: Thu, 25 Jul 2019 16:55:30 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH 1/4] dt-bindings: crypto: Add DT bindings documentation for amlogic-crypto To: Corentin Labbe Cc: David Miller , Herbert Xu , Kevin Hilman , Mark Rutland , devicetree@vger.kernel.org, linux-amlogic@lists.infradead.org, "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" , "open list:HARDWARE RANDOM NUMBER GENERATOR CORE" , "linux-kernel@vger.kernel.org" , baylibre-upstreaming@groups.io Content-Type: text/plain; charset="UTF-8" Sender: linux-crypto-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org On Thu, Jul 25, 2019 at 1:43 PM Corentin Labbe wrote: > > This patch adds documentation for Device-Tree bindings for the > Amlogic GXL cryptographic offloader driver. > > Signed-off-by: Corentin Labbe > --- > .../bindings/crypto/amlogic-gxl-crypto.yaml | 45 +++++++++++++++++++ Follow the compatible string for the filename: amlogic,gxl-crypto.yaml > 1 file changed, 45 insertions(+) > create mode 100644 Documentation/devicetree/bindings/crypto/amlogic-gxl-crypto.yaml > > diff --git a/Documentation/devicetree/bindings/crypto/amlogic-gxl-crypto.yaml b/Documentation/devicetree/bindings/crypto/amlogic-gxl-crypto.yaml > new file mode 100644 > index 000000000000..41265e57c00b > --- /dev/null > +++ b/Documentation/devicetree/bindings/crypto/amlogic-gxl-crypto.yaml > @@ -0,0 +1,45 @@ > +# SPDX-License-Identifier: GPL-2.0 Dual (GPL-2.0 OR BSD-2-Clause) is preferred for new bindings. Not a requirement though. > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/crypto/amlogic-gxl-crypto.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: Amlogic GXL Cryptographic Offloader > + > +maintainers: > + - Corentin Labbe > + > +properties: > + compatible: > + oneOf: Don't need 'oneOf' when there is only 1. > + - const: amlogic,gxl-crypto > + > + reg: > + maxItems: 1 > + > + interrupts: > + maxItems: 1 > + > + clocks: > + maxItems: 1 > + > + clock-names: > + const: blkmv > + > +required: > + - compatible > + - reg > + - interrupts > + - clocks > + - clock-names > + > +examples: > + - | > + crypto: crypto@c883e000 { > + compatible = "amlogic,gxl-crypto"; > + reg = <0x0 0xc883e000 0x0 0x36>; This should throw errors because the default size on examples are 1 cell. But validating the examples with the schema only just landed in 5.3-rc1. > + interrupts = , > + ; This doesn't match the schema. > + clocks = <&clkc CLKID_BLKMV>; > + clock-names = "blkmv"; > + }; > -- > 2.21.0 >