From: Timo Kokkonen <timo.t.kokkonen@iki.fi>
To: Jean Pihet <jean.pihet@newoldbits.com>
Cc: linux-omap@vger.kernel.org, linux-media@vger.kernel.org
Subject: Re: [PATCH 7/8] ir-rx51: Remove MPU wakeup latency adjustments
Date: Fri, 24 Aug 2012 13:48:59 +0300 [thread overview]
Message-ID: <50375C1B.5000308@iki.fi> (raw)
In-Reply-To: <CAORVsuX_J0xkYOaTN_v3KG7MLeaeFgf1zGMbQNoXikzur_MKSA@mail.gmail.com>
On 08/24/12 12:04, Jean Pihet wrote:
> Hi Timo,
>
> On Fri, Aug 24, 2012 at 10:14 AM, Timo Kokkonen <timo.t.kokkonen@iki.fi> wrote:
>> Hi Jean,
>>
>> On 08/23/12 14:58, Jean Pihet wrote:
>>> Hi Timo,
>>>
>>> On Wed, Aug 22, 2012 at 9:50 PM, Timo Kokkonen <timo.t.kokkonen@iki.fi> wrote:
>>> That is correct. The API to use is the PM QoS API which cpuidle uses
>>> to determine the next MPU state based on the allowed latency.
>>>
>>>> A more appropriate fix for the problem would be to modify the idle
>>>> layer so that it does not allow MPU going to too deep sleep modes when
>>>> it is expected that the timers need to wake up MPU.
>>> The idle layer already uses the PM QoS framework to decide the next
>>> MPU state. I think the right solution is to convert from
>>> omap_pm_set_max_mpu_wakeup_lat to the PM QoS API.
>>>
>>> Cf. http://marc.info/?l=linux-omap&m=133968658305580&w=2 for an
>>> example of the conversion.
>>>
>>
>> Thanks. It looks like really easy and straightforward conversion.
>> However, I couldn't find the patch you were referring to from any trees
> Correct, this patch is not applied to the mainline code yet, it is
> provided as an example of the conversion.
>
>> I could find. So, I take that this API does not really have omap2
>> support in it yet? I tried git grepping through the source and to me it
>> appears there is nothing in place yet that actually restricts the MPU
>> sleep states on omap2 when requested.
> The MPU state is controlled from the cpuidle framework, which
> retrieves the MPU allowed latency from the PM QoS framework. This is
> supported on OMAP2.
> Cf. the table of states and the associated latency in
> arch/arm/mach-omap2/cpuidle34xx.c.
>
Thanks for the pointer. I took a look at the state table and adjusted
the latency requirements in my code. If I lower the latency from 50us to
10us, the timers are then waking up as they should be.
I'll replace this patch with one where I convert it using the new API.
Thanks!
-Timo
next prev parent reply other threads:[~2012-08-24 10:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-22 19:50 [PATCH 0/8] ir-rx51: Fixes in response to review comments Timo Kokkonen
2012-08-22 19:50 ` [PATCH 1/8] ir-rx51: Adjust dependencies Timo Kokkonen
2012-08-22 19:50 ` [PATCH 2/8] ir-rx51: Handle signals properly Timo Kokkonen
2012-08-24 10:03 ` Sean Young
2012-08-24 10:29 ` Timo Kokkonen
2012-08-22 19:50 ` [PATCH 3/8] ir-rx51: Trivial fixes Timo Kokkonen
2012-08-22 19:50 ` [PATCH 4/8] ir-rx51: Clean up timer initialization code Timo Kokkonen
2012-08-22 19:50 ` [PATCH 5/8] ir-rx51: Move platform data checking into probe function Timo Kokkonen
2012-08-22 19:50 ` [PATCH 6/8] ir-rx51: Replace module_{init,exit} macros with module_platform_driver Timo Kokkonen
2012-08-22 19:50 ` [PATCH 7/8] ir-rx51: Remove MPU wakeup latency adjustments Timo Kokkonen
2012-08-23 11:58 ` Jean Pihet
2012-08-24 8:14 ` Timo Kokkonen
2012-08-24 9:04 ` Jean Pihet
2012-08-24 10:48 ` Timo Kokkonen [this message]
2012-08-22 19:50 ` [PATCH 8/8] ir-rx51: Remove useless variable from struct lirc_rx51 Timo Kokkonen
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=50375C1B.5000308@iki.fi \
--to=timo.t.kokkonen@iki.fi \
--cc=jean.pihet@newoldbits.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
/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.