public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
To: linux-amlogic@lists.infradead.org, devicetree@vger.kernel.org,
	khilman@baylibre.com, carlo@caione.org, robh+dt@kernel.org,
	mark.rutland@arm.com
Cc: balbes-150@yandex.ru,
	Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Subject: [PATCH 0/6] Meson8m2 (32-bit ARM) SoC support
Date: Sun,  6 May 2018 11:21:13 +0200	[thread overview]
Message-ID: <20180506092119.467-1-martin.blumenstingl@googlemail.com> (raw)

This series adds support for the Meson8m2 SoC. This SoC is mostly
compatible with Meson8 while using some peripherals from Meson8b. Patch
#4 contains a list of (known) differences between the Meson8 and Meson8m2
SoCs.

The first supported board with Meson8m2 SoC is the "Tronsmart MXIII Plus"
where Oleg contributed the initial .dts and heavily tested it (many
thanks!). His testing also confirmed that the Meson8m2 SoC uses the same
register layout for the Ethernet "glue registers (supported by the
dwmac-meson8b driver) as Meson8b.


Martin Blumenstingl (5):
  dt-bindings: arm: amlogic: add support for the Meson8m2 SoC
  dt-bindings: arm: amlogic: add support for the Tronsmart MXIII Plus
  ARM: meson: add support for the Meson8m2 SoCs
  ARM: dts: meson: add support for the Meson8m2 SoC
  ARM: dts: meson8: add the uart_A pins

Oleg Ivanov (1):
  ARM: dts: meson8m2: add support for the Tronsmart MXIII Plus

 .../devicetree/bindings/arm/amlogic.txt       |   6 +
 arch/arm/boot/dts/Makefile                    |   2 +
 arch/arm/boot/dts/meson8.dtsi                 |  16 ++
 arch/arm/boot/dts/meson8m2-mxiii-plus.dts     | 244 ++++++++++++++++++
 arch/arm/boot/dts/meson8m2.dtsi               |  54 ++++
 arch/arm/mach-meson/Kconfig                   |   7 +
 arch/arm/mach-meson/meson.c                   |   1 +
 7 files changed, 330 insertions(+)
 create mode 100644 arch/arm/boot/dts/meson8m2-mxiii-plus.dts
 create mode 100644 arch/arm/boot/dts/meson8m2.dtsi

-- 
2.17.0

             reply	other threads:[~2018-05-06  9:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-06  9:21 Martin Blumenstingl [this message]
2018-05-06  9:21 ` [PATCH 1/6] dt-bindings: arm: amlogic: add support for the Meson8m2 SoC Martin Blumenstingl
2018-05-08 16:25   ` Rob Herring
2018-05-09 22:30     ` Kevin Hilman
2018-05-06  9:21 ` [PATCH 2/6] dt-bindings: arm: amlogic: add support for the Tronsmart MXIII Plus Martin Blumenstingl
2018-05-08 16:51   ` Rob Herring
2018-05-09 22:31     ` Kevin Hilman
2018-05-06  9:21 ` [PATCH 3/6] ARM: meson: add support for the Meson8m2 SoCs Martin Blumenstingl
2018-05-09 22:32   ` Kevin Hilman
2018-05-09 23:02     ` Martin Blumenstingl
2018-05-06  9:21 ` [PATCH 4/6] ARM: dts: meson: add support for the Meson8m2 SoC Martin Blumenstingl
2018-05-06  9:21 ` [PATCH 5/6] ARM: dts: meson8: add the uart_A pins Martin Blumenstingl
2018-05-06  9:21 ` [PATCH 6/6] ARM: dts: meson8m2: add support for the Tronsmart MXIII Plus 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=20180506092119.467-1-martin.blumenstingl@googlemail.com \
    --to=martin.blumenstingl@googlemail.com \
    --cc=balbes-150@yandex.ru \
    --cc=carlo@caione.org \
    --cc=devicetree@vger.kernel.org \
    --cc=khilman@baylibre.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.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