All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
To: Marek Vasut <marex@denx.de>,
	"u-boot@lists.denx.de" <u-boot@lists.denx.de>
Cc: Fabio Estevam <festevam@denx.de>, Peng Fan <peng.fan@nxp.com>,
	Stefano Babic <sbabic@denx.de>
Subject: Re: [PATCH] spi: nxp_fspi: Add i.MX8MP compatible string
Date: Mon, 14 Mar 2022 21:03:01 +0800	[thread overview]
Message-ID: <cc4a00fe-c01b-9b06-f2f6-a8ad3a36a79c@oss.nxp.com> (raw)
In-Reply-To: <20220309031857.134823-1-marex@denx.de>



On 2022/3/9 11:18, Marek Vasut wrote:
> The i.MX8M Mini and i.MX8M Plus flexspi IPs are compatible with one
> another, however the linux kernel DT uses separate compatible string
> for each SoC. Add the missing i.MX8MP compatible into this driver.
> 
> Signed-off-by: Marek Vasut <marex@denx.de>
> Cc: Fabio Estevam <festevam@denx.de>
> Cc: Peng Fan <peng.fan@nxp.com>
> Cc: Stefano Babic <sbabic@denx.de>

Reviewed-by: Peng Fan <peng.fan@nxp.com>
> ---
>   drivers/spi/nxp_fspi.c | 1 +
>   1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/spi/nxp_fspi.c b/drivers/spi/nxp_fspi.c
> index b7c922b1dfd..607c953987b 100644
> --- a/drivers/spi/nxp_fspi.c
> +++ b/drivers/spi/nxp_fspi.c
> @@ -1053,6 +1053,7 @@ static const struct dm_spi_ops nxp_fspi_ops = {
>   static const struct udevice_id nxp_fspi_ids[] = {
>   	{ .compatible = "nxp,lx2160a-fspi", .data = (ulong)&lx2160a_data, },
>   	{ .compatible = "nxp,imx8mm-fspi", .data = (ulong)&imx8mm_data, },
> +	{ .compatible = "nxp,imx8mp-fspi", .data = (ulong)&imx8mm_data, },
>   	{ }
>   };
>   
> 

  reply	other threads:[~2022-03-14 13:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-09  3:18 [PATCH] spi: nxp_fspi: Add i.MX8MP compatible string Marek Vasut
2022-03-14 13:03 ` Peng Fan (OSS) [this message]
2022-04-12 21:40 ` sbabic

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=cc4a00fe-c01b-9b06-f2f6-a8ad3a36a79c@oss.nxp.com \
    --to=peng.fan@oss.nxp.com \
    --cc=festevam@denx.de \
    --cc=marex@denx.de \
    --cc=peng.fan@nxp.com \
    --cc=sbabic@denx.de \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.