Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp2059606ybt; Sun, 21 Jun 2020 07:58:58 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxiV1S+OE/iOIrQ8UUkbgMexcCkEsoVKCYRkTApSDS844zBkIVycI81nzgEHX0IWfJIErcW X-Received: by 2002:a05:6402:228a:: with SMTP id cw10mr12327433edb.147.1592751537957; Sun, 21 Jun 2020 07:58:57 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1592751537; cv=none; d=google.com; s=arc-20160816; b=fOt2TjvBYr3caDzCSsrBl7Bhm02DVtEbodjEGLoTT7/X3FxlGB5X1K89voLNxxvkKR oDKDW5FH9I+Lgo6epC6H3pAse4rGAYSnuYAQEpaeYSEZ6f5VpLxlv0Qm2JryGn92Hqqg 8IrzDAfn+f1e+zIbhUvuVMmu1BYd0nT3vZAbh0ChaWPyENJbSxrkuZ0A8LzCHWfpvq/x gWq8FGzu2OVScv6KZ0l546guzxXiiemhOgBIcUZclEtMxF2IM++m9WQc1fSaKSd29St/ c2p0dRCeNqcKTy4qdStH8x31nM2KaNflfeNkDHM1+3yV1xB416tB5AWNRQZmQ5SModQY p0XQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from; bh=+OurotLoD53uULfBJK3u3GYzX/1GpfXQGyYdhDw30c8=; b=ryjV6bcb7ewaoM3oALyHwpaIDd0uC7jEIolUlasYMD8IwuSua2mCufov3ky1x5KHp2 qjUbvEYDdq0l0L8r/evJE7w+xYESIG2J6xqKrVNGAlQrymINQibSnmk4O+icb67gDZwO LbEBLvfdYjNWrWaSujknzPwSPQSQEfeXEiWwqrEnOujJjTUlKjFlYiC2sxcgl04kKPxB qVK9KxX49/UHVBZGuchOuRZmPGOMKya06NdVol98c2CsMeN5yGO7AdcR3/XUybjuDFd6 81tbHusdG8HZb9fCIdJwitj5q5B6YeK4fQr4mFkResBPOZW6nJBxo01lIo10WWDf7w2D QtJg== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=nxp.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id l20si7671777ejr.66.2020.06.21.07.58.35; Sun, 21 Jun 2020 07:58:57 -0700 (PDT) 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=nxp.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730281AbgFUO5T (ORCPT + 99 others); Sun, 21 Jun 2020 10:57:19 -0400 Received: from inva020.nxp.com ([92.121.34.13]:53600 "EHLO inva020.nxp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730257AbgFUO5T (ORCPT ); Sun, 21 Jun 2020 10:57:19 -0400 Received: from inva020.nxp.com (localhost [127.0.0.1]) by inva020.eu-rdc02.nxp.com (Postfix) with ESMTP id BD8D21A074D; Sun, 21 Jun 2020 16:57:16 +0200 (CEST) Received: from inva024.eu-rdc02.nxp.com (inva024.eu-rdc02.nxp.com [134.27.226.22]) by inva020.eu-rdc02.nxp.com (Postfix) with ESMTP id B0BBE1A0744; Sun, 21 Jun 2020 16:57:16 +0200 (CEST) Received: from fsr-ub1864-014.ea.freescale.net (fsr-ub1864-014.ea.freescale.net [10.171.95.219]) by inva024.eu-rdc02.nxp.com (Postfix) with ESMTP id 092BF203C2; Sun, 21 Jun 2020 16:57:16 +0200 (CEST) From: =?UTF-8?q?Horia=20Geant=C4=83?= To: Rob Herring , Shawn Guo , Sascha Hauer , Matt Mackall , Herbert Xu Cc: Pengutronix Kernel Team , Fabio Estevam , NXP Linux Team , devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Arnd Bergmann , Greg Kroah-Hartman , Martin Kaiser , Franck Lenormand , Iuliana Prodan , Silvano Di Ninno , linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH v2 1/5] dt-bindings: rng: add RNGB compatibles for i.MX6 SoCs Date: Sun, 21 Jun 2020 17:56:54 +0300 Message-Id: <20200621145658.12528-2-horia.geanta@nxp.com> X-Mailer: git-send-email 2.17.1 In-Reply-To: <20200621145658.12528-1-horia.geanta@nxp.com> References: <20200621145658.12528-1-horia.geanta@nxp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Virus-Scanned: ClamAV using ClamSMTP Sender: linux-crypto-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org RNGB block is found in some i.MX6 SoCs - 6SL, 6SLL, 6ULL, 6ULZ. Add corresponding compatible strings. Note: Several NXP SoC from QorIQ family (P1010, P1023, P4080, P3041, P5020) also have a RNGB, however it's part of the CAAM (Cryptograhic Accelerator and Assurance Module) crypto accelerator. In this case, RNGB is managed in the caam driver (drivers/crypto/caam/), since it's tightly related to the caam "job ring" interface, not to mention CAAM internally relying on RNGB as source of randomness. On the other hand, the i.MX6 SoCs with RNGB have a DCP (Data Co-Processor) crypto accelerator and this block and RNGB are independent. Signed-off-by: Horia Geantă --- Documentation/devicetree/bindings/rng/imx-rng.txt | 3 +++ 1 file changed, 3 insertions(+) diff --git a/Documentation/devicetree/bindings/rng/imx-rng.txt b/Documentation/devicetree/bindings/rng/imx-rng.txt index 405c2b00ccb0..eb227db9e684 100644 --- a/Documentation/devicetree/bindings/rng/imx-rng.txt +++ b/Documentation/devicetree/bindings/rng/imx-rng.txt @@ -5,6 +5,9 @@ Required properties: "fsl,imx21-rnga" "fsl,imx31-rnga" (backward compatible with "fsl,imx21-rnga") "fsl,imx25-rngb" + "fsl,imx6sl-rngb" + "fsl,imx6sll-rngb" + "fsl,imx6ull-rngb" "fsl,imx35-rngc" - reg : offset and length of the register set of this block - interrupts : the interrupt number for the RNG block -- 2.17.1