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 Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 96EF1C5DF81 for ; Thu, 20 Aug 2026 18:21:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:Content-Type: List-Subscribe:List-Help:List-Post:List-Archive:List-Unsubscribe:List-Id: In-Reply-To:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date: Reply-To:Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date :Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=R1e7q/svll/jJoWXMFO7wt5gnqC6ryynbcUfPlyRJR4=; b=lUVrh28DfJhDGX5hEyMquXq42C mL0n7UUEanrapfv+/LoXB+N/15+2E46p0mqIVlTdmrZPB2yrSNZC2CiTlMWVeNA1ECAvCU05DNthj Vz5NDyqFeWtTxmJwb1JGFo/ceVB50CFgpR+/Ln7B2sjrfCW883l87GYecOp6gdZ8BKeMKHjc/vLf2 jAP9pcdJ4UHXCyu0/r/h6PuKn+84Dh6BYh5g6YYmt+0SHnIPvmVdQHWz2MhrZ4i8mUWMGZeHTB0Y8 uLweEdhn6atGcbXgk1RGsgyeHYBWv9hgNa+CG7HCVQLz1EUhBQTZehGwSeA+jpddat0S4SK2QkKPW TZRlH8og==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.99.1 #2 (Red Hat Linux)) id 1wx7Nj-0000000C2lq-0QjS; Thu, 20 Aug 2026 18:20:51 +0000 Received: from sea.source.kernel.org ([2600:3c0a:e001:78e:0:1991:8:25]) by bombadil.infradead.org with esmtps (Exim 4.99.1 #2 (Red Hat Linux)) id 1wx7Nh-0000000C2lM-0x8X for linux-riscv@lists.infradead.org; Thu, 20 Aug 2026 18:20:49 +0000 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) by sea.source.kernel.org (Postfix) with ESMTP id DA49743F85; Thu, 20 Aug 2026 18:20:48 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 4D4B91F000E9; Thu, 20 Aug 2026 18:20:46 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1787250048; bh=Dt1ularuwh4GAmniGZXU1TkEHbWNs9aSSgtoCZdHQQA=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=j5WjCTHj2OOop5JTee/9oCrF08yTx4iYKqVa+YvFXGrQXHk48pBpCcWRgD0mu+m1o 7pdvlVtRqV5MXA4tcnPyIGtFiF6j5aC+YhFsHVn6FM9cHPXyUbFy9WEHO++8C43b2p r5RaLV+ZioRfh6qrAJ6qkbDYJpCuX9Zk3m+DQCytK+vLjV5XdLOjE2vn4Iaz9JwGZT O+x3goDl04p9J//mxxriKH/CqBuSHet6eQ919vhK3a450/iyJ7EjCi1g1Czad31FHg AI1W0P62B42o7PPmiEWMnqxLt5y8v6Q1wI6tK0uGhKaBC0m/x5YVl3Ll94v0Two6Pv 84AMNSso17REA== Date: Thu, 20 Aug 2026 19:20:44 +0100 From: Conor Dooley To: Yaxing Guo Cc: Rob Herring , Krzysztof Kozlowski , Conor Dooley , Paul Walmsley , Palmer Dabbelt , Albert Ou , Alexandre Ghiti , devicetree@vger.kernel.org, inux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org, yangyinglu@bosc.ac.cn, yangyinglu Subject: Re: [PATCH] dt-bindings: riscv: firmware: Add OpenSBI configuration binding Message-ID: <20260820-mowing-marbling-ff0a0c82804c@spud> References: <20260819090411.18561-1-guoyaxing@bosc.ac.cn> <20260819-extent-decrease-0483d66a87af@spud> MIME-Version: 1.0 In-Reply-To: <20260819-extent-decrease-0483d66a87af@spud> X-BeenThere: linux-riscv@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============9206981976750155679==" Sender: "linux-riscv" Errors-To: linux-riscv-bounces+linux-riscv=archiver.kernel.org@lists.infradead.org --===============9206981976750155679== Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="NAPYhvb5+gg4INVm" Content-Disposition: inline --NAPYhvb5+gg4INVm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Aug 19, 2026 at 06:03:12PM +0100, Conor Dooley wrote: > On Wed, Aug 19, 2026 at 05:04:11PM +0800, Yaxing Guo wrote: > > From: yangyinglu > >=20 > > Add a Devicetree binding for OpenSBI configuration data in the > > chosen node, including the cold-boot-harts property. > >=20 > > OpenSBI supports describing certain Generic Platform configurations in > > the device tree passed by the previous boot stage. The OpenSBI source > > tree documents the `opensbi,config` node and provides the corresponding > > device tree parsing flow. > >=20 > > The `/chosen/opensbi-config` node can be used to configure OpenSBI, > > including the set of harts permitted to perform a cold boot through the > > `cold-boot-harts` property. OpenSBI parses this node during the boot > > phase and removes it from the device tree after cold boot. > >=20 > > Add the Devicetree binding for this OpenSBI configuration node to > > document the supported `compatible` and `cold-boot-harts` properties. > >=20 > > Signed-off-by: yangyinglu > > --- > > .../bindings/firmware/opensbi,config.yaml | 38 +++++++++++++++++++ > > 1 file changed, 38 insertions(+) > > create mode 100644 Documentation/devicetree/bindings/firmware/opensbi,= config.yaml > >=20 > > diff --git a/Documentation/devicetree/bindings/firmware/opensbi,config.= yaml b/Documentation/devicetree/bindings/firmware/opensbi,config.yaml > > new file mode 100644 > > index 000000000000..86b1e1e673a8 > > --- /dev/null > > +++ b/Documentation/devicetree/bindings/firmware/opensbi,config.yaml > > @@ -0,0 +1,38 @@ > > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > > +%YAML 1.2 > > +--- > > +$id: http://devicetree.org/schemas/firmware/opensbi,config.yaml# > > +$schema: http://devicetree.org/meta-schemas/core.yaml# > > + > > +title: OpenSBI Firmware Configuration > > + > > +maintainers: >=20 > You probably should've waited for a response to your question about who > should maintain it before sending, becuase I am not entirely sure this > software configuration node should be documented or if the maintainers > of opensbi would want it to be. And to quote Anup: | The opensbi configuration is all under "/chosen" DT node so I am | not sure if we should have related bindings under Linux sources. |=20 | Other projects (such as U-boot or Xen) who use "/chosen" DT node | also don't have their bindings under Linux sources. So this is a nack from me on that basis, sorry. Did you have some user for this that could change my mind? Thanks, Conor. >=20 > Cheers, > Conor. >=20 > > + > > +description: | > > + OpenSBI configuration data passed in the chosen node. > > + > > +properties: > > + compatible: > > + const: opensbi,config > > + > > + cold-boot-harts: > > + $ref: /schemas/types.yaml#/definitions/phandle-array > > + description: > > + List of hart CPU nodes selected as cold boot harts by OpenSBI. > > + > > +required: > > + - compatible > > + > > +additionalProperties: false > > + > > +examples: > > + - | > > + / { > > + chosen { > > + opensbi-config { > > + compatible =3D "opensbi,config"; > > + cold-boot-harts =3D <&cpu0>; > > + }; > > + }; > > + }; > > +... > > --=20 > > 2.43.0 > >=20 --NAPYhvb5+gg4INVm Content-Type: application/pgp-signature; name=signature.asc -----BEGIN PGP SIGNATURE----- iHUEABYKAB0WIQRh246EGq/8RLhDjO14tDGHoIJi0gUCaodFewAKCRB4tDGHoIJi 0rIDAP9KaJzdKUnGV/A5JJJ7EmTMo1fKndvtfhOidaamNZuoFwEA4QEPjPvvPMfi Dxa3fwxFgwi+xB0QaJhJKcdI1T+pBAQ= =2xDn -----END PGP SIGNATURE----- --NAPYhvb5+gg4INVm-- --===============9206981976750155679== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv --===============9206981976750155679==--