From: Nishanth Menon <nm@ti.com>
To: Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
<arm@kernel.org>, <soc@kernel.org>
Cc: Tero Kristo <kristo@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
Vignesh Raghavendra <vigneshr@ti.com>, Nishanth Menon <nm@ti.com>
Subject: [GIT PULL 2/3] arm64: dts: TI K3 updates for v5.20
Date: Fri, 8 Jul 2022 18:27:01 -0500 [thread overview]
Message-ID: <20220708232701.vpk45lwogpasaaay@enchilada> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2543 bytes --]
Hi ARM SoC maintainers,
Please pull (baseline used is v5.19-rc1 based
ti-k3-dt-fixes-for-v5.19[1] which was merged in 5.19 rc cycle).
The following changes since commit 0c0af88f3f318e73237f7fadd02d0bf2b6c996bb:
arm64: dts: ti: k3-am64-main: Remove support for HS400 speed mode (2022-06-17 20:24:01 -0500)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git tags/ti-k3-dt-for-v5.20
for you to fetch changes up to 8af893654c027fb679f67851aedb569ce7acb1e4:
arm64: dts: ti: k3-am62-main: Enable crypto accelerator (2022-07-06 19:34:30 -0500)
----------------------------------------------------------------
TI K3 device tree updates for v5.20
* AM62: fixups, sa2ul enabled, ramoops for sk
* others: whitespace and gpio-key cleanup.
----------------------------------------------------------------
Aswath Govindraju (1):
arm64: dts: ti: k3-am642-sk: Add pinmux corresponding to main_uart0
Guillaume La Roque (1):
arm64: dts: ti: k3-am625-sk: Enable ramoops
Jayesh Choudhary (1):
arm64: dts: ti: k3-am62-main: Enable crypto accelerator
Krzysztof Kozlowski (2):
arm64: dts: ti: Adjust whitespace around '='
arm64: dts: ti: Align gpio-key node names with dtschema
arch/arm64/boot/dts/ti/k3-am62-main.dtsi | 17 +++++++++++++++--
arch/arm64/boot/dts/ti/k3-am625-sk.dts | 11 ++++++++++-
arch/arm64/boot/dts/ti/k3-am64-main.dtsi | 4 ++--
arch/arm64/boot/dts/ti/k3-am642-evm.dts | 2 +-
arch/arm64/boot/dts/ti/k3-am642-sk.dts | 16 +++++++++++++++-
arch/arm64/boot/dts/ti/k3-am65-iot2050-common.dtsi | 4 ++--
arch/arm64/boot/dts/ti/k3-am65-main.dtsi | 14 +++++++-------
arch/arm64/boot/dts/ti/k3-am65-wakeup.dtsi | 4 ++--
arch/arm64/boot/dts/ti/k3-am654-base-board.dts | 8 ++++----
arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi | 4 ++--
arch/arm64/boot/dts/ti/k3-j721e-common-proc-board.dts | 4 ++--
arch/arm64/boot/dts/ti/k3-j721e-mcu-wakeup.dtsi | 4 ++--
arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi | 4 ++--
arch/arm64/boot/dts/ti/k3-j721s2-mcu-wakeup.dtsi | 4 ++--
14 files changed, 68 insertions(+), 32 deletions(-)
[1] https://lore.kernel.org/all/165608641371.3411.17669885978824514952.git-patchwork-summary@kernel.org/
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
reply other threads:[~2022-07-08 23:28 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=20220708232701.vpk45lwogpasaaay@enchilada \
--to=nm@ti.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=kristo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=soc@kernel.org \
--cc=vigneshr@ti.com \
/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