Linux kernel and device drivers for NXP i.MX platforms
 help / color / mirror / Atom feed
From: "Rob Herring (Arm)" <robh@kernel.org>
To: Frank Li <Frank.Li@nxp.com>
Cc: devicetree@vger.kernel.org, imx@lists.linux.dev,
	Conor Dooley <conor+dt@kernel.org>,
	Fabio Estevam <festevam@gmail.com>,
	linux-arm-kernel@lists.infradead.org,
	Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] dt-bindings: fsl: convert m4if.txt and tigerp.txt to yaml format
Date: Tue, 22 Apr 2025 07:56:54 -0500	[thread overview]
Message-ID: <174532661282.962885.3469691185487125433.robh@kernel.org> (raw)
In-Reply-To: <20250417150608.3569512-1-Frank.Li@nxp.com>


On Thu, 17 Apr 2025 11:06:04 -0400, Frank Li wrote:
> Convert m4if.txt and tigerp.txt to yaml format. These just use reg to
> indicate memory region.
> 
> Additional changes:
> - Add compatible string fsl,imx51-aipstz.
> - Add fsl,imx53-tigerp and fail back to fsl,imx51-tigerp
> - Add compatible string fsl,imx7d-pcie-phy, which is not real phy and just
> indicate a memory region.
> 
> Signed-off-by: Frank Li <Frank.Li@nxp.com>
> ---
>  .../arm/freescale/fsl,imx51-m4if.yaml         | 41 +++++++++++++++++++
>  .../bindings/arm/freescale/m4if.txt           | 12 ------
>  .../bindings/arm/freescale/tigerp.txt         | 12 ------
>  3 files changed, 41 insertions(+), 24 deletions(-)
>  create mode 100644 Documentation/devicetree/bindings/arm/freescale/fsl,imx51-m4if.yaml
>  delete mode 100644 Documentation/devicetree/bindings/arm/freescale/m4if.txt
>  delete mode 100644 Documentation/devicetree/bindings/arm/freescale/tigerp.txt
> 

Applied, thanks!


      reply	other threads:[~2025-04-22 12:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-17 15:06 [PATCH 1/1] dt-bindings: fsl: convert m4if.txt and tigerp.txt to yaml format Frank Li
2025-04-22 12:56 ` Rob Herring (Arm) [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=174532661282.962885.3469691185487125433.robh@kernel.org \
    --to=robh@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=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