Re: [PATCH] i2c: tegra: Don't mark devices with pins as IRQ safe

[Mikko Perttunen <mperttunen@nvidia.com>]

On Thursday, February 5, 2026 7:47 PM Andi Shyti wrote:
> Hi Mikko,
> 
> On Mon, Feb 02, 2026 at 01:42:34PM +0900, Mikko Perttunen wrote:
> > I2C devices with associated pinctrl states (DPAUX I2C controllers)
> > will change pinctrl state during runtime PM. This requires taking
> > a mutex, so these devices cannot be marked as IRQ safe.
> > 
> > Discovered through lockdep.
> 
> I removed this sentence...

Sorry about that.

> 
> > Signed-off-by: Mikko Perttunen <mperttunen@nvidia.com>
> 
> ... and merged the patch in i2c/i2c-host-2.
> 
> Thanks,
> Andi
> 

Thank you!

Looks like there's a COMPILE_TEST failure so we'll need to do something like ..

diff --git a/drivers/i2c/busses/Kconfig b/drivers/i2c/busses/Kconfig
index e11d50750e63..09152088b79f 100644
--- a/drivers/i2c/busses/Kconfig
+++ b/drivers/i2c/busses/Kconfig
@@ -1211,7 +1211,7 @@ config I2C_SYNQUACER
 
 config I2C_TEGRA
 	tristate "NVIDIA Tegra internal I2C controller"
-	depends on ARCH_TEGRA || (COMPILE_TEST && (ARC || ARM || ARM64 || M68K || RISCV || SUPERH || SPARC))
+	depends on ARCH_TEGRA || (COMPILE_TEST && (ARC || ARM || ARM64 || M68K || RISCV || SUPERH || SPARC) && PINCTRL)
 	# COMPILE_TEST needs architectures with readsX()/writesX() primitives
 	help
 	  If you say yes to this option, support will be included for the
-- 
2.52.0

Please let me know how you'd like to go about it.

Mikko