From: Krzysztof Kozlowski <krzk@kernel.org>
To: Neha Malcom Francis <n-francis@ti.com>,
nm@ti.com, vigneshr@ti.com, kristo@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, u-kumar1@ti.com
Subject: Re: [PATCH v2 1/2] dt-bindings: soc: ti: bist: Add BIST for K3 devices
Date: Fri, 28 Mar 2025 12:48:03 +0100 [thread overview]
Message-ID: <fc4d9a33-2d3f-47e2-b1cf-59962cc54bce@kernel.org> (raw)
In-Reply-To: <20250328111439.374748-2-n-francis@ti.com>
On 28/03/2025 12:14, Neha Malcom Francis wrote:
> +properties:
> + compatible:
> + const: ti,j784s4-bist
> +
> + reg:
> + maxItems: 2
> +
> + reg-names:
> + items:
> + - const: cfg
> + - const: ctrl_mmr
> +
> + clocks:
> + maxItems: 1
> +
> + power-domains:
> + maxItems: 1
> +
> + ti,bist-under-test:
> + $ref: /schemas/types.yaml#/definitions/uint32-array
> + description:
> + the device IDs of the devices under test control of the BIST device, the
Still not phandle... What is a "device ID"?
> + number of devices may be more than one. The HW logic will trigger the
> + tests on all of these devices at once.
> +
> +required:
> + - compatible
> + - reg
> + - reg-names
> + - ti,bist-under-test
> +
> +additionalProperties: false
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-03-28 11:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-28 11:14 [PATCH v2 0/2] Add support for K3 BIST Neha Malcom Francis
2025-03-28 11:14 ` [PATCH v2 1/2] dt-bindings: soc: ti: bist: Add BIST for K3 devices Neha Malcom Francis
2025-03-28 11:48 ` Krzysztof Kozlowski [this message]
2025-03-28 12:42 ` Neha Malcom Francis
2025-03-29 4:38 ` Krzysztof Kozlowski
2025-04-10 7:08 ` Neha Malcom Francis
2025-03-28 11:14 ` [PATCH v2 2/2] arm64: dts: ti: k3-j784s4-main: Add PBIST_14 node Neha Malcom Francis
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=fc4d9a33-2d3f-47e2-b1cf-59962cc54bce@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=n-francis@ti.com \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=u-kumar1@ti.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