linux-kernel - Re: [PATCH 1/2] dt-bindings: i3c: dw: Add property to select IBI ops

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <c15045b4-2e5f-4fcc-b25c-76a5e4973e93@linaro.org>
Date: Wed, 26 Jun 2024 10:06:18 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Jeremy Kerr <jk@...econstruct.com.au>, Aniket <aniketmaurya@...gle.com>,
 Alexandre Belloni <alexandre.belloni@...tlin.com>,
 Joel Stanley <joel@....id.au>, Billy Tsai <billy_tsai@...eedtech.com>,
 Rob Herring <robh@...nel.org>,
 Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>
Cc: linux-i3c@...ts.infradead.org, linux-kernel@...r.kernel.org,
 devicetree@...r.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: i3c: dw: Add property to select IBI ops

On 26/06/2024 07:31, Jeremy Kerr wrote:
> Hi Aniket,
> 
>> Use this property to select IBI related ops in the base platform
>> driver. Otherwise the driver defaults to return EINVAL for any IBI
>> requests.
> 
> [...]
> 
>> --- a/Documentation/devicetree/bindings/i3c/snps,dw-i3c-master.yaml
>> +++ b/Documentation/devicetree/bindings/i3c/snps,dw-i3c-master.yaml
>> @@ -25,6 +25,10 @@ properties:
>>    interrupts:
>>      maxItems: 1
>>  
>> +  ibi-capable:
>> +    description: Set to select IBI ops.

What are IBI ops? Standard form letter:

You described the desired Linux feature or behavior, not the actual
hardware. The bindings are about the latter, so instead you need to
rephrase the property and its description to match actual hardware
capabilities/features/configuration etc.

>> +    type: boolean
>> +
> 
> Wouldn't the compatible string select whether the hardware instance
> supports IBI or not?
> 
> I'd imagine that each specific synthesis of the DW IP would imply
> corresponding hardware settings, and so would warrant its own compatible
> value.
> 
> Maybe one for the DT folks: would this work better as individual
> properties? Is there a policy here?

Usually if feature is specific to given hardware, e.g. always capable of
foobar, then it can be deduced from compatible, so no need for new property.

Best regards,
Krzysztof