Devicetree
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Yaxing Guo <guoyaxing@bosc.ac.cn>
Cc: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Paul Walmsley <pjw@kernel.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Alexandre Ghiti <alex@ghiti.fr>,
	devicetree@vger.kernel.org, inux-kernel@vger.kernel.org,
	linux-riscv@lists.infradead.org, yangyinglu@bosc.ac.cn,
	yangyinglu <yangyinglu@bosc.cn>
Subject: Re: [PATCH] dt-bindings: riscv: firmware: Add OpenSBI configuration binding
Date: Wed, 19 Aug 2026 18:03:12 +0100	[thread overview]
Message-ID: <20260819-extent-decrease-0483d66a87af@spud> (raw)
In-Reply-To: <20260819090411.18561-1-guoyaxing@bosc.ac.cn>

[-- Attachment #1: Type: text/plain, Size: 2721 bytes --]

On Wed, Aug 19, 2026 at 05:04:11PM +0800, Yaxing Guo wrote:
> From: yangyinglu <yangyinglu@bosc.cn>
> 
> Add a Devicetree binding for OpenSBI configuration data in the
> chosen node, including the cold-boot-harts property.
> 
> 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.
> 
> 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.
> 
> Add the Devicetree binding for this OpenSBI configuration node to
> document the supported `compatible` and `cold-boot-harts` properties.
> 
> Signed-off-by: yangyinglu <yangyinglu@bosc.cn>
> ---
>  .../bindings/firmware/opensbi,config.yaml     | 38 +++++++++++++++++++
>  1 file changed, 38 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/firmware/opensbi,config.yaml
> 
> 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:

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.

Cheers,
Conor.

> +
> +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 = "opensbi,config";
> +                cold-boot-harts = <&cpu0>;
> +            };
> +        };
> +    };
> +...
> -- 
> 2.43.0
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      parent reply	other threads:[~2026-08-19 17:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-19  9:04 [PATCH] dt-bindings: riscv: firmware: Add OpenSBI configuration binding Yaxing Guo
2026-08-19  9:12 ` sashiko-bot
2026-08-19 17:03 ` Conor Dooley [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260819-extent-decrease-0483d66a87af@spud \
    --to=conor@kernel.org \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=guoyaxing@bosc.ac.cn \
    --cc=inux-kernel@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=pjw@kernel.org \
    --cc=robh@kernel.org \
    --cc=yangyinglu@bosc.ac.cn \
    --cc=yangyinglu@bosc.cn \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox