From: martin.blumenstingl@googlemail.com (Martin Blumenstingl)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] Amlogic Meson (32-bit) .dts cleanups
Date: Mon, 17 Apr 2017 23:39:36 +0200 [thread overview]
Message-ID: <20170417213938.22626-1-martin.blumenstingl@googlemail.com> (raw)
This series provides a few cleanups in the 32-bit Amlogic .dts files.
The first patch introduces the actual busses so the .dts' basic structure
is similar to what we have in the 64-bit .dts files.
The second patch removes even more duplication by inheriting meson.dtsi
from meson8b.dtsi (just like meson6.dtsi and meson8.dtsi are doing).
There should not be any functional changes with these patches. However,
I was only test this on a Meson8 based device, so it would be great if
somebody could test this on a Meson8b device.
Martin Blumenstingl (2):
ARM: dts: meson: organize devices in their corresponding busses
ARM: dts: meson8b: inherit meson.dtsi from meson8b.dtsi
arch/arm/boot/dts/meson.dtsi | 180 ++++++++++++++++++-----------------
arch/arm/boot/dts/meson6.dtsi | 2 -
arch/arm/boot/dts/meson8.dtsi | 116 +++++++++++++++--------
arch/arm/boot/dts/meson8b.dtsi | 210 +++++++++++++++++------------------------
4 files changed, 255 insertions(+), 253 deletions(-)
--
2.12.2
next reply other threads:[~2017-04-17 21:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-17 21:39 Martin Blumenstingl [this message]
2017-04-17 21:39 ` [PATCH 1/2] ARM: dts: meson: organize devices in their corresponding busses Martin Blumenstingl
2017-05-19 22:49 ` Kevin Hilman
2017-05-20 8:45 ` Martin Blumenstingl
2017-05-26 18:20 ` Kevin Hilman
2017-04-17 21:39 ` [PATCH 2/2] ARM: dts: meson8b: inherit meson.dtsi from meson8b.dtsi Martin Blumenstingl
2017-05-06 17:29 ` [PATCH 0/2] Amlogic Meson (32-bit) .dts cleanups Martin Blumenstingl
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=20170417213938.22626-1-martin.blumenstingl@googlemail.com \
--to=martin.blumenstingl@googlemail.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).