From: Tero Kristo <t-kristo@ti.com>
To: Stephen Boyd <sboyd@kernel.org>,
Andreas Kemnade <andreas@kemnade.info>, <bcousson@baylibre.com>,
<letux-kernel@openphoenux.org>, <linux-clk@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-omap@vger.kernel.org>,
<mturquette@baylibre.com>, <paul@pwsan.com>, <tony@atomide.com>
Subject: Re: [PATCH v2 0/3] mach-omap2: handle autoidle denial
Date: Fri, 30 Nov 2018 09:37:35 +0200 [thread overview]
Message-ID: <6c450d4f-8dbf-5122-edcc-3ac17e295bbe@ti.com> (raw)
In-Reply-To: <154353757335.88331.5161306764126530976@swboyd.mtv.corp.google.com>
On 30/11/2018 02:26, Stephen Boyd wrote:
> Quoting Andreas Kemnade (2018-11-10 12:31:12)
>> On the gta04 with a dm3730 omap_hdq does not work properly when the
>> device enters lower power states. Idling uart1 and 2 is enough
>> to show up that problem, if there are no other things enabled.
>> Further research reveals that hdq iclk must not be turned off during
>> transfers, also according to the TRM. That fact is also correctly described
>> in the flags but the code to handle that is incomplete.
>>
>> To handle multiple users of a single ick, autoidle is disabled
>> when a user of that ick requires that (has the OCPIF_SWSUP_IDLE))
>>
>> Changes since v1:
>> - uses spinlocks instead of mutexes
>> - invert counter logic
>> - check whether clock type is basic
>>
>
> I'm expecting someone like Tero or Tony to review this.
>
Rest of it looks fine to me, except for the discussion under the
CLK_IS_BASIC flag, which might trigger a bigger rework of the code.
-Tero
--
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
next prev parent reply other threads:[~2018-11-30 7:37 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-10 20:31 [PATCH v2 0/3] mach-omap2: handle autoidle denial Andreas Kemnade
2018-11-10 20:31 ` [PATCH v2 1/3] clk: ti: add a usecount for autoidle Andreas Kemnade
2018-11-10 20:31 ` [PATCH v2 2/3] clk: ti: check clock type before doing autoidle ops Andreas Kemnade
2018-11-30 0:25 ` Stephen Boyd
2018-11-30 6:15 ` Andreas Kemnade
2018-11-30 7:20 ` Stephen Boyd
2018-11-30 7:35 ` Tero Kristo
2018-11-30 7:57 ` Stephen Boyd
2018-11-30 9:20 ` Tero Kristo
2018-11-30 12:17 ` Andreas Kemnade
2018-11-30 15:37 ` Tony Lindgren
2018-11-30 23:51 ` Stephen Boyd
2018-12-03 15:39 ` Tony Lindgren
2018-12-03 16:22 ` Andreas Kemnade
2018-12-04 16:45 ` Tony Lindgren
2018-12-27 20:12 ` Andreas Kemnade
2018-12-28 20:02 ` Tony Lindgren
2018-12-31 7:23 ` Tero Kristo
2018-12-31 8:30 ` Andreas Kemnade
2019-01-03 23:39 ` Stephen Boyd
2019-01-04 7:28 ` Tero Kristo
2019-01-11 22:49 ` Stephen Boyd
2019-01-14 8:25 ` Tero Kristo
2018-12-03 17:06 ` Stephen Boyd
2018-11-10 20:31 ` [PATCH v2 3/3] arm: omap_hwmod disable ick autoidling when a hwmod requires that Andreas Kemnade
2018-11-30 0:26 ` [PATCH v2 0/3] mach-omap2: handle autoidle denial Stephen Boyd
2018-11-30 7:37 ` Tero Kristo [this message]
2018-11-30 7:57 ` Stephen Boyd
2018-11-30 9:21 ` 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=6c450d4f-8dbf-5122-edcc-3ac17e295bbe@ti.com \
--to=t-kristo@ti.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=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;
as well as URLs for NNTP newsgroup(s).