From: Rob Herring <robh@kernel.org>
To: Sascha Silbe <x-linux@se-silbe.de>
Cc: NXP Linux Team <linux-imx@nxp.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Rob Herring <robh+dt@kernel.org>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
devicetree@vger.kernel.org, Shawn Guo <shawnguo@kernel.org>,
linux-arm-kernel@lists.infradead.org,
Fabio Estevam <festevam@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: imx8mq: add defines for IOMUXC_SW_PAD_CTL register values
Date: Thu, 28 Oct 2021 21:14:37 -0500 [thread overview]
Message-ID: <YXtZDelpt8fJhU/V@robh.at.kernel.org> (raw)
In-Reply-To: <20211024152832.649738-1-x-linux@se-silbe.de>
On Sun, 24 Oct 2021 17:28:32 +0200, Sascha Silbe wrote:
> The IOMUXC_SW_PAD_CTL_* registers on i.MX8M Dual/QuadLite/Quad all
> have the same basic structure. Add defines for a common subset
> supported by most of the registers. They can be used in Device Tree
> source files instead of magic values, making the sources a lot more
> readable and easier to write as well.
>
> Signed-off-by: Sascha Silbe <x-linux@se-silbe.de>
> ---
> .../arm64/boot/dts/freescale/imx8mq-pinfunc.h | 28 +++++++++++++++++++
> 1 file changed, 28 insertions(+)
>
> The board I'm using this for is an out-of-tree prototype. If there's
> interest I can convert the in-tree DTS files. I have don't have any of
> those boards but comparing the built DTBs before vs. after the change
> should be sufficient.
>
>
Acked-by: Rob Herring <robh@kernel.org>
prev parent reply other threads:[~2021-10-29 2:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-24 15:28 [PATCH] arm64: dts: imx8mq: add defines for IOMUXC_SW_PAD_CTL register values Sascha Silbe
2021-10-29 2:14 ` Rob Herring [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=YXtZDelpt8fJhU/V@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=x-linux@se-silbe.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).