From: Krzysztof Kozlowski <krzk@kernel.org>
To: Prajna Rajendra Kumar <prajna.rajendrakumar@microchip.com>,
Mark Brown <broonie@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-riscv@lists.infradead.org, linux-spi@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Conor Dooley <conor.dooley@microchip.com>,
Daire McNamara <daire.mcnamara@microchip.com>,
Valentina Fernandez Alanis
<valentina.fernandezalanis@microchip.com>,
Cyril Jean <cyril.jean@microchip.com>
Subject: Re: [PATCH v1 2/3] spi: dt-binding: document Microchip CoreSPI
Date: Tue, 4 Nov 2025 10:23:02 +0100 [thread overview]
Message-ID: <015568df-63d8-45ed-bb21-b09fe323b528@kernel.org> (raw)
In-Reply-To: <20251103160515.412706-3-prajna.rajendrakumar@microchip.com>
On 03/11/2025 17:05, Prajna Rajendra Kumar wrote:
> Add device tree bindings for Microchip's CoreSPI controller.
>
> CoreSPI is a "soft" IP core intended for FPGA implementations. Its
> configurations are set in Libero. These properties represent
> non-discoverable configurations determined by Verilog parameters to the
> IP.
>
> Signed-off-by: Prajna Rajendra Kumar <prajna.rajendrakumar@microchip.com>
> ---
> .../bindings/spi/microchip,mpfs-spi.yaml | 65 +++++++++++++++++++
> 1 file changed, 65 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/spi/microchip,mpfs-spi.yaml b/Documentation/devicetree/bindings/spi/microchip,mpfs-spi.yaml
> index 62a568bdbfa0..62c38d0c93e7 100644
> --- a/Documentation/devicetree/bindings/spi/microchip,mpfs-spi.yaml
> +++ b/Documentation/devicetree/bindings/spi/microchip,mpfs-spi.yaml
> @@ -26,6 +26,7 @@ properties:
> - const: microchip,pic64gx-spi
> - const: microchip,mpfs-spi
> - const: microchip,mpfs-spi
> + - const: microchip,corespi-rtl-v5 # FPGA CoreSPI
Please keep alphabetical order. Or better, combine such (you have there
already!) into enum.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-11-04 9:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 16:05 [PATCH v1 0/3] Add support for Microchip CoreSPI Controller Prajna Rajendra Kumar
2025-11-03 16:05 ` [PATCH v1 1/3] spi: microchip: rename driver file and internal identifiers Prajna Rajendra Kumar
2025-11-04 8:46 ` Conor Dooley
2025-11-04 15:29 ` kernel test robot
2025-11-03 16:05 ` [PATCH v1 2/3] spi: dt-binding: document Microchip CoreSPI Prajna Rajendra Kumar
2025-11-04 8:48 ` Conor Dooley
2025-11-04 9:23 ` Krzysztof Kozlowski [this message]
2025-11-03 16:05 ` [PATCH v1 3/3] spi: add support for microchip "soft" spi controller Prajna Rajendra Kumar
2025-11-04 8:19 ` kernel test robot
2025-11-04 8:19 ` kernel test robot
2025-11-04 8:59 ` 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=015568df-63d8-45ed-bb21-b09fe323b528@kernel.org \
--to=krzk@kernel.org \
--cc=broonie@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=cyril.jean@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=linux-spi@vger.kernel.org \
--cc=prajna.rajendrakumar@microchip.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;
as well as URLs for NNTP newsgroup(s).