public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kalle.valo@iki.fi>
To: Kevin Hilman <khilman@deeprootsystems.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: OMAP PM status?
Date: Thu, 13 Aug 2009 19:41:33 +0300	[thread overview]
Message-ID: <877hx7k6o2.fsf@litku.valot.fi> (raw)
In-Reply-To: <873a7wsjm9.fsf@deeprootsystems.com> (Kevin Hilman's message of "Wed\, 12 Aug 2009 16\:22\:22 -0700")

Kevin Hilman <khilman@deeprootsystems.com> writes:

> Hi Kalle,

Hello,

> Kalle Valo <kalle.valo@iki.fi> writes:
>
>> as you might guess, I'm eagerly waiting for OMAP PM support to hit
>> mainline :) I'm just curious, what's the current status? Are we
>> going to get PM support in 2.6.32?
>
> Hmmm, good question.  To avoid giving an answer that can be archived
> and used against me, I updated the PM branch wiki page[1] with a
> 'mainline plans' section[2] which I can edit as plans slip^Wchange. :)

Excellent, the page was very helpful for me and I'm sure also for
others.

>> Especially I'm interested about 2420 support for n8x0.
>
> Well, I'm afraid I've done basically no testing for OMAP2, and have
> been focusing solely on OMAP3.  I'm pretty sure things at least should
> compile for OMAP2, as care has been taken to keep OMAP2 up to speed
> with OMAP3 for the base features, but I haven't done any boot testing
> on OMAP2 for some time.

I'm sorry to hear that, but I understand that you don't have time for
everything.

> That being said, all the infrastructure for OMAP2 that was in
> linux-omap is already in mainline so will work as good as it did in
> linux-omap.  The last time I actually tried PM on OMAP2, I found/fixed
> a bug[3] in the asm sleep code for OMAP2 that was causing fault.  At
> least it no longer faults when suspended
>
> Of course, I'll be glad to take any OMAP2 patches/fixes and get them
> upstream with the rest of my changes, but I'm afraid with my current
> plans, I do not have the cycles to spend on OMAP2.

As soon as I find some spare time (which usually means three to four
months from now :) I'll start experimenting with N800 PM. If I have any
problems, I'll send email to the list as usual.

Thanks.

-- 
Kalle Valo

      reply	other threads:[~2009-08-13 16:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-12 19:40 OMAP PM status? Kalle Valo
2009-08-12 23:22 ` Kevin Hilman
2009-08-13 16:41   ` Kalle Valo [this message]

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=877hx7k6o2.fsf@litku.valot.fi \
    --to=kalle.valo@iki.fi \
    --cc=khilman@deeprootsystems.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox