From: haibo.chen@nxp.com
To: 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
Cc: 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, haibo.chen@nxp.com
Subject: [PATCH v2 0/3] fix the flexspi error on imx8ulp
Date: Thu, 5 Sep 2024 09:26:14 +0800 [thread overview]
Message-ID: <20240905012617.1864997-1-haibo.chen@nxp.com> (raw)
From: Haibo Chen <haibo.chen@nxp.com>
The flexspi on imx8ulp only has 16 LUTs, different with others
which has 32 LUTs. So currently flexspi driver will write the
wrong register when fill LUT.
This patch set add a new compatible string for imx8ulp to
distinguish the LUT number.
Changes for V2:
- Remove the change for imx8mp, since this broken users
Haibo Chen (3):
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 | 1 +
arch/arm64/boot/dts/freescale/imx8ulp.dtsi | 2 +-
drivers/spi/spi-nxp-fspi.c | 54 ++++++++++++-------
3 files changed, 37 insertions(+), 20 deletions(-)
--
2.34.1
next reply other threads:[~2024-09-05 1:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 1:26 haibo.chen [this message]
2024-09-05 1:26 ` [PATCH v2 1/3] dt-bindings: spi: nxp-fspi: add imx8ulp support haibo.chen
2024-09-05 3:07 ` Frank Li
2024-09-05 6:43 ` Krzysztof Kozlowski
2024-09-05 1:26 ` [PATCH v2 2/3] spi: fspi: add support for imx8ulp haibo.chen
2024-09-05 1:38 ` Fabio Estevam
2024-09-05 1:49 ` Bough Chen
2024-09-05 3:03 ` Fabio Estevam
2024-09-05 3:05 ` Frank Li
2024-09-05 1:26 ` [PATCH v2 3/3] arm64: dts: imx8ulp: correct the flexspi compatible string haibo.chen
2024-09-05 3:08 ` Frank Li
2024-09-05 3:22 ` Bough Chen
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=20240905012617.1864997-1-haibo.chen@nxp.com \
--to=haibo.chen@nxp.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.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