public inbox for soc@kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>,
	E Shattow <e@freeshell.de>,
	soc@kernel.org, linux-riscv@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	Hal Feng <hal.feng@starfivetech.com>,
	Ilya Sorochan <k0tran@altlinux.org>
Subject: Re: [GIT PULL] ~RISC-V~Starfive devicetrees fixes for v7.0-rc6
Date: Fri, 27 Mar 2026 12:16:41 +0000	[thread overview]
Message-ID: <20260327-duress-swoop-81695580967f@spud> (raw)
In-Reply-To: <8c411e55-7043-4987-bd6b-cb5b139902c5@kernel.org>

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

On Fri, Mar 27, 2026 at 11:50:39AM +0100, Krzysztof Kozlowski wrote:
> On 27/03/2026 10:49, Krzysztof Kozlowski wrote:
> > On 27/03/2026 10:45, Conor Dooley wrote:
> >>
> >>> The commit touches only DTS, not DTSO, so how can you claim that a DTS
> >>> file change breaks some completely other board (Raspberry)?
> >>>
> >>> This DTS file is nowhere included (and should not be).
> >>>
> >>> Of course maybe the true question would be why anyone described a hat as
> >>> DTS file...
> >>>
> >>>>
> >>>> E. we know that by chance you have found a base board that ignores the 
> >>>> standard.
> >>>>
> >>>> Your patch 4cce8b2503ab5 made my standard compliant baseboard unusable. 
> >>>
> >>> DTS of some board is a final product, so it cannot be applied to a
> >>> baseboard, that's pretty messed DTS tree...
> >>
> >> The cm-lite is a rpi compute module compatible device, the base boards
> >> don't have any devices on them in a lot of cases and just provide
> >> physical connectors, so there's no point having a distinct dts for every
> >> baseboard of that type.
> >> https://www.waveshare.com/product/cm4-io-base-a.htm
> >>
> > I saw the picture and it looked like it should never be a DTS, because
> > it is not usable on its own. You cannot run it.
> 
> 
> ... although what I found earlier was different. I typed the model name
> from DTS "Milk-V Mars CM Lite" and it gave me this:
> 
> https://milkv.io/mars-cm
> which misses the "Lite" suffix.

Lite is the same thing without an emmc.

> 
> What you pasted is called "Mini Base Board (A) Designed for Raspberry Pi
> Compute Module 4" and it also does not have "Lite" in the name and
> picture does not have the SoM.
> 
> I am confused now and I do not know what the DTS "Milk-V Mars CM Lite"
> is. Answering to this is crucial, because it determines whether this
> particular deviec has broken-cd or not.

It's an Raspberry Pi compatible SoM, what you linked.
I was linking to the kind of base-board that Heinrich has, to show that
it pretty much is a connector to the SoM and the physical connectors for
ethernet etc and nothing else on the board.

The dts was done the way it was, IIRC, to permit using overlays on top
of the $som.dts file to describe the minor differences between the
pretty trivial I/O boards, such as the one I linked to or the standard
RPi one: https://www.raspberrypi.com/products/compute-module-4-io-board/

It's akin to having "jh7110-milkv-marscm-lite-generic-trivial-base-board.dts"
which I think isn't problematic. There's a jh7110-milkv-marscm.dtsi that
is what actually describes the bulk of the SoM.

> Arguments that something else has broken-cd, thus you add such property
> to "Milk-V Mars CM Lite" are obviously wrong.

The argument is that "broken-cd" is the standard for RPi compute module
baseboards, so the rare baseboard that doesn't do that is the one which
would have to use an overlay to function.
I think that that is the right approach to take, in a world where having
a dts for the SoM is permitted.

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

  reply	other threads:[~2026-03-27 12:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-26 11:13 [GIT PULL] ~RISC-V~Starfive devicetrees fixes for v7.0-rc6 Conor Dooley
2026-03-26 14:36 ` E Shattow
2026-03-26 15:14   ` Conor Dooley
2026-03-26 15:44     ` Heinrich Schuchardt
2026-03-26 19:27       ` Ilya Sorochan
2026-03-27  4:53         ` E Shattow
2026-03-27  8:52           ` Ilya Sorochan
2026-03-28 10:07             ` E Shattow
2026-03-30  9:24               ` Ilya Sorochan
2026-03-27  8:19       ` Krzysztof Kozlowski
2026-03-27  9:45         ` Conor Dooley
2026-03-27  9:49           ` Krzysztof Kozlowski
2026-03-27 10:50             ` Krzysztof Kozlowski
2026-03-27 12:16               ` Conor Dooley [this message]
2026-03-28  4:22                 ` E Shattow

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=20260327-duress-swoop-81695580967f@spud \
    --to=conor@kernel.org \
    --cc=e@freeshell.de \
    --cc=hal.feng@starfivetech.com \
    --cc=heinrich.schuchardt@canonical.com \
    --cc=k0tran@altlinux.org \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=soc@kernel.org \
    /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