From: Udit Kumar <u-kumar1@ti.com>
To: <vigneshr@ti.com>, <trini@konsulko.com>, <m-chawdhry@ti.com>
Cc: <bb@ti.com>, <n-francis@ti.com>, <nm@ti.com>,
<gehariprasath@ti.com>, <u-boot@lists.denx.de>,
Udit Kumar <u-kumar1@ti.com>
Subject: [PATCH v2 0/3] j721s2: j784s4: Add workaround for errata i2437
Date: Wed, 15 Apr 2026 20:51:49 +0530 [thread overview]
Message-ID: <20260415152152.3048491-1-u-kumar1@ti.com> (raw)
Add a necessary hardware errata workaround for J721S2 and J784S4.
Bootlogs
https://gist.github.com/uditkumarti/da2a489a78d3241ecd2791c9df1c1317
Changelog:
Changes in v2:
1- Added verified macro (this is new patch)
2- updated macro from ERRATA2437 to ERRATA_2437
3- instead of using hardcoded write, used verified write macro
Link to v1:
https://lore.kernel.org/u-boot/20251106063929.2232788-1-n-francis@ti.com/
Neha Malcom Francis (2):
arch: mach-k3: j721s2_init: Add workaround for errata i2437
arch: mach-k3: j784s4_init: Add workaround for errata i2437
Udit Kumar (1):
arm: mach-k3: arm: mach-k3: Add writel_verify macro for register write
verification
arch/arm/mach-k3/include/mach/hardware.h | 10 ++++++
arch/arm/mach-k3/j721s2/j721s2_init.c | 39 ++++++++++++++++++++++++
arch/arm/mach-k3/j784s4/j784s4_init.c | 39 ++++++++++++++++++++++++
3 files changed, 88 insertions(+)
--
2.34.1
next reply other threads:[~2026-04-15 15:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-15 15:21 Udit Kumar [this message]
2026-04-15 15:21 ` [PATCH v2 1/3] arm: mach-k3: arm: mach-k3: Add writel_verify macro for register write verification Udit Kumar
2026-04-15 15:21 ` [PATCH v2 2/3] arch: mach-k3: j721s2_init: Add workaround for errata i2437 Udit Kumar
2026-04-15 15:21 ` [PATCH v2 3/3] arch: mach-k3: j784s4_init: " Udit Kumar
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=20260415152152.3048491-1-u-kumar1@ti.com \
--to=u-kumar1@ti.com \
--cc=bb@ti.com \
--cc=gehariprasath@ti.com \
--cc=m-chawdhry@ti.com \
--cc=n-francis@ti.com \
--cc=nm@ti.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--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