.../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
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 -- 2.34.1
Hi Neha Malcom Francis,
On Thu, 05 Jun 2025 12:05:04 +0530, 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
>
> [...]
I have applied the following to branch ti-k3-dts-next on [1].
Thank you!
[1/2] dt-bindings: soc: ti: bist: Add BIST for K3 devices
commit: 04ee170b69749851c74666079ac8f64dba52a2f1
[2/2] arm64: dts: ti: k3-j784s4-j742s2-main-common: Add PBIST_14 node
commit: 387727d7e5d9c2499aafbd04e22c9d39e8eec4c5
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
--
Vignesh
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? -- Regards Vignesh https://ti.com/opensource
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
© 2016 - 2025 Red Hat, Inc.