Received: by 10.223.164.202 with SMTP id h10csp4259555wrb; Mon, 20 Nov 2017 12:29:54 -0800 (PST) X-Google-Smtp-Source: AGs4zManaU8VfdcVeIq9dTkrFxk3jAzzPoSCXhhMuiLrEDsiq1pc2rcmtK/uSHeNIph077hwQt8V X-Received: by 10.99.127.85 with SMTP id p21mr14773224pgn.425.1511209794791; Mon, 20 Nov 2017 12:29:54 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1511209794; cv=none; d=google.com; s=arc-20160816; b=uNR3J4ZUANNN1Sgwd+AkQeDdiNprBWvOdu2CfztffWbhjvY18hffrx9iIMgiKixQF7 h6e3i1kLTapQc0JdirXROibYhJ3uQlZK/SF+5MDeHjJKVQ+3CgLgJ7Xpqt/EeUYMqMPB ynIWM9gqTfhOuKabvXUQ7Qhocy5YR9vrXO9JftQLMPsWjYqlxON4YLf6/HAOYtsBkFgM qzWpJQXOEdTHBciH4Ea+fB2uAn06e8J/w7WmaPjKeVLXGoLdxyhhofY80BIxGxcDnG8L 1d3tLOVH2ZbLYJq6hH6aotQlCs9RXIhJ/m9RMsYpK8L+1eVXyRo7RK+8VOlolg82lfry 0gNw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=o89oWGjHGOJt0EYhgoI3IayNA4l0sO3+cWponjwxwQY=; b=o+XtEcI+aVuJg+qhJc+6dEoOcvtfq/a3CXFFsm+M7/3cvOe2Oz1wy3ikmmD7/fNckt 7DJD4F+y4EUYP1+abeYDdN0O99meXT2SqkSLJzJeJTJGwhWjUlBXI8mCjvRVDyYdiTjo GSSmUsk3J50kWR7JIioLQ0C4cxNkU1lr8sNbhDHnda0LLUjwY8+gWjuvK1SO8/AEQ2T8 GMdd3WBASdh8moS8Ne4nbU+Qq4VsOQQy6Eu805UZC3NzW62Xbsg/T34pP/AmB4kL7wpT ZiTgvS1v4AftiqTjWtmsFF7aB+QC3XjyKIBSpHOKBtY6P5R+gsmTI3mAW/PLthFDsakg FnIg== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id bf4si2950320plb.142.2017.11.20.12.29.44; Mon, 20 Nov 2017 12:29:54 -0800 (PST) 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752689AbdKTU3H (ORCPT + 67 others); Mon, 20 Nov 2017 15:29:07 -0500 Received: from mout.gmx.net ([212.227.17.22]:49495 "EHLO mout.gmx.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752358AbdKTU3F (ORCPT ); Mon, 20 Nov 2017 15:29:05 -0500 Received: from latitude ([88.153.7.8]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MVIva-1efdmW0l7G-00YkJX; Mon, 20 Nov 2017 21:28:58 +0100 Date: Mon, 20 Nov 2017 21:28:56 +0100 From: Jonathan =?utf-8?Q?Neusch=C3=A4fer?= To: Palmer Dabbelt Cc: mark.rutland@arm.com, robh+dt@kernel.org, devicetree@vger.kernel.org, patches@groups.riscv.org, linux-kernel@vger.kernel.org, Jonathan=20Neusch=C3=A4fer?= Subject: Re: [PATCH] dt-bindings: Add a RISC-V SBI firmware node Message-ID: <20171120202856.nptoirhm5luiamt7@latitude> References: <20171120195000.2070-1-palmer@sifive.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="zfmnly5vfaibiovm" Content-Disposition: inline In-Reply-To: <20171120195000.2070-1-palmer@sifive.com> User-Agent: NeoMutt/20170113 (1.7.2) X-Provags-ID: V03:K0:bYaeCEXAQZ10Qh6VAciHXbQANhsIIRbhz3fTS4Fl5teM0Aj9GlQ WvMEzaEqAyLI5Q+5e8u7PZasQd0YsN2Zx91XQ5nJGIYQ9YtXzY7OyqjpXnbze8Iz+5OlUWE M3ucM2v1uAN2wWSfQJSxcDEf3lV45zPOYfazc8dwZh0wnii6OV2mdry0+PwOwJFTQH0rdLl d+ozcSoaRFW7SHPoi6IyQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:nOW3qIhQkHI=:Iuq6EYzRIWLNs5R4Ag7MVY muPD+q8xhgy/fcjp0Spe240/08W/r2ilmWk+zAwyfnBAsLN2hIdUWqUp0K0m4E16IA/SurJgh LBcN0KLClyjEN4bZB7kJDgDQBqeGgdy6n/HX/7XmF/XfUc4y1VRQyrFDeG2rwp0Pnlm+M/KI4 Ckkmq0SEBeqMo3RkzucIOV8RfOs/uuCc2uvGtXvgZrgEuhUbX/vIiyIshPGgqy1nWt5IPtKkf BYVDIaSZJsglQD3g/4bYWdSO5d2cMeTdefUDFX9bnV9U8FDQeKGQPhKE2d+5xmOVomOcY+JwY zG1yj+6cVVgQlMqekyCLO/y9IUPbosaD6IhQoZgxwDHhDM/S7r0KRwyM/bSbTvJ72eB2tqFzW m9TPg7f0+52cmUBCJgH4/22sH4edsUcX44BYdPQKDfrHG512iZyJvqKtmqi3loMbwBq2wIQ2A DpcBIxp/80hpeUBGfLFJUKM94YfyfeE80Q355/0clEbKg+/BykLMmB1UAq6l7HndseMgGQ+j2 OXqmmu7BSITxSC9qBoU6bR7Gi9pCrPVnLI0wyu9KseXcZVpF5iRv2Ts1VLiCMx/VnvrLd6tCR XtfebmyPFglucRhaSvlLQXopfb+0VQzOMEy611blyOMaWQo3/kRj/rCGjE/CBY1jaP1UOOzJL YgwktibOtBF9f9VvOS6xUEn8ZPJmmg9IwLi5Lty3nkma7/e8b0+WF6DTZKOtz6q1puU+BhBx/ aCJJ3gZ88/FmSTyRTTfl9P4OQjpLpz/IQ2BgLH4nptzZL56APC8Ztkoa1HMFoPAcQameUS/Mk 24bIre6dQypqb9nGq06ZTmz0iCSXA== Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --zfmnly5vfaibiovm Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Nov 20, 2017 at 11:50:00AM -0800, Palmer Dabbelt wrote: > The RISC-V privileged ISA mandates the presence of an SBI, but there's > no reason not to put it in the device tree. This would allow us to > possibly remove the SBI later. Thanks! >=20 > CC: Jonathan Neusch=C3=A4fer > Signed-off-by: Palmer Dabbelt > --- > .../devicetree/bindings/firmware/riscv.sbi.txt | 20 ++++++++++++++= ++++++ > 1 file changed, 20 insertions(+) > create mode 100644 Documentation/devicetree/bindings/firmware/riscv.sbi.= txt >=20 > diff --git a/Documentation/devicetree/bindings/firmware/riscv.sbi.txt b/D= ocumentation/devicetree/bindings/firmware/riscv.sbi.txt > new file mode 100644 > index 000000000000..42384d5d52cf > --- /dev/null > +++ b/Documentation/devicetree/bindings/firmware/riscv.sbi.txt Nit: Other bindings use either a comma (as in the compatible string, "riscv,sbi.txt") or a dash (vendor-product.txt, "riscv-sbi.txt") in the file name. > @@ -0,0 +1,20 @@ > +RISC-V Supervisor Binary Interface (SBI) > + > +The RISC-V privileged ISA specification mandates the presence of a super= visor > +binary interface that performs some operations which might otherwise req= uire > +particularly complicated instructions. This interface includes > +inter-processor interrupts, TLB flushes, i-cache and TLB shootdowns, a > +console, and power management. > + > +Required properties: > +- compatible: must contain one of the following > + * "riscv,sbi" for the SBI defined by the privileged specification of the > + system. "of the system" seems to imply that different RISC-V systems (different RISC-V implementations) can have different privileged specifications. I think it's better to refer to concrete documents, that don't depend on the rest of the system, instead. Either: * "riscv,sbi" for the SBI defined by the RISC-V Privileged ISA Specificati= on. Or something like: * "sifive,sbi" for the SBI defined by SiFive document XYZ. [ I know that there currently is no SBI spec, because the chapter has been removed from the Priv Spec, but this can be fixed later, once the final name of the document describing the SBI is clear. ] > + > +Example: > + > +firmware { > + sbi { > + compatible =3D "riscv,sbi"; > + }; > +}; > --=20 Thanks, Jonathan Neusch=C3=A4fer --zfmnly5vfaibiovm Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJaEzr9AAoJEAgwRJqO81/b5aAP/2WD4PEZofUxQCXsFOrby4cg YvmKna0iKTFbBddgDK7l+1ln5d5i/HWoXGjOk+71r+BxAW8NF+H+MNGj59tgeQYs 060hOcTpLBn3gxdNh5LWon1KBmkSzS6wGX917elTqJ97Ucjpeql8E/xq3hBOBotd E6YxmidgfZFz0i8Dq2g25Y4ogDuDKrj8P+ewH9t9hi2huKuT1xqFlufC5o1ziajL Rz4iBYTCryEYBB5wzZl3+g6FtS5cnmjGdMKDTp8CtczvfRp8miaZlfPIoXZtTPc8 qQr9L5jlF+AgJo7CLARnBY7Zrln5uQ33/bnL8JfMn2K05Og+Ev8mV7H/0tiHxX+4 jhrPBaUjzdUkMtug5OC2EGXqKDvgXeyhC7WBOIUkZE3JhcT/MmQCpL+0gG9elJ2A 74H4CYv6xNF0Yn1CNoFvtVjnMkRdzU9nSTHY5ZDr349vXe7mPdBpNsKr3xxmSZ5u Pn4l5Xpc8CL5Udrh55U0h2mgtFalojHIfoS0Bw8lMnB6AvD6h0W9zgOOpD7ZTCzu d0ca0hQSGr/0T661BP1H1G+ci5pMeTLcvoOLpgCpTsl6ieqhXA0xHp3098MaYxTF NzAFaZ9gZDWLOefP9czL+yQKT1jo5tFev1BNNHsRw4RF0TtdLcwGTGU82FrpfZ+C X11lhKoaNvhZ4dBZmFfq =IYaV -----END PGP SIGNATURE----- --zfmnly5vfaibiovm-- From 1584615981624343565@xxx Mon Nov 20 19:52:43 +0000 2017 X-GM-THRID: 1584615981624343565 X-Gmail-Labels: Inbox,Category Forums,HistoricalUnread