From: Shawn Guo <shawnguo@kernel.org>
To: peng.fan@nxp.com
Cc: fabio.estevam@nxp.com, kernel@pengutronix.de,
aisheng.dong@nxp.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-imx@nxp.com,
leonard.crestez@nxp.com, daniel.baluta@nxp.com,
l.stach@pengutronix.de, devicetree@vger.kernel.org
Subject: Re: [PATCH 2/3] arm64: dts: imx8qxp: add i2c aliases
Date: Tue, 23 Jun 2020 11:56:16 +0800 [thread overview]
Message-ID: <20200623035615.GN30139@dragon> (raw)
In-Reply-To: <1590977180-9957-3-git-send-email-peng.fan@nxp.com>
On Mon, Jun 01, 2020 at 10:06:19AM +0800, peng.fan@nxp.com wrote:
> From: Peng Fan <peng.fan@nxp.com>
>
> The devices could be enumerated properly with aliases.
>
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
> ---
> arch/arm64/boot/dts/freescale/imx8qxp.dtsi | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/freescale/imx8qxp.dtsi b/arch/arm64/boot/dts/freescale/imx8qxp.dtsi
> index 33363c127478..8ce997110cd6 100644
> --- a/arch/arm64/boot/dts/freescale/imx8qxp.dtsi
> +++ b/arch/arm64/boot/dts/freescale/imx8qxp.dtsi
> @@ -19,6 +19,10 @@
> #size-cells = <2>;
>
> aliases {
> + i2c0 = &adma_i2c0;
> + i2c1 = &adma_i2c1;
> + i2c2 = &adma_i2c2;
> + i2c3 = &adma_i2c3;
Had a second look. It breaks alphabetical order. So dropped the
series.
Shawn
> gpio0 = &lsio_gpio0;
> gpio1 = &lsio_gpio1;
> gpio2 = &lsio_gpio2;
> --
> 2.16.4
>
next prev parent reply other threads:[~2020-06-23 3:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-01 2:06 [PATCH 0/3] arm64: dts: imx8qxp: dtb aliases fix/update peng.fan
2020-06-01 2:06 ` [PATCH 1/3] arm64: dts: imx8qxp: add alias for lsio MU peng.fan
2020-06-01 2:06 ` [PATCH 2/3] arm64: dts: imx8qxp: add i2c aliases peng.fan
2020-06-23 3:56 ` Shawn Guo [this message]
2020-06-23 7:06 ` Peng Fan
2020-06-01 2:06 ` [PATCH 3/3] arm64: dts: imx8qxp: Add ethernet alias peng.fan
2020-06-23 3:53 ` [PATCH 0/3] arm64: dts: imx8qxp: dtb aliases fix/update Shawn Guo
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=20200623035615.GN30139@dragon \
--to=shawnguo@kernel.org \
--cc=aisheng.dong@nxp.com \
--cc=daniel.baluta@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=leonard.crestez@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.com \
/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