From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Josua Mayer <josua@solid-run.com>, Andrew Lunn <andrew@lunn.ch>,
Gregory Clement <gregory.clement@bootlin.com>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: Yazan Shhady <yazan.shhady@solid-run.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] dt-bindings: arm64: marvell: add solidrun cn9130 clearfog boards
Date: Thu, 28 Mar 2024 10:14:19 +0100 [thread overview]
Message-ID: <539eaf79-cff5-4bb7-84c8-7c9943c6d8ae@linaro.org> (raw)
In-Reply-To: <1153cdd4-ed86-4a1f-ae4d-d9da1161f763@solid-run.com>
On 27/03/2024 11:55, Josua Mayer wrote:
>>
>> I don't even understand what is your case.
> I see :(
> Yes there is a disconnect *somewhere*.
>
Your way of quoting, including removing blank lines, weird wrapping,
does not make it easy to answer anything here. Use decent email client
which solves all these problems.
> I shall try again:
> Marvell is selling two chips:
> 1. CN9130, High-Performance Multi-Core CPU, System on Chip
> (can be used alone)
So this is the main SoC?
> 2. 88F8215, SouthBridge Communication Processor, System on Chip
> (only usable in combination with a CN9130)
>
> Now, in terms of compatible string, what happens when a board
> has multiples of these?
Multiple of CN9130? 2x CN9130? Nothing happens, does not really matter.
Anyway the compatible is just to uniquely identify the device for users,
not represent some programming model, because there is no programming
model of a board.
>
>> What is 9131 and 9132?
> I have no idea who came up with 9131 and 9132.
> But explanation is given by Grzegorz Jaszczyk <jaz@semihalf.com>
> when he submitted cn9131-db.dts (Marvell evaluation board):
>
> Extend the support of the CN9130 by adding an external CP115.
> The last number indicates how many external CP115 are used.
You use the compatibles in your patchset, so you should know, not me. I
have zero knowledge, also actually almost zero interest, in learning
your particular platform. I tried to fixup some bindings and maintainers
for Marvell: failed with not really helpful comments. Therefore I don't
care anymore about Marvell.
You or your platform maintainers should know what is this about and come
with explanation to the community.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-03-28 9:14 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 21:47 [PATCH 0/2] arm64: dts: add description for solidrun cn9130 som and clearfog boards Josua Mayer
2024-03-21 21:47 ` [PATCH 1/2] dt-bindings: arm64: marvell: add solidrun cn9130 " Josua Mayer
2024-03-22 2:16 ` Rob Herring
2024-03-22 10:08 ` Josua Mayer
2024-03-25 19:34 ` Krzysztof Kozlowski
2024-03-25 20:12 ` Josua Mayer
2024-03-26 6:41 ` Krzysztof Kozlowski
2024-03-26 19:26 ` Josua Mayer
2024-03-27 10:19 ` Krzysztof Kozlowski
2024-03-27 10:55 ` Josua Mayer
2024-03-28 9:14 ` Krzysztof Kozlowski [this message]
2024-03-28 9:33 ` Josua Mayer
2024-03-28 9:41 ` Krzysztof Kozlowski
2024-03-28 9:46 ` Josua Mayer
2024-03-28 16:22 ` Josua Mayer
2024-03-21 21:47 ` [PATCH 2/2] arm64: dts: add description for solidrun cn9130 som and " Josua Mayer
2024-03-21 21:59 ` Andrew Lunn
2024-03-22 9:54 ` Josua Mayer
2024-03-22 13:11 ` Andrew Lunn
2024-03-22 15:38 ` Josua Mayer
2024-03-22 15:49 ` Andrew Lunn
2024-03-22 15:58 ` Josua Mayer
2024-03-22 18:14 ` Josua Mayer
2024-03-22 18:27 ` Andrew Lunn
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=539eaf79-cff5-4bb7-84c8-7c9943c6d8ae@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=josua@solid-run.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=yazan.shhady@solid-run.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).