From: Kevin Hilman <khilman@baylibre.com>
To: Neil Armstrong <narmstrong@baylibre.com>
Cc: carlo@caione.org, linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] ARM64: dts: Add support for Meson GXM
Date: Mon, 21 Nov 2016 09:06:54 -0800 [thread overview]
Message-ID: <m2wpfw3gpd.fsf@baylibre.com> (raw)
In-Reply-To: <20161121162905.14285-2-narmstrong@baylibre.com> (Neil Armstrong's message of "Mon, 21 Nov 2016 17:29:04 +0100")
Neil Armstrong <narmstrong@baylibre.com> writes:
> Following the Amlogic Linux kernel, it seem the only differences
> between the GXL and GXM SoCs are the CPU Clusters.
>
> This commit renames the gxl-s905d-p23x DTSI in a common file for
> S905D p20x and S912 q20x boards.
>
> Then adds a meson-gxm dtsi and reproduce the P23x to Q20x boards
> dts files since the S905D and S912 SoCs shares the same pinout
> and the P23x and Q20x boards are identical.
>
> Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
> ---
> Documentation/devicetree/bindings/arm/amlogic.txt | 6 +
> arch/arm64/boot/dts/amlogic/Makefile | 2 +
> .../arm64/boot/dts/amlogic/meson-gx-p23x-q20x.dtsi | 190 +++++++++++++++++++++
> arch/arm64/boot/dts/amlogic/meson-gxbb-p200.dts | 19 +++
> arch/arm64/boot/dts/amlogic/meson-gxbb-p201.dts | 7 +
> .../boot/dts/amlogic/meson-gxl-s905d-p230.dts | 3 +-
> .../boot/dts/amlogic/meson-gxl-s905d-p231.dts | 3 +-
> .../boot/dts/amlogic/meson-gxl-s905d-p23x.dtsi | 188 --------------------
> .../arm64/boot/dts/amlogic/meson-gxm-s912-q200.dts | 77 +++++++++
> .../arm64/boot/dts/amlogic/meson-gxm-s912-q201.dts | 58 +++++++
> arch/arm64/boot/dts/amlogic/meson-gxm.dtsi | 114 +++++++++++++
> 11 files changed, 477 insertions(+), 190 deletions(-)
> create mode 100644 arch/arm64/boot/dts/amlogic/meson-gx-p23x-q20x.dtsi
> delete mode 100644 arch/arm64/boot/dts/amlogic/meson-gxl-s905d-p23x.dtsi
> create mode 100644 arch/arm64/boot/dts/amlogic/meson-gxm-s912-q200.dts
> create mode 100644 arch/arm64/boot/dts/amlogic/meson-gxm-s912-q201.dts
> create mode 100644 arch/arm64/boot/dts/amlogic/meson-gxm.dtsi
Applied.
Git tip: for future reference, set 'git config diff.renames true' so and
the diffstat shows a better summary when files are moved/renamed.
e.g, rather than the large ++ and -- above, you'd see:
...gxl-s905d-p23x.dtsi => meson-gx-p23x-q20x.dtsi} | 4 +-
Which is much more comforting to a maintainer than a bunch of
(potentially unrelated) adds and removes.
Thanks,
Kevin
next prev parent reply other threads:[~2016-11-21 17:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-21 16:29 [PATCH 0/2] ARM64: dts: Add support for Meson GXM Neil Armstrong
2016-11-21 16:29 ` [PATCH 1/2] " Neil Armstrong
2016-11-21 17:06 ` Kevin Hilman [this message]
2016-11-21 23:42 ` Kevin Hilman
2016-11-22 9:41 ` Neil Armstrong
2016-11-21 16:29 ` [PATCH 2/2] Add support for the Nexbox A1 board based on the Amlogic S912 SoC Neil Armstrong
2016-11-23 22:52 ` Rob Herring
2016-11-28 20:16 ` Kevin Hilman
2016-11-21 17:10 ` [PATCH 0/2] ARM64: dts: Add support for Meson GXM Kevin Hilman
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=m2wpfw3gpd.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=carlo@caione.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=narmstrong@baylibre.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).