public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: "Premi, Sanjeev" <premi@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: new PM branch available
Date: Thu, 15 Jan 2009 07:01:41 -0800	[thread overview]
Message-ID: <496F4FD5.2020006@deeprootsystems.com> (raw)
In-Reply-To: <B85A65D85D7EB246BE421B3FB0FBB59301BB9845FE@dbde02.ent.ti.com>

Premi, Sanjeev wrote:
>> -----Original Message-----
>> From: linux-omap-owner@vger.kernel.org 
>> [mailto:linux-omap-owner@vger.kernel.org] On Behalf Of Kevin Hilman
>> Sent: Wednesday, January 14, 2009 10:10 PM
>> To: Sriram V
>> Cc: linux-omap@vger.kernel.org
>> Subject: Re: new PM branch available
>>
>> Sriram V wrote:
>>> Hi,
>>>     OMAP3EVM. all domains hit retention in suspend.
>>>
>>>   On enabling cpuidle, network and mmc is not stable. network is 
>>> unable to get an IP address.
>> Sriram,
>>
>> Can you send me your .config for omap3evm?  I'm trying to get 
>> my recently received EVM working but I am getting lots of 
>> garbage on the serial console on linux-omap HEAD and PM 
>> branch on omap3evm.  Do you have any additional patches for 
>> EVM that you're using?
>>
>> Kevin
>>
> 
> Hi Kevin,
> 
> I was able to test against the HEAD 'pm' branch on the EVM.
> Here are my observations with default configuration:
> 
> 1) CONFIG_DEBUG_LL=y is set by default. The kernel boots fine.
>    I did not notice any 'garbage' problems you and Koen seem to
>    be getting.
> 
> 2) Same result when CONFIG_DEBUG_LL is deselcted.

Sanjeev,

Is this on an an ES3 EVM?  What boot loader revs are you using?

> 3) With default config, suspend operation fails with this message:
>    <3>omapfb omapfb: timeout waiting for FRAME DONE

This is not a failure, just a warning from the fb driver.  This should 
not prevent retention.  I see this on beagle as well, and it doesn't 
prevent retention.

 From the log below, you didn't copy the part which reports whether all 
domains hit target state.

Kevin

