PM branch update: rebase to .31-rc, added omap_hwmod/omap_device

The PM branch hosted in my linux-omap-pm repo[1] has been updated.

Significant changes:

- rebased to omap/master (currently v2.6.31-rc1)
- Using new omap_hwmod and omap_device infrastructure from Paul Walmsley
- more reorg into groups of commits for easier submission upstream

Tested on the following platforms using omap3_pm_defconfig with busybox-based initramfs, and tested full-chip RET and OFF in idle and suspend:

- 3430SDP
- OMAP3EVM
- Beagle
- Overo
- RX51
- Zoom2 (use 'pm-staging/zoom2' branch as well, which is Vikram's zoom2 branch rebased on top of PM branch with DEBUG_LL support and misc. fixes)

Known problems:

- no DVFS because of next item...

- SRF driver broken, needs update for new hwmod/omap_device layer (default config used PM NOOP)

- network drivers and off-mode
- various hangs when using off-while-idle and NFS-mounted rootfs
- network drivers likely need some context save/restore support

- SDRAM on 2 CSes (Beagle, Overo, RX51)
- need to boot with mem=128M so only a single CS is used
- 2 CS support patches from Jean Pihet solve this problem, but not yet merged.

- 3430SDP ES3.0
- UART1 doesn't come back from off-while-idle (ok on es3.1 SDP)

[1] http://git.kernel.org/?p=linux/kernel/git/khilman/linux-omap-pm.git

----- Original Message ----- From: "Kevin Hilman" <[email protected]>

Kevin, was this known to work earlier. Could this be related to GPMC context save/restore.

Thanks
Hemanth

I wrote this based on some early testing of the latest PM branch, where I may of still had some bugs. But I also have not seen this in a while, so it may have been just a problem when I was reworking/reordering the context save/restore code.

I decided to leave it in the 'known problems' list in case anyone else has seen it and because I didn't go back and re-test all the boards for this issue.

I don't see any issues on SDP or EVM anymore, have you tested the current PM branch for this?

Kevin

Kevin,

I did some testing with the current PM branch and don't see this issue on SDP.

I could not find the patch which fixes this issue. Can you please point us to the patch which fixes this issue?

Regards,
Teerth

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Kevin Hilman
Sent: Wednesday, August 12, 2009 8:28 PM
To: V, Hemanth
Cc: [email protected]
Subject: Re: PM branch update: rebase to .31-rc, added omap_hwmod/omap_device

I wrote this based on some early testing of the latest PM branch, where I may of still had some bugs. But I also have not seen this in a while, so it may have been just a problem when I was reworking/reordering the context save/restore code.

I decided to leave it in the 'known problems' list in case anyone else has seen it and because I didn't go back and re-test all the boards for this issue.

I don't see any issues on SDP or EVM anymore, have you tested the current PM branch for this?

Kevin
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

Thanks for testing.

To be honest, I actually don't know which patch fixed the issue. I saw the problem during some early testing of the latest PM branch, and in the process of restructuring the tree it went away.

More than likely, I had left out part of the series when reorganizing that caused this temporary problem.

I think I'll remove it from the 'known problems' list as it appears to have been operator error on my part.

Kevin