From: Andreas Kemnade <andreas@kemnade.info>
To: Tony Lindgren <tony@atomide.com>
Cc: Adam Ford <aford173@gmail.com>,
bcousson@baylibre.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, linux-omap@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
"H. Nikolaus Schaller" <hns@goldelico.com>
Subject: Re: [PATCH] ARM: dts: gta04: fix excess dma channel usage
Date: Thu, 7 Nov 2024 10:35:52 +0100 [thread overview]
Message-ID: <20241107103552.22583403@akair> (raw)
In-Reply-To: <20230122100852.32ae082c@aktux>
Revisiting it again...
Am Sun, 22 Jan 2023 10:08:52 +0100
schrieb Andreas Kemnade <andreas@kemnade.info>:
> On Thu, 19 Jan 2023 09:30:20 +0200
> Tony Lindgren <tony@atomide.com> wrote:
>
> > * Tony Lindgren <tony@atomide.com> [230116 17:33]:
> > > * Adam Ford <aford173@gmail.com> [230116 17:00]:
> > > > Doesn't this imply the target-module stuff needs to be implemented for
> > > > the drivers? It looks like a lot of the omap3 drivers are still using
> > > > hwmods although some have target-modules. In this case, the mcspi
> > > > drivers that Andreas is disabling don't appear to have target-module
> > > > stuff configured.
> > >
> > > Sorry I don't remember if omap_device.c ignores status disabled or not.
> > > But in any case, it should be trivial to update omap3.dtsi to configure
> > > some of the devices like mcspi to probe with device tree data and ti-sysc
> > > as needed.
> >
> > So as long as gta04 power management still behaves with this patch it
> > should good to go.
> >
> # sleep 10 ; /usr/local/bin/idledump
> CM_IDLEST1_CORE 00000042
RAM + SCM on, no issue, cross-checked, force-enabling mcspi brings more
activity, so this an indication thet mcspi is off.
> CM_IDLEST3_CORE 00000000
> CM_FCLKEN1_CORE 00000000
same here with force-enabling mcspi, brings in some bits set.
> CM_FCLKEN3_CORE 00000002
see comments below.
> CM_CLKSTST_CORE 00000003
> CM_IDLEST_CKGEN 00000209
this becomes 1 without this patch.
> CM_IDLEST2_CKGEN 00000000
> CM_FCLKEN_DSS 00000000
> CM_IDLEST_DSS 00000000
> CM_FCLKEN_CAM 00000000
> CM_IDLEST_CAM 00000000
> CM_FCLKEN_PER 00000000
> CM_IDLEST_PER 00000000
>
>
> FCLKEN3_CORE becomes 0 after unbinding the bandgap sensor.
>
> but...
> # cat /sys/kernel/debug/pm_debug/time
> usbhost_pwrdm (ON),OFF:830267486567,RET:0,INA:0,ON:12202880865
> sgx_pwrdm (INA),OFF:0,RET:0,INA:841224365234,ON:1245971680
> core_pwrdm (ON),OFF:0,RET:0,INA:0,ON:842470336914
> per_pwrdm (ON),OFF:520406799328,RET:30043365464,INA:0,ON:292020111087
>
> hmmm....
>
> but does not look like anything related to mcspi*.
>
it does not look like, but it is, but how... There is something below
my radar.
Regards,
Andreas
next prev parent reply other threads:[~2024-11-07 9:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 21:11 [PATCH] ARM: dts: gta04: fix excess dma channel usage Andreas Kemnade
2023-01-16 14:16 ` Adam Ford
2023-01-16 14:51 ` Tony Lindgren
2023-01-16 15:29 ` H. Nikolaus Schaller
2023-01-16 17:00 ` Tony Lindgren
2023-01-16 16:39 ` Andreas Kemnade
2023-01-16 16:56 ` Tony Lindgren
2023-01-16 17:00 ` Adam Ford
2023-01-16 17:08 ` Tony Lindgren
2023-01-19 7:30 ` Tony Lindgren
2023-01-22 9:08 ` Andreas Kemnade
2024-11-07 9:35 ` Andreas Kemnade [this message]
2023-03-27 8:13 ` 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=20241107103552.22583403@akair \
--to=andreas@kemnade.info \
--cc=aford173@gmail.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=hns@goldelico.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.