From: Andreas Kemnade <andreas@kemnade.info>
To: Tony Lindgren <tony@atomide.com>
Cc: Roger Quadros <rogerq@kernel.org>,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
hns@goldelico.com, linux-omap@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
aaro.koskinen@iki.fi, khilman@baylibre.com,
stable@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: ti/omap: gta04: fix pm issues caused by spi module
Date: Mon, 11 Nov 2024 23:46:04 +0100 [thread overview]
Message-ID: <20241111234604.66a9691b@akair> (raw)
In-Reply-To: <20241111193117.5a5f5ecb@akair>
Am Mon, 11 Nov 2024 19:31:17 +0100
schrieb Andreas Kemnade <andreas@kemnade.info>:
> Am Mon, 11 Nov 2024 17:09:53 +0200
> schrieb Tony Lindgren <tony@atomide.com>:
>
> > * Andreas Kemnade <andreas@kemnade.info> [241108 17:41]:
> > > They are not used, if they are just disabled, kernel does not touch
> > > them, so if it is there, the kernel can handle
> > > pm. At least as long as it is not under ti,sysc.
> > >
> > > There are probably cleaner solutions for this, but for a CC: stable I
> > > would prefer something less invasive.
> >
> > For unused devices, it's best to configure things to use ti-sysc, and
> > then set status disabled (or reserved) for the child devices only. This
> > way the parent interconnect target module is PM runtime managed by
> > Linux, and it's power domain gets properly idled for the unused devices
> > too.
> >
> Hmm, we also have omap_hwmod_setup_all() which is still called if
> without device nodes being available.
>
> Converting mcspi to ti-sysc is more than 100 lines. So it does not
> qualify for stable.
>
> > > I can try a ti-sysc based fix in parallel.
> >
> > Yeah that should be trivial hopefully :)
> >
> I played around, got pm issues too, tried to force-enable things (via
> power/control),
> watched CM_IDLEST1_CORE and CM_FCLKEN1_CORE, they behave. Bits are set
> or reset.
>
> but not CM_IDLEST_CKGEN, it is 0x209 instead of 0x1.
>
> I test from initramfs, so no mmc activity involved
>
> removing status = "disabled" from mcspi3 solves things.
> With and without ti-sysc conversion. removing status = "disabled" from
> mcspi4 seems not to help.
>
> That all cannot be... I will retry tomorrow.
>
well, I tried a bit further:
I build the omap spi driver as module.
and booted With mcspi3 not disabled and no module autoload.
without module loaded: pm bad, same as with mcspi3 disabled
with module loaded: core pm ok
with module loaded and unloaded: core pm ok.
so at least a trace.
Regards,
Andreas
next prev parent reply other threads:[~2024-11-11 22:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 22:51 [PATCH] ARM: dts: ti/omap: gta04: fix pm issues caused by spi module Andreas Kemnade
2024-11-08 12:42 ` Roger Quadros
2024-11-08 17:41 ` Andreas Kemnade
2024-11-09 10:59 ` Roger Quadros
2024-11-11 15:09 ` Tony Lindgren
2024-11-11 18:31 ` Andreas Kemnade
2024-11-11 22:46 ` Andreas Kemnade [this message]
2024-11-16 20:27 ` Andreas Kemnade
2024-11-17 11:19 ` Tony Lindgren
2024-11-17 21:22 ` Andreas Kemnade
2024-11-18 13:08 ` Roger Quadros
2024-11-27 22:58 ` Andreas Kemnade
2024-11-28 12:39 ` Roger Quadros
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=20241111234604.66a9691b@akair \
--to=andreas@kemnade.info \
--cc=aaro.koskinen@iki.fi \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hns@goldelico.com \
--cc=khilman@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=robh@kernel.org \
--cc=rogerq@kernel.org \
--cc=stable@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