Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp9111354ybi; Tue, 23 Jul 2019 22:04:33 -0700 (PDT) X-Google-Smtp-Source: APXvYqyn5BQZ6HwABSKLx6Z8B49QytwdKWN6hcBoQvfYxOHQMmRSusu/LXrF1gdnJXBoni0npOXX X-Received: by 2002:a17:902:124:: with SMTP id 33mr85964355plb.145.1563944673223; Tue, 23 Jul 2019 22:04:33 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1563944673; cv=none; d=google.com; s=arc-20160816; b=iiSMbR25pxktBoo7IICixhpcsyu8u5pqWeHSvqh0cnDKcvPQc/9OC6zlDcirp6mQbr x8bnYF3HDxgr1wXLKRwMPWbgwSnmeBmaKzzLsJK2k1xPSXAvrslL6lVr9iGMqSk+VM6a y9uWasfYJ3P7t9RJ67eyvu96yM46KPr9rrk+fRl6j5KazYROpLWUnup9+/uDG6ErZM+f wfVNW7RMeq4vj/AYT3rOADRQUS1kfUTrP+0gClgMZ4cxYZt63ltVqmOZ6dW11Z6NP/1O uvxmbEDCYzAs8s2Ql4TrwZR4k4DIxs+br+4Nx9XNc4X0Luihg2ypAyjMU+aIH8rshGnK 9xfg== 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=M/Qtn823XTjTxQXaqSX91buiolLX83jZ7LcMKHKsl1A=; b=bOQ3SHvM8sPufVheIuIFOSS5LIUQIAt0fVt/TeYqWdziqnmlBmlQOj5vUxkBeDpD5a AwNL86/Dup1VLbsTjf2rAyigUQ3rMS4JCJ34bWI3VW7vNhwWujuI/TA0NetCFj1scz3j E/u09ZzZoI6DHImgDRNq1XI1AL6sX5rSLLfNT2dwgI6IpwP37B0EWuI1IrylzJiZ3OgH BdN52GipQztCJ421UWo1ZKEGj+B/ZoCccEscCZ8GmNEPyjMj5v814GDuWmqgFqztooZ5 QY9H2ieyRR7AhClLFW3T5qq1rDWHmPzU4jpSMwbqro4PhdDQbv1QkrAtCql8YEVZYHzf MSog== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=mediatek.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id d23si11731262pjv.56.2019.07.23.22.04.12; Tue, 23 Jul 2019 22:04:33 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=mediatek.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725900AbfGXFEL (ORCPT + 99 others); Wed, 24 Jul 2019 01:04:11 -0400 Received: from mailgw01.mediatek.com ([210.61.82.183]:59979 "EHLO mailgw01.mediatek.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1725870AbfGXFEL (ORCPT ); Wed, 24 Jul 2019 01:04:11 -0400 X-UUID: e0f47eec30464f22bd9e18ba89f1f95a-20190724 X-UUID: e0f47eec30464f22bd9e18ba89f1f95a-20190724 Received: from mtkmrs01.mediatek.inc [(172.21.131.159)] by mailgw01.mediatek.com (envelope-from ) (mhqrelay.mediatek.com ESMTP with TLS) with ESMTP id 29376682; Wed, 24 Jul 2019 13:04:03 +0800 Received: from mtkcas09.mediatek.inc (172.21.101.178) by mtkmbs07n1.mediatek.inc (172.21.101.16) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Wed, 24 Jul 2019 13:04:02 +0800 Received: from [172.21.77.33] (172.21.77.33) by mtkcas09.mediatek.inc (172.21.101.73) with Microsoft SMTP Server id 15.0.1395.4 via Frontend Transport; Wed, 24 Jul 2019 13:04:02 +0800 Message-ID: <1563944642.13531.0.camel@mtkswgap22> Subject: Re: [PATCH v4 2/3] dt-bindings: rng: add bindings for MediaTek ARMv8 SoCs From: Neal Liu To: Rob Herring CC: Mark Rutland , "devicetree@vger.kernel.org" , Herbert Xu , wsd_upstream , Sean Wang , "linux-kernel@vger.kernel.org" , Crystal Guo =?UTF-8?Q?=28=E9=83=AD=E6=99=B6=29?= , "linux-crypto@vger.kernel.org" , Matt Mackall , Matthias Brugger , "linux-mediatek@lists.infradead.org" , "linux-arm-kernel@lists.infradead.org" Date: Wed, 24 Jul 2019 13:04:02 +0800 In-Reply-To: References: <1561361052-13072-1-git-send-email-neal.liu@mediatek.com> <1561361052-13072-3-git-send-email-neal.liu@mediatek.com> <20190722171320.GA9806@bogus> <1563848465.31451.4.camel@mtkswgap22> 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 On Tue, 2019-07-23 at 08:35 -0600, Rob Herring wrote: > On Mon, Jul 22, 2019 at 8:21 PM Neal Liu wrote: > > > > Please don't top post to lists. > > > Dear Rob, > > You can check my driver for detail: > > http://patchwork.kernel.org/patch/11012475/ or patchset 3/3 > > I could, or you could just answer my question. > > > > > This driver is registered as hardware random number generator, and > > combines with rng-core. > > We want to add one rng hw based on the dts. Is this proper or do you > > have other suggestion to meet this requirement? > > It depends. There doesn't appear to be any resource configuration, so > why does it need to be in DT. DT is not the only way instantiate > drivers. > > Rob This hwrng is only supported on some chipsets. It needs DT to identify which platform is supported or not. Is there any better idea to meet this requirement? Neal > > > > Thanks > > > > > > On Tue, 2019-07-23 at 01:13 +0800, Rob Herring wrote: > > > On Mon, Jun 24, 2019 at 03:24:11PM +0800, Neal Liu wrote: > > > > Document the binding used by the MediaTek ARMv8 SoCs random > > > > number generator with TrustZone enabled. > > > > > > > > Signed-off-by: Neal Liu > > > > --- > > > > .../devicetree/bindings/rng/mtk-sec-rng.txt | 10 ++++++++++ > > > > 1 file changed, 10 insertions(+) > > > > create mode 100644 Documentation/devicetree/bindings/rng/mtk-sec-rng.txt > > > > > > > > diff --git a/Documentation/devicetree/bindings/rng/mtk-sec-rng.txt b/Documentation/devicetree/bindings/rng/mtk-sec-rng.txt > > > > new file mode 100644 > > > > index 0000000..c04ce15 > > > > --- /dev/null > > > > +++ b/Documentation/devicetree/bindings/rng/mtk-sec-rng.txt > > > > @@ -0,0 +1,10 @@ > > > > +MediaTek random number generator with TrustZone enabled > > > > + > > > > +Required properties: > > > > +- compatible : Should be "mediatek,mtk-sec-rng" > > > > > > What's the interface to access this? > > > > > > A node with a 'compatible' and nothing else is a sign of something that > > > a parent device should instantiate and doesn't need to be in DT. IOW, > > > what do complete bindings for firmware functions look like? > > > > > > > + > > > > +Example: > > > > + > > > > +hwrng: hwrng { > > > > + compatible = "mediatek,mtk-sec-rng"; > > > > +} > > > > -- > > > > 1.7.9.5 > > > > > > > > > > _______________________________________________ > > > Linux-mediatek mailing list > > > Linux-mediatek@lists.infradead.org > > > http://lists.infradead.org/mailman/listinfo/linux-mediatek > > > >