From: Bryan Brattlof <bb@ti.com>
To: Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
"Andrew Davis" <afd@ti.com>, Tero Kristo <kristo@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
"Tony Lindgren" <tony@atomide.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
<linux-gpio@vger.kernel.org>, Bryan Brattlof <bb@ti.com>,
Dhruva Gole <d-gole@ti.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: [PATCH v8 0/3] arm64: dts: ti: introduce basic support for the AM62L
Date: Wed, 5 Nov 2025 09:46:41 -0600 [thread overview]
Message-ID: <20251105-am62lx-v8-0-496f353e8237@ti.com> (raw)
Hello Everyone,
This small series adds the initial support (currently just a UART) for
TI's AM62L SoC family.
The AM62L is a lite, low power and performance optimized family of
application processors that are built for Linux application development.
AM62L is well suited for a wide range of general-purpose applications
with scalable ARM Cortex-A53 core performance and embedded features such
as: Multimedia DSI/DPI support, integrated ADC on chip, advanced lower
power management modes, and extensive security options for IP protection
with the built-in security features.
Additionally, the AM62Lx devices includes an extensive set of
peripherals that make it a well-suited for a broad range of industrial
applications while offering intelligent features and optimized power
architecture as well. In addition, the extensive set of peripherals
included in AM62Lx enables system-level connectivity, such as: USB,
MMC/SD, OSPI, CAN-FD and an ADC.
AM62L is a general purpose processor, however some of the applications
well suited for it include: Human Machine Interfaces (HMI), Medical
patient monitoring , Building automation, Smart secure gateways, Smart
Thermostats, EV charging stations, Smart Metering, Solar energy and
more.
Some highlights of AM62L SoC are:
- Single to Dual 64-bit Arm® Cortex®-A53 microprocessor subsystem up to
1.25GHz Integrated Giga-bit Ethernet switch supporting up to a total
of two external
- 16-bit DDR Subsystem that supports LPDDR4, DDR4 memory types.
- Display support: 1x display support over MIPI DSI (4 lanes DPHY) or
DPI (24-bit RGB LVCMOS)
- Multiple low power modes support, ex: Deep sleep and Standby
- Support for secure boot, Trusted Execution Environment (TEE) &
Cryptographic Acceleration
For more information check out our Technical Reference Manual (TRM)
which is located here:
https://www.ti.com/lit/pdf/sprujb4
Happy Hacking
~Bryan
Changes from v1:
- switched to non-direct links so TRM updates are automatic
- fixed indentation issues with a few nodes
- separated bindings into a different patch
- removed current-speed property from main_uart0{}
- removed empty reserved-memory{} node
- removed serial2 from aliases{} node
- corrected the main_uart0{} pinmux
- Link: https://lore.kernel.org/all/20241117-am62lx-v1-0-4e71e42d781d@ti.com/
Changes from v2:
- alphabetized phandles
- corrected macro and node names for main_uart0 pinmux
- Link to v2: https://lore.kernel.org/r/20250108-am62lx-v2-0-581285a37d8f@ti.com
Changes from v3:
- added more nodes which have been validated
- added link to data sheet which is now public
- Link to v3: https://lore.kernel.org/r/20250109-am62lx-v3-0-ef171e789527@ti.com
Changes from v4:
- corrected copyright date
- used the ranges property for the fss{} node
- converted control MMR's space into a syscon{} node
- Link to v4: https://lore.kernel.org/r/20250407-am62lx-v4-0-ce97749b9eae@ti.com
Changes from v5:
- added new compatible for the am62l pinmux driver
- increased thermal trip point to 125C
- reduced size of &conf its correct size of 0x380000
- replaced dss with display: s/dss@/display@/
- expanded chipid to include the JTAG_USER_ID information
- removed nodes requiring parent clocks until sorted in firmware
- expanded &wkup_conf length to properly contain the &usb_phy_ctrl
- moved back to &wkup_conf as a simple bus and grouped both
&usb*_phy_ctrl into one syscon node rather than individual nodes
- Link to v5: https://lore.kernel.org/r/20250507-am62lx-v5-0-4b57ea878e62@ti.com
Changes from v6:
- moved thermal-zones{} into the k3-am62l3-evm.dts to allow other boards
to select whichever thermal nodes trip points they wish.
- removed dss{} for now until binding doc is updated.
- Link to v6: https://lore.kernel.org/r/20250912-am62lx-v6-0-29d5a6c60512@ti.com
Changes from v7:
- enabled &i2c0 node in reference board file.
- enabled &gpio0 and &gpio1 by default like with other AM62* SoCs
- Link to v7: https://lore.kernel.org/r/20251031-am62lx-v7-0-cb426be9d6ee@ti.com
---
Cc: linux-arm-kernel@lists.infradead.org
Cc: devicetree@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Cc: Sascha Hauer <s.hauer@pengutronix.de>
Cc: linux-gpio@vger.kernel.org
To: Nishanth Menon <nm@ti.com>
To: Vignesh Raghavendra <vigneshr@ti.com>
To: Andrew Davis <afd@ti.com>
To: Tero Kristo <kristo@kernel.org>
To: Rob Herring <robh@kernel.org>
To: Krzysztof Kozlowski <krzk+dt@kernel.org>
To: Conor Dooley <conor+dt@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
To: Tony Lindgren <tony@atomide.com>
Signed-off-by: Bryan Brattlof <bb@ti.com>
---
Bryan Brattlof (1):
dt-bindings: arm: ti: Add binding for AM62L SoCs
Vignesh Raghavendra (2):
arm64: dts: ti: k3-am62l: add initial infrastructure
arm64: dts: ti: k3-am62l: add initial reference board file
Documentation/devicetree/bindings/arm/ti/k3.yaml | 6 +
arch/arm64/boot/dts/ti/Makefile | 3 +
arch/arm64/boot/dts/ti/k3-am62l-main.dtsi | 580 +++++++++++++++++++++++
arch/arm64/boot/dts/ti/k3-am62l-wakeup.dtsi | 141 ++++++
arch/arm64/boot/dts/ti/k3-am62l.dtsi | 118 +++++
arch/arm64/boot/dts/ti/k3-am62l3-evm.dts | 362 ++++++++++++++
arch/arm64/boot/dts/ti/k3-am62l3.dtsi | 67 +++
arch/arm64/boot/dts/ti/k3-pinctrl.h | 2 +
8 files changed, 1279 insertions(+)
---
base-commit: da84d094ded6e332c88c67218faabfbf8d3d59e5
change-id: 20241220-am62lx-ca9498efd87e
Best regards,
--
Bryan Brattlof <bb@ti.com>
next reply other threads:[~2025-11-05 15:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-05 15:46 Bryan Brattlof [this message]
2025-11-05 15:46 ` [PATCH v8 1/3] dt-bindings: arm: ti: Add binding for AM62L SoCs Bryan Brattlof
2025-11-05 15:46 ` [PATCH v8 2/3] arm64: dts: ti: k3-am62l: add initial infrastructure Bryan Brattlof
2025-11-05 15:46 ` [PATCH v8 3/3] arm64: dts: ti: k3-am62l: add initial reference board file Bryan Brattlof
2025-11-14 10:58 ` Vignesh Raghavendra
2025-11-14 13:05 ` Bryan Brattlof
2025-11-16 12:43 ` [PATCH v8 0/3] arm64: dts: ti: introduce basic support for the AM62L Vignesh Raghavendra
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=20251105-am62lx-v8-0-496f353e8237@ti.com \
--to=bb@ti.com \
--cc=afd@ti.com \
--cc=conor+dt@kernel.org \
--cc=d-gole@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=tony@atomide.com \
--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;
as well as URLs for NNTP newsgroup(s).