From: Tony Lindgren <tony@atomide.com>
To: Andreas Kemnade <andreas@kemnade.info>
Cc: t-kristo@ti.com, 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, letux-kernel@openphoenux.org
Subject: Re: [PATCH v3 3/3] arm: omap_hwmod disable ick autoidling when a hwmod requires that
Date: Fri, 18 Jan 2019 07:48:07 -0800 [thread overview]
Message-ID: <20190118154807.GV5544@atomide.com> (raw)
In-Reply-To: <20190116220429.9136-4-andreas@kemnade.info>
Hi,
* Andreas Kemnade <andreas@kemnade.info> [190116 22:04]:
> Deny autoidle for hwmods with the OCPIF_SWSUP_IDLE flag,
> that makes hwmods working properly which cannot handle
> autoidle properly in lower power states.
Sorry if I'm still missing something :)
But doesn't this now block autoidle for all modules
with OCPIF_SWSUP_IDLE even if they work just fine with
autoidle?
I think what you want to do is keep clocks enabled
while in use?
If so, how about using HWMOD_CLKDM_NOAUTO:
"HWMOD_CLKDM_NOAUTO: Allows the hwmod's clockdomain to
be prevented from entering HW_AUTO while hwmod is
active."
> Affected is e. g. the omap_hdq.
Have you already tried what happens if you just tag
omap_hdq with HWMOD_CLKDM_NOAUTO?
Regards,
Tony
next prev parent reply other threads:[~2019-01-18 15:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 22:04 [PATCH v3 0/3] mach-omap2: handle autoidle denial Andreas Kemnade
2019-01-16 22:04 ` [PATCH v3 1/3] clk: ti: add a usecount for autoidle Andreas Kemnade
2019-01-16 22:04 ` [PATCH v3 2/3] clk: ti: check clock type before doing autoidle ops Andreas Kemnade
2019-01-16 22:04 ` [PATCH v3 3/3] arm: omap_hwmod disable ick autoidling when a hwmod requires that Andreas Kemnade
2019-01-18 15:48 ` Tony Lindgren [this message]
2019-01-18 17:18 ` Andreas Kemnade
2019-01-18 18:36 ` Tony Lindgren
2019-01-18 19:38 ` Andreas Kemnade
2019-01-18 19:42 ` [Letux-kernel] " Andreas Kemnade
2019-01-18 19:48 ` Tony Lindgren
2019-01-19 6:39 ` J, KEERTHY
2019-01-19 7:12 ` Andreas Kemnade
2019-01-19 7:58 ` J, KEERTHY
2019-01-22 6:26 ` Keerthy
2019-01-18 19:45 ` Tony Lindgren
2019-01-21 7:12 ` Tero Kristo
2019-01-21 17:07 ` Tony Lindgren
2019-01-21 17:53 ` Andreas Kemnade
2019-01-21 19:56 ` Tony Lindgren
2019-01-21 19:58 ` [PATCH v3 0/3] mach-omap2: handle autoidle denial Tony Lindgren
2019-02-09 18:53 ` Andreas Kemnade
2019-02-15 19:19 ` Tero Kristo
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=20190118154807.GV5544@atomide.com \
--to=tony@atomide.com \
--cc=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 \
/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;
as well as URLs for NNTP newsgroup(s).