From: Thomas Bonnefille <thomas.bonnefille@bootlin.com>
To: Inochi Amaoto <inochiama@outlook.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Chen Wang <unicorn_wang@outlook.com>,
Chao Wei <chao.wei@sophgo.com>
Cc: "Albert Ou" <aou@eecs.berkeley.edu>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Samuel Holland" <samuel.holland@sifive.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Daniel Lezcano" <daniel.lezcano@linaro.org>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
"Miquèl Raynal" <miquel.raynal@bootlin.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH 5/5] riscv: dts: sophgo: Add LicheeRV Nano board device tree
Date: Mon, 10 Jun 2024 09:30:55 +0200 [thread overview]
Message-ID: <addbe5b3-04bc-4f02-be44-bdfe3aeba319@bootlin.com> (raw)
In-Reply-To: <IA1PR20MB49535CBF66DB31C2059C291ABBF02@IA1PR20MB4953.namprd20.prod.outlook.com>
Thank you for your answer :)
On 5/28/24 12:25 AM, Inochi Amaoto wrote:
>> +
>> + aliases {
>> + serial0 = &uart0;
>> + };
>> +
>> + chosen {
>> + stdout-path = "serial0:115200n8";
>> + };
>
> It is also better to add all already support nodes, such as gpio,
> other uart port.
I'm importing, cv18xx.dtsi through sg2002.dtsi, so GPIOs are already
configured and activated by default.
For the other peripherals, all of them are, with the default pinctrl,
set to function that haven't any driver yet (ADC, MIPI, PWM...).
Based on what I just said, I'm not sure to understand what you mean, can
you be more specific about the changes you want?
next prev parent reply other threads:[~2024-06-10 7:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 10:28 [PATCH 0/5] Add board support for Sipeed LicheeRV Nano Thomas Bonnefille
2024-05-27 10:28 ` [PATCH 1/5] dt-bindings: interrupt-controller: Add SOPHGO SG2002 plic Thomas Bonnefille
2024-05-27 16:39 ` Conor Dooley
2024-06-17 0:36 ` Yixun Lan
2024-06-17 3:33 ` Inochi Amaoto
2024-06-17 8:03 ` Conor Dooley
2024-05-27 10:28 ` [PATCH 2/5] dt-bindings: timer: Add SOPHGO SG2002 clint Thomas Bonnefille
2024-05-27 16:39 ` Conor Dooley
2024-05-27 10:28 ` [PATCH 3/5] dt-bindings: riscv: Add Sipeed LicheeRV Nano board compatibles Thomas Bonnefille
2024-05-27 16:40 ` Conor Dooley
2024-05-27 10:28 ` [PATCH 4/5] riscv: dts: sophgo: Add initial SG2002 SoC device tree Thomas Bonnefille
2024-05-27 10:28 ` [PATCH 5/5] riscv: dts: sophgo: Add LicheeRV Nano board " Thomas Bonnefille
2024-05-27 16:41 ` Conor Dooley
2024-05-27 18:12 ` Thomas Bonnefille
2024-05-27 22:25 ` Inochi Amaoto
2024-06-10 7:30 ` Thomas Bonnefille [this message]
2024-06-10 7:38 ` Inochi Amaoto
2024-05-29 0:57 ` kernel test robot
2024-05-28 17:41 ` [PATCH 0/5] Add board support for Sipeed LicheeRV Nano Rob Herring (Arm)
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=addbe5b3-04bc-4f02-be44-bdfe3aeba319@bootlin.com \
--to=thomas.bonnefille@bootlin.com \
--cc=aou@eecs.berkeley.edu \
--cc=chao.wei@sophgo.com \
--cc=conor+dt@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=inochiama@outlook.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.org \
--cc=samuel.holland@sifive.com \
--cc=tglx@linutronix.de \
--cc=thomas.petazzoni@bootlin.com \
--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