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: <d256cd72ef2011c3bfd045b04fb6509d1ac827e9.camel@codeconstruct.com.au>
Date: Wed, 26 Jun 2024 17:00:34 +0800
From: Jeremy Kerr <jk@...econstruct.com.au>
To: "Aniket ." <aniketmaurya@...gle.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>, 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>,
 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

Hi Aniket,

> > For cases where no other special behaviour is required, we can
> > represent this just as an entry in the OF match table.
> 
> Actually I see that IBI support is always present in the HW(DW I3C
> IP). It's just that we have an option in SW to decide whether to
> populate function pointers for IBI or not.

OK, in that case this /definitely/ doesn't belong in the DT then, as
it's purely software configuration.

> So can we remove this selection of ops and always go with ibi ops?

Sounds fine to me, but I don't have direct experience with the non-
ast2600 uses of the dw core.

Cheers,


Jeremy