From: Andre Przywara <andre.przywara@arm.com>
To: Maxime Ripard <mripard@kernel.org>, Chen-Yu Tsai <wens@csie.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-sunxi@googlegroups.com,
Icenowy Zheng <icenowy@aosc.io>
Subject: [PATCH 0/3] ARM: dts: sun8i: R40: DT fixes and updates
Date: Thu, 2 Jan 2020 01:26:54 +0000 [thread overview]
Message-ID: <20200102012657.9278-1-andre.przywara@arm.com> (raw)
Hi,
some changes I made to the R40 .dtsi when playing around with a
Bananapi M2 Berry board:
- The GICC region is wrongly reported as 4K only, preventing KVM
from using its VGIC emulation.
- The PMU node is missing, similar story as with the other SoCs: this
time the SPI numbers are not even mentioned in the manual.
- I hooked up a SPI flash to the PortC SPI0 header pins (from which
the board can even boot from). So patch 3 adds the SPI nodes and its
pinmux setup, in case people need this for their peripherals.
Please have a look and apply!
Cheers,
Andre.
Andre Przywara (3):
ARM: dts: sun8i: R40: Upgrade GICC reg size to 8K
ARM: dts: sun8i: R40: Add PMU node
ARM: dts: sun8i: R40: Add SPI controllers nodes and pinmuxes
arch/arm/boot/dts/sun8i-r40.dtsi | 108 +++++++++++++++++++++++++++++++++++++--
1 file changed, 103 insertions(+), 5 deletions(-)
--
2.14.5
next reply other threads:[~2020-01-02 1:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-02 1:26 Andre Przywara [this message]
2020-01-02 1:26 ` [PATCH 1/3] ARM: dts: sun8i: R40: Upgrade GICC reg size to 8K Andre Przywara
2020-01-02 9:31 ` Maxime Ripard
2020-01-02 1:26 ` [PATCH 2/3] ARM: dts: sun8i: R40: Add PMU node Andre Przywara
2020-01-02 9:32 ` Maxime Ripard
2020-01-02 1:26 ` [PATCH 3/3] ARM: dts: sun8i: R40: Add SPI controllers nodes and pinmuxes Andre Przywara
2020-01-02 9:57 ` Maxime Ripard
2020-01-02 10:41 ` Andre Przywara
2020-01-02 10:54 ` Chen-Yu Tsai
2020-01-04 10:04 ` Maxime Ripard
2020-01-05 16:40 ` André Przywara
2020-01-05 18:28 ` Maxime Ripard
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=20200102012657.9278-1-andre.przywara@arm.com \
--to=andre.przywara@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=icenowy@aosc.io \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=mark.rutland@arm.com \
--cc=mripard@kernel.org \
--cc=robh+dt@kernel.org \
--cc=wens@csie.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