linux-kernel - Re: [PATCH v3 1/1] i2c: core: support no-detect property

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: <Y1Bc4AjlZPs512Ao@shikoro>
Date:   Wed, 19 Oct 2022 22:24:00 +0200
From:   Wolfram Sang <wsa@...nel.org>
To:     Vincent Whitchurch <vincent.whitchurch@...s.com>
Cc:     kernel@...s.com, linux-i2c@...r.kernel.org,
        devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 1/1] i2c: core: support no-detect property

On Fri, Apr 29, 2022 at 03:07:49PM +0200, Vincent Whitchurch wrote:
> If the devicetree specifies the no-detect property (documented in
> dt-schema [0]) for the I2C bus, we know that there are no other devices
> on the bus other than the ones listed in the devicetree, so avoid
> calling drivers' detect callbacks and wasting time looking for devices
> which do not exist.

Setting 'classes' in the adapter struct to 0 (actually to
'I2C_CLASS_DEPRECATED' for a while) is not good enough? Or do you need
class based instantiation on some busses?


Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)