From: Fabio Estevam <festevam@gmail.com>
To: Dong Aisheng <aisheng.dong@nxp.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>, Dong Aisheng <dongas86@gmail.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Rob Herring <robh+dt@kernel.org>,
NXP Linux Team <linux-imx@nxp.com>,
Sascha Hauer <kernel@pengutronix.de>,
Fabio Estevam <fabio.estevam@nxp.com>,
Shawn Guo <shawnguo@kernel.org>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH V2 2/4] arm64: dts: imx: add imx8qxp support
Date: Sun, 14 Oct 2018 20:13:32 -0300 [thread overview]
Message-ID: <CAOMZO5BEwNQy0HA80qOzm_w-c63tFK1eL+cOHNCxKYq9PHGsqw@mail.gmail.com> (raw)
In-Reply-To: <1539527419-23613-3-git-send-email-aisheng.dong@nxp.com>
Hi Dong,
On Sun, Oct 14, 2018 at 11:35 AM A.s. Dong <aisheng.dong@nxp.com> wrote:
>
> Add imx8qxp support
You could probably expand the commit log by explaining a bit of what
im8qxp means.
> diff --git a/arch/arm64/boot/dts/freescale/imx8qxp.dtsi b/arch/arm64/boot/dts/freescale/imx8qxp.dtsi
> new file mode 100644
> index 0000000..e1d2578
> --- /dev/null
> +++ b/arch/arm64/boot/dts/freescale/imx8qxp.dtsi
> @@ -0,0 +1,861 @@
> +// SPDX-License-Identifier: GPL-2.0+
> +/*
> + * Copyright (C) 2016 Freescale Semiconductor, Inc.
> + * Copyright 2017~2018 NXP
I guess you meant "-" instead of "~".
> + memory@80000000 {
> + device_type = "memory";
> + reg = <0x00000000 0x80000000 0 0x40000000>;
> + };
This should go to the board dts file instead as the memory size may
vary from board to board.
> + imx8qx-pm {
> + compatible = "fsl,scu-pd";
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + pd_lsio: lsio-power-domain {
> + #power-domain-cells = <0>;
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + pd_lsio_pwm0: lsio-pwm0@191 {
> + reg = <191>;
The number after @ is in hex, so the reg property should be 0x191.
next prev parent reply other threads:[~2018-10-14 23:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1539527419-23613-1-git-send-email-aisheng.dong@nxp.com>
2018-10-14 14:34 ` [PATCH V2 2/4] arm64: dts: imx: add imx8qxp support A.s. Dong
2018-10-14 23:13 ` Fabio Estevam [this message]
2018-10-15 6:27 ` Daniel Baluta
2018-10-15 7:30 ` Leonard Crestez
2018-10-15 9:29 ` A.s. Dong
2018-10-15 7:57 ` A.s. Dong
2018-10-18 0:51 ` Rob Herring
2018-10-18 2:32 ` A.s. Dong
2018-10-15 6:58 ` Sascha Hauer
2018-10-15 8:08 ` A.s. Dong
2018-10-15 8:27 ` Sascha Hauer
2018-10-15 9:03 ` A.s. Dong
2018-10-15 9:40 ` Sascha Hauer
2018-10-15 16:09 ` A.s. Dong
2018-10-16 7:08 ` Sascha Hauer
2018-10-14 14:34 ` [PATCH V2 3/4] arm64: dts: imx: add imx8qxp mek support A.s. Dong
2018-10-15 7:01 ` Sascha Hauer
2018-10-15 8:40 ` A.s. Dong
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=CAOMZO5BEwNQy0HA80qOzm_w-c63tFK1eL+cOHNCxKYq9PHGsqw@mail.gmail.com \
--to=festevam@gmail.com \
--cc=aisheng.dong@nxp.com \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=dongas86@gmail.com \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.org \
--cc=will.deacon@arm.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;
as well as URLs for NNTP newsgroup(s).