From: "Andreas Färber" <afaerber@suse.de>
To: linux-arm-kernel@lists.infradead.org
Cc: linux-kernel@vger.kernel.org, service@rdamicro.com,
zhao_steven@263.net, "Andreas Färber" <afaerber@suse.de>,
"Arnd Bergmann" <arnd@arndb.de>,
"Olof Johansson" <olof@lixom.net>,
devicetree@vger.kernel.org
Subject: [PATCH 0/6] ARM: Initial RDA8810PL and Orange Pi 2G-IoT enablement
Date: Tue, 27 Jun 2017 02:55:14 +0200 [thread overview]
Message-ID: <20170627005520.23731-1-afaerber@suse.de> (raw)
Hello,
This mini-series adds initial Device Trees for the RDA Micro RDA8810PL SoC and
the Orange Pi 2G-IoT board.
With the vendor U-Boot the .dtb needs to be appended to the zImage.
It then boots with earlycon until it is lacking a timer driver.
Cf. https://en.opensuse.org/HCL:Orange_Pi_2G-IoT
Patches at:
https://github.com/afaerber/linux/commits/opi2g-next
Have a lot of fun!
Cheers,
Andreas
Cc: service@rdamicro.com
Cc: zhao_steven@263.net
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Olof Johansson <olof@lixom.net>
Cc: devicetree@vger.kernel.org
Andreas Färber (6):
dt-bindings: Add RDA Micro vendor prefix
dt-bindings: arm: Document RDA8810PL and Orange Pi 2G-IoT
ARM: Prepare RDA8810PL
dt-bindings: serial: Document RDA Micro UART
tty: serial: Add RDA Micro UART driver
ARM: dts: Add RDA8810PL and Orange Pi 2G-IoT
Documentation/admin-guide/kernel-parameters.txt | 6 ++
Documentation/devicetree/bindings/arm/rda.txt | 17 +++
.../devicetree/bindings/serial/rda-uart.txt | 13 +++
.../devicetree/bindings/vendor-prefixes.txt | 1 +
arch/arm/Kconfig | 2 +
arch/arm/Makefile | 1 +
arch/arm/boot/dts/Makefile | 2 +
arch/arm/boot/dts/rda8810pl-orangepi-2g-iot.dts | 27 +++++
arch/arm/boot/dts/rda8810pl.dtsi | 94 +++++++++++++++++
arch/arm/mach-rda/Kconfig | 7 ++
arch/arm/mach-rda/Makefile | 1 +
drivers/tty/serial/Kconfig | 19 ++++
drivers/tty/serial/Makefile | 1 +
drivers/tty/serial/rda-uart.c | 117 +++++++++++++++++++++
14 files changed, 308 insertions(+)
create mode 100644 Documentation/devicetree/bindings/arm/rda.txt
create mode 100644 Documentation/devicetree/bindings/serial/rda-uart.txt
create mode 100644 arch/arm/boot/dts/rda8810pl-orangepi-2g-iot.dts
create mode 100644 arch/arm/boot/dts/rda8810pl.dtsi
create mode 100644 arch/arm/mach-rda/Kconfig
create mode 100644 arch/arm/mach-rda/Makefile
create mode 100644 drivers/tty/serial/rda-uart.c
--
2.12.3
next reply other threads:[~2017-06-27 0:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-27 0:55 Andreas Färber [this message]
2017-06-27 0:55 ` [PATCH 1/6] dt-bindings: Add RDA Micro vendor prefix Andreas Färber
2017-06-29 20:08 ` Rob Herring
2017-06-27 0:55 ` [PATCH 2/6] dt-bindings: arm: Document RDA8810PL and Orange Pi 2G-IoT Andreas Färber
2017-06-29 20:09 ` Rob Herring
2017-06-27 0:55 ` [PATCH 3/6] ARM: Prepare RDA8810PL Andreas Färber
2017-06-27 0:55 ` [PATCH 4/6] dt-bindings: serial: Document RDA Micro UART Andreas Färber
2017-06-29 20:10 ` Rob Herring
2017-06-30 11:12 ` Andreas Färber
2017-06-30 14:27 ` Rob Herring
2017-07-02 1:52 ` Andreas Färber
2017-07-05 14:12 ` Rob Herring
2017-06-27 0:55 ` [PATCH 5/6] tty: serial: Add RDA Micro UART driver Andreas Färber
2017-06-27 0:55 ` [PATCH 6/6] ARM: dts: Add RDA8810PL and Orange Pi 2G-IoT Andreas Färber
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=20170627005520.23731-1-afaerber@suse.de \
--to=afaerber@suse.de \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=service@rdamicro.com \
--cc=zhao_steven@263.net \
/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).