From: mattias.wallin@stericsson.com (Mattias Wallin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 0/3] clocksource: add db8500 PRCMU timer
Date: Fri, 10 Jun 2011 18:00:19 +0200 [thread overview]
Message-ID: <4DF23F93.8070102@stericsson.com> (raw)
In-Reply-To: <4DF1DBB2.4040501@stericsson.com>
On 06/10/2011 10:54 AM, Mattias Wallin wrote:
> On 06/09/2011 11:59 PM, Russell King - ARM Linux wrote:
>> No - I'd like you to check whether the patch I sent fixes your
>> sched_clock problem across suspend/resume so that we can get that sorted
>> for everyone, instead of coming up with platform specific fixes. Then
>> we can work out how to hook that into cpuidle so that it works properly
>> there.
>
> Ahh, I see your plan. I was focused on the cpuidle problem and your
> patch only addressed suspend/resume.
> Anyway, now that I understand more what you are after I'll have a look
> at it and come back to you.
Unfortunately you will not get an answer if your patch works or not now.
Our u8500 mainline code is missing suspend support and I have been
trying to get suspend for u8500 to work without success. Since I will be
away for two weeks I will try to get the suspend guys to work on it
meanwhile.
Kind Regards,
Mattias Wallin
next prev parent reply other threads:[~2011-06-10 16:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-02 9:34 [PATCHv2 0/3] clocksource: add db8500 PRCMU timer Mattias Wallin
2011-06-02 9:46 ` Russell King - ARM Linux
2011-06-02 10:18 ` Mattias Wallin
2011-06-02 11:01 ` Russell King - ARM Linux
2011-06-02 12:10 ` Mattias Wallin
2011-06-02 12:57 ` Santosh Shilimkar
2011-06-02 13:04 ` Russell King - ARM Linux
2011-06-02 13:16 ` Santosh Shilimkar
2011-06-02 18:47 ` john stultz
2011-06-08 13:44 ` Mattias Wallin
2011-06-09 21:59 ` Russell King - ARM Linux
2011-06-10 8:54 ` Mattias Wallin
2011-06-10 16:00 ` Mattias Wallin [this message]
2011-07-10 14:19 ` Russell King - ARM Linux
2012-02-04 12:30 ` Russell King - ARM Linux
2012-02-05 15:11 ` Linus Walleij
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=4DF23F93.8070102@stericsson.com \
--to=mattias.wallin@stericsson.com \
--cc=linux-arm-kernel@lists.infradead.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 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).