From: Fabio Estevam <festevam@gmail.com>
To: Frank Li <Frank.Li@nxp.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"open list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<imx@lists.linux.dev>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/3] arm64: dts: imx8qm-mek: add flexspi0 support
Date: Mon, 26 Feb 2024 17:38:16 -0300 [thread overview]
Message-ID: <CAOMZO5CoucMLo2T7z25EpBeakmKt38jis-_OC1-_C1vGtXEwWw@mail.gmail.com> (raw)
In-Reply-To: <20240226203358.275986-3-Frank.Li@nxp.com>
On Mon, Feb 26, 2024 at 5:34 PM Frank Li <Frank.Li@nxp.com> wrote:
> +&flexspi0 {
> + pinctrl-names = "default";
> + pinctrl-0 = <&pinctrl_flexspi0>;
> + nxp,fspi-dll-slvdly = <4>;
> + status = "okay";
> +
> + flash0: mt35xu512aba@0 {
Node names should be generic.
Please run dt-schema checks. Otherwise, you will introduce more warnings.
next prev parent reply other threads:[~2024-02-26 20:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 20:33 [PATCH 1/3] arm64: dts: imx8qm-mek: add adc0 support Frank Li
2024-02-26 20:33 ` [PATCH 2/3] arm64: dts: imx8qm-mek: add lpspi2 support Frank Li
2024-02-26 20:33 ` [PATCH 3/3] arm64: dts: imx8qm-mek: add flexspi0 support Frank Li
2024-02-26 20:38 ` Fabio Estevam [this message]
2024-02-27 7:42 ` Alexander Stein
2024-02-27 13:44 ` [PATCH 1/3] arm64: dts: imx8qm-mek: add adc0 support Rob Herring
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=CAOMZO5CoucMLo2T7z25EpBeakmKt38jis-_OC1-_C1vGtXEwWw@mail.gmail.com \
--to=festevam@gmail.com \
--cc=Frank.Li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).