> Here is a sample session from my terminal:
> 
> [root@OMAP3EVM /]# uname -a
> Linux OMAP3EVM 2.6.28-omap1-00115-g998bd56 #146 Thu Jan 15 18:47:26 IST 2009 armv7l unknown
> [root@OMAP3EVM /]# echo 1 > /sys/power/clocks_off_while_idle
> [root@OMAP3EVM /]# echo 1 > /sys/power/sleep_while_idle
> [root@OMAP3EVM /]#
> [root@OMAP3EVM /]# echo mem > /sys/power/state
> <6>PM: Syncing filesystems ... PM: Syncing filesystems ... done.
> done.
> Freezing user space processes ... Freezing user space processes ... (elapsed 0.00 seconds) (elapsed 0.00 seconds) done.
> done.
> Freezing remaining freezable tasks ... Freezing remaining freezable tasks ... (elapsed 0.06 seconds) (elapsed 0.06 seconds) done.done.
> 
> Suspending console(s) (use no_console_suspend to debug)
> Suspending console(s) (use no_console_suspend to debug)
> 
> Best regards,
> Sanjeev 
> 
>>> On Wed, Jan 14, 2009 at 3:21 AM, Kevin Hilman 
>>> <khilman@deeprootsystems.com> wrote:
>>>> Hello,
>>>>
>>>> The latest PM branch is now available[1].
>>>>
>>>> I've done basic testing of retention and off-mode (suspend and 
>>>> dynamic
>>>> idle) on Beagle and custom HW.  My SDP has something still keeping 
>>>> CORE active that others have not seen, but I have yet to 
>> debug.  Any 
>>>> other reports from SDP testing would be appreciated.
>>>>
>>>> Notable changes/updates
>>>> - rebased on latest clock updates and fixes from Paul
>>>> - clockfw pre- and post- notifiers
>>>> - DVFS for VDD2
>>>>
>>>> Full git shortlog below[2]
>>>>
>>>> Enjoy,
>>>>
>>>> Kevin
>>>>
>>>> [1] See branch 'pm' in my git repo:
>>>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap-pm.g
>>>> it which is also mirrored as the branch 'pm' of the normal 
>> linux-omap 
>>>> repo (but will not sync until 03:30 GMT)
>>>>
>>>>
>>>> [2] git shortlog:
>>>>
>>>> Carlos Chinea (1):
>>>>      OMAP3:PM: Update SSI omapdev record
>>>>
>>>> Jouni Hogander (5):
>>>>      OMAP3: PM: Use pwrdm_set_next_pwrst instead of 
>> set_pwrdm_state in idle loop
>>>>      OMAP3: PM: Fix wrong sequence in suspend.
>>>>      OMAP3: PM: Do not build suspend code if SUSPEND is not enabled
>>>>      OMAP: PM: Build fails if PM is not enabled
>>>>      OMAP2: PM: Fix omap2 build
>>>>
>>>> Kalle Jokiniemi (3):
>>>>      OMAP: PM: sysfs interface for enabling voltage off in idle
>>>>      OMAP3: PM: Fix cpu idle init sequencing
>>>>      OMAP: SRF: Fixes to shared resource framework (Ver.3)
>>>>
>>>> Kevin Hilman (4):
>>>>      OMAP3: PM: CPUidle: obey enable_off_mode flag
>>>>      OMAP3: PM: CPUidle: restrict C-states on UART activity
>>>>      OMAP3: PM: decouple PER and CORE context save and restore
>>>>      OMAP2/3: PM: system_rev -> omap_rev()
>>>>
>>>> Paul Walmsley (29):
>>>>      OMAP2/3 clock: implement clock notifier infrastructure
>>>>      OMAP clock: add notifier infrastructure
>>>>      OMAP2/3 clock: store planned clock rates into 
>> temporary rate storage
>>>>      OMAP2/3 clock: add clk post-rate-change notifiers
>>>>      OMAP2/3 clock: add clock pre-rate-change notification
>>>>      OMAP2/3 clock: add clock prepare-rate-change notifications
>>>>      OMAP2/3 clock: add clock abort-rate-change notifications
>>>>      OMAP2/3 PM: create the OMAP PM interface and add a 
>> default OMAP PM no-op layer.
>>>>      OMAP2/3 omapdev: add basic omapdev structure
>>>>      OMAP242x omapdev: add OMAP242x omapdev records
>>>>      OMAP243x omapdev: add OMAP243x omapdev records
>>>>      OMAP3xxx omapdev: add OMAP3xxx omapdev records
>>>>      OMAP2/3 omapdev: add code to walk the omapdev records
>>>>      ARM: MMU: add a Non-cacheable Normal executable memory type
>>>>      OMAP3 SRAM: mark OCM RAM as Non-cacheable Normal memory
>>>>      OMAP3 SRAM: add ARM barriers to omap3_sram_configure_core_dpll
>>>>      OMAP3 clock: add interconnect barriers to CORE DPLL M2 change
>>>>      OMAP3 SRAM: clear the SDRC PWRENA bit during SDRC 
>> frequency change
>>>>      OMAP3 SDRC: Add 166MHz, 83MHz SDRC settings for the 
>> BeagleBoard
>>>>      OMAP3 SDRC: initialize SDRC_POWER at boot
>>>>      OMAP3 SRAM: renumber registers to make space for 
>> argument passing
>>>>      OMAP3 clock: only unlock SDRC DLL if SDRC clk < 83MHz
>>>>      OMAP3 clock: use pr_debug() rather than pr_info() in 
>> some clock change code
>>>>      OMAP3 clock: remove wait for DPLL3 M2 clock to stabilize
>>>>      OMAP3 clock: initialize SDRC timings at kernel start
>>>>      OMAP3 clock: add a short delay when lowering CORE clk rate
>>>>      OMAP3 clock/SDRC: program SDRC_MR register during 
>> SDRC clock change
>>>>      OMAP3 SRAM: add more comments on the SRAM code
>>>>      OMAP3 SRAM: convert SRAM code to use macros rather than magic 
>>>> numbers
>>>>
>>>> Peter 'p2' De Schrijver (12):
>>>>      OMAP: PM counter infrastructure.
>>>>      OMAP: PM: Hook into PM counters
>>>>      OMAP: PM: Add closures to clkdm_for_each and pwrdm_for_each.
>>>>      OMAP: PM: Add pm-debug counters
>>>>      OMAP: PM debug: make powerdomains use PM-debug counters
>>>>      OMAP: PM: Add definitions for ETK pads and 
>> observability registers
>>>>      OMAP: Debug observability and ETK padconf implementation
>>>>      OMAP: Add debug observablity (debobs) Kconfig item
>>>>      OMAP: PM: Implement get_last_off_on_transaction_id()
>>>>      Save sram context after changing MPU, DSP or core clocks
>>>>      Fix omap_getspeed.
>>>>      Make sure omap cpufreq driver initializes after cpufreq 
>>>> framework and governors
>>>>
>>>> Rajendra Nayak (35):
>>>>      OMAP3: PM: GPMC context save/restore
>>>>      OMAP3: PM: GPIO context save/restore
>>>>      OMAP3: PM: I2C context save/restore
>>>>      OMAP3: PM: INTC context save/restore
>>>>      OMAP3: PM: PRCM context save/restore
>>>>      OMAP3: PM: Populate scratchpad contents
>>>>      OMAP3: PM: SCM context save/restore
>>>>      OMAP3: PM: SRAM restore function
>>>>      OMAP3: PM: handle PER/NEON/CORE in idle
>>>>      OMAP3: PM: Restore MMU table entry
>>>>      OMAP3: PM: MPU off-mode support
>>>>      OMAP3: PM: CORE domain off-mode support
>>>>      OMAP3: PM: allow runtime enable/disable of OFF mode
>>>>      OMAP3: 3430SDP minimal kernel defconfig
>>>>      OMAP3: PM: CPUidle: Basic support for C1-C2
>>>>      OMAP3: PM: CPUidle: Enables state C4
>>>>      OMAP3: PM: CPUidle: Enables C3 and C5
>>>>      OMAP3: PM: CPUidle: Safe-state on bm-activity
>>>>      OMAP3 SRF: Generic shared resource f/w
>>>>      OMAP3 SRF: MPU/CORE/PD latency modeling
>>>>      OMAP3 SRF: omap3 srf driver
>>>>      OMAP3 SRF: OMAP PM srf implementation
>>>>      OMAP3 SRF: Add CORE rate table param in OMAP-PM
>>>>      OMAP3 SRF: Add VDD1/VDD2 rate tables for 3430SDP
>>>>      OMAP3 SRF: Add virt clk nodes for VDD1/VDD2
>>>>      OMAP3 SRF: Adds OPP/Freq res's in SRF
>>>>      OMAP3 SRF: Update OMAP-PM layer
>>>>      OMAP3 SRF: Voltage scaling support
>>>>      OMAP3 SRF: VDD2 scaling support
>>>>      OMAP3 SRF: Adds sysfs control for VDD1/VDD2 OPP's
>>>>      OMAP3 PM: Replace spinlocks with mutex in SRF
>>>>      OMAP3 PM: CPUFreq driver for OMAP3
>>>>      OMAP3 PM: Update the min defconfig for 3430sdp
>>>>      OMAP3 SRF: Fix crash on non-3430SDP platforms with 
>> DVFS/CPUFreq
>>>>      OMAP3: PM: Scale VDD2 OPP for VDD1 OPP3 and higher
>>>>
>>>> Tero Kristo (26):
>>>>      OMAP: PM debug: do not print out status for meta 
>> powerdomains (dpll*)
>>>>      OMAP: PM debug: Add PRCM register dump support
>>>>      OMAP: PM: DMA context save / restore
>>>>      OMAP: PM: off-mode support for DMA on EMU/HS devices
>>>>      OMAP3: SRAM size fix for HS/EMU devices
>>>>      OMAP3 PM: off-mode support for HS/EMU devices
>>>>      OMAP3: PM: Enable SDRAM auto-refresh during sleep
>>>>      OMAP: SDRC: Add new register definitions for SDRAM controller
>>>>      OMAP3: PM: SDRC auto-refresh workaround for off-mode
>>>>      PM: Added three PLL registers to the PRCM context save
>>>>      PM: Changed secure RAM storage size from 0x8000 to 0x803F
>>>>      PM: Added suspend target state control to debugfs for OMAP3
>>>>      OMAP3: PM: Prevent PER from going OFF when CORE is going INA
>>>>      PM OMAP3: Change omap3_save_secure_ram to be called 
>> only during init
>>>>      OMAP3: PM: MPU and CORE should stay awake if there is 
>> CAM domain ACTIVE
>>>>      OMAP3: GPIO fixes for off-mode
>>>>      PM: OMAP3: Refreshed DVFS VDD1 control against latest clock fw
>>>>      OMAP3: Add support for DPLL3 divisor values higher than 2
>>>>      OMAP3: PM: Fixed VDD2 control to work from both sysfs 
>> and SRF API
>>>>      OMAP3: PM: Added DVFS OPP locking interface for VDD1 and VDD2
>>>>      OMAP3: Fix rate calculation bug in omap3_select_table_rate
>>>>      OMAP3: PM: Prevented DVFS state switches when 
>> enabling off-mode
>>>>      OMAP3: PM: Enable VDD2 OPP1
>>>>      OMAP3: PM: Fix linker error without CONFIG_PM option
>>>>      PM: OMAP3: Removed a couple of unused variables from DVFS code
>>>>      PM: OMAP3: Added support for possibly failing clk_set_rate to 
>>>> DVFS
>>>>
>>>> --
>>>> To unsubscribe from this list: send the line "unsubscribe 
>> linux-omap" 
>>>> in the body of a message to majordomo@vger.kernel.org More 
>> majordomo 
>>>> info at  http://vger.kernel.org/majordomo-info.html
>>>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe 
>> linux-omap" in the body of a message to 
>> majordomo@vger.kernel.org More majordomo info at  
>> http://vger.kernel.org/majordomo-info.html
>>


  reply	other threads:[~2009-01-15 15:01 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-13 21:51 new PM branch available Kevin Hilman
2009-01-14  7:35 ` Koen Kooi
2009-01-14 18:09   ` David Brownell
2009-01-14 22:14   ` Kevin Hilman
2009-01-15  8:18     ` Koen Kooi
2009-01-14 12:40 ` Ramesh Gupta Guntha
2009-01-14 16:35   ` Kevin Hilman
2009-01-14 13:57 ` Sriram V
2009-01-14 16:39   ` Kevin Hilman
2009-01-15 13:42     ` Premi, Sanjeev
2009-01-15 15:01       ` Kevin Hilman [this message]
2009-01-15 15:17         ` Premi, Sanjeev
2009-01-15 15:34           ` Kevin Hilman
2009-01-15 16:00             ` Premi, Sanjeev
2009-01-15 15:00     ` Sriram V
     [not found]     ` <8bf247760901150654n78b198f0o5c2270186e9c119e@mail.gmail.com>
2009-01-15 15:07       ` Kevin Hilman
2009-01-16 13:49 ` Nayak, Rajendra
2009-01-16 19:03   ` Kevin Hilman
2009-01-19 15:46     ` Premi, Sanjeev
2009-01-19 16:04       ` Premi, Sanjeev
2009-01-23 10:19     ` Nayak, Rajendra
2009-01-23 11:21       ` Högander Jouni
2009-01-23 12:00         ` Nayak, Rajendra
2009-01-23 12:10           ` Nayak, Rajendra
2009-01-23 16:49             ` Kevin Hilman
2009-01-23 12:10           ` Koen Kooi
2009-01-23 17:20             ` Kevin Hilman
2009-01-23 18:27               ` Koen Kooi
2009-01-23 17:48           ` Kevin Hilman
2009-01-27  9:18             ` Nayak, Rajendra
2009-02-02 17:45 ` Peter 'p2' De Schrijver
2009-02-02 19:42   ` Kevin Hilman
2009-02-02 20:06     ` Kevin Hilman
2009-02-04  0:52     ` Peter 'p2' De Schrijver
2009-02-04 16:04       ` Kevin Hilman
2009-02-04 16:15         ` Koen Kooi
2009-02-04 16:38         ` Peter 'p2' De Schrijver
  -- strict thread matches above, loose matches on Subject: below --
2009-03-18 18:56 Nicholas Chen
2009-03-18 19:01 ` Kevin Hilman
2009-03-18 19:22   ` Nicholas Chen

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=496F4FD5.2020006@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=premi@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