From: Neil Armstrong <narmstrong@baylibre.com>
To: soc@kernel.org, arm@kernel.org
Cc: linux-amlogic@lists.infradead.org, linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] amlogic fixes for v5.18-rc
Date: Mon, 11 Apr 2022 18:18:41 +0200 [thread overview]
Message-ID: <1132bd6e-cd29-6e58-1fae-38e074545b25@baylibre.com> (raw)
Hi,
Here's a couple of DT fixes for v5.18-rc1, first removing the unstable lower OPPs
for the G12B & SM1 in order to increase stability over time, then fixing the S4
cpu compatible and finally fixing the GPIO Line Names for the BananaPi M5 board.
Neil
The following changes since commit 3123109284176b1532874591f7c81f3837bbdc17:
Linux 5.18-rc1 (2022-04-03 14:08:21 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/amlogic/linux.git v5.18/fixes
for you to fetch changes up to 962dd65e575dde950ef0844568edc37cfb39f302:
arm64: dts: meson-sm1-bananapi-m5: fix wrong GPIO pin labeling for CON1 (2022-04-11 17:53:38 +0200)
----------------------------------------------------------------
Christian Hewitt (2):
arm64: dts: meson: remove CPU opps below 1GHz for G12B boards
arm64: dts: meson: remove CPU opps below 1GHz for SM1 boards
Guillaume Giraudon (1):
arm64: dts: meson-sm1-bananapi-m5: fix wrong GPIO pin labeling for CON1
Xianwei Zhao (1):
arm64: dts: remove cpu compatible "arm,armv8" for s4
arch/arm64/boot/dts/amlogic/meson-g12b-a311d.dtsi | 40 ----------------------
arch/arm64/boot/dts/amlogic/meson-g12b-s922x.dtsi | 40 ----------------------
arch/arm64/boot/dts/amlogic/meson-s4.dtsi | 8 ++---
.../boot/dts/amlogic/meson-sm1-bananapi-m5.dts | 1 +
arch/arm64/boot/dts/amlogic/meson-sm1.dtsi | 20 -----------
5 files changed, 5 insertions(+), 104 deletions(-)
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
reply other threads:[~2022-04-11 16:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1132bd6e-cd29-6e58-1fae-38e074545b25@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=arm@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=soc@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®