public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
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>, Rob Herring <robh@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 v3 3/4] arm64: dts: add description for solidrun cn9130 som and clearfog boards
Date: Sun, 14 Apr 2024 15:30:56 +0200	[thread overview]
Message-ID: <12e2f3b7-6b2c-4fd2-a19e-d4802df95a71@linaro.org> (raw)
In-Reply-To: <8d0cd34c-ca04-45db-a95b-3bf5e3800958@solid-run.com>

On 14/04/2024 15:02, Josua Mayer wrote:
> Am 14.04.24 um 14:58 schrieb Josua Mayer:
>> Add description for the SolidRun CN9130 SoM, and Clearfog Base / Pro
>> reference boards.
>>
>> The SoM has been designed as a pin-compatible replacement for the older
>> Armada 388 based SoM. Therefore it supports the same boards and a
>> similar feature set.
>>
>> Most notable upgrades:
>> - 4x Cortex-A72
>> - 10Gbps SFP
>> - Both eMMC and SD supported at the same time
>>
>> The developer first supporting this product at SolidRun decided to use
>> different filenames for the DTBs: Armada 388 uses the full
>> "clearfog" string while cn9130 uses the abbreviation "cf".
>> This name is already hard-coded in pre-installed vendor u-boot and can
>> not be changed easily.
>>
>> NOTICE IN CASE ANYBODY WANTS TO SELF-UPGRADE:
>> CN9130 SoM has a different footprint from Armada 388 SoM.
>> Components on the carrier board below the SoM may collide causing
>> damage, such as on Clearfog Base.
>>
>> Signed-off-by: Josua Mayer <josua@solid-run.com>
>> ---
> 
> Previous version had received an ack from Krzysztof Kozlowski,
> which I dropped because I made additional changes.
> 
> To simplify review, please find below
> the incremental changes from v2 to v3:

If you send patches correctly, b4 gives diff, so no need for this diff here.

Best regards,
Krzysztof


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2024-04-14 13:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-14 12:58 [PATCH v3 0/4] arm64: dts: add description for solidrun cn9130 som and clearfog boards Josua Mayer
2024-04-14 12:58 ` [PATCH v3 1/4] dt-bindings: arm64: marvell: add solidrun cn9130 som based boards Josua Mayer
2024-04-22 13:38   ` Andrew Lunn
2024-04-14 12:58 ` [PATCH v3 2/4] dt-bindings: arm64: marvell: add solidrun cn9132 CEX-7 evaluation board Josua Mayer
2024-04-22 13:38   ` Andrew Lunn
2024-04-14 12:58 ` [PATCH v3 3/4] arm64: dts: add description for solidrun cn9130 som and clearfog boards Josua Mayer
2024-04-14 13:02   ` Josua Mayer
2024-04-14 13:30     ` Krzysztof Kozlowski [this message]
2024-04-22 13:38   ` Andrew Lunn
2024-04-14 12:58 ` [PATCH v3 4/4] arm64: dts: add description for solidrun cn9131 solidwan board Josua Mayer
2024-04-14 13:07   ` Josua Mayer
2024-04-14 13:18   ` Josua Mayer
2024-04-22 13:37     ` Andrew Lunn
2024-04-22 13:47       ` Josua Mayer
2024-04-26 18:18         ` Andrew Lunn
2024-04-26 18:51           ` Josua Mayer
2024-04-26 19:43             ` Andrew Lunn
2024-04-15 18:47 ` [PATCH v3 0/4] arm64: dts: add description for solidrun cn9130 som and clearfog boards Rob Herring

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=12e2f3b7-6b2c-4fd2-a19e-d4802df95a71@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=robh@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