mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Joacim Zetterling <joacim.zetterling@westermo.com>,
	barebox@lists.infradead.org
Subject: Re: [PATCH 1/1] ARM: imx: spi: Add NXP IMX8 Flex SPI/QSPI support
Date: Mon, 28 Feb 2022 18:06:22 +0100	[thread overview]
Message-ID: <8f7d5e59-37ff-9d78-6ad4-ec904201cddb@pengutronix.de> (raw)
In-Reply-To: <20220228165733.247646-1-joacim.zetterling@westermo.com>

Hello Joacim,

On 28.02.22 17:57, Joacim Zetterling wrote:
> This driver is ported from the linux kernel and adapted to barebox
> for the NXP IMX8 platforms.
> 
> This commit add support for the NXP IMX8 Flex SPI controller in master
> mode. Up to four slave devices can be connected on two buses with two
> chip selects each. This controller does not support generic SPI messages
> and only supports the high-level SPI memory interface.
> 
> Tested on the NXP IMX8MN-EVK evaluation board as well as on a 
> IMX8MN custom board supporting a Micron N25Q00 QSPI flash.

I haven't reviewed the driver itself, but some general feedback below.

> 
> Signed-off-by: Joacim Zetterling <joacim.zetterling@westermo.com>
> ---
>  drivers/spi/Kconfig                |   10 +
>  drivers/spi/Makefile               |    1 +
>  drivers/spi/spi-nxp-fspi.c         | 1061 ++++++++++++++++++++++++++++
>  dts/Bindings/spi/spi-nxp-fspi.yaml |    1 +
>  4 files changed, 1073 insertions(+)
>  create mode 100644 drivers/spi/spi-nxp-fspi.c
> 
> diff --git a/drivers/spi/Kconfig b/drivers/spi/Kconfig
> index b0137d21e073..f7e92665d5a8 100644
> --- a/drivers/spi/Kconfig
> +++ b/drivers/spi/Kconfig
> @@ -114,6 +114,16 @@ config DRIVER_SPI_STM32
>  	  Enable the STM32 Serial Peripheral Interface (SPI) driver for STM32MP
>  	  SoCs.
>  
> +config SPI_NXP_FLEXSPI
> +	tristate "NXP Flex SPI controller"
> +	depends on ARCH_IMX8M || HAS_IOMEM

HAS_IOMEM doesn't exist in barebox. You can replace this with COMPILE_TEST

> diff --git a/dts/Bindings/spi/spi-nxp-fspi.yaml b/dts/Bindings/spi/spi-nxp-fspi.yaml
> index 283815d59e85..62930d0cf43f 100644
> --- a/dts/Bindings/spi/spi-nxp-fspi.yaml
> +++ b/dts/Bindings/spi/spi-nxp-fspi.yaml
> @@ -17,6 +17,7 @@ properties:
>      enum:
>        - nxp,imx8dxl-fspi
>        - nxp,imx8mm-fspi
> +      - nxp,imx8mn-fspi
>        - nxp,imx8mp-fspi
>        - nxp,imx8qxp-fspi
>        - nxp,lx2160a-fspi

dts/ is imported from Linux as-is. You shouldn't edit stuff there.

Cheers,
Ahmad

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox


      reply	other threads:[~2022-02-28 17:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-28 16:57 Joacim Zetterling
2022-02-28 17:06 ` Ahmad Fatoum [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=8f7d5e59-37ff-9d78-6ad4-ec904201cddb@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=joacim.zetterling@westermo.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