Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp3625748ybi; Sun, 2 Jun 2019 19:28:20 -0700 (PDT) X-Google-Smtp-Source: APXvYqwmotoMqfzd6wg1jeCSNlzLFeVsDry+Kl02KL4aQww3Ymo0kTq7hGMuuLxAwVIAY25CgZlH X-Received: by 2002:a63:4754:: with SMTP id w20mr25420324pgk.31.1559528900796; Sun, 02 Jun 2019 19:28:20 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1559528900; cv=none; d=google.com; s=arc-20160816; b=B7R7dSdWT6r7VkeqIYDgm2iDI2hbMx/zrUYZnslyT2wj/ZIP0b8w24dvGqYckB0Mqx opZikjGJ7uQl6obeTZpPRi+Y/3n7LSv7/OrYvGXzVwVf9oH1VS4ixKF/LtYLSHjmsPQt VFpiFzJG5Gpl7WJ7xF7KRgjeTDVmp8Bxo9YNJ4xdE7GenkiLhEBbbhmVaCzidJevdFX4 IyCV6ONX34bykFeWHU0Az73VAZMQ2RlQpPzY4oeA7vx40Hr4u1gxymZYst1Vr8CuyhC7 yFTuqVig1kXvMl88mwTFv4p5uymAZW3G9cagcaaJ3FjgBSym46W01WsL/lX3q4aihl3w U7ng== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:content-transfer-encoding :references:in-reply-to:date:cc:to:from:subject:message-id; bh=633ulwgIXu2xJiIzTNeqItHNd7b8JYJA51KXhpD0OjY=; b=QsZZ30NpHPEGBoXdtD9aQ1oKqrf8TFQ3QDco5lIpuRZ5JMCtvdycZ2x99gLm+miO/b xwoSJBJ4MUWX/2nSdHPyg0dmgVAYbFRpDNNCUxbnD9ka/Gs83AlphDcNcoWZZ+mssN6t aIQYm59jFP6nF35K+vCcT338n7LdsXTGsbH5PQxjRL69hegwpiqZq5hp4T+Kpi0xsX0n 1JL7+GbvzaOq03J/rHRLO9NRC2/2HB7j4DbyjD+7zDZogpnsBc5fq3uyRtDM1rcTorhD OxXYEAuctDcfCmCpjKMKP5wl3c/yW7FmvmbR94G5khaO68VPQt0JwxuYwWVh6vQ0Oybf Fs0w== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m39si18744505plg.155.2019.06.02.19.27.52; Sun, 02 Jun 2019 19:28:20 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726349AbfFCC1Z (ORCPT + 99 others); Sun, 2 Jun 2019 22:27:25 -0400 Received: from mailgw02.mediatek.com ([210.61.82.184]:62896 "EHLO mailgw02.mediatek.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1725965AbfFCC1Z (ORCPT ); Sun, 2 Jun 2019 22:27:25 -0400 X-UUID: 09855579fe6449a79b62bcff16a04d23-20190603 X-UUID: 09855579fe6449a79b62bcff16a04d23-20190603 Received: from mtkcas07.mediatek.inc [(172.21.101.84)] by mailgw02.mediatek.com (envelope-from ) (mhqrelay.mediatek.com ESMTP with TLS) with ESMTP id 659888550; Mon, 03 Jun 2019 10:27:08 +0800 Received: from mtkcas07.mediatek.inc (172.21.101.84) by mtkmbs07n2.mediatek.inc (172.21.101.141) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Mon, 3 Jun 2019 10:27:07 +0800 Received: from [172.21.77.33] (172.21.77.33) by mtkcas07.mediatek.inc (172.21.101.73) with Microsoft SMTP Server id 15.0.1395.4 via Frontend Transport; Mon, 3 Jun 2019 10:27:07 +0800 Message-ID: <1559528827.6663.8.camel@mtkswgap22> Subject: Re: [PATCH v2 2/3] dt-bindings: rng: update bindings for MediaTek ARMv8 SoCs From: Neal Liu To: Sean Wang CC: Matt Mackall , Herbert Xu , Rob Herring , "Mark Rutland" , Matthias Brugger , , , "linux-arm Mailing List" , "moderated list:ARM/Mediatek SoC support" , lkml , , Crystal Guo Date: Mon, 3 Jun 2019 10:27:07 +0800 In-Reply-To: References: <1558946326-13630-1-git-send-email-neal.liu@mediatek.com> <1558946326-13630-3-git-send-email-neal.liu@mediatek.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.2.3-0ubuntu6 Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-MTK: N Sender: linux-crypto-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org Hi Sean, On Thu, 2019-05-30 at 15:56 -0700, Sean Wang wrote: > Hi, Neal > > On Mon, May 27, 2019 at 1:39 AM Neal Liu wrote: > > > > Document the binding used by the MediaTek ARMv8 SoCs random > > number generator with TrustZone enabled. > > > > Signed-off-by: Neal Liu > > --- > > Documentation/devicetree/bindings/rng/mtk-rng.txt | 13 ++++++++++--- > > 1 file changed, 10 insertions(+), 3 deletions(-) > > > > diff --git a/Documentation/devicetree/bindings/rng/mtk-rng.txt b/Documentation/devicetree/bindings/rng/mtk-rng.txt > > index 2bc89f1..1fb9b1d 100644 > > --- a/Documentation/devicetree/bindings/rng/mtk-rng.txt > > +++ b/Documentation/devicetree/bindings/rng/mtk-rng.txt > > @@ -3,9 +3,12 @@ found in MediaTek SoC family > > > > Required properties: > > - compatible : Should be > > - "mediatek,mt7622-rng", "mediatek,mt7623-rng" : for MT7622 > > - "mediatek,mt7629-rng", "mediatek,mt7623-rng" : for MT7629 > > - "mediatek,mt7623-rng" : for MT7623 > > + "mediatek,mt7622-rng", "mediatek,mt7623-rng" for MT7622 > > + "mediatek,mt7629-rng", "mediatek,mt7623-rng" for MT7629 > > + "mediatek,mt7623-rng" for MT7623 > > No make any change for those lines not belong to the series There are some unused spaces and symbols. We try to align coding style with other bindings. > > > + "mediatek,mtk-sec-rng" for MediaTek ARMv8 SoCs > > I thought "mediatek,mtk-sec-rng" is only for those MediaTek ARMv8 SoCs > with security RNG Yes, sure. It's better to describe with "MediaTek ARMv8 SoCs with security RNG". > > > + > > +Optional properties: > > - clocks : list of clock specifiers, corresponding to > > entries in clock-names property; > > - clock-names : Should contain "rng" entries; > > @@ -19,3 +22,7 @@ rng: rng@1020f000 { > > clocks = <&infracfg CLK_INFRA_TRNG>; > > clock-names = "rng"; > > }; > > For those MediaTek ARMv8 SoCs with security RNG Are you suggesting we create a new binding file with security RNG? > > > + > > +hwrng: hwrng { > > + compatible = "mediatek,mtk-sec-rng"; > > +}; > > -- > > 1.7.9.5 > >