From: Bough Chen <haibo.chen@oss.nxp.com>
To: Alexander Stein <alexander.stein@ew.tq-group.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Frank Li <Frank.Li@nxp.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Markus Niebel <Markus.Niebel@ew.tq-group.com>,
linux@ew.tq-group.com, devicetree@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] arm64: dts: imx8mm-tqma8mqml: restrict clock for SPI-NOR flash
Date: Thu, 8 Oct 2026 16:34:27 +0800 [thread overview]
Message-ID: <20261008083427.33iide6apbktyv6p@shlinux89> (raw)
In-Reply-To: <20261007072017.2311818-1-alexander.stein@ew.tq-group.com>
On Wed, Oct 07, 2026 at 09:20:13AM +0200, Alexander Stein wrote:
> From: Markus Niebel <Markus.Niebel@ew.tq-group.com>
>
> The FlexSPI controller uses quad SPI with internal clock recovery.
> The i.MX 8M Mini Applications Processor Datasheet for Industrial Products,
> Rev. 2, 11/2022 lists a maximum FlexSPI frequency of 66.666666 MHz for
> that mode.
>
> Fixes: dfcd1b6f7620 ("arm64: dts: freescale: add initial device tree for TQMa8MQML with i.MX8MM")
There is already one patch to limit the clock rate based on SoCs, refer to:
https://patch.msgid.link/20260728-fspi-clock-v2-1-dbe786a4a6eb@nxp.com
I think the max frequency in the DTS flash node should describe only the
SPI NOR device limitation, not the host limitation.
Regards
Haibo Chen
> Signed-off-by: Markus Niebel <Markus.Niebel@ew.tq-group.com>
> Signed-off-by: Alexander Stein <alexander.stein@ew.tq-group.com>
> ---
> Changes in v2:
> * Clarify which datasheet is referred to
> * Add Fixes tag
>
> arch/arm64/boot/dts/freescale/imx8mm-tqma8mqml.dtsi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm64/boot/dts/freescale/imx8mm-tqma8mqml.dtsi b/arch/arm64/boot/dts/freescale/imx8mm-tqma8mqml.dtsi
> index 1b5ba3c47164f..48285bcbe9bbb 100644
> --- a/arch/arm64/boot/dts/freescale/imx8mm-tqma8mqml.dtsi
> +++ b/arch/arm64/boot/dts/freescale/imx8mm-tqma8mqml.dtsi
> @@ -60,7 +60,7 @@ &flexspi {
> flash0: flash@0 {
> compatible = "jedec,spi-nor";
> reg = <0>;
> - spi-max-frequency = <84000000>;
> + spi-max-frequency = <66666666>;
> spi-tx-bus-width = <1>;
> spi-rx-bus-width = <4>;
> vcc-supply = <&buck5_reg>;
> --
> 2.55.0
>
next prev parent reply other threads:[~2026-10-08 8:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 7:20 Alexander Stein
2026-10-07 7:20 ` [PATCH v2 2/3] arm64: dts: imx8mn-tqma8mqnl: " Alexander Stein
2026-10-07 7:20 ` [PATCH v2 3/3] arm64: dts: imx8mp-tqma8mpql: " Alexander Stein
2026-10-08 8:34 ` Bough Chen [this message]
2026-10-08 9:18 ` [PATCH v2 1/3] arm64: dts: imx8mm-tqma8mqml: " Alexander Stein
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=20261008083427.33iide6apbktyv6p@shlinux89 \
--to=haibo.chen@oss.nxp.com \
--cc=Frank.Li@nxp.com \
--cc=Markus.Niebel@ew.tq-group.com \
--cc=alexander.stein@ew.tq-group.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--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@ew.tq-group.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®