linux-kernel - Re: [PATCH 1/2] dt-bindings: misc: bist: Add BIST dt-binding for TI K3 devices

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <e57dfc3e-b702-4803-b776-20c6dbd98fef@kernel.org>
Date: Fri, 29 Nov 2024 10:15:05 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Neha Malcom Francis <n-francis@...com>
Cc: nm@...com, vigneshr@...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 1/2] dt-bindings: misc: bist: Add BIST dt-binding for TI
 K3 devices

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