From: afaerber@suse.de (Andreas Färber)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] ARM64: Initial Realtek RTD1295 enablement
Date: Tue, 14 Feb 2017 04:34:35 +0100 [thread overview]
Message-ID: <20170214033440.18667-1-afaerber@suse.de> (raw)
Hello,
This mini-series adds initial support for the Realtek RTD1295 SoC and
the Zidoo X9S TV box.
With these patches CPU0 can be booted with earlycon.
PSCI doesn't work despite present in the vendor device tree; as enable-method
it instead used a custom "rtk-spin-table" that I sadly have no source code of.
The UARTs use a custom interrupt controller that I again lack source code of;
with interrupts = <GIC_SPI 41 IRQ_TYPE_LEVEL_HIGH> it can boot into an initrd.
The boot process is slightly twisted: The files need to be loaded from a
32-bit U-Boot, then boot into 64-bit U-Boot where the kernel can be booted.
Similar to my previous Amlogic S905 work, the TEXT_OFFSET poses a problem, so
a uImage needs to be used (or the kernel patched) for load address 0x00280000.
I haven't succeeded loading an initrd via bootm/booti; but as quick workaround
initrd=$rootfs_loadaddr,0x$filesize can manually be specified in $bootargs.
Cf. https://en.opensuse.org/HCL:Zidoo_X9S
KVM appears to initialize okay, but was not yet tested with QEMU.
[ 0.256947] kvm [1]: 8-bit VMID
[ 0.256986] kvm [1]: IDMAP page: 73b000
[ 0.257025] kvm [1]: HYP VA range: 800000000000:ffffffffffff
[ 0.257458] kvm [1]: Hyp mode initialized successfully
[ 0.257529] kvm [1]: virtual timer IRQ3
More experimental patches at:
https://github.com/afaerber/linux/commits/rtd1295-next
Have a lot of fun!
Cheers,
Andreas
Cc: service at zidoo.tv
Cc: devicetree at vger.kernel.org
Andreas F?rber (4):
Documentation: devicetree: Add vendor prefix for Zidoo
Documentation: devicetree: arm: Add Realtek RTD1295 bindings
ARM64: Prepare Realtek RTD1295
ARM64: dts: Prepare Realtek RTD1295 and Zidoo X9S
Documentation/devicetree/bindings/arm/realtek.txt | 15 ++
.../devicetree/bindings/vendor-prefixes.txt | 1 +
arch/arm64/Kconfig.platforms | 6 +
arch/arm64/boot/dts/Makefile | 1 +
arch/arm64/boot/dts/realtek/Makefile | 5 +
arch/arm64/boot/dts/realtek/rtd1295-zidoo-x9s.dts | 79 ++++++++++
arch/arm64/boot/dts/realtek/rtd1295.dtsi | 162 +++++++++++++++++++++
7 files changed, 269 insertions(+)
create mode 100644 Documentation/devicetree/bindings/arm/realtek.txt
create mode 100644 arch/arm64/boot/dts/realtek/Makefile
create mode 100644 arch/arm64/boot/dts/realtek/rtd1295-zidoo-x9s.dts
create mode 100644 arch/arm64/boot/dts/realtek/rtd1295.dtsi
--
2.10.2
next reply other threads:[~2017-02-14 3:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 3:34 Andreas Färber [this message]
2017-02-14 3:34 ` [PATCH 1/4] Documentation: devicetree: Add vendor prefix for Zidoo Andreas Färber
2017-02-22 16:54 ` Rob Herring
2017-02-14 3:34 ` [PATCH 2/4] Documentation: devicetree: arm: Add Realtek RTD1295 bindings Andreas Färber
2017-02-22 16:56 ` Rob Herring
2017-02-22 17:03 ` Andreas Färber
2017-02-14 3:34 ` [PATCH 3/4] ARM64: Prepare Realtek RTD1295 Andreas Färber
2017-02-14 3:34 ` [PATCH 4/4] ARM64: dts: Prepare Realtek RTD1295 and Zidoo X9S Andreas Färber
2017-02-14 4:56 ` Andreas Färber
2017-02-16 13:51 ` [PATCH 0/4] ARM64: Initial Realtek RTD1295 enablement Arnd Bergmann
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=20170214033440.18667-1-afaerber@suse.de \
--to=afaerber@suse.de \
--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