From: Andreas Kemnade <andreas@kemnade.info>
To: Tero Kristo <t-kristo@ti.com>
Cc: <mturquette@baylibre.com>, <sboyd@kernel.org>,
<linux-omap@vger.kernel.org>, <linux-clk@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <bcousson@baylibre.com>,
<paul@pwsan.com>, <tony@atomide.com>,
<letux-kernel@openphoenux.org>
Subject: Re: [PATCH 2/2] arm: omap_hwmod disable ick autoidling when a hwmod requires that
Date: Thu, 8 Nov 2018 12:08:47 +0100 [thread overview]
Message-ID: <20181108120847.1ef7ec02@kemnade.info> (raw)
In-Reply-To: <bac125b7-68c5-4c90-ad98-22872db9ccff@ti.com>
[-- Attachment #1: Type: text/plain, Size: 2067 bytes --]
Hi,
On Thu, 8 Nov 2018 12:26:08 +0200
Tero Kristo <t-kristo@ti.com> wrote:
> On 04/10/2018 23:38, Andreas Kemnade wrote:
> > Deny autoidle for hwmods with the OCPIF_SWSUP_IDLE flag,
> > that makes hwmods working properly which cannot handle
> > autoidle properly in lower power states.
> > Affected is e. g. the omap_hdq.
> > Since an ick might have mulitple users, autoidle is disabled
> > when an individual user requires that rather than in
> > _setup_iclk_autoidle. dss_ick is an example for that.
> >
> > Signed-off-by: Andreas Kemnade <andreas@kemnade.info>
> > ---
> > arch/arm/mach-omap2/omap_hwmod.c | 16 ++++++++++++----
> > 1 file changed, 12 insertions(+), 4 deletions(-)
> >
> > diff --git a/arch/arm/mach-omap2/omap_hwmod.c b/arch/arm/mach-omap2/omap_hwmod.c
> > index bb641e6c93d0..0078b0e1d242 100644
> > --- a/arch/arm/mach-omap2/omap_hwmod.c
> > +++ b/arch/arm/mach-omap2/omap_hwmod.c
> > @@ -986,8 +986,10 @@ static int _enable_clocks(struct omap_hwmod *oh)
> > clk_enable(oh->_clk);
> >
> > list_for_each_entry(os, &oh->slave_ports, node) {
> > - if (os->_clk && (os->flags & OCPIF_SWSUP_IDLE))
> > + if (os->_clk && (os->flags & OCPIF_SWSUP_IDLE)) {
> > + omap2_clk_deny_idle(os->_clk);
>
> I think calling this unconditionally across all platforms / clock types
> might cause problems. Checking kernel, am33xx seems to have one clock
> with this flag that is not of omap2 type. Do we have any testing data
> that this doesn't break things?
>
Somehow I have missed that am33xx clock. I have not tested it on that
platform. Concerning am3xxx I have only a beaglebone block but it not
am33xx I guess. So I have to recheck I guess.
But I think the intention of this flag was to control autoidle
vs. sw-controlled idle according to...
[...]
> > if (os->flags & OCPIF_SWSUP_IDLE) {
> > - /* XXX omap_iclk_deny_idle(c); */
> > + /*
this comment. So we need a if (clock_is_omap2()) or something like that
or remove that flag from any other clocks?
Regards,
Andreas
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-11-08 11:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-04 20:38 [PATCH 0/2] mach-omap2: handle autoidle denial Andreas Kemnade
2018-10-04 20:38 ` [PATCH 1/2] clk: ti: add a usecount for autoidle Andreas Kemnade
2018-11-08 10:36 ` Tero Kristo
2018-11-10 7:52 ` Andreas Kemnade
2018-10-04 20:38 ` [PATCH 2/2] arm: omap_hwmod disable ick autoidling when a hwmod requires that Andreas Kemnade
2018-11-08 10:26 ` Tero Kristo
2018-11-08 11:08 ` Andreas Kemnade [this message]
2018-11-08 12:35 ` Tero Kristo
2018-11-08 6:00 ` [PATCH 0/2] mach-omap2: handle autoidle denial Andreas Kemnade
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=20181108120847.1ef7ec02@kemnade.info \
--to=andreas@kemnade.info \
--cc=bcousson@baylibre.com \
--cc=letux-kernel@openphoenux.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=paul@pwsan.com \
--cc=sboyd@kernel.org \
--cc=t-kristo@ti.com \
--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