From: "Junhui Liu" <junhui.liu@pigmoral.tech>
To: "Rob Herring" <robh@kernel.org>
Cc: "Bjorn Andersson" <andersson@kernel.org>,
"Mathieu Poirier" <mathieu.poirier@linaro.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Chen Wang" <unicorn_wang@outlook.com>,
"Inochi Amaoto" <inochiama@gmail.com>,
"Philipp Zabel" <p.zabel@pengutronix.de>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Alexandre Ghiti" <alex@ghiti.fr>,
<linux-remoteproc@vger.kernel.org>, <devicetree@vger.kernel.org>,
<sophgo@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
<linux-riscv@lists.infradead.org>
Subject: Re: [PATCH 1/2] dt-bindings: remoteproc: Add C906L rproc for Sophgo CV1800B SoC
Date: Sun, 29 Jun 2025 03:19:03 +0000 [thread overview]
Message-ID: <184d653d449ed7b0.6a3574329a6ead7.ebc417e4db758a3b@Mac> (raw)
In-Reply-To: <20250625191613.GA2059062-robh@kernel.org>
Hi Rob,
Thanks for your review.
On 25/06/2025 14:16, Rob Herring wrote:
> On Sun, Jun 08, 2025 at 10:37:39AM +0800, Junhui Liu wrote:
>> Add C906L remote processor for CV1800B SoC, which is an asymmetric
>> processor typically running RTOS.
>>
>> Signed-off-by: Junhui Liu <junhui.liu@pigmoral.tech>
>> ---
>> .../bindings/remoteproc/sophgo,cv1800b-c906l.yaml | 68 ++++++++++++++++++++++
>> 1 file changed, 68 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/remoteproc/sophgo,cv1800b-c906l.yaml b/Documentation/devicetree/bindings/remoteproc/sophgo,cv1800b-c906l.yaml
>> new file mode 100644
>> index 0000000000000000000000000000000000000000..455e957dec01c16424c49ebe5ef451883b0c3d4a
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/remoteproc/sophgo,cv1800b-c906l.yaml
>> @@ -0,0 +1,68 @@
>> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/remoteproc/sophgo,cv1800b-c906l.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: Sophgo C906L remote processor controller for CV1800B SoC
>> +
>> +maintainers:
>> + - Junhui Liu <junhui.liu@pigmoral.tech>
>> +
>> +description:
>> + Document the bindings for the C906L remoteproc component that loads and boots
>> + firmwares on the CV1800B SoC.
>> +
>> +properties:
>> + compatible:
>> + const: sophgo,cv1800b-c906l
>> +
>> + firmware-name:
>> + $ref: /schemas/types.yaml#/definitions/string
>
> Already has a type. You just need 'maxItems: 1'.
Will do.
>
>> + description:
>> + The name of the firmware file to load for this remote processor, relative
>> + to the firmware search path (typically /lib/firmware/).
>
> That's the same for every 'firmware-name' instance. So drop.
>
> Is there a default name?
The firmware name would be specified in the board device tree, and
there is no default value. For reference, an example value is provided
in the example DT.
>
>> +
>> + memory-region:
>
> maxItems: 1
I plan to add a description for the rpmsg-related regions in the next
version. Since the number of these regions may be flexible, I think I
will only add a minItems property to ensure the execution memory
region is specified.
>
>> + description:
>> + Phandle to a reserved memory region that is used to load the firmware for
>> + this remote processor. The remote processor will use this memory region
>> + as its execution memory.
>> +
>> + resets:
>> + maxItems: 1
>> +
>> + sophgo,syscon:
>> + $ref: /schemas/types.yaml#/definitions/phandle
>> + description:
>> + A phandle to the SEC_SYS region, used for configuration of the remote processor.
>> +
>> +required:
>> + - compatible
>> + - firmware-name
>> + - memory-region
>> + - resets
>> + - sophgo,syscon
>> +
>> +additionalProperties: false
>> +
>> +examples:
>> + - |
>> + reserved-memory {
>> + #address-cells = <1>;
>> + #size-cells = <1>;
>> + ranges;
>> +
>> + c906l_mem: region@83f40000 {
>> + reg = <0x83f40000 0xc0000>;
>> + no-map;
>> + };
>> + };
>
> Drop. No need to show how /reserved-memory works here.
Will do.
>
>> +
>> + c906l-rproc {
>> + compatible = "sophgo,cv1800b-c906l";
>> + firmware-name = "c906l-firmware.elf";
>> + memory-region = <&c906l_mem>;
>> + resets = <&rst 294>;
>> + sophgo,syscon = <&sec_sys>;
>> + };
>>
>>
--
Best regards,
Junhui Liu
next prev parent reply other threads:[~2025-06-29 3:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-08 2:37 [PATCH 0/2] remoteproc: cv1800b: Add initial support for C906L processor Junhui Liu
2025-06-08 2:37 ` [PATCH 1/2] dt-bindings: remoteproc: Add C906L rproc for Sophgo CV1800B SoC Junhui Liu
2025-06-11 9:01 ` Chen Wang
2025-06-11 9:23 ` Junhui Liu
2025-06-25 19:16 ` Rob Herring
2025-06-29 3:19 ` Junhui Liu [this message]
2025-06-08 2:37 ` [PATCH 2/2] drivers: remoteproc: Add C906L controller " Junhui Liu
2025-06-09 8:43 ` Peng Fan
2025-06-10 3:42 ` Junhui Liu
2025-06-11 6:29 ` Peng Fan
2025-06-10 5:15 ` kernel test robot
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=184d653d449ed7b0.6a3574329a6ead7.ebc417e4db758a3b@Mac \
--to=junhui.liu@pigmoral.tech \
--cc=alex@ghiti.fr \
--cc=andersson@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=inochiama@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mathieu.poirier@linaro.org \
--cc=p.zabel@pengutronix.de \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.org \
--cc=sophgo@lists.linux.dev \
--cc=unicorn_wang@outlook.com \
/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;
as well as URLs for NNTP newsgroup(s).