From: Christian Hewitt <christianshewitt@gmail.com>
To: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Kevin Hilman <khilman@baylibre.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: Christian Hewitt <christianshewitt@gmail.com>
Subject: [PATCH 0/3] arm64: dts: meson: fixups for WeTek common dtsi
Date: Tue, 12 Oct 2021 05:25:19 +0000 [thread overview]
Message-ID: <20211012052522.30873-1-christianshewitt@gmail.com> (raw)
Two fixes from work on u-boot support and following access to the original
vendor schematics, plus a minor change to use revised LED bindings.
- Mark VDDIO_AO18 always-on and link hdmi-supply to fix HDMI on boot
- Add missing GPIO binding
- Update LED bindings
Christian Hewitt (3):
arm64: dts: meson-gxbb-wetek: fix HDMI in early boot
arm64: dts: meson-gxbb-wetek: fix missing GPIO binding
arm64: dts: meson-gxbb-wetek: use updated LED bindings
arch/arm64/boot/dts/amlogic/meson-gxbb-wetek.dtsi | 10 ++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)
--
2.17.1
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next reply other threads:[~2021-10-12 5:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-12 5:25 Christian Hewitt [this message]
2021-10-12 5:25 ` [PATCH 1/3] arm64: dts: meson-gxbb-wetek: fix HDMI in early boot Christian Hewitt
2021-11-15 9:24 ` Neil Armstrong
2021-10-12 5:25 ` [PATCH 2/3] arm64: dts: meson-gxbb-wetek: fix missing GPIO binding Christian Hewitt
2021-11-15 9:24 ` Neil Armstrong
2021-10-12 5:25 ` [PATCH 3/3] arm64: dts: meson-gxbb-wetek: use updated LED bindings Christian Hewitt
2021-11-15 9:25 ` Neil Armstrong
2021-11-15 9:29 ` [PATCH 0/3] arm64: dts: meson: fixups for WeTek common dtsi 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=20211012052522.30873-1-christianshewitt@gmail.com \
--to=christianshewitt@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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