From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from devils.ext.ti.com ([198.47.26.153]) by bombadil.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1aIqmQ-0008Ns-3y for linux-mtd@lists.infradead.org; Tue, 12 Jan 2016 04:42:02 +0000 Subject: Re: [PATCH V10 2/2] mtd: spi-nor: Add driver for Cadence Quad SPI Flash Controller. To: Marek Vasut References: <1452486886-8049-1-git-send-email-marex@denx.de> <1452486886-8049-2-git-send-email-marex@denx.de> <5693D3B4.2090304@opensource.altera.com> CC: Dinh Nguyen , "linux-mtd@lists.infradead.org" , Graham Moore , Alan Tull , Brian Norris , David Woodhouse , Yves Vandervennet , "devicetree@vger.kernel.org" From: Vignesh R Message-ID: <569483DE.4070901@ti.com> Date: Tue, 12 Jan 2016 10:11:02 +0530 MIME-Version: 1.0 In-Reply-To: <5693D3B4.2090304@opensource.altera.com> Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On 01/11/2016 09:39 PM, Dinh Nguyen wrote: > On 01/10/2016 10:34 PM, Marek Vasut wrote: >> From: Graham Moore >> >> Add support for the Cadence QSPI controller. This controller is >> present in the Altera SoCFPGA SoCs and this driver has been tested >> on the Cyclone V SoC. >> [...] >> diff --git a/drivers/mtd/spi-nor/Kconfig b/drivers/mtd/spi-nor/Kconfig >> index 43bafde..7e29050 100644 >> --- a/drivers/mtd/spi-nor/Kconfig >> +++ b/drivers/mtd/spi-nor/Kconfig >> @@ -50,4 +50,15 @@ config SPI_NXP_SPIFI >> Flash. Enable this option if you have a device with a SPIFI >> controller and want to access the Flash as a mtd device. >> >> +config SPI_CADENCE_QUADSPI >> + tristate "Cadence Quad SPI controller" >> + depends on OF && (ARCH_SOCFPGA || COMPILE_TEST) > > I think you can remove the ARCH_SOCFPGA dependency as this driver is > used on a TI EVM as well. I think above usage is correct. This will enable SPI_CADENCE_QUADSPI to be selected when ARCH_SOCFPGA=y without having to enable COMPILE_TEST. AFAIK, COMPILE_TEST is used usually to build test the driver w/o having to enable ARCH specific configs (usually by maintainers). For TI EVM, I would patch this file to add my architecture later(i.e along with DT patch to my board). -- Regards Vignesh