From: Frank Li <Frank.li@nxp.com>
To: haibo.chen@nxp.com
Cc: han.xu@nxp.com, yogeshgaur.83@gmail.com, broonie@kernel.org,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
shawnguo@kernel.org, s.hauer@pengutronix.de,
kernel@pengutronix.de, festevam@gmail.com,
singh.kuldeep87k@gmail.com, hs@denx.de,
linux-spi@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/6] few clean up for flexspi driver on imx8ulp and imx8mp
Date: Wed, 4 Sep 2024 11:17:32 -0400 [thread overview]
Message-ID: <Zth6DNhPt2EnFWAL@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <20240904111727.1834935-1-haibo.chen@nxp.com>
On Wed, Sep 04, 2024 at 07:17:21PM +0800, haibo.chen@nxp.com wrote:
> From: Haibo Chen <haibo.chen@nxp.com>
>
> PATCH1~3 clean up the redundant imx8mp compatible string
look through these 3 patches, look like we can't get much benefit and broke
compatibility, I think it is not worth. just leave as it and add 8ulp
support.
Frank
> PATCH4~5 add support on imx8ulp. The flexspi on imx8ulp has a difference
> with others, it only has 16 LUTs, while others all has upper to
> 32 LUTs. so add this distinguish in the driver.
>
> Haibo Chen (6):
> dt-bindings: spi: nxp-fspi: adjust imx8mp to compatible with imx8mm
> spi: nxp-fspi: remove the imx8mp compatible string
> arm64: dts: imx8mp: add the compatible string for flexspi
> dt-bindings: spi: nxp-fspi: add imx8ulp support
> spi: fspi: add support for imx8ulp
> arm64: dts: imx8ulp: correct the flexspi compatible string
>
> .../devicetree/bindings/spi/spi-nxp-fspi.yaml | 3 +-
> arch/arm64/boot/dts/freescale/imx8mp.dtsi | 2 +-
> arch/arm64/boot/dts/freescale/imx8ulp.dtsi | 2 +-
> drivers/spi/spi-nxp-fspi.c | 55 ++++++++++++-------
> 4 files changed, 39 insertions(+), 23 deletions(-)
>
> --
> 2.34.1
>
prev parent reply other threads:[~2024-09-04 15:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 11:17 [PATCH 0/6] few clean up for flexspi driver on imx8ulp and imx8mp haibo.chen
2024-09-04 11:17 ` [PATCH 1/6] dt-bindings: spi: nxp-fspi: adjust imx8mp to compatible with imx8mm haibo.chen
2024-09-04 11:17 ` [PATCH 2/6] spi: nxp-fspi: remove the imx8mp compatible string haibo.chen
2024-09-04 11:20 ` Marc Kleine-Budde
2024-09-04 16:31 ` Krzysztof Kozlowski
2024-09-04 17:47 ` Adam Ford
2024-09-04 11:17 ` [PATCH 3/6] arm64: dts: imx8mp: add the compatible string for flexspi haibo.chen
2024-09-04 11:17 ` [PATCH 4/6] dt-bindings: spi: nxp-fspi: add imx8ulp support haibo.chen
2024-09-04 11:17 ` [PATCH 5/6] spi: fspi: add support for imx8ulp haibo.chen
2024-09-04 11:17 ` [PATCH 6/6] arm64: dts: imx8ulp: correct the flexspi compatible string haibo.chen
2024-09-04 15:17 ` Frank Li [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=Zth6DNhPt2EnFWAL@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=haibo.chen@nxp.com \
--cc=han.xu@nxp.com \
--cc=hs@denx.de \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=singh.kuldeep87k@gmail.com \
--cc=yogeshgaur.83@gmail.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