public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Valentina Fernandez <valentina.fernandezalanis@microchip.com>
Cc: conor.dooley@microchip.com, daire.mcnamara@microchip.com,
	paul.walmsley@sifive.com, palmer@dabbelt.com, robh@kernel.org,
	krzk+dt@kernel.org, aou@eecs.berkeley.edu, alex@ghiti.fr,
	linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v3 0/6] Icicle Kit with prod device and Discovery Kit support
Date: Wed, 10 Sep 2025 18:55:51 +0100	[thread overview]
Message-ID: <20250910-visa-fanfare-ec0bfa5c588c@spud> (raw)
In-Reply-To: <20250908115732.31092-1-valentina.fernandezalanis@microchip.com>

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

On Mon, Sep 08, 2025 at 12:57:26PM +0100, Valentina Fernandez wrote:
> Hi all,
> 
> With the introduction of the Icicle Kit with the production device
> (MPFS250T) to the market, it's necessary to distinguish it from the
> engineering sample (-es) variant. This is because engineering samples
> cannot write to flash from the MSS, as noted in the PolarFire SoC
> FPGA ES errata.
> 
> This series adds a common board DTSI for the Icicle Kit, containing
> hardware shared by both the engineering sample and production
> versions, as well as a DTS for each Icicle Kit variant.
> 
> The last two patches add support for the PolarFire SoC Discovery Kit
> board.
> 
> Changes since v2:
>  - rename ccc clock to clock-cccref to match fixed clock binding
> 
> Changes since v1:
>  - fix order of properties in mailbox nodes
>  - drop redundant status property from ddrc_cache nodes
>  - fix lowercase hex in reserved memory regions

I've replaced v1 with this version in my tree.

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

      parent reply	other threads:[~2025-09-10 17:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-08 11:57 [PATCH v3 0/6] Icicle Kit with prod device and Discovery Kit support Valentina Fernandez
2025-09-08 11:57 ` [PATCH v3 1/6] riscv: dts: microchip: add common board dtsi for icicle kit variants Valentina Fernandez
2025-09-08 11:57 ` [PATCH v3 2/6] dt-bindings: riscv: microchip: document icicle kit with production device Valentina Fernandez
2025-09-09  6:53   ` Krzysztof Kozlowski
2025-09-09  8:35     ` Conor Dooley
2025-09-08 11:57 ` [PATCH v3 3/6] riscv: dts: microchip: add " Valentina Fernandez
2025-09-08 11:57 ` [PATCH v3 4/6] riscv: dts: microchip: rename icicle kit ccc clock and other minor fixes Valentina Fernandez
2025-09-08 11:57 ` [PATCH v3 5/6] dt-bindings: riscv: microchip: document Discovery Kit Valentina Fernandez
2025-09-08 11:57 ` [PATCH v3 6/6] riscv: dts: microchip: add a device tree for " Valentina Fernandez
2025-09-10 17:55 ` Conor Dooley [this message]

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=20250910-visa-fanfare-ec0bfa5c588c@spud \
    --to=conor@kernel.org \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=conor.dooley@microchip.com \
    --cc=daire.mcnamara@microchip.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=robh@kernel.org \
    --cc=valentina.fernandezalanis@microchip.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