From: Conor Dooley <conor@kernel.org>
To: Alex Elder <elder@riscstar.com>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
Guodong Xu <guodong@riscstar.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Emil Renner Berthing <kernel@esmil.dk>,
rafal@milecki.pl, Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Neil Armstrong <neil.armstrong@linaro.org>,
Heiko Stuebner <heiko.stuebner@cherry.de>,
Michael Zhu <michael.zhu@starfivetech.com>,
Drew Fustini <drew@beagleboard.org>,
Alexandru Stan <ams@frame.work>, Daniel Schaefer <dhs@frame.work>,
Sandie Cao <sandie.cao@deepcomputing.io>,
Yuning Liang <yuning.liang@deepcomputing.io>,
Huiming Qiu <huiming.qiu@deepcomputing.io>,
linux@frame.work, devicetree@vger.kernel.org,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 3/3] riscv: dts: starfive: add DeepComputing FML13V01 board device tree
Date: Mon, 21 Oct 2024 17:48:22 +0100 [thread overview]
Message-ID: <20241021-crimson-translate-291eaba4e640@spud> (raw)
In-Reply-To: <2b449955-6596-4c9a-9799-f15d186e260f@riscstar.com>
[-- Attachment #1: Type: text/plain, Size: 2614 bytes --]
On Mon, Oct 21, 2024 at 08:44:16AM -0500, Alex Elder wrote:
> On 10/21/24 7:47 AM, Krzysztof Kozlowski wrote:
> > On 21/10/2024 13:16, Conor Dooley wrote:
> > > On Mon, Oct 21, 2024 at 09:17:59AM +0200, Krzysztof Kozlowski wrote:
> > > > On Sun, Oct 20, 2024 at 09:49:59PM +0800, Guodong Xu wrote:
> > > > > From: Sandie Cao <sandie.cao@deepcomputing.io>
> > > > > +&camss {
> > > > > + status = "disabled";
> > > > > +};
> > > > > +
> > > > > +&csi2rx {
> > > > > + status = "disabled";
> > > > > +};
> > >
> > > You can drop these two, I marked them disabled in the common file
> > > earlier this week.
> > > 1
> > > > > +
> > > > > +&gmac0 {
> > > > > + status = "disabled";
> > > > > +};
> > > > > +
> > > > > +&i2c0 {
> > > > > + status = "disabled";
> > > > > +};
> > > > > +
> > > > > +&pwm {
> > > > > + status = "disabled";
> > > > > +};
> > > > > +
> > > > > +&pwmdac {
> > > > > + status = "disabled";
> > > > > +};
> > > > > +
> > > > > +&spi0 {
> > > > > + status = "disabled";
> > > >
> > > > If your board has to disable all these, then they should not have been
> > > > enabled in DTSI in the first place. Only blocks present and working in
> > > > the SoC (without amny external needs) should be enabled.
> > > >
> > > > I suggest to fix that aspect first.
> > >
> > > Eh, I don't think I agree. Having 5 disables here is a lesser evil than
> > > reproducing 90% of jh7110-common.dtsi or shunting a bunch of stuff
> > > around. Emil?
> >
> > Why reproducing 90%? Only enable would be here, no? Or you want to say
> > the common DTSI has things which do not exist?
>
> For what it's worth, I agree with Krzysztof. In the (long) cover
> page we pointed this out, and offered to do it in a followup patch.
> But if requested we can do it now.
>
> So in v6, a new patch would be inserted before the other three,
> and it would:
> - Remove the status = "okay" lines for those nodes that are not enabled
> in this new platform, in "jh7110-common.dtsi"
> - Add nodes where appropriate in:
> jh7110-milkv-mars.dts
> jh7110-pine64-star64.dts
> jh7110-starfive-visionfive-2.dtsi
> They'll look like this, to enable the ones disabled above, e.g.:
> &gmac0 {
> status = "okay";
> };
>
> &i2c0 {
> status = "okay";
> };
>
> You guys should come to agreement, but I do think what Krzysztof says
> is the right approach. And unless convinced otherwise, this will be
> what shows up in the next version of this series.
Ultimately, it is up to Emil how he wants these laid out.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-10-21 16:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-20 13:49 [PATCH v5 0/3] Add DeepComputing FML13V01 board dts Guodong Xu
2024-10-20 13:49 ` [PATCH v5 1/3] dt-bindings: vendor: add deepcomputing Guodong Xu
2024-10-20 13:49 ` [PATCH v5 2/3] dt-bindings: riscv: starfive: add deepcomputing,fml13v01 Guodong Xu
2024-10-23 16:38 ` Emil Renner Berthing
2024-10-20 13:49 ` [PATCH v5 3/3] riscv: dts: starfive: add DeepComputing FML13V01 board device tree Guodong Xu
2024-10-21 7:17 ` Krzysztof Kozlowski
2024-10-21 11:16 ` Conor Dooley
2024-10-21 12:47 ` Krzysztof Kozlowski
2024-10-21 13:44 ` Alex Elder
2024-10-21 16:48 ` Conor Dooley [this message]
2024-10-23 16:49 ` Emil Renner Berthing
2024-10-23 17:20 ` Alex Elder
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=20241021-crimson-translate-291eaba4e640@spud \
--to=conor@kernel.org \
--cc=ams@frame.work \
--cc=aou@eecs.berkeley.edu \
--cc=devicetree@vger.kernel.org \
--cc=dhs@frame.work \
--cc=drew@beagleboard.org \
--cc=elder@riscstar.com \
--cc=gregkh@linuxfoundation.org \
--cc=guodong@riscstar.com \
--cc=heiko.stuebner@cherry.de \
--cc=huiming.qiu@deepcomputing.io \
--cc=kernel@esmil.dk \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux@frame.work \
--cc=michael.zhu@starfivetech.com \
--cc=neil.armstrong@linaro.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=rafal@milecki.pl \
--cc=robh@kernel.org \
--cc=sandie.cao@deepcomputing.io \
--cc=yuning.liang@deepcomputing.io \
/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