Received: by 2002:a25:824b:0:0:0:0:0 with SMTP id d11csp825423ybn; Wed, 2 Oct 2019 06:49:53 -0700 (PDT) X-Google-Smtp-Source: APXvYqwhjCf7i7YH3SSzBwzYeyFLoP2cDfXHHTFq/tHDo84l9fai1U9rfnmqouD5x/UXxVCDiLaL X-Received: by 2002:a17:906:4e57:: with SMTP id g23mr3083129ejw.264.1570024193405; Wed, 02 Oct 2019 06:49:53 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1570024193; cv=none; d=google.com; s=arc-20160816; b=RQHh/5tyaJ4xK57BWpttE3/52m8JV5nVxhVcVuuw94cDMrhpRU23F4GUJA2A+w33Y8 lsGGHUQQmwqFRG2gHvsRITFeQ49dJe8sa105juZbYy384xav9W+RFdC8ATCv17trIIFl OnPvezRdPXO/CG5QrvPy835kGFAxq/vqrDYuq0l+cILbk28Why9qYgz6hCPAKseL/CyV CW/jxPA94atZlkRY9aJgfxUbxz2AHWfOP/fexRISrvO823JRopnTtmy+ixiEL1GvWyK4 qm7VuPh8bej5uIFkwnp1NBxKhVnouENEsUPNMWH/x5fYj3N0tgJ4c2HOsSNl1mUDFm5v zA5w== 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=5rPiu9CvDpBAaahOaCBqhOmsr7AjdbDELNs3E0HW3lo=; b=glWbt10zPWs1ChqBJUmaaIdBMSI2A+bDgU+xNfSsASRJpPoJ3js12fNNTyyaGzdbs2 yVHrPuO5eoBM1f82QUnCbyvBrYduadPTU0ONI8qVg5j3gzy/T52VJp/lM4bQrOnpqbmZ LpjJR4RAzdjzak3hDux7odEeua6jlHz5igrgRW2n5+V67DCI+bHkfoDm0u2H7F52M4XL B8kzQdQY1M/v9vBJCTzv4zaKCbRoXjyn2h/O0rWqJ2BRPD/e5BEege4W5KZOrX8B2wJ7 E5Y04BM4h3KnaAHuA6LeT+abd0RQzmJt3D+lMlaA5APJJmnlAundpq2A0LUDxCFoaxdT QBjw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-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 w6si10840830ejf.8.2019.10.02.06.49.28; Wed, 02 Oct 2019 06:49:53 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-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-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-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 S1728048AbfJBNsA (ORCPT + 99 others); Wed, 2 Oct 2019 09:48:00 -0400 Received: from mailgw01.mediatek.com ([210.61.82.183]:54417 "EHLO mailgw01.mediatek.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1728031AbfJBNr6 (ORCPT ); Wed, 2 Oct 2019 09:47:58 -0400 X-UUID: a9454dd52135451797b80bf2ba97a4f6-20191002 X-UUID: a9454dd52135451797b80bf2ba97a4f6-20191002 Received: from mtkcas08.mediatek.inc [(172.21.101.126)] by mailgw01.mediatek.com (envelope-from ) (Cellopoint E-mail Firewall v4.1.10 Build 0809 with TLS) with ESMTP id 727753782; Wed, 02 Oct 2019 21:47:52 +0800 Received: from mtkcas08.mediatek.inc (172.21.101.126) by mtkmbs07n2.mediatek.inc (172.21.101.141) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Wed, 2 Oct 2019 21:47:48 +0800 Received: from [172.21.77.33] (172.21.77.33) by mtkcas08.mediatek.inc (172.21.101.73) with Microsoft SMTP Server id 15.0.1395.4 via Frontend Transport; Wed, 2 Oct 2019 21:47:48 +0800 Message-ID: <1570024070.4002.1.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" , Neal Liu Date: Wed, 2 Oct 2019 21:47:50 +0800 In-Reply-To: <1568771054.21700.7.camel@mtkswgap22> 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> <1568771054.21700.7.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-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Dear Rob, Just a gentle ping. Neal On Wed, 2019-09-18 at 09:44 +0800, Neal Liu wrote: > On Tue, 2019-07-23 at 22:35 +0800, 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 > > > > We would like to consult more about this patch. > We cannot figure out what method should be used instead of DT. > The interface to access firmware is "smc" and firmware function only > exists on certain platforms. > Some DT has similar way, like: > http://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts#L470 > > firmware { > optee { > compatible = "linaro,optee-tz"; > method = "smc"; > }; > }; > > Is there any way to instantiate driver on certain platforms without DT? > Could you give us some examples? > Thanks > > > > > > > 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 > > > > > > >