public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Neha Malcom Francis <n-francis@ti.com>
Cc: nm@ti.com, vigneshr@ti.com, kristo@kernel.org, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, u-kumar1@ti.com
Subject: Re: [PATCH 1/2] dt-bindings: misc: bist: Add BIST dt-binding for TI K3 devices
Date: Fri, 29 Nov 2024 10:15:05 +0100	[thread overview]
Message-ID: <e57dfc3e-b702-4803-b776-20c6dbd98fef@kernel.org> (raw)
In-Reply-To: <837d329b-bcdd-4c3b-b508-e916b110ce25@ti.com>

On 29/11/2024 08:43, Neha Malcom Francis wrote:
>>> +
>>> +  power-domains:
>>> +    maxItems: 1
>>> +
>>> +  ti,bist-instance:
>>> +    $ref: /schemas/types.yaml#/definitions/uint32
>>> +    description:
>>> +      the BIST instance in the SoC represented as an integer
>>
>> No instance indices are allowed. Drop.
>>
> 
> Question on this, this is not a property that is driven by software but rather 
> indicates which register sequences have to be picked up for triggering this test 
> from this instance. So I don't see how I can workaround this without getting 
> this number. Or maybe call it ID rather than instance?

I don't understand how the device operates, so what is exactly behind
some sequences of registers for triggering this test. You described
property as index or ID of one instance of the block. That's not what we
want in the binding. That's said maybe other, different hardware
characteristic is behind, who knows. Or maybe it's about callers... or
maybe that's not hardware property at all, but runtime OS, who knows.

Best regards,
Krzysztof

  reply	other threads:[~2024-11-29  9:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-28 14:08 [PATCH 0/2] Add support for K3 BIST Neha Malcom Francis
2024-11-28 14:08 ` [PATCH 1/2] dt-bindings: misc: bist: Add BIST dt-binding for TI K3 devices Neha Malcom Francis
2024-11-29  7:20   ` Krzysztof Kozlowski
2024-11-29  7:43     ` Neha Malcom Francis
2024-11-29  9:15       ` Krzysztof Kozlowski [this message]
2025-03-13 11:14         ` Neha Malcom Francis
2025-03-19  7:46           ` Krzysztof Kozlowski
2025-03-19  9:02             ` Neha Malcom Francis
2025-03-24  7:23               ` Krzysztof Kozlowski
2025-03-27  4:12                 ` Neha Malcom Francis
2024-11-28 14:08 ` [PATCH 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=e57dfc3e-b702-4803-b776-20c6dbd98fef@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