linux-kernel - Re: [PATCH v3] i2c: lpi2c: cache peripheral clock rate

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: <ZE4TU0rCw9MSwrmB@sai>
Date:   Sun, 30 Apr 2023 09:05:55 +0200
From:   Wolfram Sang <wsa@...nel.org>
To:     Alexander Stein <alexander.stein@...tq-group.com>
Cc:     Marc Kleine-Budde <mkl@...gutronix.de>,
        NXP Linux Team <linux-imx@....com>,
        "A. Sverdlin" <alexander.sverdlin@...mens.com>,
        Dong Aisheng <aisheng.dong@....com>,
        Shawn Guo <shawnguo@...nel.org>,
        Sascha Hauer <s.hauer@...gutronix.de>,
        Pengutronix Kernel Team <kernel@...gutronix.de>,
        Fabio Estevam <festevam@...il.com>, linux-i2c@...r.kernel.org,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] i2c: lpi2c: cache peripheral clock rate


> > IIRC this is a general problem^w limitation of the clock framework,
> > clock providers cannot use clocks themselves in certain callback, e.g.
> > set_rate.
> 
> Well, that's essentially impossible when this clock provider is attached via 
> i2c. i2c transfers potentially need to change or prepare clocks.

So, as I get it, this is not a specific lpi2c problem but affecting any
I2C controller driver which uses get_rate() to setup a transfer to a
remote I2C clock provider? And this lockdep warning is a false-positive?


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