From: Tasslehoff Kjappfot <tasskjapp@gmail.com>
To: "Shilimkar, Santosh" <santosh.shilimkar@ti.com>
Cc: Kevin Hilman <khilman@ti.com>, linux-omap@vger.kernel.org
Subject: Re: Bringing back gptimer_wakeup
Date: Tue, 19 Jun 2012 10:24:50 +0200 [thread overview]
Message-ID: <4FE03752.7030009@gmail.com> (raw)
In-Reply-To: <CAMQu2gwsL6v06fk=nJuRtuP0HZ5Jt0BmitaQ=FHJeVC__QQXAw@mail.gmail.com>
On 06/19/2012 08:07 AM, Shilimkar, Santosh wrote:
> On Mon, Jun 18, 2012 at 11:31 PM, Kevin Hilman<khilman@ti.com> wrote:
>> Tasslehoff Kjappfot<tasskjapp@gmail.com> writes:
>>
>>> The support for using a timer to wake from suspend was removed in:
>>> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=98e182a26bbbf5575457622337684ef61493e864
>>>
>>> I found an alternative patch
>>> (http://www.mail-archive.com/linux-omap@vger.kernel.org/msg47836.html)
>>> that claimed to keep it working using GPTIMER1 instead, but I haven't
>>> been able to make it work (likely because the timer code has changed a
>>> good deal since the patch was posted).
>>>
>>> Anyone got
>>> a) a patch that enables this feature on newer kernels, or
>>> b) an idea how the patch above can be made to work?
>>
>> The branch below (based on v3.4) will work (at least on OMAP3)
>>
>> We've been holding off on putting this back becasue the timer interface
>> has been going through some major cleanup/rework, but I would like to
>> see this make it back in soonish.
>>
> I got an off-list message from Tasslehoff, that the patch I sent worked for him.
>
> Regards
> Santosh
Ah, that was meant to be an on-list message. Santosh' fix worked well on
my 3.2.18 kernel.
- Tasslehoff
next prev parent reply other threads:[~2012-06-19 8:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 9:18 Bringing back gptimer_wakeup Tasslehoff Kjappfot
2012-06-18 10:00 ` Shilimkar, Santosh
2012-06-18 18:01 ` Kevin Hilman
2012-06-19 6:07 ` Shilimkar, Santosh
2012-06-19 8:24 ` Tasslehoff Kjappfot [this message]
2012-06-28 14:00 ` Kevin Hilman
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=4FE03752.7030009@gmail.com \
--to=tasskjapp@gmail.com \
--cc=khilman@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=santosh.shilimkar@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