From: Conor Dooley <conor@kernel.org>
To: 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,
Valentina Fernandez <valentina.fernandezalanis@microchip.com>
Cc: Conor Dooley <conor.dooley@microchip.com>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v1 0/5] Icicle Kit with prod device and Discovery Kit support
Date: Thu, 28 Aug 2025 17:14:30 +0100 [thread overview]
Message-ID: <20250828-aloft-procurer-7316559f2e30@spud> (raw)
In-Reply-To: <20250825161952.3902672-1-valentina.fernandezalanis@microchip.com>
From: Conor Dooley <conor.dooley@microchip.com>
On Mon, 25 Aug 2025 17:19:47 +0100, Valentina Fernandez wrote:
> 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.
>
> [...]
Applied to riscv-dt-for-next, thanks!
[1/5] riscv: dts: microchip: add common board dtsi for icicle kit variants
https://git.kernel.org/conor/c/2a95aaa34dfe
[2/5] dt-bindings: riscv: microchip: document icicle kit with production device
https://git.kernel.org/conor/c/4b9e63bb6491
[3/5] riscv: dts: microchip: add icicle kit with production device
https://git.kernel.org/conor/c/1ba401aae7a1
[4/5] dt-bindings: riscv: microchip: document Discovery Kit
https://git.kernel.org/conor/c/0d880b095a19
[5/5] riscv: dts: microchip: add a device tree for Discovery Kit
https://git.kernel.org/conor/c/f66eb149b876
Thanks,
Conor.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2025-08-28 19:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-25 16:19 [PATCH v1 0/5] Icicle Kit with prod device and Discovery Kit support Valentina Fernandez
2025-08-25 16:19 ` [PATCH v1 1/5] riscv: dts: microchip: add common board dtsi for icicle kit variants Valentina Fernandez
2025-08-25 16:19 ` [PATCH v1 2/5] dt-bindings: riscv: microchip: document icicle kit with production device Valentina Fernandez
2025-08-25 16:19 ` [PATCH v1 3/5] riscv: dts: microchip: add " Valentina Fernandez
2025-08-25 16:19 ` [PATCH v1 4/5] dt-bindings: riscv: microchip: document Discovery Kit Valentina Fernandez
2025-08-25 16:19 ` [PATCH v1 5/5] riscv: dts: microchip: add a device tree for " Valentina Fernandez
2025-08-28 17:46 ` Krzysztof Kozlowski
2025-09-01 15:28 ` Valentina.FernandezAlanis
2025-09-02 6:22 ` Krzysztof Kozlowski
2025-09-02 8:31 ` Conor Dooley
2025-09-02 13:47 ` Krzysztof Kozlowski
2025-09-02 16:38 ` Conor Dooley
2025-09-02 8:39 ` Valentina.FernandezAlanis
2025-08-28 16:14 ` 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=20250828-aloft-procurer-7316559f2e30@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