From: Guenter Roeck <linux@roeck-us.net>
To: Naga Sureshkumar Relli <naga.sureshkumar.relli@xilinx.com>
Cc: broonie@kernel.org, bbrezillon@kernel.org, vigneshr@ti.com,
linux-spi@vger.kernel.org, dwmw2@infradead.org,
marek.vasut@gmail.com, richard@nod.at,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
michal.simek@xilinx.com, nagasuresh12@gmail.com
Subject: Re: [LINUX PATCH v2 3/3] spi: spi-mem: Add support for Zynq QSPI controller
Date: Mon, 8 Apr 2019 10:51:57 -0700 [thread overview]
Message-ID: <20190408175157.GA11988@roeck-us.net> (raw)
In-Reply-To: <1554105553-20207-1-git-send-email-naga.sureshkumar.relli@xilinx.com>
On Mon, Apr 01, 2019 at 01:29:13PM +0530, Naga Sureshkumar Relli wrote:
> Add support for QSPI controller driver used by Xilinx Zynq SOC.
>
> Signed-off-by: Naga Sureshkumar Relli <naga.sureshkumar.relli@xilinx.com>
> ---
> Changes in v2
> - Updated the driver to call spi_mem_default_supports_op() from
> ctrl->supports_op()
> Changes in v1
> - Added COMPILE_TEST macro
> - converted MASKs to GENMASK() and BIT() macros
> - Renamed MODEBITS to ZYNQ_QSPI_MODEBITS
> - Removed checking buswidth() code, as it is already handled by framework
> - Updated in comments regarding baud rate calculation
> ---
> drivers/spi/Kconfig | 10 +-
> drivers/spi/Makefile | 1 +
> drivers/spi/spi-zynq-qspi.c | 761 ++++++++++++++++++++++++++++++++++++++++++++
> 3 files changed, 771 insertions(+), 1 deletion(-)
> create mode 100644 drivers/spi/spi-zynq-qspi.c
>
> diff --git a/drivers/spi/Kconfig b/drivers/spi/Kconfig
> index 9f89cb1..7bf7d38 100644
> --- a/drivers/spi/Kconfig
> +++ b/drivers/spi/Kconfig
> @@ -816,9 +816,17 @@ config SPI_XTENSA_XTFPGA
> 16 bit words in SPI mode 0, automatically asserting CS on transfer
> start and deasserting on end.
>
> +config SPI_ZYNQ_QSPI
> + tristate "Xilinx Zynq QSPI controller"
> + depends on ARCH_ZYNQ || COMPILE_TEST
This results in
drivers/spi/spi-zynq-qspi.c: In function 'zynq_qspi_write_op':
drivers/spi/spi-zynq-qspi.c:410:3: error: implicit declaration of function 'writesl'; did you mean 'writel'?
drivers/spi/spi-zynq-qspi.c: In function 'zynq_qspi_read_op':
drivers/spi/spi-zynq-qspi.c:436:3: error: implicit declaration of function 'readsl'; did you mean 'readl'?
when building allmodconfig/allyesconfig on architectures not supporting
writesl/readsl (such as alpha or parisc).
Guenter
prev parent reply other threads:[~2019-04-08 17:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 7:59 [LINUX PATCH v2 3/3] spi: spi-mem: Add support for Zynq QSPI controller Naga Sureshkumar Relli
2019-04-05 3:26 ` Applied "spi: spi-mem: Add support for Zynq QSPI controller" to the spi tree Mark Brown
2019-04-05 4:43 ` [LINUX PATCH v2 3/3] spi: spi-mem: Add support for Zynq QSPI controller Vignesh Raghavendra
2019-04-05 5:25 ` Naga Sureshkumar Relli
2019-04-05 6:15 ` Vignesh Raghavendra
2019-04-08 17:51 ` Guenter Roeck [this message]
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=20190408175157.GA11988@roeck-us.net \
--to=linux@roeck-us.net \
--cc=bbrezillon@kernel.org \
--cc=broonie@kernel.org \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=marek.vasut@gmail.com \
--cc=michal.simek@xilinx.com \
--cc=naga.sureshkumar.relli@xilinx.com \
--cc=nagasuresh12@gmail.com \
--cc=richard@nod.at \
--cc=vigneshr@ti.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).