From: Krzysztof Kozlowski <krzk@kernel.org>
To: Frank Li <Frank.Li@nxp.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
"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 1/4] arm64: dts: imx95-19x19-evk: add adc0 flexcan[1,2] i2c[2,3] uart5 spi3 and tpm3
Date: Thu, 5 Jun 2025 07:51:28 +0200 [thread overview]
Message-ID: <7d4ec7c9-c95a-4e7e-9750-f6310ecb59fc@kernel.org> (raw)
In-Reply-To: <20250604200301.1192096-1-Frank.Li@nxp.com>
On 04/06/2025 22:02, Frank Li wrote:
> + num-cs = <1>;
> + pinctrl-names = "default";
> + pinctrl-0 = <&pinctrl_lpspi7>;
> + cs-gpios = <&gpio2 4 GPIO_ACTIVE_LOW>;
> + status = "okay";
> +
> + spidev0: spi@0 {
> + reg = <0>;
> + compatible = "lwn,bk4-spi";
NAK
You do not have big excavator attached to your eval kit. Don't add fake,
non-existing or incorrect nodes.
Best regards,
Krzysztof
prev parent reply other threads:[~2025-06-05 5:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-04 20:02 [PATCH 1/4] arm64: dts: imx95-19x19-evk: add adc0 flexcan[1,2] i2c[2,3] uart5 spi3 and tpm3 Frank Li
2025-06-04 20:02 ` [PATCH 2/4] arm64: dts: imx95-evk: add USB3 PHY tuning properties Frank Li
2025-06-04 20:03 ` [PATCH 3/4] arm64: dts: imx95-19x19-evk: adjust pinctrl settings for usdhc2 Frank Li
2025-06-04 20:03 ` [PATCH 4/4] arm64: dts: imx95-19x19-evk: add GPIO reset for ethphy0 Frank Li
2025-06-05 1:51 ` [PATCH 1/4] arm64: dts: imx95-19x19-evk: add adc0 flexcan[1,2] i2c[2,3] uart5 spi3 and tpm3 Fabio Estevam
2025-06-05 5:51 ` Krzysztof Kozlowski [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=7d4ec7c9-c95a-4e7e-9750-f6310ecb59fc@kernel.org \
--to=krzk@kernel.org \
--cc=Frank.Li@nxp.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=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