From: Neil Armstrong <narmstrong@baylibre.com>
To: khilman@baylibre.com, carlo@caione.org
Cc: Neil Armstrong <narmstrong@baylibre.com>,
linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] soc: amlogic: add support for Meson GX VPU Domains
Date: Tue, 17 Oct 2017 09:38:00 +0200 [thread overview]
Message-ID: <1508225882-8795-1-git-send-email-narmstrong@baylibre.com> (raw)
On the Amlogic Gx SoCs (GXBB, GXL & GXM), the VPU power domain is initialized
by the vendor U-Boot code, but running mainline U-boot has been possible
on these SoCs. But lacking such init made the system lock at kernel boot.
This patchset adds the Video Processing Unit power domain driver to enable
the same power-on and power-down sequences and was designed to allow booting
with the power domain already initialized or not.
This driver has been tested on :
- Odroid-C2 (GXBB) with Vendor and Mainline U-Boot
- P212 (GXL) with Vendor and Mainline U-Boot
- Khadas Vim (GXL) with Vendor U-Boot
- Khadas Vim2 with (GXM) Vendor U-Boot
Neil Armstrong (2):
soc: amlogic: add Meson GX VPU Domains driver
dt-bindings: power: add amlogic meeson power domain bindings
.../bindings/power/amlogic,meson-gx-pwrc.txt | 65 ++++++
drivers/soc/amlogic/Kconfig | 10 +
drivers/soc/amlogic/Makefile | 1 +
drivers/soc/amlogic/meson-gx-pwrc-vpu.c | 234 +++++++++++++++++++++
4 files changed, 310 insertions(+)
create mode 100644 Documentation/devicetree/bindings/power/amlogic,meson-gx-pwrc.txt
create mode 100644 drivers/soc/amlogic/meson-gx-pwrc-vpu.c
--
2.7.4
next reply other threads:[~2017-10-17 7:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 7:38 Neil Armstrong [this message]
2017-10-17 7:38 ` [PATCH 1/2] soc: amlogic: add Meson GX VPU Domains driver Neil Armstrong
2017-10-17 7:38 ` [PATCH 2/2] dt-bindings: power: add amlogic meeson power domain bindings Neil Armstrong
2017-10-17 8:11 ` Neil Armstrong
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=1508225882-8795-1-git-send-email-narmstrong@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=carlo@caione.org \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®