Re: tps65219/am62p kernel oops

Francesco Dolcini
2025-04-30T10:21:41Z

On Wed, Apr 30, 2025 at 10:01:14AM +0200, Francesco Dolcini wrote:
> On Tue, Apr 29, 2025 at 06:52:40PM +0200, Andreas Kemnade wrote:
> > Am Tue, 29 Apr 2025 15:21:19 +0200
> > schrieb Francesco Dolcini <francesco@dolcini.it>:
> >
> > > Hello all,
> > > while working on adding support in mainline for a new board based on TI
> > > AM62P SoC I noticed the following Kernel Oops.
> > >
> > > This oops was reproduced running current Linux
> > > master, 6.15.0-rc4+, ca91b9500108d4cf083a635c2e11c884d5dd20ea, but I was able
> > > to reproduce the same with 6.14.4.
> > >
> >
> > [...]
> > > [ +0.000022] Call trace:
> > > [ +0.000011] regulator_notifier_call_chain+0x20/0xa4 (P)
> > > [ +0.000018] tps65219_regulator_irq_handler+0x34/0x80
> >
> > wild guessing: maybe because irqdata->rdev is not initalized in
> > _probe()? At least I do not see where it would be initialized.
>
> your wild guess seems correct, I'll send a proper patch with your
> suggested-by after doing a couple of more tests, thanks.

so, the bug is clear, however the fix is not an obvious one liner as I was
wishing.

we would need to add a link from each of the interrupts to the specific
regulator. as of now such a connection is not existing in the code.

I would not have the time to fix the code in the next few days, if someone is
able to pick this up before, just let me know ...

Francesco