[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20251106-cable-generic-819b798c7068@spud>
Date: Thu, 6 Nov 2025 17:50:25 +0000
From: Conor Dooley <conor@...nel.org>
To: Mark Brown <broonie@...nel.org>
Cc: Prajna Rajendra Kumar <prajna.rajendrakumar@...rochip.com>,
Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
linux-riscv@...ts.infradead.org, linux-spi@...r.kernel.org,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
Conor Dooley <conor.dooley@...rochip.com>,
Daire McNamara <daire.mcnamara@...rochip.com>,
Valentina Fernandez Alanis <valentina.fernandezalanis@...rochip.com>,
Cyril Jean <cyril.jean@...rochip.com>
Subject: Re: [PATCH v2 3/3] spi: add support for microchip "soft" spi
controller
On Wed, Nov 05, 2025 at 04:18:30PM +0000, Mark Brown wrote:
> On Wed, Nov 05, 2025 at 03:28:23PM +0000, Prajna Rajendra Kumar wrote:
>
> > drivers/spi/Kconfig | 9 +
> > drivers/spi/Makefile | 1 +
> > drivers/spi/spi-microchip-core.c | 442 +++++++++++++++++++++++++++++++
> > 3 files changed, 452 insertions(+)
>
> > +config SPI_MICROCHIP_CORE
> > + tristate "Microchip FPGA SPI controllers"
> > + depends on SPI_MASTER
>
> Reusing the same filename and config symbol is almost certainly going to
> create issues and confusion for people upgrading their kernel or doing
> backports. Perhaps CoreSPI instead?
The qspi driver (which is shared between SoC and FPGA IP) uses
SPI_MICROCHIP_CORE_QSPI, so probably SPI_MICROCHIP_CORE_SPI should be
used here. Prajna?
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists