Messages in this thread | | | Date | Sun, 30 Apr 2023 09:05:55 +0200 | From | Wolfram Sang <> | 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?
[unhandled content-type:application/pgp-signature]
| |