public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Valentina Fernandez <valentina.fernandezalanis@microchip.com>,
	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 2/6] dt-bindings: riscv: microchip: document icicle kit with production device
Date: Tue, 9 Sep 2025 09:35:46 +0100	[thread overview]
Message-ID: <20250909-division-fetch-01bf5027f6d9@spud> (raw)
In-Reply-To: <20250909-accurate-wisteria-spider-222341@kuoka>

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

On Tue, Sep 09, 2025 at 08:53:05AM +0200, Krzysztof Kozlowski wrote:
> On Mon, Sep 08, 2025 at 12:57:28PM +0100, Valentina Fernandez wrote:
> > With the introduction of the Icicle Kit using the production MPFS250T
> > device, it's necessary to distinguish it from the engineering sample
> > (-es) variant. Engineering samples cannot write to flash from the MSS,
> > as noted in the PolarFire SoC FPGA ES errata.
> > 
> > Add specific compatibles for the Icicle Kit with Production device
> > (MPFS250T) and Icicle Kit with Engineering Sample (MPFS250T_ES).
> > 
> > The icicle kit reference designs in the v2025.07 release include the
> > Mi-V IHC IP v2, used to send/receive data between clusters when
> > using Asymmetric Multiprocessing (AMP) mode.
> > 
> > In reference design releases prior to v2025.07, the MI-V IHC subsystem
> > was included as a proof of concept in the design prior to becoming an
> > IP available in the Libero catalog.
> > 
> > Among other improvements, the new Mi-V IHC IP v2 includes some
> > changes to the register map. For this reason, make use of a new
> > reference design compatible to denote that v2025.07 reference design
> > releases are not backwards compatible.
> > 
> > Signed-off-by: Valentina Fernandez <valentina.fernandezalanis@microchip.com>
> > ---
> >  Documentation/devicetree/bindings/riscv/microchip.yaml | 8 ++++++++
> >  1 file changed, 8 insertions(+)
> 
> Why are you sending patches which are already applied? For two weeks?

That's probably my bad, I dropped the series when you had complaints
about the version that I applied and forgot to mention it.

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

  reply	other threads:[~2025-09-09  8:35 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 [this message]
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 ` [PATCH v3 0/6] Icicle Kit with prod device and Discovery Kit support Conor Dooley

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=20250909-division-fetch-01bf5027f6d9@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=krzk@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