From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.1 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id C2602C433E0 for ; Tue, 14 Jul 2020 21:09:53 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 9B27120658 for ; Tue, 14 Jul 2020 21:09:53 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1594760993; bh=ArJuSwehu3eqi2k6YsxpjQ7tdEvCHdkWkCFNGLW+GGQ=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=1Msy5/N39jqGICEO0N9o4OohPiUJ1UPZR8MBMDcScX9sy46uaKiq4OdwqIt5EOO5Q 48fhZH99JCXzM7Yimw3Sa9N9t2SqvTZrZVxIBJHhcWcGlO4toZmaMmCNo4hkbWk6BL sUwx6wD5xdnmSF91cwhZanvet1FRhQn38m/9dpYk= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728164AbgGNVJr (ORCPT ); Tue, 14 Jul 2020 17:09:47 -0400 Received: from mail-il1-f194.google.com ([209.85.166.194]:43510 "EHLO mail-il1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726750AbgGNVJr (ORCPT ); Tue, 14 Jul 2020 17:09:47 -0400 Received: by mail-il1-f194.google.com with SMTP id i18so43204ilk.10; Tue, 14 Jul 2020 14:09:46 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to; bh=7n1eCfcIXRzp8Zf/h32IGI3ysZU8V6mXbcHVjQ48LpM=; b=pyKmC1iUGPTpESp5UMsKKB8qMGHSZYTG3QAWfP9O6DfL/dhCSRBo7hYqVDFUPQLbXB AwtEVltT2cRklulEZ5N08nsVNMdUmf1Y608Q0vHnEXmwsYfnUWa3a+xXiC1TJj4XNZYV E53s+iO0ATpir+MMmN3vryeS8+96VWAtl/plIKUtZvHGP6ksq4E5SfaJTMQ8LxdUaHj1 bpFHsfLQ2v+8f4t21pg0RFTz8xIBCJ/w6xmhN69Lrc4JVbUHqg3SJDtSH0kZ6D4pUIbg 2sEfEl2BuFI+cqSoTEMlVSBm/HfCSBjuONy29rRbZRQzQS6seBFRKUyUb9z3EBU/0sUv CkOg== X-Gm-Message-State: AOAM531wDsS6JMD2Ob2ASYR5HEziOU31/RMklbkWn4yEEB+LvkuVuvGl 4pERuDrNz5WLvxS+/7H8dh7//cK03ZTK X-Google-Smtp-Source: ABdhPJy2M+RM7ODxSIifUBuOn2xzZSlv5UJSECY0kHYVvd6TGRWoVCEMCkEvE+CKWf8plGmQrP4TkA== X-Received: by 2002:a92:6a02:: with SMTP id f2mr5984073ilc.68.1594760986430; Tue, 14 Jul 2020 14:09:46 -0700 (PDT) Received: from xps15 ([64.188.179.252]) by smtp.gmail.com with ESMTPSA id x71sm57098ilk.43.2020.07.14.14.09.44 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 14 Jul 2020 14:09:45 -0700 (PDT) Received: (nullmailer pid 2921463 invoked by uid 1000); Tue, 14 Jul 2020 21:09:44 -0000 Date: Tue, 14 Jul 2020 15:09:44 -0600 From: Rob Herring To: Horia =?utf-8?Q?Geant=C4=83?= Cc: Franck Lenormand , Marco Felsch , Matt Mackall , Iuliana Prodan , linux-crypto@vger.kernel.org, Fabio Estevam , Pengutronix Kernel Team , Martin Kaiser , linux-arm-kernel@lists.infradead.org, NXP Linux Team , Greg Kroah-Hartman , Arnd Bergmann , linux-kernel@vger.kernel.org, Herbert Xu , Rob Herring , devicetree@vger.kernel.org, Shawn Guo , Silvano Di Ninno , Sascha Hauer Subject: Re: [PATCH v3 1/5] dt-bindings: rng: add RNGB compatibles for i.MX6 SoCs Message-ID: <20200714210944.GA2921406@bogus> References: <20200714123920.23711-1-horia.geanta@nxp.com> <20200714123920.23711-2-horia.geanta@nxp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20200714123920.23711-2-horia.geanta@nxp.com> Sender: linux-crypto-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org On Tue, 14 Jul 2020 15:39:16 +0300, Horia Geantă wrote: > 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(+) > Reviewed-by: Rob Herring