From: Andreas Kemnade <andreas@kemnade.info>
To: Tony Lindgren <tony@atomide.com>
Cc: Jarkko Nikula <jarkko.nikula@bitmer.com>,
linux-omap@vger.kernel.org,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: Re: Regression with e428e250fde6 on BeagleBoard Rev C2
Date: Tue, 21 Sep 2021 18:25:47 +0200 [thread overview]
Message-ID: <20210921182547.6dd6a382@aktux> (raw)
In-Reply-To: <YUmDKzMko81wc/C+@atomide.com>
On Tue, 21 Sep 2021 10:00:59 +0300
Tony Lindgren <tony@atomide.com> wrote:
> * Andreas Kemnade <andreas@kemnade.info> [210920 15:26]:
> > Hi,
> >
> > On Mon, 20 Sep 2021 16:34:59 +0300
> > Tony Lindgren <tony@atomide.com> wrote:
> >
> > > > I fail to understand how omap3isp affects this since it actually disable
> > > > clocks after probe. Does it keep some power domain active which then
> > > > keeps the timer active etc?
> > >
> > > Sounds like it's because omap3isp never allows the SoC to enter deeper
> > > idle states. The mpu clock is stopped for idle states.
> >
> > On GTA04 I experienced also some strange pm issues with omap3isp:
> > rmmod clears up everything fine.
> >
> > After probing, clocks seems to be turned off, but power consumption
> > does not drop. It only drops when there is an iommu_detach paired to
> > that iommu_attach in the driver.
> > But if I add it, the driver does not work properly.
>
> Are you also seeing a timer issue? Or just the omap3isp not idling the
> SoC issue?
>
Just the omap3isp not idling the SoC.
That are just general pm experience I had with the omap3isp issue, I
have seen on earlier kernel versions but never succeeded in properly
fixing them. I have not tried the 5.15-rcX on gta04 yet.
Regards,
Andreas
next prev parent reply other threads:[~2021-09-21 16:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-19 17:41 Regression with e428e250fde6 on BeagleBoard Rev C2 Jarkko Nikula
2021-09-20 13:34 ` Tony Lindgren
2021-09-20 14:52 ` Andreas Kemnade
2021-09-21 7:00 ` Tony Lindgren
2021-09-21 16:25 ` Andreas Kemnade [this message]
2021-09-20 16:35 ` Jarkko Nikula
2021-09-21 7:00 ` Tony Lindgren
2021-09-21 17:49 ` Jarkko Nikula
2021-09-22 10:07 ` Tony Lindgren
2021-09-22 17:21 ` Jarkko Nikula
2021-09-23 5:41 ` Tony Lindgren
2021-09-23 18:03 ` Jarkko Nikula
2021-09-24 7:02 ` Tony Lindgren
2021-09-25 14:55 ` Jarkko Nikula
2021-09-30 7:04 ` Tony Lindgren
2021-10-20 17:52 ` Jarkko Nikula
2021-10-21 13:58 ` Tony Lindgren
2021-10-21 18:10 ` Jarkko Nikula
2021-10-24 6:41 ` Tony Lindgren
2021-09-20 18:19 ` H. Nikolaus Schaller
2021-09-21 7:02 ` Tony Lindgren
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=20210921182547.6dd6a382@aktux \
--to=andreas@kemnade.info \
--cc=jarkko.nikula@bitmer.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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