U-boot Archive mirror
 help / color / mirror / Atom feed
From: Frieder Schrempf <frieder@fris.de>
To: Jagan Teki <jagan@amarulasolutions.com>
Cc: Frieder Schrempf <frieder.schrempf@kontron.de>,
	Aaron Williams <awilliams@marvell.com>,
	Daniel Schwierzeck <daniel.schwierzeck@gmail.com>,
	Lukasz Majewski <lukma@denx.de>,
	Pengpeng Chen <pengpeng.chen@cortina-access.com>,
	"SkyLake.Huang" <skylake.huang@mediatek.com>,
	Stefan Roese <sr@denx.de>,
	Suneel Garapati <sgarapati@marvell.com>,
	u-boot@lists.denx.de, Weijie Gao <weijie.gao@mediatek.com>
Subject: [PATCH 2/6] spi: fsl_qspi: Build driver only if DM_SPI is available
Date: Mon,  7 Jun 2021 14:05:09 +0200	[thread overview]
Message-ID: <20210607120534.183091-3-frieder@fris.de> (raw)
In-Reply-To: <20210607120534.183091-1-frieder@fris.de>

From: Frieder Schrempf <frieder.schrempf@kontron.de>

The driver depends on DM_SPI and if it's not available (e. g. in SPL),
then we should not try to build it as this will fail.

Signed-off-by: Frieder Schrempf <frieder.schrempf@kontron.de>
---
 drivers/spi/Makefile | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/spi/Makefile b/drivers/spi/Makefile
index cfe4fae1d4..2eb9267ce9 100644
--- a/drivers/spi/Makefile
+++ b/drivers/spi/Makefile
@@ -11,6 +11,7 @@ obj-$(CONFIG_SANDBOX) += spi-emul-uclass.o
 obj-$(CONFIG_SOFT_SPI) += soft_spi.o
 obj-$(CONFIG_SPI_MEM) += spi-mem.o
 obj-$(CONFIG_TI_QSPI) += ti_qspi.o
+obj-$(CONFIG_FSL_QSPI) += fsl_qspi.o
 else
 obj-y += spi.o
 obj-$(CONFIG_SPI_MEM) += spi-mem-nodm.o
@@ -30,7 +31,6 @@ obj-$(CONFIG_DESIGNWARE_SPI) += designware_spi.o
 obj-$(CONFIG_EXYNOS_SPI) += exynos_spi.o
 obj-$(CONFIG_FSL_DSPI) += fsl_dspi.o
 obj-$(CONFIG_FSL_ESPI) += fsl_espi.o
-obj-$(CONFIG_FSL_QSPI) += fsl_qspi.o
 obj-$(CONFIG_ICH_SPI) +=  ich.o
 obj-$(CONFIG_KIRKWOOD_SPI) += kirkwood_spi.o
 obj-$(CONFIG_MESON_SPIFC) += meson_spifc.o
-- 
2.25.1


  parent reply	other threads:[~2021-06-07 12:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-07 12:05 [PATCH 0/6] Add support for Kontron i.MX6UL/ULL and i.MX8MM modules/boards Frieder Schrempf
2021-06-07 12:05 ` [PATCH 1/6] mtd: spi-nor-ids: Add support for Macronix MX25V8035F and MX25R1635F Frieder Schrempf
2021-06-07 12:05 ` Frieder Schrempf [this message]
2021-06-07 12:05 ` [PATCH 3/6] clk: imx8mm: Add SPI clocks Frieder Schrempf
2021-06-08  9:33   ` Lukasz Majewski
2021-06-07 12:05 ` [PATCH 4/6] imx8m: Restrict usable memory to space below 4G boundary Frieder Schrempf
2021-06-07 12:38   ` Marek Vasut
2021-06-15  0:28     ` Peng Fan (OSS)
2021-06-15  0:41       ` Marek Vasut
2021-07-13  9:25         ` Frieder Schrempf
2021-07-13 10:31           ` Marek Vasut
2021-06-07 12:05 ` [PATCH 5/6] imx: imx6ul: Add support for Kontron Electronics SL/BL i.MX6UL/ULL boards (N63xx/N64xx) Frieder Schrempf
2021-06-10  8:40   ` Stefano Babic
2021-06-07 12:05 ` [PATCH 6/6] imx: imx8mm: Add support for Kontron Electronics SL/BL i.MX8M-Mini boards (N801x) Frieder Schrempf

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=20210607120534.183091-3-frieder@fris.de \
    --to=frieder@fris.de \
    --cc=awilliams@marvell.com \
    --cc=daniel.schwierzeck@gmail.com \
    --cc=frieder.schrempf@kontron.de \
    --cc=jagan@amarulasolutions.com \
    --cc=lukma@denx.de \
    --cc=pengpeng.chen@cortina-access.com \
    --cc=sgarapati@marvell.com \
    --cc=skylake.huang@mediatek.com \
    --cc=sr@denx.de \
    --cc=u-boot@lists.denx.de \
    --cc=weijie.gao@mediatek.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 read-only IMAP folder(s) and NNTP newsgroup(s).