From: Alexander Sverdlin <alexander.sverdlin@gmail.com>
To: Shree Ramamoorthy <s-ramamoorthy@ti.com>,
Francesco Dolcini <francesco@dolcini.it>
Cc: Andreas Kemnade <andreas@kemnade.info>,
Jerome Neanne <jneanne@baylibre.com>,
Nishanth Menon <nm@ti.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: tps65219/am62p kernel oops
Date: Mon, 16 Mar 2026 18:41:31 +0100 [thread overview]
Message-ID: <50002e822278e6474dfd1ea37f22aad1c27003cd.camel@gmail.com> (raw)
In-Reply-To: <d6de7066-a802-41fc-bb10-2f5d248743db@ti.com>
Hi Shree,
On Tue, 2025-12-09 at 12:16 -0600, Shree Ramamoorthy wrote:
> > > > > > > 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'll try out implementing and testing the solution, but will get to it early next week. Will email with any updates!
> > What's the status on this? Were you able to do any progress or work on
> > it?
> >
> > Thanks
> > Francesco
>
> Thanks for following up on this, the task got lost on my end. My apologies!
> The original line deleted `irq_data[i].rdev = rdev;` was never replaced.
> The correct code should be re-implementing a version of the tps65219_get_rdev_by_name() function that was removed in commit 64a6b57
> & add in irq_data.rdev = rdev;` where the other irq_data fields are being assigned within _probe.
>
> Is there anything missing with this solution?
Thanks for looking into this issue!
I would be happy to test your patch, but cannot find it.
Have you published it in the meanwhile?
Regards,
--
Alexander Sverdlin.
prev parent reply other threads:[~2026-03-16 17:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 13:21 tps65219/am62p kernel oops Francesco Dolcini
2025-04-29 16:52 ` Andreas Kemnade
2025-04-30 8:01 ` Francesco Dolcini
2025-04-30 10:21 ` Francesco Dolcini
2025-05-01 15:32 ` Shree Ramamoorthy
2025-12-09 13:43 ` Francesco Dolcini
2025-12-09 18:16 ` Shree Ramamoorthy
2025-12-10 8:10 ` Francesco Dolcini
2026-03-16 17:41 ` Alexander Sverdlin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50002e822278e6474dfd1ea37f22aad1c27003cd.camel@gmail.com \
--to=alexander.sverdlin@gmail.com \
--cc=andreas@kemnade.info \
--cc=francesco@dolcini.it \
--cc=jneanne@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=s-ramamoorthy@ti.com \
--cc=vigneshr@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox