Re: [BUG] 6.16-rc7: lockdep failure with max77620-gpio/max77686-rtc

["Russell King (Oracle)" <linux@armlinux.org.uk>]

On Thu, Jul 31, 2025 at 05:16:13PM +0100, Mark Brown wrote:
> On Thu, Jul 31, 2025 at 04:57:42PM +0100, Russell King (Oracle) wrote:
> > On Thu, Jul 31, 2025 at 02:18:24PM +0100, Mark Brown wrote:
> 
> > > I *think* mutex_lock_nested() is what we're looking for here, with the
> > > depth information from the irq_desc but I'm also not super familiar with
> > > this stuff.
> 
> > I'm not sure about that, because the irq_desc locks don't nest:
> 
> >         raw_spin_lock_init(&desc->lock);
> >         lockdep_set_class(&desc->lock, &irq_desc_lock_class);
> 
> > What saves irq_desc lock nesting in this case is that
> > __irq_put_desc_unlock() unlocks desc->lock calling the
> > irq_bus_sync_unlock() method. So, I don't think we have anything at
> > the irq_desc level which deals with lock-nesting.
> 
> Yeah, and that's all internals which we're not super encouraged to peer
> at.  There should be something that'll give us a nesting level
> somewhere...  
> 
> Lockdep's handling of nesting is generally fun.

As I said, I'm just going to disable lockdep to shut up the warning and
not pursue any further time on this. If someone else cares about it
(which I doubt) they can try to come up with a solution. I suspect
nested regmap-irq is extremely rare.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!