[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20260115163108.hhpzibzbb62co2zj@bryanbrattlof.com>
Date: Thu, 15 Jan 2026 10:31:08 -0600
From: Bryan Brattlof <bb@...com>
To: Beleswar Padhi <b-padhi@...com>
CC: <nm@...com>, <vigneshr@...com>, <kristo@...nel.org>, <robh@...nel.org>,
<krzk+dt@...nel.org>, <conor+dt@...nel.org>, <afd@...com>, <u-kumar1@...com>,
<hnagalla@...com>, <devicetree@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v3 0/2] Add TI K3 HSM M4F nodes in device-tree
On January 14, 2026 thus sayeth Beleswar Padhi:
> Some of the TI K3 family of SoCs (like J721S2, J784S4, J722S) have a
> HSM (High Security Module) M4F core in the Wakeup Voltage Domain which
> could be used to run secure services like Authentication. Add the device
> device-tree node definitions for this HSM M4F core. The bindings for
> this has already been merged[0].
>
> The HSM M4 core is typically booted early from the bootloader and the
> driver for the same is posted in U-Boot mailing list[1].
>
Nice! Amazing job cleaning up the remote core drivers Beleswar! And
defining them so well in DT for us. For the series
Reviewed-by: Bryan Brattlof <bb@...com>
~Bryan
Powered by blists - more mailing lists