i2c: qup: Vote for interconnect bandwidth to DRAM
authorStephan Gerhold <stephan.gerhold@kernkonzept.com>
Tue, 28 Nov 2023 09:48:37 +0000 (10:48 +0100)
committerAndi Shyti <andi.shyti@kernel.org>
Tue, 18 Mar 2025 20:53:53 +0000 (21:53 +0100)
commitd4f35233a6345f62637463ef6e0708f44ffaa583
tree1ed8c37cfd136c50b7b905a9f23700da0b2660d3
parentd15971447f1a503bd30be618e4f650724874e2ad
i2c: qup: Vote for interconnect bandwidth to DRAM

When the I2C QUP controller is used together with a DMA engine it needs
to vote for the interconnect path to the DRAM. Otherwise it may be
unable to access the memory quickly enough.

The requested peak bandwidth is dependent on the I2C core clock.

To avoid sending votes too often the bandwidth is always requested when
a DMA transfer starts, but dropped only on runtime suspend. Runtime
suspend should only happen if no transfer is active. After resumption we
can defer the next vote until the first DMA transfer actually happens.

The implementation is largely identical to the one introduced for
spi-qup in commit ecdaa9473019 ("spi: qup: Vote for interconnect
bandwidth to DRAM") since both drivers represent the same hardware
block.

Signed-off-by: Stephan Gerhold <stephan.gerhold@kernkonzept.com>
Signed-off-by: Andi Shyti <andi.shyti@kernel.org>
Link: https://lore.kernel.org/r/20231128-i2c-qup-dvfs-v1-3-59a0e3039111@kernkonzept.com
drivers/i2c/busses/i2c-qup.c