[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250708123835.x6sedlift3xljzvh@scabbed>
Date: Tue, 8 Jul 2025 07:38:35 -0500
From: Nishanth Menon <nm@...com>
To: Vignesh Raghavendra <vigneshr@...com>
CC: Neha Malcom Francis <n-francis@...com>, <kristo@...nel.org>,
<robh@...nel.org>, <krzk+dt@...nel.org>, <conor+dt@...nel.org>,
<linux-arm-kernel@...ts.infradead.org>, <devicetree@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <u-kumar1@...com>
Subject: Re: [PATCH v4 0/2] Add support for K3 BIST
On 09:40-20250626, Vignesh Raghavendra wrote:
>
>
> On 05/06/25 12:05, Neha Malcom Francis wrote:
> > BIST (Built-In Self Test) is an IP responsible for triggering hardware
> > circuitry tests on both logic as well as memory blocks. This driver is
> > currently being upstreamed in U-Boot [1] (on hold till the dt-binding
> > is approved here) and triggers these tests on cores. This patch series
> > adds the dt-binding as well as a node for BIST on J784S4 and J742S2.
> >
> > Changes since v3:
> > https://lore.kernel.org/all/20250514072056.639346-1-n-francis@ti.com/
> > - Udit
> > - add support for J742S2
> >
> > Changes since v2:
> > https://lore.kernel.org/all/20250328111439.374748-1-n-francis@ti.com/
> > - Krzysztof
> > - use existing common definition (ti,sci-dev-id) for grabbing
> > the device ID instead of redefining properties
> >
> > Changes since v1:
> > https://lore.kernel.org/all/20241128140825.263216-1-n-francis@ti.com/
> > - Krzysztof
> > - move from misc/ to soc/ti/
> > - minor property changes
> > - drop ti,bist-instance and instead opt for ti,bist-under-test
> > - correct example dt
> >
> > [1] https://lore.kernel.org/all/20250204123147.939917-1-n-francis@ti.com/
> >
> > Neha Malcom Francis (2):
> > dt-bindings: soc: ti: bist: Add BIST for K3 devices
> > arm64: dts: ti: k3-j784s4-j742s2-main-common: Add PBIST_14 node
> >
> > .../bindings/soc/ti/ti,j784s4-bist.yaml | 63 +++++++++++++++++++
> > .../dts/ti/k3-j784s4-j742s2-main-common.dtsi | 11 ++++
> > 2 files changed, 74 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/soc/ti/ti,j784s4-bist.yaml
> >
>
>
> Nishanth,
>
> Ok to take the dt-bindings via ti-k3-dts-next branch? Or would you
> prefer to queue bindings and DT changes separately?
The ti-k3-dts-next should be fine here. I dont seem to have anything to
queue on the soc driver this time around..
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
Powered by blists - more mailing lists