devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Rogerio Pimentel <rpimentel.silva@gmail.com>,
	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,
	alexander.stein@ew.tq-group.com,
	dario.binacchi@amarulasolutions.com, marex@denx.de,
	Markus.Niebel@tq-group.com, y.moog@phytec.de,
	joao.goncalves@toradex.com, frieder.schrempf@kontron.de,
	josua@solid-run.com, francesco.dolcini@toradex.com,
	primoz.fiser@norik.com, imx@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, Xiaofeng Wei <xiaofeng.wei@nxp.com>
Subject: Re: [PATCH v4 2/2] arm64: dts: add support for NXP i.MX8MP FRDM board
Date: Mon, 10 Nov 2025 21:12:51 +0100	[thread overview]
Message-ID: <9d48a54c-0585-4524-b9d5-30696f5ecc8b@kernel.org> (raw)
In-Reply-To: <20251109214515.121742-2-rpimentel.silva@gmail.com>

On 09/11/2025 22:45, Rogerio Pimentel wrote:
> The FRDM-i.MX8MP is an NXP development platform based on the i.MX8M Plus
> SoC, featuring a quad Cortex-A53, Cortex-M7 co-processor, 4GB LPDDR4,
> 32GB eMMC, Wi-Fi 6/Bluetooth 5.4/802.15.4 tri-radio, Ethernet, HDMI/MIPI
> display interfaces, camera connectors, and standard expansion headers.
> 
> Based on the device tree found in the NXP repository at github
> https://github.com/nxp-imx-support/meta-imx-frdm and on imx8mp-evk
> board kernel mainline device tree.
> 
> This is a basic device tree supporting:
> 
>  - Quad Cortex-A53
>  - 4GB LPDDR4 DRAM
>  - PCA9450C PMIC with regulators
>  - Two NXP PCAL6416 GPIO expanders
>  - RGB LEDs via GPIO expander
>  - I2C1, I2C2, I2C3 controllers
>  - UART2 (console) and UART3 (with RTS/CTS)
>  - USDHC3 (8-bit eMMC)
>  - SNVS power key (onboard power button)
> 
> Signed-off-by: Rogerio Pimentel <rpimentel.silva@gmail.com>
> Signed-off-by: Xiaofeng Wei <xiaofeng.wei@nxp.com>

Incorrect DCO chain. Please look at submitting patches which explain
what is DCO and how it should be organized.

> ---
> 
> Changes in v4:




> +
> +	pinctrl_pmic: pmicgrp {
> +		fsl,pins = <
> +			MX8MP_IOMUXC_GPIO1_IO03__GPIO1_IO03	0x000001c0
> +		>;
> +	};
> +
> +	pinctrl_pcal6416_0_int: pcal6416_0_int_grp {


Don't use underscores in node names. See DTS coding style.

Best regards,
Krzysztof

  parent reply	other threads:[~2025-11-10 20:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-09 21:45 [PATCH v4 1/2] dt-bindings: arm: fsl: Add i.MX8MP FRDM board Rogerio Pimentel
2025-11-09 21:45 ` [PATCH v4 2/2] arm64: dts: add support for NXP " Rogerio Pimentel
2025-11-10  5:15   ` Joseph Guo
2025-11-10 19:26     ` Fabio Estevam
2025-11-11 10:22       ` Daniel Baluta
2025-11-10 20:14     ` Krzysztof Kozlowski
2025-11-10 20:12   ` Krzysztof Kozlowski [this message]
2025-11-11  8:47     ` Daniel Baluta
2025-11-11 11:50       ` Fabio Estevam
2025-11-11 12:49         ` Daniel Baluta
2025-11-12  8:15           ` Daniel Baluta
2025-11-12  9:08             ` Krzysztof Kozlowski
2025-11-12  9:14               ` Krzysztof Kozlowski
2025-11-12  9:32                 ` Daniel Baluta
2025-11-12  9:40                   ` Krzysztof Kozlowski
2025-11-12 12:35                     ` Daniel Baluta
2025-11-12 14:04                       ` Rogerio Pimentel
2025-11-12 14:24                         ` Krzysztof Kozlowski
2025-11-10  1:04 ` [PATCH v4 1/2] dt-bindings: arm: fsl: Add " 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=9d48a54c-0585-4524-b9d5-30696f5ecc8b@kernel.org \
    --to=krzk@kernel.org \
    --cc=Markus.Niebel@tq-group.com \
    --cc=alexander.stein@ew.tq-group.com \
    --cc=conor+dt@kernel.org \
    --cc=dario.binacchi@amarulasolutions.com \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=francesco.dolcini@toradex.com \
    --cc=frieder.schrempf@kontron.de \
    --cc=imx@lists.linux.dev \
    --cc=joao.goncalves@toradex.com \
    --cc=josua@solid-run.com \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marex@denx.de \
    --cc=primoz.fiser@norik.com \
    --cc=robh@kernel.org \
    --cc=rpimentel.silva@gmail.com \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --cc=xiaofeng.wei@nxp.com \
    --cc=y.moog@phytec.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;
as well as URLs for NNTP newsgroup(s).