* [ANNOUNCE] new PM branch: pm-20081119
@ 2008-11-20 0:53 Kevin Hilman
2008-11-20 8:45 ` Peter Reid
0 siblings, 1 reply; 19+ messages in thread
From: Kevin Hilman @ 2008-11-20 0:53 UTC (permalink / raw)
To: linux-omap
Hello,
A new PM branch is available named pm-20081119.
This is mostly a new set of patches on top of the previous PM branch,
rather than a rebase. We finally found the root cause of some DPLL
relocking bugs. Special thanks to Paul Walmsley and Tero Kristo for
debugging and fixing this problem. Now the DPLL fix that was reverted
in the previous PM branch is re-applied as well as some fixes on top
of it. It also has some additional UART fixes, so I think the UART
idle work is ready to go to Tony. Special thanks to Jouni Hogander
for the extra testing and fixes here.
The shortlog is below[1] and the root of the tree is still
v2.6.27-omap1 + T2 power patches from Peter.
This has primarily been tested on custom HW since I'm _still_ waiting
for my SDP to arrive. I have boot tested on Beagle, but I think there
are still some problems with ES2 silicon. On my ES2 Beagle, neither
DSS or IVA will leave the ON state, even when all clocks in their
powerdomains are off. I have not debugged this further yet.
Functionally, this tree is in pretty good shape, so I will do some
bugfixes here when necessary, but will now spent some time focusing on
getting the patches in this branch merged into linux-omap.
Kevin
[1] git shortlog:
Amit Kucheria (2):
OMAP: PM: Typo fix for clock_allow_idle
HSMMC: Make driver support dynamic idle
Jouni Hogander (11):
OMAP3: PM: Use pwrdm_set_next_pwrst instead of set_pwrdm_state in idle loop
OMAP3: Do not set mpu, core, neon states if cpuidle is used
OMAP3: PM: Do not set next states sw to control those is available
OMAP3: PM: Always return value in pwrdms_setup
OMAP3: PM: Fix wrong sequence in suspend.
OMAP3: UART: Make sure that uart clocks are enabled when needed
OMAP3: PM: Check in set_pwrdm_state that target state is supported by pwrdm v2
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
OMAP: MCSPI: Enable mcspi wake-up
Kalle Jokiniemi (4):
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)
OMAP3: I2C: Enable I2C wakeups
Kevin Hilman (16):
OMAP3: PM: Add wake-up bit defintiions for CONTROL_PADCONF_X
OMAP3: PM: Allow UARTs to be unclocked when inactive
8250: Allow platform to register PM hook
8250: when waking, PM hook should be called before accessing port
OMAP3: PM: UART: Add 8250 UART PM hook for suspend/resume
OMAP3: PM: UART save/restore support for OFF-mode
OMAP2/3: HSMMC: Ensure HSMMC is fully reset on boot
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
Revert "OMAP3 clock: fix non-CORE DPLL rate assignment bugs"
Revert "OMAP3: PM: Do not set next states sw to control those is available"
Revert "OMAP3: Do not set mpu, core, neon states if cpuidle is used"
OMAP: PM: UART: fix can_sleep hook to return correct value
OMAP: PM: UART: Only disable clocks in prepare-idle hook
OMAP3: PM: Check for UART wakeups in 'resume_idle' hook
Paul Walmsley (14):
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
OMAP3 clock: fix non-CORE DPLL rate assignment bugs
OMAP3 powerdomains: remove RET from SGX power states list
OMAP3 powerdomains: remove RET from SGX power states list
OMAP3 clock: remove unnecessary dpll_data dereferences
OMAP3 clock: optimize DPLL rate rounding algorithm
OMAP3 clock: avoid invalid FREQSEL values during DPLL rate rounding
OMAP2/3 I2C: reprogram OCP_SYSCONFIG register after reset
OMAP: I2C: convert 'rev1' flag to generic 'rev' u8
Peter 'p2' De Schrijver (9):
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()
Rajendra Nayak (23):
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: PM: CPUidle: Enable Kconfig option for OMAP
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
Tero Kristo (13):
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: Fix a bug with noncore dpll rate calculation
PM: Added three PLL registers to the PRCM context save
PM: OMAP3: Make sure clk_disable_unused() order is correct
PM: Changed secure RAM storage size from 0x8000 to 0x803F
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [ANNOUNCE] new PM branch: pm-20081119
2008-11-20 0:53 [ANNOUNCE] new PM branch: pm-20081119 Kevin Hilman
@ 2008-11-20 8:45 ` Peter Reid
2008-11-20 14:13 ` Premi, Sanjeev
2008-11-20 17:38 ` Kevin Hilman
0 siblings, 2 replies; 19+ messages in thread
From: Peter Reid @ 2008-11-20 8:45 UTC (permalink / raw)
To: Kevin Hilman; +Cc: linux-omap
Hello kevin,
Here is what i did to put it to suspend, which fails.
[root@beagleboard]# echo mem > /sys/power/state
PM: Syncing filesystems ... done.
Freezing user space processes ... (elapsed 0.00 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
Suspending console(s)
Class driver suspend failed for cpu0
PM: Some devices failed to power down
Regards,
Reid.
On Thu, Nov 20, 2008 at 6:23 AM, Kevin Hilman
<khilman@deeprootsystems.com> wrote:
> Hello,
>
> A new PM branch is available named pm-20081119.
>
> This is mostly a new set of patches on top of the previous PM branch,
> rather than a rebase. We finally found the root cause of some DPLL
> relocking bugs. Special thanks to Paul Walmsley and Tero Kristo for
> debugging and fixing this problem. Now the DPLL fix that was reverted
> in the previous PM branch is re-applied as well as some fixes on top
> of it. It also has some additional UART fixes, so I think the UART
> idle work is ready to go to Tony. Special thanks to Jouni Hogander
> for the extra testing and fixes here.
>
> The shortlog is below[1] and the root of the tree is still
> v2.6.27-omap1 + T2 power patches from Peter.
>
> This has primarily been tested on custom HW since I'm _still_ waiting
> for my SDP to arrive. I have boot tested on Beagle, but I think there
> are still some problems with ES2 silicon. On my ES2 Beagle, neither
> DSS or IVA will leave the ON state, even when all clocks in their
> powerdomains are off. I have not debugged this further yet.
>
> Functionally, this tree is in pretty good shape, so I will do some
> bugfixes here when necessary, but will now spent some time focusing on
> getting the patches in this branch merged into linux-omap.
>
> Kevin
>
>
> [1] git shortlog:
>
> Amit Kucheria (2):
> OMAP: PM: Typo fix for clock_allow_idle
> HSMMC: Make driver support dynamic idle
>
> Jouni Hogander (11):
> OMAP3: PM: Use pwrdm_set_next_pwrst instead of set_pwrdm_state in idle loop
> OMAP3: Do not set mpu, core, neon states if cpuidle is used
> OMAP3: PM: Do not set next states sw to control those is available
> OMAP3: PM: Always return value in pwrdms_setup
> OMAP3: PM: Fix wrong sequence in suspend.
> OMAP3: UART: Make sure that uart clocks are enabled when needed
> OMAP3: PM: Check in set_pwrdm_state that target state is supported by pwrdm v2
> 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
> OMAP: MCSPI: Enable mcspi wake-up
>
> Kalle Jokiniemi (4):
> 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)
> OMAP3: I2C: Enable I2C wakeups
>
> Kevin Hilman (16):
> OMAP3: PM: Add wake-up bit defintiions for CONTROL_PADCONF_X
> OMAP3: PM: Allow UARTs to be unclocked when inactive
> 8250: Allow platform to register PM hook
> 8250: when waking, PM hook should be called before accessing port
> OMAP3: PM: UART: Add 8250 UART PM hook for suspend/resume
> OMAP3: PM: UART save/restore support for OFF-mode
> OMAP2/3: HSMMC: Ensure HSMMC is fully reset on boot
> 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
> Revert "OMAP3 clock: fix non-CORE DPLL rate assignment bugs"
> Revert "OMAP3: PM: Do not set next states sw to control those is available"
> Revert "OMAP3: Do not set mpu, core, neon states if cpuidle is used"
> OMAP: PM: UART: fix can_sleep hook to return correct value
> OMAP: PM: UART: Only disable clocks in prepare-idle hook
> OMAP3: PM: Check for UART wakeups in 'resume_idle' hook
>
> Paul Walmsley (14):
> 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
> OMAP3 clock: fix non-CORE DPLL rate assignment bugs
> OMAP3 powerdomains: remove RET from SGX power states list
> OMAP3 powerdomains: remove RET from SGX power states list
> OMAP3 clock: remove unnecessary dpll_data dereferences
> OMAP3 clock: optimize DPLL rate rounding algorithm
> OMAP3 clock: avoid invalid FREQSEL values during DPLL rate rounding
> OMAP2/3 I2C: reprogram OCP_SYSCONFIG register after reset
> OMAP: I2C: convert 'rev1' flag to generic 'rev' u8
>
> Peter 'p2' De Schrijver (9):
> 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()
>
> Rajendra Nayak (23):
> 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: PM: CPUidle: Enable Kconfig option for OMAP
> 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
>
> Tero Kristo (13):
> 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: Fix a bug with noncore dpll rate calculation
> PM: Added three PLL registers to the PRCM context save
> PM: OMAP3: Make sure clk_disable_unused() order is correct
> PM: Changed secure RAM storage size from 0x8000 to 0x803F
>
> --
> 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
>
^ permalink raw reply [flat|nested] 19+ messages in thread
* RE: [ANNOUNCE] new PM branch: pm-20081119
2008-11-20 8:45 ` Peter Reid
@ 2008-11-20 14:13 ` Premi, Sanjeev
2008-11-20 14:48 ` Koen Kooi
` (3 more replies)
2008-11-20 17:38 ` Kevin Hilman
1 sibling, 4 replies; 19+ messages in thread
From: Premi, Sanjeev @ 2008-11-20 14:13 UTC (permalink / raw)
To: Peter Reid, Kevin Hilman; +Cc: linux-omap@vger.kernel.org
> -----Original Message-----
> From: linux-omap-owner@vger.kernel.org
> [mailto:linux-omap-owner@vger.kernel.org] On Behalf Of Peter Reid
> Sent: Thursday, November 20, 2008 2:16 PM
> To: Kevin Hilman
> Cc: linux-omap@vger.kernel.org
> Subject: Re: [ANNOUNCE] new PM branch: pm-20081119
>
> Hello kevin,
> Here is what i did to put it to suspend, which fails.
>
> [root@beagleboard]# echo mem > /sys/power/state
> PM: Syncing filesystems ... done.
> Freezing user space processes ... (elapsed 0.00 seconds) done.
> Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
> Suspending console(s)
> Class driver suspend failed for cpu0
> PM: Some devices failed to power down
>
> Regards,
> Reid.
These are my observations on OMAP3EVM:
1) Very frequently I see these messages:
<4>__ratelimit: 6736 callbacks suppressed
__ratelimit: 6736 callbacks suppressed
<3>omapfb omapfb: irq error status 00c2
omapfb omapfb: irq error status 00c2
<3>omapfb omapfb: irq error status 0060
omapfb omapfb: irq error status 0060
<3>omapfb omapfb: irq error status 00c2
omapfb omapfb: irq error status 00c2
<3>omapfb omapfb: irq error status 0060
omapfb omapfb: irq error status 0060
<3>omapfb omapfb: irq error status 00e2
omapfb omapfb: irq error status 00e2
<3>omapfb omapfb: irq error status 00c2
omapfb omapfb: irq error status 00c2
<3>omapfb omapfb: irq error status 0060
omapfb omapfb: irq error status 0060
<3>omapfb omapfb: irq error status 00e2
omapfb omapfb: irq error status 00e2
<3>omapfb omapfb: irq error status 00c2
omapfb omapfb: irq error status 00c2
<3>omapfb omapfb: irq error status 0060
omapfb omapfb: irq error status 0060
2) Also:
# 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.00 seconds) (elapsed 0.00 seconds) done.
done.
Suspending console(s) (use no_console_suspend to debug)
Suspending console(s) (use no_console_suspend to debug)
<3>omapfb omapfb: timeout waiting for FRAME DONE
However, I the "resume" doesn't happen.
Trying to debug further.
Best regards,
Sanjeev
> On Thu, Nov 20, 2008 at 6:23 AM, Kevin Hilman
> <khilman@deeprootsystems.com> wrote:
> > Hello,
> >
> > A new PM branch is available named pm-20081119.
> >
> > This is mostly a new set of patches on top of the previous
> PM branch,
> > rather than a rebase. We finally found the root cause of some DPLL
> > relocking bugs. Special thanks to Paul Walmsley and Tero
> Kristo for
> > debugging and fixing this problem. Now the DPLL fix that
> was reverted
> > in the previous PM branch is re-applied as well as some
> fixes on top
> > of it. It also has some additional UART fixes, so I think the UART
> > idle work is ready to go to Tony. Special thanks to Jouni Hogander
> > for the extra testing and fixes here.
> >
> > The shortlog is below[1] and the root of the tree is still
> > v2.6.27-omap1 + T2 power patches from Peter.
> >
> > This has primarily been tested on custom HW since I'm
> _still_ waiting
> > for my SDP to arrive. I have boot tested on Beagle, but I
> think there
> > are still some problems with ES2 silicon. On my ES2
> Beagle, neither
> > DSS or IVA will leave the ON state, even when all clocks in their
> > powerdomains are off. I have not debugged this further yet.
> >
> > Functionally, this tree is in pretty good shape, so I will do some
> > bugfixes here when necessary, but will now spent some time
> focusing on
> > getting the patches in this branch merged into linux-omap.
> >
> > Kevin
> >
> >
> > [1] git shortlog:
> >
> > Amit Kucheria (2):
> > OMAP: PM: Typo fix for clock_allow_idle
> > HSMMC: Make driver support dynamic idle
> >
> > Jouni Hogander (11):
> > OMAP3: PM: Use pwrdm_set_next_pwrst instead of
> set_pwrdm_state in idle loop
> > OMAP3: Do not set mpu, core, neon states if cpuidle is used
> > OMAP3: PM: Do not set next states sw to control those
> is available
> > OMAP3: PM: Always return value in pwrdms_setup
> > OMAP3: PM: Fix wrong sequence in suspend.
> > OMAP3: UART: Make sure that uart clocks are enabled when needed
> > OMAP3: PM: Check in set_pwrdm_state that target state
> is supported by pwrdm v2
> > 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
> > OMAP: MCSPI: Enable mcspi wake-up
> >
> > Kalle Jokiniemi (4):
> > 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)
> > OMAP3: I2C: Enable I2C wakeups
> >
> > Kevin Hilman (16):
> > OMAP3: PM: Add wake-up bit defintiions for CONTROL_PADCONF_X
> > OMAP3: PM: Allow UARTs to be unclocked when inactive
> > 8250: Allow platform to register PM hook
> > 8250: when waking, PM hook should be called before
> accessing port
> > OMAP3: PM: UART: Add 8250 UART PM hook for suspend/resume
> > OMAP3: PM: UART save/restore support for OFF-mode
> > OMAP2/3: HSMMC: Ensure HSMMC is fully reset on boot
> > 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
> > Revert "OMAP3 clock: fix non-CORE DPLL rate assignment bugs"
> > Revert "OMAP3: PM: Do not set next states sw to
> control those is available"
> > Revert "OMAP3: Do not set mpu, core, neon states if
> cpuidle is used"
> > OMAP: PM: UART: fix can_sleep hook to return correct value
> > OMAP: PM: UART: Only disable clocks in prepare-idle hook
> > OMAP3: PM: Check for UART wakeups in 'resume_idle' hook
> >
> > Paul Walmsley (14):
> > 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
> > OMAP3 clock: fix non-CORE DPLL rate assignment bugs
> > OMAP3 powerdomains: remove RET from SGX power states list
> > OMAP3 powerdomains: remove RET from SGX power states list
> > OMAP3 clock: remove unnecessary dpll_data dereferences
> > OMAP3 clock: optimize DPLL rate rounding algorithm
> > OMAP3 clock: avoid invalid FREQSEL values during DPLL
> rate rounding
> > OMAP2/3 I2C: reprogram OCP_SYSCONFIG register after reset
> > OMAP: I2C: convert 'rev1' flag to generic 'rev' u8
> >
> > Peter 'p2' De Schrijver (9):
> > 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()
> >
> > Rajendra Nayak (23):
> > 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: PM: CPUidle: Enable Kconfig option for OMAP
> > 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
> >
> > Tero Kristo (13):
> > 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: Fix a bug with noncore dpll rate calculation
> > PM: Added three PLL registers to the PRCM context save
> > PM: OMAP3: Make sure clk_disable_unused() order is correct
> > PM: Changed secure RAM storage size from 0x8000 to 0x803F
> >
> > --
> > 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
>
>
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [ANNOUNCE] new PM branch: pm-20081119
2008-11-20 14:13 ` Premi, Sanjeev
@ 2008-11-20 14:48 ` Koen Kooi
2008-11-20 15:25 ` Premi, Sanjeev
2008-11-21 7:29 ` Kalle Jokiniemi
2008-11-20 16:00 ` Premi, Sanjeev
` (2 subsequent siblings)
3 siblings, 2 replies; 19+ messages in thread
From: Koen Kooi @ 2008-11-20 14:48 UTC (permalink / raw)
To: Premi, Sanjeev; +Cc: Peter Reid, Kevin Hilman, linux-omap@vger.kernel.org
[-- Attachment #1: Type: text/plain, Size: 542 bytes --]
Op 20 nov 2008, om 15:13 heeft Premi, Sanjeev het volgende geschreven:
>>
> These are my observations on OMAP3EVM:
>
> 1) Very frequently I see these messages:
>
> <4>__ratelimit: 6736 callbacks suppressed
> __ratelimit: 6736 callbacks suppressed
> <3>omapfb omapfb: irq error status 00c2
> omapfb omapfb: irq error status 00c2
There should be a workaround for those in 2.6.28rc3. Rick Bronson
posted a message about it on 7 november titled "Fix for dispc's error
"omapfb omapfb: irq error status 4020"
regards,
Koen
regards,
Koen
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 186 bytes --]
^ permalink raw reply [flat|nested] 19+ messages in thread
* RE: [ANNOUNCE] new PM branch: pm-20081119
2008-11-20 14:48 ` Koen Kooi
@ 2008-11-20 15:25 ` Premi, Sanjeev
2008-11-21 7:29 ` Kalle Jokiniemi
1 sibling, 0 replies; 19+ messages in thread
From: Premi, Sanjeev @ 2008-11-20 15:25 UTC (permalink / raw)
To: Koen Kooi; +Cc: Peter Reid, Kevin Hilman, linux-omap@vger.kernel.org
> -----Original Message-----
> From: Koen Kooi [mailto:k.kooi@student.utwente.nl]
> Sent: Thursday, November 20, 2008 8:19 PM
> To: Premi, Sanjeev
> Cc: Peter Reid; Kevin Hilman; linux-omap@vger.kernel.org
> Subject: Re: [ANNOUNCE] new PM branch: pm-20081119
>
>
> Op 20 nov 2008, om 15:13 heeft Premi, Sanjeev het volgende geschreven:
> >>
> > These are my observations on OMAP3EVM:
> >
> > 1) Very frequently I see these messages:
> >
> > <4>__ratelimit: 6736 callbacks suppressed
> > __ratelimit: 6736 callbacks suppressed <3>omapfb omapfb: irq error
> > status 00c2 omapfb omapfb: irq error status 00c2
>
> There should be a workaround for those in 2.6.28rc3. Rick
> Bronson posted a message about it on 7 november titled "Fix
> for dispc's error "omapfb omapfb: irq error status 4020"
>
Did not help on this branch; not sure if there are any dependencies...
> regards,
>
> Koen
>
> regards,
>
> Koen
>
^ permalink raw reply [flat|nested] 19+ messages in thread
* RE: [ANNOUNCE] new PM branch: pm-20081119
2008-11-20 14:13 ` Premi, Sanjeev
2008-11-20 14:48 ` Koen Kooi
@ 2008-11-20 16:00 ` Premi, Sanjeev
2008-11-20 17:40 ` Kevin Hilman
2008-11-21 7:20 ` Kalle Jokiniemi
3 siblings, 0 replies; 19+ messages in thread
From: Premi, Sanjeev @ 2008-11-20 16:00 UTC (permalink / raw)
To: Premi, Sanjeev, Peter Reid, Kevin Hilman; +Cc: linux-omap@vger.kernel.org
<snip>--<snip>
>
> 2) Also:
> # 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.00 seconds) (elapsed 0.00
> seconds) done.
> done.
>
> Suspending console(s) (use no_console_suspend to debug)
> Suspending console(s) (use no_console_suspend to debug)
> <3>omapfb omapfb: timeout waiting for FRAME DONE
I see a bus error generated.
Haven't been able to nail the reason so far :(
Last symbol I could trace was pm_power_off
>
> However, I the "resume" doesn't happen.
> Trying to debug further.
>
<snip>--<snip>
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [ANNOUNCE] new PM branch: pm-20081119
2008-11-20 8:45 ` Peter Reid
2008-11-20 14:13 ` Premi, Sanjeev
@ 2008-11-20 17:38 ` Kevin Hilman
2008-11-20 17:44 ` Kevin Hilman
2008-11-20 17:53 ` Koen Kooi
1 sibling, 2 replies; 19+ messages in thread
From: Kevin Hilman @ 2008-11-20 17:38 UTC (permalink / raw)
To: Peter Reid; +Cc: linux-omap
"Peter Reid" <ppeter.reid@gmail.com> writes:
> Hello kevin,
> Here is what i did to put it to suspend, which fails.
>
> [root@beagleboard]# echo mem > /sys/power/state
> PM: Syncing filesystems ... done.
> Freezing user space processes ... (elapsed 0.00 seconds) done.
> Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
> Suspending console(s)
> Class driver suspend failed for cpu0
> PM: Some devices failed to power down
Hi Peter,
Thanks for testing on Beagle. Do you mind sharing your .config? And,
would you mind testing with the attached config? This PM branch will
currently only work with a minimal set of drivers. Many of the
current drivers will still prevent retention and OFF mode.
Do you have CPUfreq enabled? I saw this 'class driver suspend'
problem when I had CPUfreq enabled. This branch doesn't currently
have CPUfreq support, so you can leave that disabled.
I've also noticed problems on ES2 Beagle as well that I haven't
figured out yet. Namely, I think the bootloader is leaving certain
modules (namely DSS and IVA) in a state that is preventing hitting
retention.
Immediately after boot, the DSS powerdomain is still ON and it should
be in retention, same for IVA but I haven't debugged this further on
Beagle. The same kernel works on 3430SDP so that's why my hunch
points to the u-boot.
The kernel needs a way to ensure that after booting all the unused
modules are in a state where they are not preventing idle. Even with
disabled clocks, certain modules can prevent idle. Paul Walmsley has
written the 'omapdev' layer which will now make it easier to do this
boot-time init, but it is currently not there. We currently have to
rely on bootloaders doing the right thing.
The beagle bootloader does all sorts of stuff with DSS, MMC, audio
etc. so it is a likely candidate.
Kevin
>
> On Thu, Nov 20, 2008 at 6:23 AM, Kevin Hilman
> <khilman@deeprootsystems.com> wrote:
>> Hello,
>>
>> A new PM branch is available named pm-20081119.
>>
>> This is mostly a new set of patches on top of the previous PM branch,
>> rather than a rebase. We finally found the root cause of some DPLL
>> relocking bugs. Special thanks to Paul Walmsley and Tero Kristo for
>> debugging and fixing this problem. Now the DPLL fix that was reverted
>> in the previous PM branch is re-applied as well as some fixes on top
>> of it. It also has some additional UART fixes, so I think the UART
>> idle work is ready to go to Tony. Special thanks to Jouni Hogander
>> for the extra testing and fixes here.
>>
>> The shortlog is below[1] and the root of the tree is still
>> v2.6.27-omap1 + T2 power patches from Peter.
>>
>> This has primarily been tested on custom HW since I'm _still_ waiting
>> for my SDP to arrive. I have boot tested on Beagle, but I think there
>> are still some problems with ES2 silicon. On my ES2 Beagle, neither
>> DSS or IVA will leave the ON state, even when all clocks in their
>> powerdomains are off. I have not debugged this further yet.
>>
>> Functionally, this tree is in pretty good shape, so I will do some
>> bugfixes here when necessary, but will now spent some time focusing on
>> getting the patches in this branch merged into linux-omap.
>>
>> Kevin
>>
>>
>> [1] git shortlog:
>>
>> Amit Kucheria (2):
>> OMAP: PM: Typo fix for clock_allow_idle
>> HSMMC: Make driver support dynamic idle
>>
>> Jouni Hogander (11):
>> OMAP3: PM: Use pwrdm_set_next_pwrst instead of set_pwrdm_state in idle loop
>> OMAP3: Do not set mpu, core, neon states if cpuidle is used
>> OMAP3: PM: Do not set next states sw to control those is available
>> OMAP3: PM: Always return value in pwrdms_setup
>> OMAP3: PM: Fix wrong sequence in suspend.
>> OMAP3: UART: Make sure that uart clocks are enabled when needed
>> OMAP3: PM: Check in set_pwrdm_state that target state is supported by pwrdm v2
>> 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
>> OMAP: MCSPI: Enable mcspi wake-up
>>
>> Kalle Jokiniemi (4):
>> 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)
>> OMAP3: I2C: Enable I2C wakeups
>>
>> Kevin Hilman (16):
>> OMAP3: PM: Add wake-up bit defintiions for CONTROL_PADCONF_X
>> OMAP3: PM: Allow UARTs to be unclocked when inactive
>> 8250: Allow platform to register PM hook
>> 8250: when waking, PM hook should be called before accessing port
>> OMAP3: PM: UART: Add 8250 UART PM hook for suspend/resume
>> OMAP3: PM: UART save/restore support for OFF-mode
>> OMAP2/3: HSMMC: Ensure HSMMC is fully reset on boot
>> 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
>> Revert "OMAP3 clock: fix non-CORE DPLL rate assignment bugs"
>> Revert "OMAP3: PM: Do not set next states sw to control those is available"
>> Revert "OMAP3: Do not set mpu, core, neon states if cpuidle is used"
>> OMAP: PM: UART: fix can_sleep hook to return correct value
>> OMAP: PM: UART: Only disable clocks in prepare-idle hook
>> OMAP3: PM: Check for UART wakeups in 'resume_idle' hook
>>
>> Paul Walmsley (14):
>> 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
>> OMAP3 clock: fix non-CORE DPLL rate assignment bugs
>> OMAP3 powerdomains: remove RET from SGX power states list
>> OMAP3 powerdomains: remove RET from SGX power states list
>> OMAP3 clock: remove unnecessary dpll_data dereferences
>> OMAP3 clock: optimize DPLL rate rounding algorithm
>> OMAP3 clock: avoid invalid FREQSEL values during DPLL rate rounding
>> OMAP2/3 I2C: reprogram OCP_SYSCONFIG register after reset
>> OMAP: I2C: convert 'rev1' flag to generic 'rev' u8
>>
>> Peter 'p2' De Schrijver (9):
>> 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()
>>
>> Rajendra Nayak (23):
>> 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: PM: CPUidle: Enable Kconfig option for OMAP
>> 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
>>
>> Tero Kristo (13):
>> 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: Fix a bug with noncore dpll rate calculation
>> PM: Added three PLL registers to the PRCM context save
>> PM: OMAP3: Make sure clk_disable_unused() order is correct
>> PM: Changed secure RAM storage size from 0x8000 to 0x803F
>>
>> --
>> 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
>>
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [ANNOUNCE] new PM branch: pm-20081119
2008-11-20 14:13 ` Premi, Sanjeev
2008-11-20 14:48 ` Koen Kooi
2008-11-20 16:00 ` Premi, Sanjeev
@ 2008-11-20 17:40 ` Kevin Hilman
2008-11-21 15:46 ` Premi, Sanjeev
2008-11-21 7:20 ` Kalle Jokiniemi
3 siblings, 1 reply; 19+ messages in thread
From: Kevin Hilman @ 2008-11-20 17:40 UTC (permalink / raw)
To: Premi, Sanjeev; +Cc: Peter Reid, linux-omap@vger.kernel.org
"Premi, Sanjeev" <premi@ti.com> writes:
> These are my observations on OMAP3EVM:
>
> 1) Very frequently I see these messages:
>
> <4>__ratelimit: 6736 callbacks suppressed
> __ratelimit: 6736 callbacks suppressed
> <3>omapfb omapfb: irq error status 00c2
> omapfb omapfb: irq error status 00c2
> <3>omapfb omapfb: irq error status 0060
> omapfb omapfb: irq error status 0060
> <3>omapfb omapfb: irq error status 00c2
> omapfb omapfb: irq error status 00c2
> <3>omapfb omapfb: irq error status 0060
> omapfb omapfb: irq error status 0060
> <3>omapfb omapfb: irq error status 00e2
> omapfb omapfb: irq error status 00e2
> <3>omapfb omapfb: irq error status 00c2
> omapfb omapfb: irq error status 00c2
> <3>omapfb omapfb: irq error status 0060
> omapfb omapfb: irq error status 0060
> <3>omapfb omapfb: irq error status 00e2
> omapfb omapfb: irq error status 00e2
> <3>omapfb omapfb: irq error status 00c2
> omapfb omapfb: irq error status 00c2
> <3>omapfb omapfb: irq error status 0060
> omapfb omapfb: irq error status 0060
Sanjeev,
For starters can you try with a minimal kernel (no drivers, no
framebuffer, etc.)
The first goal is to hit retention and off with no drivers than start
moving out to address driver issues from there.
Kevin
> 2) Also:
> # 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.00 seconds) (elapsed 0.00 seconds) done.
> done.
>
> Suspending console(s) (use no_console_suspend to debug)
> Suspending console(s) (use no_console_suspend to debug)
> <3>omapfb omapfb: timeout waiting for FRAME DONE
>
> However, I the "resume" doesn't happen.
> Trying to debug further.
>
> Best regards,
> Sanjeev
>
>> On Thu, Nov 20, 2008 at 6:23 AM, Kevin Hilman
>> <khilman@deeprootsystems.com> wrote:
>> > Hello,
>> >
>> > A new PM branch is available named pm-20081119.
>> >
>> > This is mostly a new set of patches on top of the previous
>> PM branch,
>> > rather than a rebase. We finally found the root cause of some DPLL
>> > relocking bugs. Special thanks to Paul Walmsley and Tero
>> Kristo for
>> > debugging and fixing this problem. Now the DPLL fix that
>> was reverted
>> > in the previous PM branch is re-applied as well as some
>> fixes on top
>> > of it. It also has some additional UART fixes, so I think the UART
>> > idle work is ready to go to Tony. Special thanks to Jouni Hogander
>> > for the extra testing and fixes here.
>> >
>> > The shortlog is below[1] and the root of the tree is still
>> > v2.6.27-omap1 + T2 power patches from Peter.
>> >
>> > This has primarily been tested on custom HW since I'm
>> _still_ waiting
>> > for my SDP to arrive. I have boot tested on Beagle, but I
>> think there
>> > are still some problems with ES2 silicon. On my ES2
>> Beagle, neither
>> > DSS or IVA will leave the ON state, even when all clocks in their
>> > powerdomains are off. I have not debugged this further yet.
>> >
>> > Functionally, this tree is in pretty good shape, so I will do some
>> > bugfixes here when necessary, but will now spent some time
>> focusing on
>> > getting the patches in this branch merged into linux-omap.
>> >
>> > Kevin
>> >
>> >
>> > [1] git shortlog:
>> >
>> > Amit Kucheria (2):
>> > OMAP: PM: Typo fix for clock_allow_idle
>> > HSMMC: Make driver support dynamic idle
>> >
>> > Jouni Hogander (11):
>> > OMAP3: PM: Use pwrdm_set_next_pwrst instead of
>> set_pwrdm_state in idle loop
>> > OMAP3: Do not set mpu, core, neon states if cpuidle is used
>> > OMAP3: PM: Do not set next states sw to control those
>> is available
>> > OMAP3: PM: Always return value in pwrdms_setup
>> > OMAP3: PM: Fix wrong sequence in suspend.
>> > OMAP3: UART: Make sure that uart clocks are enabled when needed
>> > OMAP3: PM: Check in set_pwrdm_state that target state
>> is supported by pwrdm v2
>> > 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
>> > OMAP: MCSPI: Enable mcspi wake-up
>> >
>> > Kalle Jokiniemi (4):
>> > 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)
>> > OMAP3: I2C: Enable I2C wakeups
>> >
>> > Kevin Hilman (16):
>> > OMAP3: PM: Add wake-up bit defintiions for CONTROL_PADCONF_X
>> > OMAP3: PM: Allow UARTs to be unclocked when inactive
>> > 8250: Allow platform to register PM hook
>> > 8250: when waking, PM hook should be called before
>> accessing port
>> > OMAP3: PM: UART: Add 8250 UART PM hook for suspend/resume
>> > OMAP3: PM: UART save/restore support for OFF-mode
>> > OMAP2/3: HSMMC: Ensure HSMMC is fully reset on boot
>> > 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
>> > Revert "OMAP3 clock: fix non-CORE DPLL rate assignment bugs"
>> > Revert "OMAP3: PM: Do not set next states sw to
>> control those is available"
>> > Revert "OMAP3: Do not set mpu, core, neon states if
>> cpuidle is used"
>> > OMAP: PM: UART: fix can_sleep hook to return correct value
>> > OMAP: PM: UART: Only disable clocks in prepare-idle hook
>> > OMAP3: PM: Check for UART wakeups in 'resume_idle' hook
>> >
>> > Paul Walmsley (14):
>> > 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
>> > OMAP3 clock: fix non-CORE DPLL rate assignment bugs
>> > OMAP3 powerdomains: remove RET from SGX power states list
>> > OMAP3 powerdomains: remove RET from SGX power states list
>> > OMAP3 clock: remove unnecessary dpll_data dereferences
>> > OMAP3 clock: optimize DPLL rate rounding algorithm
>> > OMAP3 clock: avoid invalid FREQSEL values during DPLL
>> rate rounding
>> > OMAP2/3 I2C: reprogram OCP_SYSCONFIG register after reset
>> > OMAP: I2C: convert 'rev1' flag to generic 'rev' u8
>> >
>> > Peter 'p2' De Schrijver (9):
>> > 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()
>> >
>> > Rajendra Nayak (23):
>> > 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: PM: CPUidle: Enable Kconfig option for OMAP
>> > 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
>> >
>> > Tero Kristo (13):
>> > 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: Fix a bug with noncore dpll rate calculation
>> > PM: Added three PLL registers to the PRCM context save
>> > PM: OMAP3: Make sure clk_disable_unused() order is correct
>> > PM: Changed secure RAM storage size from 0x8000 to 0x803F
>> >
>> > --
>> > 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
>>
>>
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [ANNOUNCE] new PM branch: pm-20081119
2008-11-20 17:38 ` Kevin Hilman
@ 2008-11-20 17:44 ` Kevin Hilman
2008-11-20 17:53 ` Koen Kooi
1 sibling, 0 replies; 19+ messages in thread
From: Kevin Hilman @ 2008-11-20 17:44 UTC (permalink / raw)
To: Peter Reid; +Cc: linux-omap
[-- Attachment #1: Type: text/plain, Size: 9316 bytes --]
Kevin Hilman <khilman@deeprootsystems.com> writes:
> "Peter Reid" <ppeter.reid@gmail.com> writes:
>
>> Hello kevin,
>> Here is what i did to put it to suspend, which fails.
>>
>> [root@beagleboard]# echo mem > /sys/power/state
>> PM: Syncing filesystems ... done.
>> Freezing user space processes ... (elapsed 0.00 seconds) done.
>> Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
>> Suspending console(s)
>> Class driver suspend failed for cpu0
>> PM: Some devices failed to power down
>
> Hi Peter,
>
> Thanks for testing on Beagle. Do you mind sharing your .config? And,
> would you mind testing with the attached config? This PM branch will
> currently only work with a minimal set of drivers. Many of the
> current drivers will still prevent retention and OFF mode.
This time, with the .config attached.
> Do you have CPUfreq enabled? I saw this 'class driver suspend'
> problem when I had CPUfreq enabled. This branch doesn't currently
> have CPUfreq support, so you can leave that disabled.
>
> I've also noticed problems on ES2 Beagle as well that I haven't
> figured out yet. Namely, I think the bootloader is leaving certain
> modules (namely DSS and IVA) in a state that is preventing hitting
> retention.
>
> Immediately after boot, the DSS powerdomain is still ON and it should
> be in retention, same for IVA but I haven't debugged this further on
> Beagle. The same kernel works on 3430SDP so that's why my hunch
> points to the u-boot.
>
> The kernel needs a way to ensure that after booting all the unused
> modules are in a state where they are not preventing idle. Even with
> disabled clocks, certain modules can prevent idle. Paul Walmsley has
> written the 'omapdev' layer which will now make it easier to do this
> boot-time init, but it is currently not there. We currently have to
> rely on bootloaders doing the right thing.
>
> The beagle bootloader does all sorts of stuff with DSS, MMC, audio
> etc. so it is a likely candidate.
>
> Kevin
>
>>
>> On Thu, Nov 20, 2008 at 6:23 AM, Kevin Hilman
>> <khilman@deeprootsystems.com> wrote:
>>> Hello,
>>>
>>> A new PM branch is available named pm-20081119.
>>>
>>> This is mostly a new set of patches on top of the previous PM branch,
>>> rather than a rebase. We finally found the root cause of some DPLL
>>> relocking bugs. Special thanks to Paul Walmsley and Tero Kristo for
>>> debugging and fixing this problem. Now the DPLL fix that was reverted
>>> in the previous PM branch is re-applied as well as some fixes on top
>>> of it. It also has some additional UART fixes, so I think the UART
>>> idle work is ready to go to Tony. Special thanks to Jouni Hogander
>>> for the extra testing and fixes here.
>>>
>>> The shortlog is below[1] and the root of the tree is still
>>> v2.6.27-omap1 + T2 power patches from Peter.
>>>
>>> This has primarily been tested on custom HW since I'm _still_ waiting
>>> for my SDP to arrive. I have boot tested on Beagle, but I think there
>>> are still some problems with ES2 silicon. On my ES2 Beagle, neither
>>> DSS or IVA will leave the ON state, even when all clocks in their
>>> powerdomains are off. I have not debugged this further yet.
>>>
>>> Functionally, this tree is in pretty good shape, so I will do some
>>> bugfixes here when necessary, but will now spent some time focusing on
>>> getting the patches in this branch merged into linux-omap.
>>>
>>> Kevin
>>>
>>>
>>> [1] git shortlog:
>>>
>>> Amit Kucheria (2):
>>> OMAP: PM: Typo fix for clock_allow_idle
>>> HSMMC: Make driver support dynamic idle
>>>
>>> Jouni Hogander (11):
>>> OMAP3: PM: Use pwrdm_set_next_pwrst instead of set_pwrdm_state in idle loop
>>> OMAP3: Do not set mpu, core, neon states if cpuidle is used
>>> OMAP3: PM: Do not set next states sw to control those is available
>>> OMAP3: PM: Always return value in pwrdms_setup
>>> OMAP3: PM: Fix wrong sequence in suspend.
>>> OMAP3: UART: Make sure that uart clocks are enabled when needed
>>> OMAP3: PM: Check in set_pwrdm_state that target state is supported by pwrdm v2
>>> 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
>>> OMAP: MCSPI: Enable mcspi wake-up
>>>
>>> Kalle Jokiniemi (4):
>>> 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)
>>> OMAP3: I2C: Enable I2C wakeups
>>>
>>> Kevin Hilman (16):
>>> OMAP3: PM: Add wake-up bit defintiions for CONTROL_PADCONF_X
>>> OMAP3: PM: Allow UARTs to be unclocked when inactive
>>> 8250: Allow platform to register PM hook
>>> 8250: when waking, PM hook should be called before accessing port
>>> OMAP3: PM: UART: Add 8250 UART PM hook for suspend/resume
>>> OMAP3: PM: UART save/restore support for OFF-mode
>>> OMAP2/3: HSMMC: Ensure HSMMC is fully reset on boot
>>> 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
>>> Revert "OMAP3 clock: fix non-CORE DPLL rate assignment bugs"
>>> Revert "OMAP3: PM: Do not set next states sw to control those is available"
>>> Revert "OMAP3: Do not set mpu, core, neon states if cpuidle is used"
>>> OMAP: PM: UART: fix can_sleep hook to return correct value
>>> OMAP: PM: UART: Only disable clocks in prepare-idle hook
>>> OMAP3: PM: Check for UART wakeups in 'resume_idle' hook
>>>
>>> Paul Walmsley (14):
>>> 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
>>> OMAP3 clock: fix non-CORE DPLL rate assignment bugs
>>> OMAP3 powerdomains: remove RET from SGX power states list
>>> OMAP3 powerdomains: remove RET from SGX power states list
>>> OMAP3 clock: remove unnecessary dpll_data dereferences
>>> OMAP3 clock: optimize DPLL rate rounding algorithm
>>> OMAP3 clock: avoid invalid FREQSEL values during DPLL rate rounding
>>> OMAP2/3 I2C: reprogram OCP_SYSCONFIG register after reset
>>> OMAP: I2C: convert 'rev1' flag to generic 'rev' u8
>>>
>>> Peter 'p2' De Schrijver (9):
>>> 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()
>>>
>>> Rajendra Nayak (23):
>>> 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: PM: CPUidle: Enable Kconfig option for OMAP
>>> 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
>>>
>>> Tero Kristo (13):
>>> 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: Fix a bug with noncore dpll rate calculation
>>> PM: Added three PLL registers to the PRCM context save
>>> PM: OMAP3: Make sure clk_disable_unused() order is correct
>>> PM: Changed secure RAM storage size from 0x8000 to 0x803F
>>>
>>> --
>>> 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
>>>
[-- Attachment #2: omap3_beagle_min_defconfig --]
[-- Type: text/plain, Size: 26098 bytes --]
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.28-rc5-omap1
# Wed Nov 19 15:49:43 2008
#
CONFIG_ARM=y
CONFIG_SYS_SUPPORTS_APM_EMULATION=y
CONFIG_GENERIC_GPIO=y
CONFIG_GENERIC_TIME=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_MMU=y
# CONFIG_NO_IOPORT is not set
CONFIG_GENERIC_HARDIRQS=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_HAVE_LATENCYTOP_SUPPORT=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
CONFIG_HARDIRQS_SW_RESEND=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_RWSEM_GENERIC_SPINLOCK=y
# CONFIG_ARCH_HAS_ILOG2_U32 is not set
# CONFIG_ARCH_HAS_ILOG2_U64 is not set
CONFIG_GENERIC_HWEIGHT=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_GENERIC_HARDIRQS_NO__DO_IRQ=y
CONFIG_VECTORS_BASE=0xffff0000
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
#
# General setup
#
CONFIG_EXPERIMENTAL=y
CONFIG_BROKEN_ON_SMP=y
CONFIG_LOCK_KERNEL=y
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_LOCALVERSION=""
CONFIG_LOCALVERSION_AUTO=y
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
# CONFIG_POSIX_MQUEUE is not set
CONFIG_BSD_PROCESS_ACCT=y
# CONFIG_BSD_PROCESS_ACCT_V3 is not set
# CONFIG_TASKSTATS is not set
# CONFIG_AUDIT is not set
# CONFIG_IKCONFIG is not set
CONFIG_LOG_BUF_SHIFT=14
# CONFIG_CGROUPS is not set
CONFIG_GROUP_SCHED=y
CONFIG_FAIR_GROUP_SCHED=y
# CONFIG_RT_GROUP_SCHED is not set
CONFIG_USER_SCHED=y
# CONFIG_CGROUP_SCHED is not set
CONFIG_SYSFS_DEPRECATED=y
CONFIG_SYSFS_DEPRECATED_V2=y
# CONFIG_RELAY is not set
# CONFIG_NAMESPACES is not set
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE="/opt/kjh/rootfs/busybox"
CONFIG_INITRAMFS_ROOT_UID=0
CONFIG_INITRAMFS_ROOT_GID=0
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
CONFIG_SYSCTL=y
CONFIG_EMBEDDED=y
CONFIG_UID16=y
# CONFIG_SYSCTL_SYSCALL is not set
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_ALL is not set
CONFIG_KALLSYMS_EXTRA_PASS=y
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_COMPAT_BRK=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_ANON_INODES=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_TIMERFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_AIO=y
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_SLAB=y
# CONFIG_SLUB is not set
# CONFIG_SLOB is not set
# CONFIG_PROFILING is not set
# CONFIG_MARKERS is not set
CONFIG_HAVE_OPROFILE=y
# CONFIG_KPROBES is not set
CONFIG_HAVE_KPROBES=y
CONFIG_HAVE_KRETPROBES=y
CONFIG_HAVE_CLK=y
CONFIG_HAVE_GENERIC_DMA_COHERENT=y
CONFIG_SLABINFO=y
CONFIG_RT_MUTEXES=y
# CONFIG_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0
CONFIG_MODULES=y
# CONFIG_MODULE_FORCE_LOAD is not set
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
CONFIG_MODVERSIONS=y
CONFIG_MODULE_SRCVERSION_ALL=y
CONFIG_KMOD=y
CONFIG_BLOCK=y
# CONFIG_LBD is not set
# CONFIG_BLK_DEV_IO_TRACE is not set
# CONFIG_LSF is not set
# CONFIG_BLK_DEV_BSG is not set
# CONFIG_BLK_DEV_INTEGRITY is not set
#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
CONFIG_DEFAULT_AS=y
# CONFIG_DEFAULT_DEADLINE is not set
# CONFIG_DEFAULT_CFQ is not set
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="anticipatory"
CONFIG_CLASSIC_RCU=y
# CONFIG_FREEZER is not set
#
# System Type
#
# CONFIG_ARCH_AAEC2000 is not set
# CONFIG_ARCH_INTEGRATOR is not set
# CONFIG_ARCH_REALVIEW is not set
# CONFIG_ARCH_VERSATILE is not set
# CONFIG_ARCH_AT91 is not set
# CONFIG_ARCH_CLPS7500 is not set
# CONFIG_ARCH_CLPS711X is not set
# CONFIG_ARCH_EBSA110 is not set
# CONFIG_ARCH_EP93XX is not set
# CONFIG_ARCH_FOOTBRIDGE is not set
# CONFIG_ARCH_NETX is not set
# CONFIG_ARCH_H720X is not set
# CONFIG_ARCH_IMX is not set
# CONFIG_ARCH_IOP13XX is not set
# CONFIG_ARCH_IOP32X is not set
# CONFIG_ARCH_IOP33X is not set
# CONFIG_ARCH_IXP23XX is not set
# CONFIG_ARCH_IXP2000 is not set
# CONFIG_ARCH_IXP4XX is not set
# CONFIG_ARCH_L7200 is not set
# CONFIG_ARCH_KIRKWOOD is not set
# CONFIG_ARCH_KS8695 is not set
# CONFIG_ARCH_NS9XXX is not set
# CONFIG_ARCH_LOKI is not set
# CONFIG_ARCH_MV78XX0 is not set
# CONFIG_ARCH_MXC is not set
# CONFIG_ARCH_ORION5X is not set
# CONFIG_ARCH_PNX4008 is not set
# CONFIG_ARCH_PXA is not set
# CONFIG_ARCH_RPC is not set
# CONFIG_ARCH_SA1100 is not set
# CONFIG_ARCH_S3C2410 is not set
# CONFIG_ARCH_SHARK is not set
# CONFIG_ARCH_LH7A40X is not set
# CONFIG_ARCH_DAVINCI is not set
CONFIG_ARCH_OMAP=y
# CONFIG_ARCH_MSM is not set
#
# TI OMAP Implementations
#
CONFIG_ARCH_OMAP_OTG=y
# CONFIG_ARCH_OMAP1 is not set
# CONFIG_ARCH_OMAP2 is not set
CONFIG_ARCH_OMAP3=y
#
# OMAP Feature Selections
#
# CONFIG_OMAP_DEBUG_POWERDOMAIN is not set
# CONFIG_OMAP_DEBUG_CLOCKDOMAIN is not set
# CONFIG_OMAP_SMARTREFLEX is not set
CONFIG_OMAP_RESET_CLOCKS=y
CONFIG_OMAP_BOOT_TAG=y
CONFIG_OMAP_BOOT_REASON=y
# CONFIG_OMAP_COMPONENT_VERSION is not set
# CONFIG_OMAP_GPIO_SWITCH is not set
# CONFIG_OMAP_MUX is not set
# CONFIG_OMAP_MCBSP is not set
# CONFIG_OMAP_MMU_FWK is not set
# CONFIG_OMAP_MBOX_FWK is not set
# CONFIG_OMAP_MPU_TIMER is not set
CONFIG_OMAP_32K_TIMER=y
# CONFIG_OMAP3_DEBOBS is not set
CONFIG_OMAP_32K_TIMER_HZ=128
CONFIG_OMAP_DM_TIMER=y
# CONFIG_OMAP_LL_DEBUG_UART1 is not set
# CONFIG_OMAP_LL_DEBUG_UART2 is not set
CONFIG_OMAP_LL_DEBUG_UART3=y
# CONFIG_OMAP_PM_NONE is not set
CONFIG_OMAP_PM_NOOP=y
CONFIG_ARCH_OMAP34XX=y
CONFIG_ARCH_OMAP3430=y
#
# OMAP Board Type
#
# CONFIG_MACH_NOKIA_RX51 is not set
# CONFIG_VIDEO_MACH_RX51_OLD_I2C is not set
# CONFIG_MACH_OMAP_LDP is not set
# CONFIG_MACH_OMAP_3430SDP is not set
# CONFIG_MACH_OMAP3EVM is not set
CONFIG_MACH_OMAP3_BEAGLE=y
# CONFIG_MACH_OVERO is not set
# CONFIG_MACH_OMAP3_PANDORA is not set
CONFIG_OMAP_TICK_GPTIMER=1
#
# Boot options
#
#
# Power management
#
#
# Processor Type
#
CONFIG_CPU_32=y
CONFIG_CPU_32v6K=y
CONFIG_CPU_V7=y
CONFIG_CPU_32v7=y
CONFIG_CPU_ABRT_EV7=y
CONFIG_CPU_PABRT_IFAR=y
CONFIG_CPU_CACHE_V7=y
CONFIG_CPU_CACHE_VIPT=y
CONFIG_CPU_COPY_V6=y
CONFIG_CPU_TLB_V7=y
CONFIG_CPU_HAS_ASID=y
CONFIG_CPU_CP15=y
CONFIG_CPU_CP15_MMU=y
#
# Processor Features
#
CONFIG_ARM_THUMB=y
# CONFIG_ARM_THUMBEE is not set
# CONFIG_CPU_ICACHE_DISABLE is not set
# CONFIG_CPU_DCACHE_DISABLE is not set
# CONFIG_CPU_BPREDICT_DISABLE is not set
CONFIG_HAS_TLS_REG=y
# CONFIG_OUTER_CACHE is not set
#
# Bus support
#
# CONFIG_PCI_SYSCALL is not set
# CONFIG_ARCH_SUPPORTS_MSI is not set
# CONFIG_PCCARD is not set
#
# Kernel Features
#
CONFIG_TICK_ONESHOT=y
CONFIG_NO_HZ=y
CONFIG_HIGH_RES_TIMERS=y
CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
CONFIG_VMSPLIT_3G=y
# CONFIG_VMSPLIT_2G is not set
# CONFIG_VMSPLIT_1G is not set
CONFIG_PAGE_OFFSET=0xC0000000
CONFIG_PREEMPT=y
CONFIG_HZ=128
CONFIG_AEABI=y
CONFIG_OABI_COMPAT=y
CONFIG_ARCH_FLATMEM_HAS_HOLES=y
# CONFIG_ARCH_SPARSEMEM_DEFAULT is not set
# CONFIG_ARCH_SELECT_MEMORY_MODEL is not set
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_FLATMEM_MANUAL=y
# CONFIG_DISCONTIGMEM_MANUAL is not set
# CONFIG_SPARSEMEM_MANUAL is not set
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
CONFIG_PAGEFLAGS_EXTENDED=y
CONFIG_SPLIT_PTLOCK_CPUS=4
# CONFIG_RESOURCES_64BIT is not set
# CONFIG_PHYS_ADDR_T_64BIT is not set
CONFIG_ZONE_DMA_FLAG=0
CONFIG_VIRT_TO_BUS=y
CONFIG_UNEVICTABLE_LRU=y
# CONFIG_LEDS is not set
CONFIG_ALIGNMENT_TRAP=y
#
# Boot options
#
CONFIG_ZBOOT_ROM_TEXT=0x0
CONFIG_ZBOOT_ROM_BSS=0x0
CONFIG_CMDLINE="root=/dev/nfs nfsroot=192.168.0.1:/home/user/buildroot ip=192.168.0.2:192.168.0.1:192.168.0.1:255.255.255.0:tgt:eth0:off rw console=ttyS2,115200n8"
# CONFIG_XIP_KERNEL is not set
# CONFIG_KEXEC is not set
#
# CPU Power Management
#
# CONFIG_CPU_FREQ is not set
# CONFIG_CPU_IDLE is not set
#
# Floating point emulation
#
#
# At least one emulation must be selected
#
CONFIG_FPE_NWFPE=y
# CONFIG_FPE_NWFPE_XP is not set
# CONFIG_FPE_FASTFPE is not set
CONFIG_VFP=y
CONFIG_VFPv3=y
# CONFIG_NEON is not set
#
# Userspace binary formats
#
CONFIG_BINFMT_ELF=y
# CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS is not set
CONFIG_HAVE_AOUT=y
# CONFIG_BINFMT_AOUT is not set
CONFIG_BINFMT_MISC=y
#
# Power management options
#
CONFIG_PM=y
CONFIG_PM_DEBUG=y
# CONFIG_PM_VERBOSE is not set
# CONFIG_SUSPEND is not set
# CONFIG_APM_EMULATION is not set
CONFIG_ARCH_SUSPEND_POSSIBLE=y
CONFIG_NET=y
#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
CONFIG_UNIX=y
CONFIG_XFRM=y
# CONFIG_XFRM_USER is not set
# CONFIG_XFRM_SUB_POLICY is not set
# CONFIG_XFRM_MIGRATE is not set
# CONFIG_XFRM_STATISTICS is not set
CONFIG_NET_KEY=y
# CONFIG_NET_KEY_MIGRATE is not set
CONFIG_INET=y
# CONFIG_IP_MULTICAST is not set
# CONFIG_IP_ADVANCED_ROUTER is not set
CONFIG_IP_FIB_HASH=y
CONFIG_IP_PNP=y
CONFIG_IP_PNP_DHCP=y
CONFIG_IP_PNP_BOOTP=y
CONFIG_IP_PNP_RARP=y
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_ARPD is not set
# CONFIG_SYN_COOKIES is not set
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_INET_XFRM_TUNNEL is not set
# CONFIG_INET_TUNNEL is not set
CONFIG_INET_XFRM_MODE_TRANSPORT=y
CONFIG_INET_XFRM_MODE_TUNNEL=y
CONFIG_INET_XFRM_MODE_BEET=y
# CONFIG_INET_LRO is not set
CONFIG_INET_DIAG=y
CONFIG_INET_TCP_DIAG=y
# CONFIG_TCP_CONG_ADVANCED is not set
CONFIG_TCP_CONG_CUBIC=y
CONFIG_DEFAULT_TCP_CONG="cubic"
# CONFIG_TCP_MD5SIG is not set
# CONFIG_IPV6 is not set
# CONFIG_NETWORK_SECMARK is not set
# CONFIG_NETFILTER is not set
# CONFIG_IP_DCCP is not set
# CONFIG_IP_SCTP is not set
# CONFIG_TIPC is not set
# CONFIG_ATM is not set
# CONFIG_BRIDGE is not set
# CONFIG_NET_DSA is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_SCHED is not set
#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_HAMRADIO is not set
# CONFIG_CAN is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
# CONFIG_AF_RXRPC is not set
# CONFIG_PHONET is not set
# CONFIG_WIRELESS is not set
# CONFIG_RFKILL is not set
# CONFIG_NET_9P is not set
#
# Device Drivers
#
#
# Generic Driver Options
#
CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
# CONFIG_FW_LOADER is not set
# CONFIG_DEBUG_DRIVER is not set
# CONFIG_DEBUG_DEVRES is not set
# CONFIG_SYS_HYPERVISOR is not set
# CONFIG_CONNECTOR is not set
# CONFIG_MTD is not set
# CONFIG_PARPORT is not set
CONFIG_BLK_DEV=y
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=y
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
# CONFIG_BLK_DEV_NBD is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=16384
# CONFIG_BLK_DEV_XIP is not set
# CONFIG_CDROM_PKTCDVD is not set
# CONFIG_ATA_OVER_ETH is not set
# CONFIG_MISC_DEVICES is not set
CONFIG_HAVE_IDE=y
# CONFIG_IDE is not set
#
# SCSI device support
#
# CONFIG_RAID_ATTRS is not set
CONFIG_SCSI=y
CONFIG_SCSI_DMA=y
# CONFIG_SCSI_TGT is not set
# CONFIG_SCSI_NETLINK is not set
CONFIG_SCSI_PROC_FS=y
#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
# CONFIG_BLK_DEV_SR is not set
# CONFIG_CHR_DEV_SG is not set
# CONFIG_CHR_DEV_SCH is not set
#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
# CONFIG_SCSI_MULTI_LUN is not set
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set
# CONFIG_SCSI_SCAN_ASYNC is not set
CONFIG_SCSI_WAIT_SCAN=m
#
# SCSI Transports
#
# CONFIG_SCSI_SPI_ATTRS is not set
# CONFIG_SCSI_FC_ATTRS is not set
# CONFIG_SCSI_ISCSI_ATTRS is not set
# CONFIG_SCSI_SAS_LIBSAS is not set
# CONFIG_SCSI_SRP_ATTRS is not set
CONFIG_SCSI_LOWLEVEL=y
# CONFIG_ISCSI_TCP is not set
# CONFIG_SCSI_DEBUG is not set
# CONFIG_SCSI_DH is not set
# CONFIG_ATA is not set
# CONFIG_MD is not set
# CONFIG_NETDEVICES is not set
# CONFIG_ISDN is not set
#
# Input device support
#
CONFIG_INPUT=y
# CONFIG_INPUT_FF_MEMLESS is not set
# CONFIG_INPUT_POLLDEV is not set
#
# Userland interfaces
#
# CONFIG_INPUT_MOUSEDEV is not set
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_EVBUG is not set
#
# Input Device Drivers
#
# CONFIG_INPUT_KEYBOARD is not set
# CONFIG_INPUT_MOUSE is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TABLET is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set
#
# Hardware I/O ports
#
# CONFIG_SERIO is not set
# CONFIG_GAMEPORT is not set
#
# Character devices
#
CONFIG_VT=y
CONFIG_CONSOLE_TRANSLATIONS=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_VT_HW_CONSOLE_BINDING is not set
CONFIG_DEVKMEM=y
# CONFIG_SERIAL_NONSTANDARD is not set
#
# Serial drivers
#
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_SERIAL_8250_NR_UARTS=32
CONFIG_SERIAL_8250_RUNTIME_UARTS=4
CONFIG_SERIAL_8250_EXTENDED=y
CONFIG_SERIAL_8250_MANY_PORTS=y
CONFIG_SERIAL_8250_SHARE_IRQ=y
CONFIG_SERIAL_8250_DETECT_IRQ=y
CONFIG_SERIAL_8250_RSA=y
#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_UNIX98_PTYS=y
# CONFIG_LEGACY_PTYS is not set
# CONFIG_IPMI_HANDLER is not set
# CONFIG_HW_RANDOM is not set
# CONFIG_NVRAM is not set
# CONFIG_R3964 is not set
# CONFIG_RAW_DRIVER is not set
# CONFIG_TCG_TPM is not set
CONFIG_I2C=y
CONFIG_I2C_BOARDINFO=y
CONFIG_I2C_CHARDEV=y
CONFIG_I2C_HELPER_AUTO=y
#
# I2C Hardware Bus support
#
#
# I2C system bus drivers (mostly embedded / system-on-chip)
#
# CONFIG_I2C_GPIO is not set
# CONFIG_I2C_OCORES is not set
CONFIG_I2C_OMAP=y
# CONFIG_I2C2_OMAP_BEAGLE is not set
# CONFIG_I2C_SIMTEC is not set
#
# External I2C/SMBus adapter drivers
#
# CONFIG_I2C_PARPORT_LIGHT is not set
# CONFIG_I2C_TAOS_EVM is not set
#
# Other I2C/SMBus bus drivers
#
# CONFIG_I2C_PCA_PLATFORM is not set
# CONFIG_I2C_STUB is not set
#
# Miscellaneous I2C Chip support
#
# CONFIG_DS1682 is not set
# CONFIG_AT24 is not set
# CONFIG_SENSORS_EEPROM is not set
# CONFIG_SENSORS_PCF8574 is not set
# CONFIG_PCF8575 is not set
# CONFIG_SENSORS_PCA9539 is not set
# CONFIG_SENSORS_PCF8591 is not set
# CONFIG_ISP1301_OMAP is not set
# CONFIG_TPS65010 is not set
# CONFIG_SENSORS_TLV320AIC23 is not set
# CONFIG_TWL4030_MADC is not set
CONFIG_TWL4030_USB=y
# CONFIG_TWL4030_PWRBUTTON is not set
# CONFIG_TWL4030_POWEROFF is not set
# CONFIG_SENSORS_MAX6875 is not set
# CONFIG_SENSORS_TSL2550 is not set
# CONFIG_LP5521 is not set
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
# CONFIG_I2C_DEBUG_CHIP is not set
# CONFIG_SPI is not set
CONFIG_ARCH_REQUIRE_GPIOLIB=y
CONFIG_GPIOLIB=y
# CONFIG_DEBUG_GPIO is not set
# CONFIG_GPIO_SYSFS is not set
#
# Memory mapped GPIO expanders:
#
#
# I2C GPIO expanders:
#
# CONFIG_GPIO_MAX732X is not set
# CONFIG_GPIO_PCA953X is not set
# CONFIG_GPIO_PCF857X is not set
CONFIG_GPIO_TWL4030=y
#
# PCI GPIO expanders:
#
#
# SPI GPIO expanders:
#
# CONFIG_W1 is not set
# CONFIG_POWER_SUPPLY is not set
# CONFIG_HWMON is not set
# CONFIG_THERMAL is not set
# CONFIG_THERMAL_HWMON is not set
# CONFIG_WATCHDOG is not set
CONFIG_SSB_POSSIBLE=y
#
# Sonics Silicon Backplane
#
# CONFIG_SSB is not set
#
# Multifunction device drivers
#
# CONFIG_MFD_CORE is not set
# CONFIG_MFD_SM501 is not set
# CONFIG_MFD_ASIC3 is not set
# CONFIG_HTC_EGPIO is not set
# CONFIG_HTC_PASIC3 is not set
CONFIG_TWL4030_CORE=y
# CONFIG_TWL4030_POWER is not set
# CONFIG_MFD_TMIO is not set
# CONFIG_MFD_T7L66XB is not set
# CONFIG_MFD_TC6387XB is not set
# CONFIG_MFD_TC6393XB is not set
# CONFIG_PMIC_DA903X is not set
# CONFIG_MFD_WM8400 is not set
# CONFIG_MFD_WM8350_I2C is not set
#
# Multimedia devices
#
#
# Multimedia core support
#
# CONFIG_VIDEO_DEV is not set
# CONFIG_DVB_CORE is not set
# CONFIG_VIDEO_MEDIA is not set
#
# Multimedia drivers
#
CONFIG_DAB=y
#
# Graphics support
#
# CONFIG_VGASTATE is not set
# CONFIG_VIDEO_OUTPUT_CONTROL is not set
# CONFIG_FB is not set
# CONFIG_BACKLIGHT_LCD_SUPPORT is not set
#
# Display device support
#
# CONFIG_DISPLAY_SUPPORT is not set
#
# Console display driver support
#
# CONFIG_VGA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y
# CONFIG_SOUND is not set
# CONFIG_HID_SUPPORT is not set
# CONFIG_USB_SUPPORT is not set
# CONFIG_MMC is not set
# CONFIG_MEMSTICK is not set
# CONFIG_ACCESSIBILITY is not set
# CONFIG_NEW_LEDS is not set
CONFIG_RTC_LIB=y
CONFIG_RTC_CLASS=y
CONFIG_RTC_HCTOSYS=y
CONFIG_RTC_HCTOSYS_DEVICE="rtc0"
# CONFIG_RTC_DEBUG is not set
#
# RTC interfaces
#
CONFIG_RTC_INTF_SYSFS=y
CONFIG_RTC_INTF_PROC=y
CONFIG_RTC_INTF_DEV=y
# CONFIG_RTC_INTF_DEV_UIE_EMUL is not set
# CONFIG_RTC_DRV_TEST is not set
#
# I2C RTC drivers
#
# CONFIG_RTC_DRV_DS1307 is not set
# CONFIG_RTC_DRV_DS1374 is not set
# CONFIG_RTC_DRV_DS1672 is not set
# CONFIG_RTC_DRV_MAX6900 is not set
# CONFIG_RTC_DRV_RS5C372 is not set
# CONFIG_RTC_DRV_ISL1208 is not set
# CONFIG_RTC_DRV_X1205 is not set
# CONFIG_RTC_DRV_PCF8563 is not set
# CONFIG_RTC_DRV_PCF8583 is not set
# CONFIG_RTC_DRV_M41T80 is not set
# CONFIG_RTC_DRV_TWL4030 is not set
# CONFIG_RTC_DRV_S35390A is not set
# CONFIG_RTC_DRV_FM3130 is not set
# CONFIG_RTC_DRV_RX8581 is not set
#
# SPI RTC drivers
#
#
# Platform RTC drivers
#
# CONFIG_RTC_DRV_CMOS is not set
# CONFIG_RTC_DRV_DS1286 is not set
# CONFIG_RTC_DRV_DS1511 is not set
# CONFIG_RTC_DRV_DS1553 is not set
# CONFIG_RTC_DRV_DS1742 is not set
# CONFIG_RTC_DRV_STK17TA8 is not set
# CONFIG_RTC_DRV_M48T86 is not set
# CONFIG_RTC_DRV_M48T35 is not set
# CONFIG_RTC_DRV_M48T59 is not set
# CONFIG_RTC_DRV_BQ4802 is not set
# CONFIG_RTC_DRV_V3020 is not set
#
# on-CPU RTC drivers
#
# CONFIG_DMADEVICES is not set
# CONFIG_REGULATOR is not set
# CONFIG_UIO is not set
#
# CBUS support
#
# CONFIG_CBUS is not set
#
# File systems
#
CONFIG_EXT2_FS=y
# CONFIG_EXT2_FS_XATTR is not set
# CONFIG_EXT2_FS_XIP is not set
CONFIG_EXT3_FS=y
# CONFIG_EXT3_FS_XATTR is not set
# CONFIG_EXT4_FS is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
# CONFIG_FS_POSIX_ACL is not set
CONFIG_FILE_LOCKING=y
# CONFIG_XFS_FS is not set
# CONFIG_OCFS2_FS is not set
CONFIG_DNOTIFY=y
CONFIG_INOTIFY=y
CONFIG_INOTIFY_USER=y
CONFIG_QUOTA=y
# CONFIG_QUOTA_NETLINK_INTERFACE is not set
CONFIG_PRINT_QUOTA_WARNING=y
# CONFIG_QFMT_V1 is not set
CONFIG_QFMT_V2=y
CONFIG_QUOTACTL=y
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set
# CONFIG_FUSE_FS is not set
#
# CD-ROM/DVD Filesystems
#
# CONFIG_ISO9660_FS is not set
# CONFIG_UDF_FS is not set
#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_VFAT_FS=y
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
# CONFIG_NTFS_FS is not set
#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_SYSCTL=y
CONFIG_PROC_PAGE_MONITOR=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
# CONFIG_TMPFS_POSIX_ACL is not set
# CONFIG_HUGETLB_PAGE is not set
# CONFIG_CONFIGFS_FS is not set
#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_OMFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set
CONFIG_NETWORK_FILESYSTEMS=y
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
# CONFIG_NFS_V3_ACL is not set
CONFIG_NFS_V4=y
CONFIG_ROOT_NFS=y
# CONFIG_NFSD is not set
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=y
CONFIG_SUNRPC_GSS=y
# CONFIG_SUNRPC_REGISTER_V4 is not set
CONFIG_RPCSEC_GSS_KRB5=y
# CONFIG_RPCSEC_GSS_SPKM3 is not set
# CONFIG_SMB_FS is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set
#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
# CONFIG_ACORN_PARTITION is not set
# CONFIG_OSF_PARTITION is not set
# CONFIG_AMIGA_PARTITION is not set
# CONFIG_ATARI_PARTITION is not set
# CONFIG_MAC_PARTITION is not set
CONFIG_MSDOS_PARTITION=y
# CONFIG_BSD_DISKLABEL is not set
# CONFIG_MINIX_SUBPARTITION is not set
# CONFIG_SOLARIS_X86_PARTITION is not set
# CONFIG_UNIXWARE_DISKLABEL is not set
# CONFIG_LDM_PARTITION is not set
# CONFIG_SGI_PARTITION is not set
# CONFIG_ULTRIX_PARTITION is not set
# CONFIG_SUN_PARTITION is not set
# CONFIG_KARMA_PARTITION is not set
# CONFIG_EFI_PARTITION is not set
# CONFIG_SYSV68_PARTITION is not set
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=y
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
# CONFIG_NLS_ASCII is not set
CONFIG_NLS_ISO8859_1=y
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
# CONFIG_NLS_ISO8859_15 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
# CONFIG_NLS_UTF8 is not set
# CONFIG_DLM is not set
#
# Kernel hacking
#
# CONFIG_PRINTK_TIME is not set
CONFIG_ENABLE_WARN_DEPRECATED=y
CONFIG_ENABLE_MUST_CHECK=y
CONFIG_FRAME_WARN=1024
CONFIG_MAGIC_SYSRQ=y
# CONFIG_UNUSED_SYMBOLS is not set
CONFIG_DEBUG_FS=y
# CONFIG_HEADERS_CHECK is not set
CONFIG_DEBUG_KERNEL=y
# CONFIG_DEBUG_SHIRQ is not set
CONFIG_DETECT_SOFTLOCKUP=y
# CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC is not set
CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC_VALUE=0
CONFIG_SCHED_DEBUG=y
# CONFIG_SCHEDSTATS is not set
CONFIG_TIMER_STATS=y
# CONFIG_DEBUG_OBJECTS is not set
# CONFIG_DEBUG_SLAB is not set
CONFIG_DEBUG_PREEMPT=y
# CONFIG_DEBUG_RT_MUTEXES is not set
# CONFIG_RT_MUTEX_TESTER is not set
# CONFIG_DEBUG_SPINLOCK is not set
CONFIG_DEBUG_MUTEXES=y
# CONFIG_DEBUG_LOCK_ALLOC is not set
# CONFIG_PROVE_LOCKING is not set
# CONFIG_LOCK_STAT is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set
# CONFIG_DEBUG_KOBJECT is not set
CONFIG_DEBUG_BUGVERBOSE=y
CONFIG_DEBUG_INFO=y
# CONFIG_DEBUG_VM is not set
# CONFIG_DEBUG_WRITECOUNT is not set
# CONFIG_DEBUG_MEMORY_INIT is not set
# CONFIG_DEBUG_LIST is not set
# CONFIG_DEBUG_SG is not set
CONFIG_FRAME_POINTER=y
# CONFIG_BOOT_PRINTK_DELAY is not set
# CONFIG_RCU_TORTURE_TEST is not set
# CONFIG_RCU_CPU_STALL_DETECTOR is not set
# CONFIG_BACKTRACE_SELF_TEST is not set
# CONFIG_DEBUG_BLOCK_EXT_DEVT is not set
# CONFIG_FAULT_INJECTION is not set
# CONFIG_LATENCYTOP is not set
CONFIG_HAVE_FUNCTION_TRACER=y
#
# Tracers
#
# CONFIG_FUNCTION_TRACER is not set
# CONFIG_IRQSOFF_TRACER is not set
# CONFIG_PREEMPT_TRACER is not set
# CONFIG_SCHED_TRACER is not set
# CONFIG_CONTEXT_SWITCH_TRACER is not set
# CONFIG_BOOT_TRACER is not set
# CONFIG_STACK_TRACER is not set
# CONFIG_DYNAMIC_PRINTK_DEBUG is not set
# CONFIG_SAMPLES is not set
CONFIG_HAVE_ARCH_KGDB=y
# CONFIG_KGDB is not set
# CONFIG_DEBUG_USER is not set
CONFIG_DEBUG_ERRORS=y
# CONFIG_DEBUG_STACK_USAGE is not set
# CONFIG_DEBUG_LL is not set
#
# Security options
#
# CONFIG_KEYS is not set
# CONFIG_SECURITY is not set
# CONFIG_SECURITYFS is not set
# CONFIG_SECURITY_FILE_CAPABILITIES is not set
CONFIG_CRYPTO=y
#
# Crypto core or helper
#
# CONFIG_CRYPTO_FIPS is not set
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_AEAD=y
CONFIG_CRYPTO_BLKCIPHER=y
CONFIG_CRYPTO_HASH=y
CONFIG_CRYPTO_RNG=y
CONFIG_CRYPTO_MANAGER=y
# CONFIG_CRYPTO_GF128MUL is not set
# CONFIG_CRYPTO_NULL is not set
# CONFIG_CRYPTO_CRYPTD is not set
# CONFIG_CRYPTO_AUTHENC is not set
# CONFIG_CRYPTO_TEST is not set
#
# Authenticated Encryption with Associated Data
#
# CONFIG_CRYPTO_CCM is not set
# CONFIG_CRYPTO_GCM is not set
# CONFIG_CRYPTO_SEQIV is not set
#
# Block modes
#
CONFIG_CRYPTO_CBC=y
# CONFIG_CRYPTO_CTR is not set
# CONFIG_CRYPTO_CTS is not set
CONFIG_CRYPTO_ECB=m
# CONFIG_CRYPTO_LRW is not set
CONFIG_CRYPTO_PCBC=m
# CONFIG_CRYPTO_XTS is not set
#
# Hash modes
#
# CONFIG_CRYPTO_HMAC is not set
# CONFIG_CRYPTO_XCBC is not set
#
# Digest
#
# CONFIG_CRYPTO_CRC32C is not set
# CONFIG_CRYPTO_MD4 is not set
CONFIG_CRYPTO_MD5=y
# CONFIG_CRYPTO_MICHAEL_MIC is not set
# CONFIG_CRYPTO_RMD128 is not set
# CONFIG_CRYPTO_RMD160 is not set
# CONFIG_CRYPTO_RMD256 is not set
# CONFIG_CRYPTO_RMD320 is not set
# CONFIG_CRYPTO_SHA1 is not set
# CONFIG_CRYPTO_SHA256 is not set
# CONFIG_CRYPTO_SHA512 is not set
# CONFIG_CRYPTO_TGR192 is not set
# CONFIG_CRYPTO_WP512 is not set
#
# Ciphers
#
# CONFIG_CRYPTO_AES is not set
# CONFIG_CRYPTO_ANUBIS is not set
# CONFIG_CRYPTO_ARC4 is not set
# CONFIG_CRYPTO_BLOWFISH is not set
# CONFIG_CRYPTO_CAMELLIA is not set
# CONFIG_CRYPTO_CAST5 is not set
# CONFIG_CRYPTO_CAST6 is not set
CONFIG_CRYPTO_DES=y
# CONFIG_CRYPTO_FCRYPT is not set
# CONFIG_CRYPTO_KHAZAD is not set
# CONFIG_CRYPTO_SALSA20 is not set
# CONFIG_CRYPTO_SEED is not set
# CONFIG_CRYPTO_SERPENT is not set
# CONFIG_CRYPTO_TEA is not set
# CONFIG_CRYPTO_TWOFISH is not set
#
# Compression
#
# CONFIG_CRYPTO_DEFLATE is not set
# CONFIG_CRYPTO_LZO is not set
#
# Random Number Generation
#
# CONFIG_CRYPTO_ANSI_CPRNG is not set
CONFIG_CRYPTO_HW=y
#
# Library routines
#
CONFIG_BITREVERSE=y
CONFIG_CRC_CCITT=y
# CONFIG_CRC16 is not set
# CONFIG_CRC_T10DIF is not set
# CONFIG_CRC_ITU_T is not set
CONFIG_CRC32=y
# CONFIG_CRC7 is not set
CONFIG_LIBCRC32C=y
CONFIG_PLIST=y
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT=y
CONFIG_HAS_DMA=y
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [ANNOUNCE] new PM branch: pm-20081119
2008-11-20 17:38 ` Kevin Hilman
2008-11-20 17:44 ` Kevin Hilman
@ 2008-11-20 17:53 ` Koen Kooi
1 sibling, 0 replies; 19+ messages in thread
From: Koen Kooi @ 2008-11-20 17:53 UTC (permalink / raw)
To: Kevin Hilman; +Cc: Peter Reid, linux-omap
[-- Attachment #1: Type: text/plain, Size: 2532 bytes --]
Op 20 nov 2008, om 18:38 heeft Kevin Hilman het volgende geschreven:
> "Peter Reid" <ppeter.reid@gmail.com> writes:
>
>> Hello kevin,
>> Here is what i did to put it to suspend, which fails.
>>
>> [root@beagleboard]# echo mem > /sys/power/state
>> PM: Syncing filesystems ... done.
>> Freezing user space processes ... (elapsed 0.00 seconds) done.
>> Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
>> Suspending console(s)
>> Class driver suspend failed for cpu0
>> PM: Some devices failed to power down
>
> Hi Peter,
>
> Thanks for testing on Beagle. Do you mind sharing your .config? And,
> would you mind testing with the attached config? This PM branch will
> currently only work with a minimal set of drivers. Many of the
> current drivers will still prevent retention and OFF mode.
>
> Do you have CPUfreq enabled? I saw this 'class driver suspend'
> problem when I had CPUfreq enabled. This branch doesn't currently
> have CPUfreq support, so you can leave that disabled.
>
> I've also noticed problems on ES2 Beagle as well that I haven't
> figured out yet. Namely, I think the bootloader is leaving certain
> modules (namely DSS and IVA) in a state that is preventing hitting
> retention.
>
> Immediately after boot, the DSS powerdomain is still ON and it should
> be in retention, same for IVA but I haven't debugged this further on
> Beagle. The same kernel works on 3430SDP so that's why my hunch
> points to the u-boot.
>
> The kernel needs a way to ensure that after booting all the unused
> modules are in a state where they are not preventing idle. Even with
> disabled clocks, certain modules can prevent idle. Paul Walmsley has
> written the 'omapdev' layer which will now make it easier to do this
> boot-time init, but it is currently not there. We currently have to
> rely on bootloaders doing the right thing.
>
> The beagle bootloader does all sorts of stuff with DSS, MMC, audio
> etc. so it is a likely candidate.
Only the TI version does that, you'd be better of using the 'omap3'
branch of the u-boot arm git, or Steve Sakomans git tree (which is
where the upstream patches originate from).
I don't know if that version fixed DSS and IVA, but it is a lot
cleaner and saves a considerable amount of boot time :) A binary is
located at:
http://www.angstrom-distribution.org/demo/beagleboard/u-boot.bin
That binary also contains a fix for the 'l1neon' problem where the
optimized version of ffmpeg or mplayer would crash under heavy load.
regards,
Koen
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 186 bytes --]
^ permalink raw reply [flat|nested] 19+ messages in thread
* RE: [ANNOUNCE] new PM branch: pm-20081119
2008-11-20 14:13 ` Premi, Sanjeev
` (2 preceding siblings ...)
2008-11-20 17:40 ` Kevin Hilman
@ 2008-11-21 7:20 ` Kalle Jokiniemi
3 siblings, 0 replies; 19+ messages in thread
From: Kalle Jokiniemi @ 2008-11-21 7:20 UTC (permalink / raw)
To: ext Premi, Sanjeev
Cc: Peter Reid, Kevin Hilman, linux-omap@vger.kernel.org, Imre Deak
On to, 2008-11-20 at 19:43 +0530, ext Premi, Sanjeev wrote:
>
>
> > -----Original Message-----
> > From: linux-omap-owner@vger.kernel.org
> > [mailto:linux-omap-owner@vger.kernel.org] On Behalf Of Peter Reid
> > Sent: Thursday, November 20, 2008 2:16 PM
> > To: Kevin Hilman
> > Cc: linux-omap@vger.kernel.org
> > Subject: Re: [ANNOUNCE] new PM branch: pm-20081119
> >
> > Hello kevin,
> > Here is what i did to put it to suspend, which fails.
> >
> > [root@beagleboard]# echo mem > /sys/power/state
> > PM: Syncing filesystems ... done.
> > Freezing user space processes ... (elapsed 0.00 seconds) done.
> > Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
> > Suspending console(s)
> > Class driver suspend failed for cpu0
> > PM: Some devices failed to power down
> >
> > Regards,
> > Reid.
> These are my observations on OMAP3EVM:
>
> 1) Very frequently I see these messages:
>
> <4>__ratelimit: 6736 callbacks suppressed
> __ratelimit: 6736 callbacks suppressed
> <3>omapfb omapfb: irq error status 00c2
> omapfb omapfb: irq error status 00c2
> <3>omapfb omapfb: irq error status 0060
> omapfb omapfb: irq error status 0060
> <3>omapfb omapfb: irq error status 00c2
> omapfb omapfb: irq error status 00c2
> <3>omapfb omapfb: irq error status 0060
> omapfb omapfb: irq error status 0060
> <3>omapfb omapfb: irq error status 00e2
> omapfb omapfb: irq error status 00e2
> <3>omapfb omapfb: irq error status 00c2
> omapfb omapfb: irq error status 00c2
> <3>omapfb omapfb: irq error status 0060
> omapfb omapfb: irq error status 0060
> <3>omapfb omapfb: irq error status 00e2
> omapfb omapfb: irq error status 00e2
> <3>omapfb omapfb: irq error status 00c2
> omapfb omapfb: irq error status 00c2
> <3>omapfb omapfb: irq error status 0060
> omapfb omapfb: irq error status 0060
The interrupts we see here mean that GFX FIFO has underflown. This is
because cpu idle issues WFI very frequently making the DSS also stop
it's clocks when idle. Problem is that waking up the DSS seems to take
longer than the FIFO lasts.
You can fix this by setting the fifo thresholds to very high. TI uses
1020 for high thresholds and 956 for low thresholds in their kernel.
Maximum is 1023.
Here's a patch by Imre, that worked for us.
- Kalle
>From d23ce521f95671f1b012b8542e88100d4a143771 Mon Sep 17 00:00:00 2001
From: Imre Deak <imre.deak@nokia.com>
Date: Tue, 11 Nov 2008 13:43:39 +0200
Subject: [PATCH] ARM: OMAP: OMAPFB: Adjust DMA FIFO thresholds for power
save mode
DMA FIFO underflow error occures if power save mode is enabled, try
to tackle this by setting a higher DMA FIFO threshold values. Also
the maximum value is FIFO size - 1 not FIFO size, so fix this.
Problem report and solution from Kalle Jokiniemi.
Signed-off-by: Imre Deak <imre.deak@nokia.com>
---
drivers/video/omap/dispc.c | 13 ++++---------
1 files changed, 4 insertions(+), 9 deletions(-)
diff --git a/drivers/video/omap/dispc.c b/drivers/video/omap/dispc.c
index da827b1..b4a1542 100644
--- a/drivers/video/omap/dispc.c
+++ b/drivers/video/omap/dispc.c
@@ -296,15 +296,10 @@ static void setup_plane_fifo(int plane, int
ext_mode)
BUG_ON(plane > 2);
l = dispc_read_reg(fsz_reg[plane]);
- l &= FLD_MASK(0, 11);
- if (ext_mode) {
- low = l * 3 / 4;
- high = l;
- } else {
- low = l / 4;
- high = l * 3 / 4;
- }
- MOD_REG_FLD(ftrs_reg[plane], FLD_MASK(16, 12) | FLD_MASK(0, 12),
+ l &= FLD_MASK(0, 9);
+ low = l * 3 / 4;
+ high = l - 1;
+ MOD_REG_FLD(ftrs_reg[plane], FLD_MASK(16, 9) | FLD_MASK(0, 9),
(high << 16) | low);
}
--
1.5.4.3
>
> 2) Also:
> # 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.00 seconds) (elapsed 0.00 seconds) done.
> done.
>
> Suspending console(s) (use no_console_suspend to debug)
> Suspending console(s) (use no_console_suspend to debug)
> <3>omapfb omapfb: timeout waiting for FRAME DONE
>
> However, I the "resume" doesn't happen.
> Trying to debug further.
>
> Best regards,
> Sanjeev
>
> > On Thu, Nov 20, 2008 at 6:23 AM, Kevin Hilman
> > <khilman@deeprootsystems.com> wrote:
> > > Hello,
> > >
> > > A new PM branch is available named pm-20081119.
> > >
> > > This is mostly a new set of patches on top of the previous
> > PM branch,
> > > rather than a rebase. We finally found the root cause of some DPLL
> > > relocking bugs. Special thanks to Paul Walmsley and Tero
> > Kristo for
> > > debugging and fixing this problem. Now the DPLL fix that
> > was reverted
> > > in the previous PM branch is re-applied as well as some
> > fixes on top
> > > of it. It also has some additional UART fixes, so I think the UART
> > > idle work is ready to go to Tony. Special thanks to Jouni Hogander
> > > for the extra testing and fixes here.
> > >
> > > The shortlog is below[1] and the root of the tree is still
> > > v2.6.27-omap1 + T2 power patches from Peter.
> > >
> > > This has primarily been tested on custom HW since I'm
> > _still_ waiting
> > > for my SDP to arrive. I have boot tested on Beagle, but I
> > think there
> > > are still some problems with ES2 silicon. On my ES2
> > Beagle, neither
> > > DSS or IVA will leave the ON state, even when all clocks in their
> > > powerdomains are off. I have not debugged this further yet.
> > >
> > > Functionally, this tree is in pretty good shape, so I will do some
> > > bugfixes here when necessary, but will now spent some time
> > focusing on
> > > getting the patches in this branch merged into linux-omap.
> > >
> > > Kevin
> > >
> > >
> > > [1] git shortlog:
> > >
> > > Amit Kucheria (2):
> > > OMAP: PM: Typo fix for clock_allow_idle
> > > HSMMC: Make driver support dynamic idle
> > >
> > > Jouni Hogander (11):
> > > OMAP3: PM: Use pwrdm_set_next_pwrst instead of
> > set_pwrdm_state in idle loop
> > > OMAP3: Do not set mpu, core, neon states if cpuidle is used
> > > OMAP3: PM: Do not set next states sw to control those
> > is available
> > > OMAP3: PM: Always return value in pwrdms_setup
> > > OMAP3: PM: Fix wrong sequence in suspend.
> > > OMAP3: UART: Make sure that uart clocks are enabled when needed
> > > OMAP3: PM: Check in set_pwrdm_state that target state
> > is supported by pwrdm v2
> > > 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
> > > OMAP: MCSPI: Enable mcspi wake-up
> > >
> > > Kalle Jokiniemi (4):
> > > 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)
> > > OMAP3: I2C: Enable I2C wakeups
> > >
> > > Kevin Hilman (16):
> > > OMAP3: PM: Add wake-up bit defintiions for CONTROL_PADCONF_X
> > > OMAP3: PM: Allow UARTs to be unclocked when inactive
> > > 8250: Allow platform to register PM hook
> > > 8250: when waking, PM hook should be called before
> > accessing port
> > > OMAP3: PM: UART: Add 8250 UART PM hook for suspend/resume
> > > OMAP3: PM: UART save/restore support for OFF-mode
> > > OMAP2/3: HSMMC: Ensure HSMMC is fully reset on boot
> > > 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
> > > Revert "OMAP3 clock: fix non-CORE DPLL rate assignment bugs"
> > > Revert "OMAP3: PM: Do not set next states sw to
> > control those is available"
> > > Revert "OMAP3: Do not set mpu, core, neon states if
> > cpuidle is used"
> > > OMAP: PM: UART: fix can_sleep hook to return correct value
> > > OMAP: PM: UART: Only disable clocks in prepare-idle hook
> > > OMAP3: PM: Check for UART wakeups in 'resume_idle' hook
> > >
> > > Paul Walmsley (14):
> > > 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
> > > OMAP3 clock: fix non-CORE DPLL rate assignment bugs
> > > OMAP3 powerdomains: remove RET from SGX power states list
> > > OMAP3 powerdomains: remove RET from SGX power states list
> > > OMAP3 clock: remove unnecessary dpll_data dereferences
> > > OMAP3 clock: optimize DPLL rate rounding algorithm
> > > OMAP3 clock: avoid invalid FREQSEL values during DPLL
> > rate rounding
> > > OMAP2/3 I2C: reprogram OCP_SYSCONFIG register after reset
> > > OMAP: I2C: convert 'rev1' flag to generic 'rev' u8
> > >
> > > Peter 'p2' De Schrijver (9):
> > > 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()
> > >
> > > Rajendra Nayak (23):
> > > 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: PM: CPUidle: Enable Kconfig option for OMAP
> > > 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
> > >
> > > Tero Kristo (13):
> > > 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: Fix a bug with noncore dpll rate calculation
> > > PM: Added three PLL registers to the PRCM context save
> > > PM: OMAP3: Make sure clk_disable_unused() order is correct
> > > PM: Changed secure RAM storage size from 0x8000 to 0x803F
> > >
> > > --
> > > 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
> >
> > --
> 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
^ permalink raw reply related [flat|nested] 19+ messages in thread
* Re: [ANNOUNCE] new PM branch: pm-20081119
2008-11-20 14:48 ` Koen Kooi
2008-11-20 15:25 ` Premi, Sanjeev
@ 2008-11-21 7:29 ` Kalle Jokiniemi
1 sibling, 0 replies; 19+ messages in thread
From: Kalle Jokiniemi @ 2008-11-21 7:29 UTC (permalink / raw)
To: ext Koen Kooi
Cc: Premi, Sanjeev, Peter Reid, Kevin Hilman,
linux-omap@vger.kernel.org
On to, 2008-11-20 at 15:48 +0100, ext Koen Kooi wrote:
> Op 20 nov 2008, om 15:13 heeft Premi, Sanjeev het volgende geschreven:
> >>
> > These are my observations on OMAP3EVM:
> >
> > 1) Very frequently I see these messages:
> >
> > <4>__ratelimit: 6736 callbacks suppressed
> > __ratelimit: 6736 callbacks suppressed
> > <3>omapfb omapfb: irq error status 00c2
> > omapfb omapfb: irq error status 00c2
>
> There should be a workaround for those in 2.6.28rc3. Rick Bronson
> posted a message about it on 7 november titled "Fix for dispc's error
> "omapfb omapfb: irq error status 4020"
This interrupt is from SYNCLOST, which is different than what Premi had
(GFX fifo underflow). For that underflow one needs to set higher fifo
thresholds, like I described in my earlier mail.
- Kalle
>
> regards,
>
> Koen
>
> regards,
>
> Koen
^ permalink raw reply [flat|nested] 19+ messages in thread
* RE: [ANNOUNCE] new PM branch: pm-20081119
2008-11-20 17:40 ` Kevin Hilman
@ 2008-11-21 15:46 ` Premi, Sanjeev
2008-11-21 16:05 ` Kevin Hilman
0 siblings, 1 reply; 19+ messages in thread
From: Premi, Sanjeev @ 2008-11-21 15:46 UTC (permalink / raw)
To: Kevin Hilman; +Cc: Peter Reid, linux-omap@vger.kernel.org
[-- Attachment #1: Type: text/plain, Size: 11634 bytes --]
> -----Original Message-----
> From: Kevin Hilman [mailto:khilman@deeprootsystems.com]
> Sent: Thursday, November 20, 2008 11:10 PM
> To: Premi, Sanjeev
> Cc: Peter Reid; linux-omap@vger.kernel.org
> Subject: Re: [ANNOUNCE] new PM branch: pm-20081119
>
> "Premi, Sanjeev" <premi@ti.com> writes:
>
> > These are my observations on OMAP3EVM:
> >
> > 1) Very frequently I see these messages:
> >
> > <4>__ratelimit: 6736 callbacks suppressed
> > __ratelimit: 6736 callbacks suppressed <3>omapfb omapfb: irq error
> > status 00c2 omapfb omapfb: irq error status 00c2 <3>omapfb
> omapfb: irq
> > error status 0060 omapfb omapfb: irq error status 0060 <3>omapfb
> > omapfb: irq error status 00c2 omapfb omapfb: irq error status 00c2
> > <3>omapfb omapfb: irq error status 0060 omapfb omapfb: irq error
> > status 0060 <3>omapfb omapfb: irq error status 00e2 omapfb
> omapfb: irq
> > error status 00e2 <3>omapfb omapfb: irq error status 00c2 omapfb
> > omapfb: irq error status 00c2 <3>omapfb omapfb: irq error
> status 0060
> > omapfb omapfb: irq error status 0060 <3>omapfb omapfb: irq error
> > status 00e2 omapfb omapfb: irq error status 00e2 <3>omapfb
> omapfb: irq
> > error status 00c2 omapfb omapfb: irq error status 00c2 <3>omapfb
> > omapfb: irq error status 0060 omapfb omapfb: irq error status 0060
>
> Sanjeev,
>
> For starters can you try with a minimal kernel (no drivers,
> no framebuffer, etc.)
>
> The first goal is to hit retention and off with no drivers
> than start moving out to address driver issues from there.
>
> Kevin
>
Here is what I was able to see with the minimal config (attached).
[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.01 seconds) (elapsed 0.01 seconds) done.done.
Suspending console(s) (use no_console_suspend to debug)
Suspending console(s) (use no_console_suspend to debug)
<snip>un-printable characters<snip>
Powerdomain (per_pwrdm) didn't enter target state 1
Could not enter target state in pm_suspend
Restarting tasks ... Restarting tasks ... done.
done.
Haven't had chance to debug further. Any additional driver added repeats the same behavior. I am not yet certain if the PM_DEBUG has any role. Haven't been able to try few combinations that I wanted to.
Best regards,
Sanjeev
> > 2) Also:
> > # 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.00 seconds) (elapsed 0.00
> seconds) done.
> > done.
> >
> > Suspending console(s) (use no_console_suspend to debug) Suspending
> > console(s) (use no_console_suspend to debug) <3>omapfb
> omapfb: timeout
> > waiting for FRAME DONE
> >
> > However, I the "resume" doesn't happen.
> > Trying to debug further.
> >
> > Best regards,
> > Sanjeev
> >
> >> On Thu, Nov 20, 2008 at 6:23 AM, Kevin Hilman
> >> <khilman@deeprootsystems.com> wrote:
> >> > Hello,
> >> >
> >> > A new PM branch is available named pm-20081119.
> >> >
> >> > This is mostly a new set of patches on top of the previous
> >> PM branch,
> >> > rather than a rebase. We finally found the root cause
> of some DPLL
> >> > relocking bugs. Special thanks to Paul Walmsley and Tero
> >> Kristo for
> >> > debugging and fixing this problem. Now the DPLL fix that
> >> was reverted
> >> > in the previous PM branch is re-applied as well as some
> >> fixes on top
> >> > of it. It also has some additional UART fixes, so I
> think the UART
> >> > idle work is ready to go to Tony. Special thanks to
> Jouni Hogander
> >> > for the extra testing and fixes here.
> >> >
> >> > The shortlog is below[1] and the root of the tree is still
> >> > v2.6.27-omap1 + T2 power patches from Peter.
> >> >
> >> > This has primarily been tested on custom HW since I'm
> >> _still_ waiting
> >> > for my SDP to arrive. I have boot tested on Beagle, but I
> >> think there
> >> > are still some problems with ES2 silicon. On my ES2
> >> Beagle, neither
> >> > DSS or IVA will leave the ON state, even when all clocks
> in their
> >> > powerdomains are off. I have not debugged this further yet.
> >> >
> >> > Functionally, this tree is in pretty good shape, so I
> will do some
> >> > bugfixes here when necessary, but will now spent some time
> >> focusing on
> >> > getting the patches in this branch merged into linux-omap.
> >> >
> >> > Kevin
> >> >
> >> >
> >> > [1] git shortlog:
> >> >
> >> > Amit Kucheria (2):
> >> > OMAP: PM: Typo fix for clock_allow_idle
> >> > HSMMC: Make driver support dynamic idle
> >> >
> >> > Jouni Hogander (11):
> >> > OMAP3: PM: Use pwrdm_set_next_pwrst instead of
> >> set_pwrdm_state in idle loop
> >> > OMAP3: Do not set mpu, core, neon states if cpuidle is used
> >> > OMAP3: PM: Do not set next states sw to control those
> >> is available
> >> > OMAP3: PM: Always return value in pwrdms_setup
> >> > OMAP3: PM: Fix wrong sequence in suspend.
> >> > OMAP3: UART: Make sure that uart clocks are enabled
> when needed
> >> > OMAP3: PM: Check in set_pwrdm_state that target state
> >> is supported by pwrdm v2
> >> > 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
> >> > OMAP: MCSPI: Enable mcspi wake-up
> >> >
> >> > Kalle Jokiniemi (4):
> >> > 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)
> >> > OMAP3: I2C: Enable I2C wakeups
> >> >
> >> > Kevin Hilman (16):
> >> > OMAP3: PM: Add wake-up bit defintiions for CONTROL_PADCONF_X
> >> > OMAP3: PM: Allow UARTs to be unclocked when inactive
> >> > 8250: Allow platform to register PM hook
> >> > 8250: when waking, PM hook should be called before
> >> accessing port
> >> > OMAP3: PM: UART: Add 8250 UART PM hook for suspend/resume
> >> > OMAP3: PM: UART save/restore support for OFF-mode
> >> > OMAP2/3: HSMMC: Ensure HSMMC is fully reset on boot
> >> > 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
> >> > Revert "OMAP3 clock: fix non-CORE DPLL rate assignment bugs"
> >> > Revert "OMAP3: PM: Do not set next states sw to
> >> control those is available"
> >> > Revert "OMAP3: Do not set mpu, core, neon states if
> >> cpuidle is used"
> >> > OMAP: PM: UART: fix can_sleep hook to return correct value
> >> > OMAP: PM: UART: Only disable clocks in prepare-idle hook
> >> > OMAP3: PM: Check for UART wakeups in 'resume_idle' hook
> >> >
> >> > Paul Walmsley (14):
> >> > 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
> >> > OMAP3 clock: fix non-CORE DPLL rate assignment bugs
> >> > OMAP3 powerdomains: remove RET from SGX power states list
> >> > OMAP3 powerdomains: remove RET from SGX power states list
> >> > OMAP3 clock: remove unnecessary dpll_data dereferences
> >> > OMAP3 clock: optimize DPLL rate rounding algorithm
> >> > OMAP3 clock: avoid invalid FREQSEL values during DPLL
> >> rate rounding
> >> > OMAP2/3 I2C: reprogram OCP_SYSCONFIG register after reset
> >> > OMAP: I2C: convert 'rev1' flag to generic 'rev' u8
> >> >
> >> > Peter 'p2' De Schrijver (9):
> >> > 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()
> >> >
> >> > Rajendra Nayak (23):
> >> > 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: PM: CPUidle: Enable Kconfig option for OMAP
> >> > 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
> >> >
> >> > Tero Kristo (13):
> >> > 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: Fix a bug with noncore dpll rate calculation
> >> > PM: Added three PLL registers to the PRCM context save
> >> > PM: OMAP3: Make sure clk_disable_unused() order is correct
> >> > PM: Changed secure RAM storage size from 0x8000 to 0x803F
> >> >
> >> > --
> >> > 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
> >>
> >>
>
>
[-- Attachment #2: evm_config --]
[-- Type: application/octet-stream, Size: 21750 bytes --]
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.27-omap1
# Fri Nov 21 19:51:37 2008
#
CONFIG_ARM=y
CONFIG_SYS_SUPPORTS_APM_EMULATION=y
CONFIG_GENERIC_GPIO=y
CONFIG_GENERIC_TIME=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_MMU=y
# CONFIG_NO_IOPORT is not set
CONFIG_GENERIC_HARDIRQS=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_HAVE_LATENCYTOP_SUPPORT=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
CONFIG_HARDIRQS_SW_RESEND=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_RWSEM_GENERIC_SPINLOCK=y
# CONFIG_ARCH_HAS_ILOG2_U32 is not set
# CONFIG_ARCH_HAS_ILOG2_U64 is not set
CONFIG_GENERIC_HWEIGHT=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_ARCH_SUPPORTS_AOUT=y
CONFIG_ZONE_DMA=y
CONFIG_GENERIC_HARDIRQS_NO__DO_IRQ=y
CONFIG_VECTORS_BASE=0xffff0000
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
#
# General setup
#
CONFIG_EXPERIMENTAL=y
CONFIG_BROKEN_ON_SMP=y
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_LOCALVERSION=""
CONFIG_LOCALVERSION_AUTO=y
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_BSD_PROCESS_ACCT=y
# CONFIG_BSD_PROCESS_ACCT_V3 is not set
# CONFIG_IKCONFIG is not set
CONFIG_LOG_BUF_SHIFT=14
# CONFIG_CGROUPS is not set
CONFIG_GROUP_SCHED=y
CONFIG_FAIR_GROUP_SCHED=y
# CONFIG_RT_GROUP_SCHED is not set
CONFIG_USER_SCHED=y
# CONFIG_CGROUP_SCHED is not set
CONFIG_SYSFS_DEPRECATED=y
CONFIG_SYSFS_DEPRECATED_V2=y
# CONFIG_RELAY is not set
# CONFIG_NAMESPACES is not set
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
CONFIG_SYSCTL=y
CONFIG_EMBEDDED=y
CONFIG_UID16=y
# CONFIG_SYSCTL_SYSCALL is not set
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_ALL is not set
CONFIG_KALLSYMS_EXTRA_PASS=y
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_COMPAT_BRK=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_ANON_INODES=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_TIMERFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_SLAB=y
# CONFIG_SLUB is not set
# CONFIG_SLOB is not set
# CONFIG_PROFILING is not set
# CONFIG_MARKERS is not set
CONFIG_HAVE_OPROFILE=y
# CONFIG_KPROBES is not set
# CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS is not set
# CONFIG_HAVE_IOREMAP_PROT is not set
CONFIG_HAVE_KPROBES=y
CONFIG_HAVE_KRETPROBES=y
# CONFIG_HAVE_ARCH_TRACEHOOK is not set
# CONFIG_HAVE_DMA_ATTRS is not set
# CONFIG_USE_GENERIC_SMP_HELPERS is not set
CONFIG_HAVE_CLK=y
CONFIG_PROC_PAGE_MONITOR=y
CONFIG_HAVE_GENERIC_DMA_COHERENT=y
CONFIG_SLABINFO=y
CONFIG_RT_MUTEXES=y
# CONFIG_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0
CONFIG_MODULES=y
# CONFIG_MODULE_FORCE_LOAD is not set
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
CONFIG_MODVERSIONS=y
CONFIG_MODULE_SRCVERSION_ALL=y
CONFIG_KMOD=y
CONFIG_BLOCK=y
# CONFIG_LBD is not set
# CONFIG_BLK_DEV_IO_TRACE is not set
# CONFIG_LSF is not set
# CONFIG_BLK_DEV_BSG is not set
# CONFIG_BLK_DEV_INTEGRITY is not set
#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
CONFIG_DEFAULT_AS=y
# CONFIG_DEFAULT_DEADLINE is not set
# CONFIG_DEFAULT_CFQ is not set
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="anticipatory"
CONFIG_CLASSIC_RCU=y
#
# System Type
#
# CONFIG_ARCH_AAEC2000 is not set
# CONFIG_ARCH_INTEGRATOR is not set
# CONFIG_ARCH_REALVIEW is not set
# CONFIG_ARCH_VERSATILE is not set
# CONFIG_ARCH_AT91 is not set
# CONFIG_ARCH_CLPS7500 is not set
# CONFIG_ARCH_CLPS711X is not set
# CONFIG_ARCH_EBSA110 is not set
# CONFIG_ARCH_EP93XX is not set
# CONFIG_ARCH_FOOTBRIDGE is not set
# CONFIG_ARCH_NETX is not set
# CONFIG_ARCH_H720X is not set
# CONFIG_ARCH_IMX is not set
# CONFIG_ARCH_IOP13XX is not set
# CONFIG_ARCH_IOP32X is not set
# CONFIG_ARCH_IOP33X is not set
# CONFIG_ARCH_IXP23XX is not set
# CONFIG_ARCH_IXP2000 is not set
# CONFIG_ARCH_IXP4XX is not set
# CONFIG_ARCH_L7200 is not set
# CONFIG_ARCH_KIRKWOOD is not set
# CONFIG_ARCH_KS8695 is not set
# CONFIG_ARCH_NS9XXX is not set
# CONFIG_ARCH_LOKI is not set
# CONFIG_ARCH_MV78XX0 is not set
# CONFIG_ARCH_MXC is not set
# CONFIG_ARCH_ORION5X is not set
# CONFIG_ARCH_PNX4008 is not set
# CONFIG_ARCH_PXA is not set
# CONFIG_ARCH_RPC is not set
# CONFIG_ARCH_SA1100 is not set
# CONFIG_ARCH_S3C2410 is not set
# CONFIG_ARCH_SHARK is not set
# CONFIG_ARCH_LH7A40X is not set
# CONFIG_ARCH_DAVINCI is not set
CONFIG_ARCH_OMAP=y
# CONFIG_ARCH_MSM7X00A is not set
#
# TI OMAP Implementations
#
CONFIG_ARCH_OMAP_OTG=y
# CONFIG_ARCH_OMAP1 is not set
# CONFIG_ARCH_OMAP2 is not set
CONFIG_ARCH_OMAP3=y
#
# OMAP Feature Selections
#
# CONFIG_OMAP_DEBUG_POWERDOMAIN is not set
# CONFIG_OMAP_DEBUG_CLOCKDOMAIN is not set
CONFIG_OMAP_RESET_CLOCKS=y
CONFIG_OMAP_BOOT_TAG=y
CONFIG_OMAP_BOOT_REASON=y
# CONFIG_OMAP_COMPONENT_VERSION is not set
# CONFIG_OMAP_GPIO_SWITCH is not set
CONFIG_OMAP_MUX=y
# CONFIG_OMAP_MUX_DEBUG is not set
CONFIG_OMAP_MUX_WARNINGS=y
# CONFIG_OMAP_MCBSP is not set
# CONFIG_OMAP_MMU_FWK is not set
# CONFIG_OMAP_MBOX_FWK is not set
# CONFIG_OMAP_MPU_TIMER is not set
CONFIG_OMAP_32K_TIMER=y
CONFIG_OMAP_32K_TIMER_HZ=128
CONFIG_OMAP_DM_TIMER=y
CONFIG_OMAP_LL_DEBUG_UART1=y
# CONFIG_OMAP_LL_DEBUG_UART2 is not set
# CONFIG_OMAP_LL_DEBUG_UART3 is not set
CONFIG_OMAP_SERIAL_WAKE=y
# CONFIG_OMAP_PM_NONE is not set
CONFIG_OMAP_PM_NOOP=y
# CONFIG_OMAP_PM_SRF is not set
CONFIG_ARCH_OMAP34XX=y
CONFIG_ARCH_OMAP3430=y
#
# OMAP Board Type
#
# CONFIG_MACH_OMAP_LDP is not set
# CONFIG_MACH_OMAP_3430SDP is not set
CONFIG_MACH_OMAP3EVM=y
# CONFIG_MACH_OMAP3_BEAGLE is not set
# CONFIG_MACH_OVERO is not set
# CONFIG_MACH_OMAP3_PANDORA is not set
CONFIG_OMAP_TICK_GPTIMER=1
#
# Boot options
#
#
# Power management
#
#
# Processor Type
#
CONFIG_CPU_32=y
CONFIG_CPU_32v6K=y
CONFIG_CPU_V7=y
CONFIG_CPU_32v7=y
CONFIG_CPU_ABRT_EV7=y
CONFIG_CPU_PABRT_IFAR=y
CONFIG_CPU_CACHE_V7=y
CONFIG_CPU_CACHE_VIPT=y
CONFIG_CPU_COPY_V6=y
CONFIG_CPU_TLB_V7=y
CONFIG_CPU_HAS_ASID=y
CONFIG_CPU_CP15=y
CONFIG_CPU_CP15_MMU=y
#
# Processor Features
#
CONFIG_ARM_THUMB=y
# CONFIG_ARM_THUMBEE is not set
# CONFIG_CPU_ICACHE_DISABLE is not set
# CONFIG_CPU_DCACHE_DISABLE is not set
# CONFIG_CPU_BPREDICT_DISABLE is not set
CONFIG_HAS_TLS_REG=y
# CONFIG_OUTER_CACHE is not set
#
# Bus support
#
# CONFIG_PCI_SYSCALL is not set
# CONFIG_ARCH_SUPPORTS_MSI is not set
# CONFIG_PCCARD is not set
#
# Kernel Features
#
CONFIG_TICK_ONESHOT=y
CONFIG_NO_HZ=y
CONFIG_HIGH_RES_TIMERS=y
CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
# CONFIG_PREEMPT is not set
CONFIG_HZ=128
CONFIG_AEABI=y
CONFIG_OABI_COMPAT=y
CONFIG_ARCH_FLATMEM_HAS_HOLES=y
# CONFIG_ARCH_DISCONTIGMEM_ENABLE is not set
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_FLATMEM_MANUAL=y
# CONFIG_DISCONTIGMEM_MANUAL is not set
# CONFIG_SPARSEMEM_MANUAL is not set
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
# CONFIG_SPARSEMEM_STATIC is not set
# CONFIG_SPARSEMEM_VMEMMAP_ENABLE is not set
CONFIG_PAGEFLAGS_EXTENDED=y
CONFIG_SPLIT_PTLOCK_CPUS=4
# CONFIG_RESOURCES_64BIT is not set
CONFIG_ZONE_DMA_FLAG=1
CONFIG_BOUNCE=y
CONFIG_VIRT_TO_BUS=y
# CONFIG_LEDS is not set
CONFIG_ALIGNMENT_TRAP=y
#
# Boot options
#
CONFIG_ZBOOT_ROM_TEXT=0x0
CONFIG_ZBOOT_ROM_BSS=0x0
CONFIG_CMDLINE="root=/dev/nfs nfsroot=192.168.0.1:/home/user/buildroot ip=192.168.0.2:192.168.0.1:192.168.0.1:255.255.255.0:tgt:eth0:off rw console=ttyS2,115200n8"
# CONFIG_XIP_KERNEL is not set
# CONFIG_KEXEC is not set
#
# CPUIdle
#
# CONFIG_CPU_IDLE is not set
#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set
#
# Floating point emulation
#
#
# At least one emulation must be selected
#
CONFIG_FPE_NWFPE=y
# CONFIG_FPE_NWFPE_XP is not set
# CONFIG_FPE_FASTFPE is not set
CONFIG_VFP=y
CONFIG_VFPv3=y
CONFIG_NEON=y
#
# Userspace binary formats
#
CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_AOUT is not set
CONFIG_BINFMT_MISC=y
#
# Power management options
#
CONFIG_PM=y
# CONFIG_PM_DEBUG is not set
CONFIG_PM_SLEEP=y
CONFIG_SUSPEND=y
CONFIG_SUSPEND_FREEZER=y
# CONFIG_APM_EMULATION is not set
CONFIG_ARCH_SUSPEND_POSSIBLE=y
# CONFIG_NET is not set
#
# Device Drivers
#
#
# Generic Driver Options
#
CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
# CONFIG_FW_LOADER is not set
# CONFIG_DEBUG_DRIVER is not set
# CONFIG_DEBUG_DEVRES is not set
# CONFIG_SYS_HYPERVISOR is not set
CONFIG_MTD=y
# CONFIG_MTD_DEBUG is not set
CONFIG_MTD_CONCAT=y
CONFIG_MTD_PARTITIONS=y
# CONFIG_MTD_REDBOOT_PARTS is not set
CONFIG_MTD_CMDLINE_PARTS=y
# CONFIG_MTD_AFS_PARTS is not set
# CONFIG_MTD_AR7_PARTS is not set
#
# User Modules And Translation Layers
#
CONFIG_MTD_CHAR=y
CONFIG_MTD_BLKDEVS=y
CONFIG_MTD_BLOCK=y
# CONFIG_FTL is not set
# CONFIG_NFTL is not set
# CONFIG_INFTL is not set
# CONFIG_RFD_FTL is not set
# CONFIG_SSFDC is not set
# CONFIG_MTD_OOPS is not set
#
# RAM/ROM/Flash chip drivers
#
CONFIG_MTD_CFI=y
# CONFIG_MTD_JEDECPROBE is not set
CONFIG_MTD_GEN_PROBE=y
# CONFIG_MTD_CFI_ADV_OPTIONS is not set
CONFIG_MTD_MAP_BANK_WIDTH_1=y
CONFIG_MTD_MAP_BANK_WIDTH_2=y
CONFIG_MTD_MAP_BANK_WIDTH_4=y
# CONFIG_MTD_MAP_BANK_WIDTH_8 is not set
# CONFIG_MTD_MAP_BANK_WIDTH_16 is not set
# CONFIG_MTD_MAP_BANK_WIDTH_32 is not set
CONFIG_MTD_CFI_I1=y
CONFIG_MTD_CFI_I2=y
# CONFIG_MTD_CFI_I4 is not set
# CONFIG_MTD_CFI_I8 is not set
CONFIG_MTD_CFI_INTELEXT=y
# CONFIG_MTD_CFI_AMDSTD is not set
# CONFIG_MTD_CFI_STAA is not set
CONFIG_MTD_CFI_UTIL=y
# CONFIG_MTD_RAM is not set
# CONFIG_MTD_ROM is not set
# CONFIG_MTD_ABSENT is not set
#
# Mapping drivers for chip access
#
# CONFIG_MTD_COMPLEX_MAPPINGS is not set
# CONFIG_MTD_PHYSMAP is not set
# CONFIG_MTD_ARM_INTEGRATOR is not set
# CONFIG_MTD_OMAP_NOR is not set
# CONFIG_MTD_PLATRAM is not set
#
# Self-contained MTD device drivers
#
# CONFIG_MTD_SLRAM is not set
# CONFIG_MTD_PHRAM is not set
# CONFIG_MTD_MTDRAM is not set
# CONFIG_MTD_BLOCK2MTD is not set
#
# Disk-On-Chip Device Drivers
#
# CONFIG_MTD_DOC2000 is not set
# CONFIG_MTD_DOC2001 is not set
# CONFIG_MTD_DOC2001PLUS is not set
# CONFIG_MTD_NAND is not set
CONFIG_MTD_ONENAND=y
CONFIG_MTD_ONENAND_VERIFY_WRITE=y
# CONFIG_MTD_ONENAND_GENERIC is not set
CONFIG_MTD_ONENAND_OMAP2=y
# CONFIG_MTD_ONENAND_OTP is not set
# CONFIG_MTD_ONENAND_2X_PROGRAM is not set
# CONFIG_MTD_ONENAND_SIM is not set
#
# UBI - Unsorted block images
#
# CONFIG_MTD_UBI is not set
# CONFIG_PARPORT is not set
CONFIG_BLK_DEV=y
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=y
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=16384
# CONFIG_BLK_DEV_XIP is not set
# CONFIG_CDROM_PKTCDVD is not set
# CONFIG_MISC_DEVICES is not set
CONFIG_HAVE_IDE=y
# CONFIG_IDE is not set
#
# SCSI device support
#
# CONFIG_RAID_ATTRS is not set
# CONFIG_SCSI is not set
# CONFIG_SCSI_DMA is not set
# CONFIG_SCSI_NETLINK is not set
# CONFIG_ATA is not set
# CONFIG_MD is not set
#
# Input device support
#
CONFIG_INPUT=y
# CONFIG_INPUT_FF_MEMLESS is not set
# CONFIG_INPUT_POLLDEV is not set
#
# Userland interfaces
#
# CONFIG_INPUT_MOUSEDEV is not set
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_EVBUG is not set
#
# Input Device Drivers
#
# CONFIG_INPUT_KEYBOARD is not set
# CONFIG_INPUT_MOUSE is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TABLET is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set
#
# Hardware I/O ports
#
# CONFIG_SERIO is not set
# CONFIG_GAMEPORT is not set
#
# Character devices
#
# CONFIG_VT is not set
CONFIG_DEVKMEM=y
# CONFIG_SERIAL_NONSTANDARD is not set
#
# Serial drivers
#
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_SERIAL_8250_NR_UARTS=32
CONFIG_SERIAL_8250_RUNTIME_UARTS=4
CONFIG_SERIAL_8250_EXTENDED=y
CONFIG_SERIAL_8250_MANY_PORTS=y
CONFIG_SERIAL_8250_SHARE_IRQ=y
CONFIG_SERIAL_8250_DETECT_IRQ=y
CONFIG_SERIAL_8250_RSA=y
#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_UNIX98_PTYS=y
# CONFIG_LEGACY_PTYS is not set
# CONFIG_IPMI_HANDLER is not set
CONFIG_HW_RANDOM=y
# CONFIG_NVRAM is not set
# CONFIG_R3964 is not set
# CONFIG_RAW_DRIVER is not set
# CONFIG_TCG_TPM is not set
# CONFIG_I2C is not set
# CONFIG_SPI is not set
CONFIG_ARCH_REQUIRE_GPIOLIB=y
CONFIG_GPIOLIB=y
# CONFIG_DEBUG_GPIO is not set
# CONFIG_GPIO_SYSFS is not set
#
# I2C GPIO expanders:
#
#
# PCI GPIO expanders:
#
#
# SPI GPIO expanders:
#
# CONFIG_W1 is not set
# CONFIG_POWER_SUPPLY is not set
# CONFIG_HWMON is not set
# CONFIG_WATCHDOG is not set
#
# Sonics Silicon Backplane
#
CONFIG_SSB_POSSIBLE=y
# CONFIG_SSB is not set
#
# Multifunction device drivers
#
# CONFIG_MFD_CORE is not set
# CONFIG_MFD_SM501 is not set
# CONFIG_MFD_ASIC3 is not set
# CONFIG_HTC_EGPIO is not set
# CONFIG_HTC_PASIC3 is not set
# CONFIG_MFD_TMIO is not set
# CONFIG_MFD_T7L66XB is not set
# CONFIG_MFD_TC6387XB is not set
# CONFIG_MFD_TC6393XB is not set
#
# Multimedia devices
#
#
# Multimedia core support
#
# CONFIG_VIDEO_DEV is not set
# CONFIG_VIDEO_MEDIA is not set
#
# Multimedia drivers
#
# CONFIG_DAB is not set
#
# Graphics support
#
# CONFIG_VGASTATE is not set
# CONFIG_VIDEO_OUTPUT_CONTROL is not set
# CONFIG_FB is not set
# CONFIG_BACKLIGHT_LCD_SUPPORT is not set
#
# Display device support
#
# CONFIG_DISPLAY_SUPPORT is not set
# CONFIG_SOUND is not set
# CONFIG_HID_SUPPORT is not set
# CONFIG_USB_SUPPORT is not set
# CONFIG_MMC is not set
# CONFIG_NEW_LEDS is not set
CONFIG_RTC_LIB=y
# CONFIG_RTC_CLASS is not set
# CONFIG_DMADEVICES is not set
#
# Voltage and Current regulators
#
# CONFIG_REGULATOR is not set
# CONFIG_REGULATOR_FIXED_VOLTAGE is not set
# CONFIG_REGULATOR_VIRTUAL_CONSUMER is not set
# CONFIG_REGULATOR_BQ24022 is not set
# CONFIG_UIO is not set
#
# CBUS support
#
# CONFIG_CBUS is not set
#
# File systems
#
CONFIG_EXT2_FS=y
# CONFIG_EXT2_FS_XATTR is not set
# CONFIG_EXT2_FS_XIP is not set
CONFIG_EXT3_FS=y
# CONFIG_EXT3_FS_XATTR is not set
# CONFIG_EXT4DEV_FS is not set
CONFIG_JBD=y
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
# CONFIG_FS_POSIX_ACL is not set
# CONFIG_XFS_FS is not set
CONFIG_DNOTIFY=y
CONFIG_INOTIFY=y
CONFIG_INOTIFY_USER=y
CONFIG_QUOTA=y
CONFIG_PRINT_QUOTA_WARNING=y
# CONFIG_QFMT_V1 is not set
CONFIG_QFMT_V2=y
CONFIG_QUOTACTL=y
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set
# CONFIG_FUSE_FS is not set
#
# CD-ROM/DVD Filesystems
#
# CONFIG_ISO9660_FS is not set
# CONFIG_UDF_FS is not set
#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_VFAT_FS=y
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
# CONFIG_NTFS_FS is not set
#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_SYSCTL=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
# CONFIG_TMPFS_POSIX_ACL is not set
# CONFIG_HUGETLB_PAGE is not set
# CONFIG_CONFIGFS_FS is not set
#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
CONFIG_JFFS2_FS=y
CONFIG_JFFS2_FS_DEBUG=0
CONFIG_JFFS2_FS_WRITEBUFFER=y
# CONFIG_JFFS2_FS_WBUF_VERIFY is not set
# CONFIG_JFFS2_SUMMARY is not set
# CONFIG_JFFS2_FS_XATTR is not set
CONFIG_JFFS2_COMPRESSION_OPTIONS=y
CONFIG_JFFS2_ZLIB=y
# CONFIG_JFFS2_LZO is not set
CONFIG_JFFS2_RTIME=y
# CONFIG_JFFS2_RUBIN is not set
# CONFIG_JFFS2_CMODE_NONE is not set
CONFIG_JFFS2_CMODE_PRIORITY=y
# CONFIG_JFFS2_CMODE_SIZE is not set
# CONFIG_JFFS2_CMODE_FAVOURLZO is not set
# CONFIG_CRAMFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_OMFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set
#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
# CONFIG_ACORN_PARTITION is not set
# CONFIG_OSF_PARTITION is not set
# CONFIG_AMIGA_PARTITION is not set
# CONFIG_ATARI_PARTITION is not set
# CONFIG_MAC_PARTITION is not set
CONFIG_MSDOS_PARTITION=y
# CONFIG_BSD_DISKLABEL is not set
# CONFIG_MINIX_SUBPARTITION is not set
# CONFIG_SOLARIS_X86_PARTITION is not set
# CONFIG_UNIXWARE_DISKLABEL is not set
# CONFIG_LDM_PARTITION is not set
# CONFIG_SGI_PARTITION is not set
# CONFIG_ULTRIX_PARTITION is not set
# CONFIG_SUN_PARTITION is not set
# CONFIG_KARMA_PARTITION is not set
# CONFIG_EFI_PARTITION is not set
# CONFIG_SYSV68_PARTITION is not set
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=y
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
# CONFIG_NLS_ASCII is not set
CONFIG_NLS_ISO8859_1=y
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
# CONFIG_NLS_ISO8859_15 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
# CONFIG_NLS_UTF8 is not set
#
# Kernel hacking
#
# CONFIG_PRINTK_TIME is not set
CONFIG_ENABLE_WARN_DEPRECATED=y
CONFIG_ENABLE_MUST_CHECK=y
CONFIG_FRAME_WARN=1024
CONFIG_MAGIC_SYSRQ=y
# CONFIG_UNUSED_SYMBOLS is not set
# CONFIG_DEBUG_FS is not set
# CONFIG_HEADERS_CHECK is not set
CONFIG_DEBUG_KERNEL=y
# CONFIG_DEBUG_SHIRQ is not set
CONFIG_DETECT_SOFTLOCKUP=y
# CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC is not set
CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC_VALUE=0
# CONFIG_SCHED_DEBUG is not set
# CONFIG_SCHEDSTATS is not set
# CONFIG_TIMER_STATS is not set
# CONFIG_DEBUG_OBJECTS is not set
# CONFIG_DEBUG_SLAB is not set
# CONFIG_DEBUG_RT_MUTEXES is not set
# CONFIG_RT_MUTEX_TESTER is not set
# CONFIG_DEBUG_SPINLOCK is not set
CONFIG_DEBUG_MUTEXES=y
# CONFIG_DEBUG_LOCK_ALLOC is not set
# CONFIG_PROVE_LOCKING is not set
# CONFIG_LOCK_STAT is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set
# CONFIG_DEBUG_KOBJECT is not set
# CONFIG_DEBUG_BUGVERBOSE is not set
CONFIG_DEBUG_INFO=y
# CONFIG_DEBUG_VM is not set
# CONFIG_DEBUG_WRITECOUNT is not set
# CONFIG_DEBUG_MEMORY_INIT is not set
# CONFIG_DEBUG_LIST is not set
# CONFIG_DEBUG_SG is not set
CONFIG_FRAME_POINTER=y
# CONFIG_BOOT_PRINTK_DELAY is not set
# CONFIG_RCU_TORTURE_TEST is not set
# CONFIG_BACKTRACE_SELF_TEST is not set
# CONFIG_FAULT_INJECTION is not set
# CONFIG_LATENCYTOP is not set
CONFIG_HAVE_FTRACE=y
CONFIG_HAVE_DYNAMIC_FTRACE=y
# CONFIG_FTRACE is not set
# CONFIG_IRQSOFF_TRACER is not set
# CONFIG_SCHED_TRACER is not set
# CONFIG_CONTEXT_SWITCH_TRACER is not set
# CONFIG_SAMPLES is not set
CONFIG_HAVE_ARCH_KGDB=y
# CONFIG_KGDB is not set
# CONFIG_DEBUG_USER is not set
# CONFIG_DEBUG_ERRORS is not set
# CONFIG_DEBUG_STACK_USAGE is not set
CONFIG_DEBUG_LL=y
# CONFIG_DEBUG_ICEDCC is not set
#
# Security options
#
# CONFIG_KEYS is not set
# CONFIG_SECURITY is not set
# CONFIG_SECURITY_FILE_CAPABILITIES is not set
CONFIG_CRYPTO=y
#
# Crypto core or helper
#
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_BLKCIPHER=y
CONFIG_CRYPTO_MANAGER=y
# CONFIG_CRYPTO_GF128MUL is not set
# CONFIG_CRYPTO_NULL is not set
# CONFIG_CRYPTO_CRYPTD is not set
# CONFIG_CRYPTO_AUTHENC is not set
# CONFIG_CRYPTO_TEST is not set
#
# Authenticated Encryption with Associated Data
#
# CONFIG_CRYPTO_CCM is not set
# CONFIG_CRYPTO_GCM is not set
# CONFIG_CRYPTO_SEQIV is not set
#
# Block modes
#
CONFIG_CRYPTO_CBC=y
# CONFIG_CRYPTO_CTR is not set
# CONFIG_CRYPTO_CTS is not set
CONFIG_CRYPTO_ECB=m
# CONFIG_CRYPTO_LRW is not set
CONFIG_CRYPTO_PCBC=m
# CONFIG_CRYPTO_XTS is not set
#
# Hash modes
#
# CONFIG_CRYPTO_HMAC is not set
# CONFIG_CRYPTO_XCBC is not set
#
# Digest
#
# CONFIG_CRYPTO_CRC32C is not set
# CONFIG_CRYPTO_MD4 is not set
CONFIG_CRYPTO_MD5=y
# CONFIG_CRYPTO_MICHAEL_MIC is not set
# CONFIG_CRYPTO_RMD128 is not set
# CONFIG_CRYPTO_RMD160 is not set
# CONFIG_CRYPTO_RMD256 is not set
# CONFIG_CRYPTO_RMD320 is not set
# CONFIG_CRYPTO_SHA1 is not set
# CONFIG_CRYPTO_SHA256 is not set
# CONFIG_CRYPTO_SHA512 is not set
# CONFIG_CRYPTO_TGR192 is not set
# CONFIG_CRYPTO_WP512 is not set
#
# Ciphers
#
# CONFIG_CRYPTO_AES is not set
# CONFIG_CRYPTO_ANUBIS is not set
# CONFIG_CRYPTO_ARC4 is not set
# CONFIG_CRYPTO_BLOWFISH is not set
# CONFIG_CRYPTO_CAMELLIA is not set
# CONFIG_CRYPTO_CAST5 is not set
# CONFIG_CRYPTO_CAST6 is not set
CONFIG_CRYPTO_DES=y
# CONFIG_CRYPTO_FCRYPT is not set
# CONFIG_CRYPTO_KHAZAD is not set
# CONFIG_CRYPTO_SALSA20 is not set
# CONFIG_CRYPTO_SEED is not set
# CONFIG_CRYPTO_SERPENT is not set
# CONFIG_CRYPTO_TEA is not set
# CONFIG_CRYPTO_TWOFISH is not set
#
# Compression
#
# CONFIG_CRYPTO_DEFLATE is not set
# CONFIG_CRYPTO_LZO is not set
CONFIG_CRYPTO_HW=y
#
# Library routines
#
CONFIG_BITREVERSE=y
# CONFIG_GENERIC_FIND_FIRST_BIT is not set
# CONFIG_GENERIC_FIND_NEXT_BIT is not set
CONFIG_CRC_CCITT=y
# CONFIG_CRC16 is not set
# CONFIG_CRC_T10DIF is not set
# CONFIG_CRC_ITU_T is not set
CONFIG_CRC32=y
# CONFIG_CRC7 is not set
CONFIG_LIBCRC32C=y
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=y
CONFIG_PLIST=y
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT=y
CONFIG_HAS_DMA=y
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [ANNOUNCE] new PM branch: pm-20081119
2008-11-21 15:46 ` Premi, Sanjeev
@ 2008-11-21 16:05 ` Kevin Hilman
2008-11-23 7:57 ` Sriram V
0 siblings, 1 reply; 19+ messages in thread
From: Kevin Hilman @ 2008-11-21 16:05 UTC (permalink / raw)
To: Premi, Sanjeev; +Cc: Peter Reid, linux-omap@vger.kernel.org
"Premi, Sanjeev" <premi@ti.com> writes:
>> -----Original Message-----
>> From: Kevin Hilman [mailto:khilman@deeprootsystems.com]
>> Sent: Thursday, November 20, 2008 11:10 PM
>> To: Premi, Sanjeev
>> Cc: Peter Reid; linux-omap@vger.kernel.org
>> Subject: Re: [ANNOUNCE] new PM branch: pm-20081119
>>
>> "Premi, Sanjeev" <premi@ti.com> writes:
>>
>> > These are my observations on OMAP3EVM:
>> >
>> > 1) Very frequently I see these messages:
>> >
>> > <4>__ratelimit: 6736 callbacks suppressed
>> > __ratelimit: 6736 callbacks suppressed <3>omapfb omapfb: irq error
>> > status 00c2 omapfb omapfb: irq error status 00c2 <3>omapfb
>> omapfb: irq
>> > error status 0060 omapfb omapfb: irq error status 0060 <3>omapfb
>> > omapfb: irq error status 00c2 omapfb omapfb: irq error status 00c2
>> > <3>omapfb omapfb: irq error status 0060 omapfb omapfb: irq error
>> > status 0060 <3>omapfb omapfb: irq error status 00e2 omapfb
>> omapfb: irq
>> > error status 00e2 <3>omapfb omapfb: irq error status 00c2 omapfb
>> > omapfb: irq error status 00c2 <3>omapfb omapfb: irq error
>> status 0060
>> > omapfb omapfb: irq error status 0060 <3>omapfb omapfb: irq error
>> > status 00e2 omapfb omapfb: irq error status 00e2 <3>omapfb
>> omapfb: irq
>> > error status 00c2 omapfb omapfb: irq error status 00c2 <3>omapfb
>> > omapfb: irq error status 0060 omapfb omapfb: irq error status 0060
>>
>> Sanjeev,
>>
>> For starters can you try with a minimal kernel (no drivers,
>> no framebuffer, etc.)
>>
>> The first goal is to hit retention and off with no drivers
>> than start moving out to address driver issues from there.
>>
>> Kevin
>>
>
> Here is what I was able to see with the minimal config (attached).
>
> [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.01 seconds) (elapsed 0.01 seconds) done.done.
>
> Suspending console(s) (use no_console_suspend to debug)
> Suspending console(s) (use no_console_suspend to debug)
>
> <snip>un-printable characters<snip>
>
> Powerdomain (per_pwrdm) didn't enter target state 1
> Could not enter target state in pm_suspend
> Restarting tasks ... Restarting tasks ... done.
> done.
This is what I see on Beagle as well (PER is not entering retention.)
At this point, the current PM debug code doesn't help further in
determining exactly why a powerdomain did not hit its target state.
Some device in the domain may still have its clocks enabled, or its
idle state not set correctly. Or, a given module may have been
initialized by the bootloader in a way which prevents it from going
idle.
We need some improved PM debug capabilities in the kernel to pinpoint
exactly the module that is causing the problem.
Kevin
> Haven't had chance to debug further. Any additional driver added repeats the same behavior. I am not yet certain if the PM_DEBUG has any role. Haven't been able to try few combinations that I wanted to.
>
> Best regards,
> Sanjeev
>
>> > 2) Also:
>> > # 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.00 seconds) (elapsed 0.00
>> seconds) done.
>> > done.
>> >
>> > Suspending console(s) (use no_console_suspend to debug) Suspending
>> > console(s) (use no_console_suspend to debug) <3>omapfb
>> omapfb: timeout
>> > waiting for FRAME DONE
>> >
>> > However, I the "resume" doesn't happen.
>> > Trying to debug further.
>> >
>> > Best regards,
>> > Sanjeev
>> >
>> >> On Thu, Nov 20, 2008 at 6:23 AM, Kevin Hilman
>> >> <khilman@deeprootsystems.com> wrote:
>> >> > Hello,
>> >> >
>> >> > A new PM branch is available named pm-20081119.
>> >> >
>> >> > This is mostly a new set of patches on top of the previous
>> >> PM branch,
>> >> > rather than a rebase. We finally found the root cause
>> of some DPLL
>> >> > relocking bugs. Special thanks to Paul Walmsley and Tero
>> >> Kristo for
>> >> > debugging and fixing this problem. Now the DPLL fix that
>> >> was reverted
>> >> > in the previous PM branch is re-applied as well as some
>> >> fixes on top
>> >> > of it. It also has some additional UART fixes, so I
>> think the UART
>> >> > idle work is ready to go to Tony. Special thanks to
>> Jouni Hogander
>> >> > for the extra testing and fixes here.
>> >> >
>> >> > The shortlog is below[1] and the root of the tree is still
>> >> > v2.6.27-omap1 + T2 power patches from Peter.
>> >> >
>> >> > This has primarily been tested on custom HW since I'm
>> >> _still_ waiting
>> >> > for my SDP to arrive. I have boot tested on Beagle, but I
>> >> think there
>> >> > are still some problems with ES2 silicon. On my ES2
>> >> Beagle, neither
>> >> > DSS or IVA will leave the ON state, even when all clocks
>> in their
>> >> > powerdomains are off. I have not debugged this further yet.
>> >> >
>> >> > Functionally, this tree is in pretty good shape, so I
>> will do some
>> >> > bugfixes here when necessary, but will now spent some time
>> >> focusing on
>> >> > getting the patches in this branch merged into linux-omap.
>> >> >
>> >> > Kevin
>> >> >
>> >> >
>> >> > [1] git shortlog:
>> >> >
>> >> > Amit Kucheria (2):
>> >> > OMAP: PM: Typo fix for clock_allow_idle
>> >> > HSMMC: Make driver support dynamic idle
>> >> >
>> >> > Jouni Hogander (11):
>> >> > OMAP3: PM: Use pwrdm_set_next_pwrst instead of
>> >> set_pwrdm_state in idle loop
>> >> > OMAP3: Do not set mpu, core, neon states if cpuidle is used
>> >> > OMAP3: PM: Do not set next states sw to control those
>> >> is available
>> >> > OMAP3: PM: Always return value in pwrdms_setup
>> >> > OMAP3: PM: Fix wrong sequence in suspend.
>> >> > OMAP3: UART: Make sure that uart clocks are enabled
>> when needed
>> >> > OMAP3: PM: Check in set_pwrdm_state that target state
>> >> is supported by pwrdm v2
>> >> > 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
>> >> > OMAP: MCSPI: Enable mcspi wake-up
>> >> >
>> >> > Kalle Jokiniemi (4):
>> >> > 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)
>> >> > OMAP3: I2C: Enable I2C wakeups
>> >> >
>> >> > Kevin Hilman (16):
>> >> > OMAP3: PM: Add wake-up bit defintiions for CONTROL_PADCONF_X
>> >> > OMAP3: PM: Allow UARTs to be unclocked when inactive
>> >> > 8250: Allow platform to register PM hook
>> >> > 8250: when waking, PM hook should be called before
>> >> accessing port
>> >> > OMAP3: PM: UART: Add 8250 UART PM hook for suspend/resume
>> >> > OMAP3: PM: UART save/restore support for OFF-mode
>> >> > OMAP2/3: HSMMC: Ensure HSMMC is fully reset on boot
>> >> > 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
>> >> > Revert "OMAP3 clock: fix non-CORE DPLL rate assignment bugs"
>> >> > Revert "OMAP3: PM: Do not set next states sw to
>> >> control those is available"
>> >> > Revert "OMAP3: Do not set mpu, core, neon states if
>> >> cpuidle is used"
>> >> > OMAP: PM: UART: fix can_sleep hook to return correct value
>> >> > OMAP: PM: UART: Only disable clocks in prepare-idle hook
>> >> > OMAP3: PM: Check for UART wakeups in 'resume_idle' hook
>> >> >
>> >> > Paul Walmsley (14):
>> >> > 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
>> >> > OMAP3 clock: fix non-CORE DPLL rate assignment bugs
>> >> > OMAP3 powerdomains: remove RET from SGX power states list
>> >> > OMAP3 powerdomains: remove RET from SGX power states list
>> >> > OMAP3 clock: remove unnecessary dpll_data dereferences
>> >> > OMAP3 clock: optimize DPLL rate rounding algorithm
>> >> > OMAP3 clock: avoid invalid FREQSEL values during DPLL
>> >> rate rounding
>> >> > OMAP2/3 I2C: reprogram OCP_SYSCONFIG register after reset
>> >> > OMAP: I2C: convert 'rev1' flag to generic 'rev' u8
>> >> >
>> >> > Peter 'p2' De Schrijver (9):
>> >> > 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()
>> >> >
>> >> > Rajendra Nayak (23):
>> >> > 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: PM: CPUidle: Enable Kconfig option for OMAP
>> >> > 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
>> >> >
>> >> > Tero Kristo (13):
>> >> > 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: Fix a bug with noncore dpll rate calculation
>> >> > PM: Added three PLL registers to the PRCM context save
>> >> > PM: OMAP3: Make sure clk_disable_unused() order is correct
>> >> > PM: Changed secure RAM storage size from 0x8000 to 0x803F
>> >> >
>> >> > --
>> >> > 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
>> >>
>> >>
>>
>>
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [ANNOUNCE] new PM branch: pm-20081119
2008-11-21 16:05 ` Kevin Hilman
@ 2008-11-23 7:57 ` Sriram V
2008-11-24 7:32 ` Högander Jouni
0 siblings, 1 reply; 19+ messages in thread
From: Sriram V @ 2008-11-23 7:57 UTC (permalink / raw)
To: Kevin Hilman; +Cc: Premi, Sanjeev, Peter Reid, linux-omap@vger.kernel.org
Kevin,
On Fri, Nov 21, 2008 at 9:35 PM, Kevin Hilman
<khilman@deeprootsystems.com> wrote:
> "Premi, Sanjeev" <premi@ti.com> writes:
>
>>> -----Original Message-----
>>> From: Kevin Hilman [mailto:khilman@deeprootsystems.com]
>>> Sent: Thursday, November 20, 2008 11:10 PM
>>> To: Premi, Sanjeev
>>> Cc: Peter Reid; linux-omap@vger.kernel.org
>>> Subject: Re: [ANNOUNCE] new PM branch: pm-20081119
>>>
>>> "Premi, Sanjeev" <premi@ti.com> writes:
>>>
>>> > These are my observations on OMAP3EVM:
>>> >
>>> > 1) Very frequently I see these messages:
>>> >
>>> > <4>__ratelimit: 6736 callbacks suppressed
>>> > __ratelimit: 6736 callbacks suppressed <3>omapfb omapfb: irq error
>>> > status 00c2 omapfb omapfb: irq error status 00c2 <3>omapfb
>>> omapfb: irq
>>> > error status 0060 omapfb omapfb: irq error status 0060 <3>omapfb
>>> > omapfb: irq error status 00c2 omapfb omapfb: irq error status 00c2
>>> > <3>omapfb omapfb: irq error status 0060 omapfb omapfb: irq error
>>> > status 0060 <3>omapfb omapfb: irq error status 00e2 omapfb
>>> omapfb: irq
>>> > error status 00e2 <3>omapfb omapfb: irq error status 00c2 omapfb
>>> > omapfb: irq error status 00c2 <3>omapfb omapfb: irq error
>>> status 0060
>>> > omapfb omapfb: irq error status 0060 <3>omapfb omapfb: irq error
>>> > status 00e2 omapfb omapfb: irq error status 00e2 <3>omapfb
>>> omapfb: irq
>>> > error status 00c2 omapfb omapfb: irq error status 00c2 <3>omapfb
>>> > omapfb: irq error status 0060 omapfb omapfb: irq error status 0060
>>>
>>> Sanjeev,
>>>
>>> For starters can you try with a minimal kernel (no drivers,
>>> no framebuffer, etc.)
>>>
>>> The first goal is to hit retention and off with no drivers
>>> than start moving out to address driver issues from there.
>>>
>>> Kevin
>>>
>>
>> Here is what I was able to see with the minimal config (attached).
>>
>> [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.01 seconds) (elapsed 0.01 seconds) done.done.
>>
>> Suspending console(s) (use no_console_suspend to debug)
>> Suspending console(s) (use no_console_suspend to debug)
>>
>> <snip>un-printable characters<snip>
>>
>> Powerdomain (per_pwrdm) didn't enter target state 1
>> Could not enter target state in pm_suspend
>> Restarting tasks ... Restarting tasks ... done.
>> done.
>
> This is what I see on Beagle as well (PER is not entering retention.)
>
> At this point, the current PM debug code doesn't help further in
> determining exactly why a powerdomain did not hit its target state.
> Some device in the domain may still have its clocks enabled, or its
> idle state not set correctly. Or, a given module may have been
> initialized by the bootloader in a way which prevents it from going
> idle.
>
True. I have observed on omap3evm with minimum configuration, and
booting out of ramdisk:
with nand booting: only per powerdomain does not enter retention
with mmc boot: core and per dont enter retention
it could do with clocks set the bootloaders that is preventing it from
entering ret/off.
what do you mean by idle state not set correctly? are you referring
to auto-idle bit?
> We need some improved PM debug capabilities in the kernel to pinpoint
> exactly the module that is causing the problem.
>
Apart from PM debug, are you using any other module/methods to debug?
Regards,
sriram
> Kevin
>
>> Haven't had chance to debug further. Any additional driver added repeats the same behavior. I am not yet certain if the PM_DEBUG has any role. Haven't been able to try few combinations that I wanted to.
>>
>> Best regards,
>> Sanjeev
>>
>>> > 2) Also:
>>> > # 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.00 seconds) (elapsed 0.00
>>> seconds) done.
>>> > done.
>>> >
>>> > Suspending console(s) (use no_console_suspend to debug) Suspending
>>> > console(s) (use no_console_suspend to debug) <3>omapfb
>>> omapfb: timeout
>>> > waiting for FRAME DONE
>>> >
>>> > However, I the "resume" doesn't happen.
>>> > Trying to debug further.
>>> >
>>> > Best regards,
>>> > Sanjeev
>>> >
>>> >> On Thu, Nov 20, 2008 at 6:23 AM, Kevin Hilman
>>> >> <khilman@deeprootsystems.com> wrote:
>>> >> > Hello,
>>> >> >
>>> >> > A new PM branch is available named pm-20081119.
>>> >> >
>>> >> > This is mostly a new set of patches on top of the previous
>>> >> PM branch,
>>> >> > rather than a rebase. We finally found the root cause
>>> of some DPLL
>>> >> > relocking bugs. Special thanks to Paul Walmsley and Tero
>>> >> Kristo for
>>> >> > debugging and fixing this problem. Now the DPLL fix that
>>> >> was reverted
>>> >> > in the previous PM branch is re-applied as well as some
>>> >> fixes on top
>>> >> > of it. It also has some additional UART fixes, so I
>>> think the UART
>>> >> > idle work is ready to go to Tony. Special thanks to
>>> Jouni Hogander
>>> >> > for the extra testing and fixes here.
>>> >> >
>>> >> > The shortlog is below[1] and the root of the tree is still
>>> >> > v2.6.27-omap1 + T2 power patches from Peter.
>>> >> >
>>> >> > This has primarily been tested on custom HW since I'm
>>> >> _still_ waiting
>>> >> > for my SDP to arrive. I have boot tested on Beagle, but I
>>> >> think there
>>> >> > are still some problems with ES2 silicon. On my ES2
>>> >> Beagle, neither
>>> >> > DSS or IVA will leave the ON state, even when all clocks
>>> in their
>>> >> > powerdomains are off. I have not debugged this further yet.
>>> >> >
>>> >> > Functionally, this tree is in pretty good shape, so I
>>> will do some
>>> >> > bugfixes here when necessary, but will now spent some time
>>> >> focusing on
>>> >> > getting the patches in this branch merged into linux-omap.
>>> >> >
>>> >> > Kevin
>>> >> >
>>> >> >
>>> >> > [1] git shortlog:
>>> >> >
>>> >> > Amit Kucheria (2):
>>> >> > OMAP: PM: Typo fix for clock_allow_idle
>>> >> > HSMMC: Make driver support dynamic idle
>>> >> >
>>> >> > Jouni Hogander (11):
>>> >> > OMAP3: PM: Use pwrdm_set_next_pwrst instead of
>>> >> set_pwrdm_state in idle loop
>>> >> > OMAP3: Do not set mpu, core, neon states if cpuidle is used
>>> >> > OMAP3: PM: Do not set next states sw to control those
>>> >> is available
>>> >> > OMAP3: PM: Always return value in pwrdms_setup
>>> >> > OMAP3: PM: Fix wrong sequence in suspend.
>>> >> > OMAP3: UART: Make sure that uart clocks are enabled
>>> when needed
>>> >> > OMAP3: PM: Check in set_pwrdm_state that target state
>>> >> is supported by pwrdm v2
>>> >> > 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
>>> >> > OMAP: MCSPI: Enable mcspi wake-up
>>> >> >
>>> >> > Kalle Jokiniemi (4):
>>> >> > 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)
>>> >> > OMAP3: I2C: Enable I2C wakeups
>>> >> >
>>> >> > Kevin Hilman (16):
>>> >> > OMAP3: PM: Add wake-up bit defintiions for CONTROL_PADCONF_X
>>> >> > OMAP3: PM: Allow UARTs to be unclocked when inactive
>>> >> > 8250: Allow platform to register PM hook
>>> >> > 8250: when waking, PM hook should be called before
>>> >> accessing port
>>> >> > OMAP3: PM: UART: Add 8250 UART PM hook for suspend/resume
>>> >> > OMAP3: PM: UART save/restore support for OFF-mode
>>> >> > OMAP2/3: HSMMC: Ensure HSMMC is fully reset on boot
>>> >> > 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
>>> >> > Revert "OMAP3 clock: fix non-CORE DPLL rate assignment bugs"
>>> >> > Revert "OMAP3: PM: Do not set next states sw to
>>> >> control those is available"
>>> >> > Revert "OMAP3: Do not set mpu, core, neon states if
>>> >> cpuidle is used"
>>> >> > OMAP: PM: UART: fix can_sleep hook to return correct value
>>> >> > OMAP: PM: UART: Only disable clocks in prepare-idle hook
>>> >> > OMAP3: PM: Check for UART wakeups in 'resume_idle' hook
>>> >> >
>>> >> > Paul Walmsley (14):
>>> >> > 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
>>> >> > OMAP3 clock: fix non-CORE DPLL rate assignment bugs
>>> >> > OMAP3 powerdomains: remove RET from SGX power states list
>>> >> > OMAP3 powerdomains: remove RET from SGX power states list
>>> >> > OMAP3 clock: remove unnecessary dpll_data dereferences
>>> >> > OMAP3 clock: optimize DPLL rate rounding algorithm
>>> >> > OMAP3 clock: avoid invalid FREQSEL values during DPLL
>>> >> rate rounding
>>> >> > OMAP2/3 I2C: reprogram OCP_SYSCONFIG register after reset
>>> >> > OMAP: I2C: convert 'rev1' flag to generic 'rev' u8
>>> >> >
>>> >> > Peter 'p2' De Schrijver (9):
>>> >> > 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()
>>> >> >
>>> >> > Rajendra Nayak (23):
>>> >> > 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: PM: CPUidle: Enable Kconfig option for OMAP
>>> >> > 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
>>> >> >
>>> >> > Tero Kristo (13):
>>> >> > 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: Fix a bug with noncore dpll rate calculation
>>> >> > PM: Added three PLL registers to the PRCM context save
>>> >> > PM: OMAP3: Make sure clk_disable_unused() order is correct
>>> >> > PM: Changed secure RAM storage size from 0x8000 to 0x803F
>>> >> >
>>> >> > --
>>> >> > 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
>>> >>
>>> >>
>>>
>>>
> --
> 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
>
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [ANNOUNCE] new PM branch: pm-20081119
2008-11-23 7:57 ` Sriram V
@ 2008-11-24 7:32 ` Högander Jouni
2008-12-01 16:22 ` Sriram V
0 siblings, 1 reply; 19+ messages in thread
From: Högander Jouni @ 2008-11-24 7:32 UTC (permalink / raw)
To: ext Sriram V
Cc: Kevin Hilman, Premi, Sanjeev, Peter Reid,
linux-omap@vger.kernel.org
"ext Sriram V" <vshrirama@gmail.com> writes:
> Kevin,
>
> On Fri, Nov 21, 2008 at 9:35 PM, Kevin Hilman
> <khilman@deeprootsystems.com> wrote:
>> "Premi, Sanjeev" <premi@ti.com> writes:
>>
>>>> -----Original Message-----
>>>> From: Kevin Hilman [mailto:khilman@deeprootsystems.com]
>>>> Sent: Thursday, November 20, 2008 11:10 PM
>>>> To: Premi, Sanjeev
>>>> Cc: Peter Reid; linux-omap@vger.kernel.org
>>>> Subject: Re: [ANNOUNCE] new PM branch: pm-20081119
>>>>
>>>> "Premi, Sanjeev" <premi@ti.com> writes:
>>>>
>>>> > These are my observations on OMAP3EVM:
>>>> >
>>>> > 1) Very frequently I see these messages:
>>>> >
>>>> > <4>__ratelimit: 6736 callbacks suppressed
>>>> > __ratelimit: 6736 callbacks suppressed <3>omapfb omapfb: irq error
>>>> > status 00c2 omapfb omapfb: irq error status 00c2 <3>omapfb
>>>> omapfb: irq
>>>> > error status 0060 omapfb omapfb: irq error status 0060 <3>omapfb
>>>> > omapfb: irq error status 00c2 omapfb omapfb: irq error status 00c2
>>>> > <3>omapfb omapfb: irq error status 0060 omapfb omapfb: irq error
>>>> > status 0060 <3>omapfb omapfb: irq error status 00e2 omapfb
>>>> omapfb: irq
>>>> > error status 00e2 <3>omapfb omapfb: irq error status 00c2 omapfb
>>>> > omapfb: irq error status 00c2 <3>omapfb omapfb: irq error
>>>> status 0060
>>>> > omapfb omapfb: irq error status 0060 <3>omapfb omapfb: irq error
>>>> > status 00e2 omapfb omapfb: irq error status 00e2 <3>omapfb
>>>> omapfb: irq
>>>> > error status 00c2 omapfb omapfb: irq error status 00c2 <3>omapfb
>>>> > omapfb: irq error status 0060 omapfb omapfb: irq error status 0060
>>>>
>>>> Sanjeev,
>>>>
>>>> For starters can you try with a minimal kernel (no drivers,
>>>> no framebuffer, etc.)
>>>>
>>>> The first goal is to hit retention and off with no drivers
>>>> than start moving out to address driver issues from there.
>>>>
>>>> Kevin
>>>>
>>>
>>> Here is what I was able to see with the minimal config (attached).
>>>
>>> [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.01 seconds) (elapsed 0.01 seconds) done.done.
>>>
>>> Suspending console(s) (use no_console_suspend to debug)
>>> Suspending console(s) (use no_console_suspend to debug)
>>>
>>> <snip>un-printable characters<snip>
>>>
>>> Powerdomain (per_pwrdm) didn't enter target state 1
>>> Could not enter target state in pm_suspend
>>> Restarting tasks ... Restarting tasks ... done.
>>> done.
>>
>> This is what I see on Beagle as well (PER is not entering retention.)
>>
>
>> At this point, the current PM debug code doesn't help further in
>> determining exactly why a powerdomain did not hit its target state.
>> Some device in the domain may still have its clocks enabled, or its
>> idle state not set correctly. Or, a given module may have been
>> initialized by the bootloader in a way which prevents it from going
>> idle.
>>
>
> True. I have observed on omap3evm with minimum configuration, and
> booting out of ramdisk:
> with nand booting: only per powerdomain does not enter retention
> with mmc boot: core and per dont enter retention
>
> it could do with clocks set the bootloaders that is preventing it from
> entering ret/off.
To tackle this you should have CONFIG_OMAP_RESET_CLOCKS enabled in
config.
> what do you mean by idle state not set correctly? are you referring
> to auto-idle bit?
Not sure what Kevin meant there, but if the problem was in the
autoidle bit in *_SYSCONFIG, I would expect also CORE pwrdm to
fail. Anyway it's also worth of checking the statuses of PER modules
*_SYSCONFIG registers.
>
>
>> We need some improved PM debug capabilities in the kernel to pinpoint
>> exactly the module that is causing the problem.
>>
>
> Apart from PM debug, are you using any other module/methods to
> debug?
State of PRCM registers can be quickly checked from
/sys/kernel/debug/pm_debug/registers/current (assuming you have mount
debugfs in /sys/kernel/debug and PM_DEBUG is enabled in config).
--
Jouni Högander
--
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
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [ANNOUNCE] new PM branch: pm-20081119
2008-11-24 7:32 ` Högander Jouni
@ 2008-12-01 16:22 ` Sriram V
2008-12-02 5:17 ` Kevin Hilman
0 siblings, 1 reply; 19+ messages in thread
From: Sriram V @ 2008-12-01 16:22 UTC (permalink / raw)
To: Högander Jouni
Cc: Kevin Hilman, Premi, Sanjeev, Peter Reid,
linux-omap@vger.kernel.org
Hi,
On OMAP3EVM, with a minimum config. All domains are hitting RET.
Only SGX domain hits OFF. No other domain hits OFF.
I tried doing a echo 1 > /sys/power/enable_off_mode.
Powertop shows Sleep States upto C4. Has anyone seen Sleep States
upto C6 with this kernel?
dont know why MPU/CORE not hitting OFF even though the clocks are off.
With the most of the PM support (Suspend/Resume, Power Domains, CPU
Idle) up with minimum config.
What else remains to be supported?
CPU freq, constraint frame work and individual drivers support to
enable power domain transition to OFF/RET?
Is this all? do these cover all the pm features of omap3?
Is the constraints framework embedded within the TI SRF or is it
independently usable?
I havent seen too many drivers which specify constraints in the TI
sources though.
Regards,
sriram
On Mon, Nov 24, 2008 at 1:02 PM, Högander Jouni
<jouni.hogander@nokia.com> wrote:
> "ext Sriram V" <vshrirama@gmail.com> writes:
>
>> Kevin,
>>
>> On Fri, Nov 21, 2008 at 9:35 PM, Kevin Hilman
>> <khilman@deeprootsystems.com> wrote:
>>> "Premi, Sanjeev" <premi@ti.com> writes:
>>>
>>>>> -----Original Message-----
>>>>> From: Kevin Hilman [mailto:khilman@deeprootsystems.com]
>>>>> Sent: Thursday, November 20, 2008 11:10 PM
>>>>> To: Premi, Sanjeev
>>>>> Cc: Peter Reid; linux-omap@vger.kernel.org
>>>>> Subject: Re: [ANNOUNCE] new PM branch: pm-20081119
>>>>>
>>>>> "Premi, Sanjeev" <premi@ti.com> writes:
>>>>>
>>>>> > These are my observations on OMAP3EVM:
>>>>> >
>>>>> > 1) Very frequently I see these messages:
>>>>> >
>>>>> > <4>__ratelimit: 6736 callbacks suppressed
>>>>> > __ratelimit: 6736 callbacks suppressed <3>omapfb omapfb: irq error
>>>>> > status 00c2 omapfb omapfb: irq error status 00c2 <3>omapfb
>>>>> omapfb: irq
>>>>> > error status 0060 omapfb omapfb: irq error status 0060 <3>omapfb
>>>>> > omapfb: irq error status 00c2 omapfb omapfb: irq error status 00c2
>>>>> > <3>omapfb omapfb: irq error status 0060 omapfb omapfb: irq error
>>>>> > status 0060 <3>omapfb omapfb: irq error status 00e2 omapfb
>>>>> omapfb: irq
>>>>> > error status 00e2 <3>omapfb omapfb: irq error status 00c2 omapfb
>>>>> > omapfb: irq error status 00c2 <3>omapfb omapfb: irq error
>>>>> status 0060
>>>>> > omapfb omapfb: irq error status 0060 <3>omapfb omapfb: irq error
>>>>> > status 00e2 omapfb omapfb: irq error status 00e2 <3>omapfb
>>>>> omapfb: irq
>>>>> > error status 00c2 omapfb omapfb: irq error status 00c2 <3>omapfb
>>>>> > omapfb: irq error status 0060 omapfb omapfb: irq error status 0060
>>>>>
>>>>> Sanjeev,
>>>>>
>>>>> For starters can you try with a minimal kernel (no drivers,
>>>>> no framebuffer, etc.)
>>>>>
>>>>> The first goal is to hit retention and off with no drivers
>>>>> than start moving out to address driver issues from there.
>>>>>
>>>>> Kevin
>>>>>
>>>>
>>>> Here is what I was able to see with the minimal config (attached).
>>>>
>>>> [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.01 seconds) (elapsed 0.01 seconds) done.done.
>>>>
>>>> Suspending console(s) (use no_console_suspend to debug)
>>>> Suspending console(s) (use no_console_suspend to debug)
>>>>
>>>> <snip>un-printable characters<snip>
>>>>
>>>> Powerdomain (per_pwrdm) didn't enter target state 1
>>>> Could not enter target state in pm_suspend
>>>> Restarting tasks ... Restarting tasks ... done.
>>>> done.
>>>
>>> This is what I see on Beagle as well (PER is not entering retention.)
>>>
>>
>>> At this point, the current PM debug code doesn't help further in
>>> determining exactly why a powerdomain did not hit its target state.
>>> Some device in the domain may still have its clocks enabled, or its
>>> idle state not set correctly. Or, a given module may have been
>>> initialized by the bootloader in a way which prevents it from going
>>> idle.
>>>
>>
>> True. I have observed on omap3evm with minimum configuration, and
>> booting out of ramdisk:
>> with nand booting: only per powerdomain does not enter retention
>> with mmc boot: core and per dont enter retention
>>
>> it could do with clocks set the bootloaders that is preventing it from
>> entering ret/off.
>
> To tackle this you should have CONFIG_OMAP_RESET_CLOCKS enabled in
> config.
>
>> what do you mean by idle state not set correctly? are you referring
>> to auto-idle bit?
>
> Not sure what Kevin meant there, but if the problem was in the
> autoidle bit in *_SYSCONFIG, I would expect also CORE pwrdm to
> fail. Anyway it's also worth of checking the statuses of PER modules
> *_SYSCONFIG registers.
>
>>
>>
>>> We need some improved PM debug capabilities in the kernel to pinpoint
>>> exactly the module that is causing the problem.
>>>
>>
>> Apart from PM debug, are you using any other module/methods to
>> debug?
>
> State of PRCM registers can be quickly checked from
> /sys/kernel/debug/pm_debug/registers/current (assuming you have mount
> debugfs in /sys/kernel/debug and PM_DEBUG is enabled in config).
>
> --
> Jouni Högander
>
>
--
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
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [ANNOUNCE] new PM branch: pm-20081119
2008-12-01 16:22 ` Sriram V
@ 2008-12-02 5:17 ` Kevin Hilman
2008-12-03 14:23 ` Sriram V
0 siblings, 1 reply; 19+ messages in thread
From: Kevin Hilman @ 2008-12-02 5:17 UTC (permalink / raw)
To: Sriram V
Cc: Högander Jouni, Premi, Sanjeev, Peter Reid,
linux-omap@vger.kernel.org
Sriram V wrote:
> Hi,
> On OMAP3EVM, with a minimum config. All domains are hitting RET.
> Only SGX domain hits OFF. No other domain hits OFF.
Yes, the default boot behavior is to default to RET, but SGX does not
support RET, only ON or OFF, so it goes to OFF.
> I tried doing a echo 1 > /sys/power/enable_off_mode.
After doing this, and then 'echo mem > /sys/power/state' do you see
any other states that have hit OFF in /debug/pm_debug/count?
> Powertop shows Sleep States upto C4. Has anyone seen Sleep States
> upto C6 with this kernel?
Yes, I've seen states up to C6. The only thing preventing deeper states
is application or timer activity not being long enough. What does
powertop list as the primary interrupt or timer sources waking out of idle?
> dont know why MPU/CORE not hitting OFF even though the clocks are off.
It looks like you're primarily testing dynamic idle. Can you check via
/debug/pm_debug/count whether you're hitting OFF in any powerdomains
when going into suspend?
Kevin
> With the most of the PM support (Suspend/Resume, Power Domains, CPU
> Idle) up with minimum config.
>
> What else remains to be supported?
>
> CPU freq, constraint frame work and individual drivers support to
> enable power domain transition to OFF/RET?
> Is this all? do these cover all the pm features of omap3?
>
> Is the constraints framework embedded within the TI SRF or is it
> independently usable?
>
> I havent seen too many drivers which specify constraints in the TI
> sources though.
>
>
> Regards,
> sriram
>
> On Mon, Nov 24, 2008 at 1:02 PM, Högander Jouni
> <jouni.hogander@nokia.com> wrote:
>> "ext Sriram V" <vshrirama@gmail.com> writes:
>>
>>> Kevin,
>>>
>>> On Fri, Nov 21, 2008 at 9:35 PM, Kevin Hilman
>>> <khilman@deeprootsystems.com> wrote:
>>>> "Premi, Sanjeev" <premi@ti.com> writes:
>>>>
>>>>>> -----Original Message-----
>>>>>> From: Kevin Hilman [mailto:khilman@deeprootsystems.com]
>>>>>> Sent: Thursday, November 20, 2008 11:10 PM
>>>>>> To: Premi, Sanjeev
>>>>>> Cc: Peter Reid; linux-omap@vger.kernel.org
>>>>>> Subject: Re: [ANNOUNCE] new PM branch: pm-20081119
>>>>>>
>>>>>> "Premi, Sanjeev" <premi@ti.com> writes:
>>>>>>
>>>>>>> These are my observations on OMAP3EVM:
>>>>>>>
>>>>>>> 1) Very frequently I see these messages:
>>>>>>>
>>>>>>> <4>__ratelimit: 6736 callbacks suppressed
>>>>>>> __ratelimit: 6736 callbacks suppressed <3>omapfb omapfb: irq error
>>>>>>> status 00c2 omapfb omapfb: irq error status 00c2 <3>omapfb
>>>>>> omapfb: irq
>>>>>>> error status 0060 omapfb omapfb: irq error status 0060 <3>omapfb
>>>>>>> omapfb: irq error status 00c2 omapfb omapfb: irq error status 00c2
>>>>>>> <3>omapfb omapfb: irq error status 0060 omapfb omapfb: irq error
>>>>>>> status 0060 <3>omapfb omapfb: irq error status 00e2 omapfb
>>>>>> omapfb: irq
>>>>>>> error status 00e2 <3>omapfb omapfb: irq error status 00c2 omapfb
>>>>>>> omapfb: irq error status 00c2 <3>omapfb omapfb: irq error
>>>>>> status 0060
>>>>>>> omapfb omapfb: irq error status 0060 <3>omapfb omapfb: irq error
>>>>>>> status 00e2 omapfb omapfb: irq error status 00e2 <3>omapfb
>>>>>> omapfb: irq
>>>>>>> error status 00c2 omapfb omapfb: irq error status 00c2 <3>omapfb
>>>>>>> omapfb: irq error status 0060 omapfb omapfb: irq error status 0060
>>>>>> Sanjeev,
>>>>>>
>>>>>> For starters can you try with a minimal kernel (no drivers,
>>>>>> no framebuffer, etc.)
>>>>>>
>>>>>> The first goal is to hit retention and off with no drivers
>>>>>> than start moving out to address driver issues from there.
>>>>>>
>>>>>> Kevin
>>>>>>
>>>>> Here is what I was able to see with the minimal config (attached).
>>>>>
>>>>> [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.01 seconds) (elapsed 0.01 seconds) done.done.
>>>>>
>>>>> Suspending console(s) (use no_console_suspend to debug)
>>>>> Suspending console(s) (use no_console_suspend to debug)
>>>>>
>>>>> <snip>un-printable characters<snip>
>>>>>
>>>>> Powerdomain (per_pwrdm) didn't enter target state 1
>>>>> Could not enter target state in pm_suspend
>>>>> Restarting tasks ... Restarting tasks ... done.
>>>>> done.
>>>> This is what I see on Beagle as well (PER is not entering retention.)
>>>>
>>>> At this point, the current PM debug code doesn't help further in
>>>> determining exactly why a powerdomain did not hit its target state.
>>>> Some device in the domain may still have its clocks enabled, or its
>>>> idle state not set correctly. Or, a given module may have been
>>>> initialized by the bootloader in a way which prevents it from going
>>>> idle.
>>>>
>>> True. I have observed on omap3evm with minimum configuration, and
>>> booting out of ramdisk:
>>> with nand booting: only per powerdomain does not enter retention
>>> with mmc boot: core and per dont enter retention
>>>
>>> it could do with clocks set the bootloaders that is preventing it from
>>> entering ret/off.
>> To tackle this you should have CONFIG_OMAP_RESET_CLOCKS enabled in
>> config.
>>
>>> what do you mean by idle state not set correctly? are you referring
>>> to auto-idle bit?
>> Not sure what Kevin meant there, but if the problem was in the
>> autoidle bit in *_SYSCONFIG, I would expect also CORE pwrdm to
>> fail. Anyway it's also worth of checking the statuses of PER modules
>> *_SYSCONFIG registers.
>>
>>>
>>>> We need some improved PM debug capabilities in the kernel to pinpoint
>>>> exactly the module that is causing the problem.
>>>>
>>> Apart from PM debug, are you using any other module/methods to
>>> debug?
>> State of PRCM registers can be quickly checked from
>> /sys/kernel/debug/pm_debug/registers/current (assuming you have mount
>> debugfs in /sys/kernel/debug and PM_DEBUG is enabled in config).
>>
>> --
>> Jouni Högander
>>
>>
--
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
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [ANNOUNCE] new PM branch: pm-20081119
2008-12-02 5:17 ` Kevin Hilman
@ 2008-12-03 14:23 ` Sriram V
0 siblings, 0 replies; 19+ messages in thread
From: Sriram V @ 2008-12-03 14:23 UTC (permalink / raw)
To: Kevin Hilman; +Cc: linux-omap@vger.kernel.org
Hi Kevin,
On Tue, Dec 2, 2008 at 10:47 AM, Kevin Hilman
<khilman@deeprootsystems.com> wrote:
> Sriram V wrote:
>>
>> Hi,
>> On OMAP3EVM, with a minimum config. All domains are hitting RET.
>> Only SGX domain hits OFF. No other domain hits OFF.
>
> Yes, the default boot behavior is to default to RET, but SGX does not
> support RET, only ON or OFF, so it goes to OFF.
>
>> I tried doing a echo 1 > /sys/power/enable_off_mode.
>
> After doing this, and then 'echo mem > /sys/power/state' do you see
> any other states that have hit OFF in /debug/pm_debug/count?
Am running out of a ramdisk now, I see all domains hitting OFF.
>
>> Powertop shows Sleep States upto C4. Has anyone seen Sleep States
>> upto C6 with this kernel?
>
> Yes, I've seen states up to C6. The only thing preventing deeper states
> is application or timer activity not being long enough. What does powertop
> list as the primary interrupt or timer sources waking out of idle?
>
Powertop output:
PowerTOP version 1.10 (C) 2007 Intel Corporation
Cn Avg residency P-states (frequencies)
C0 (cpu running) ( 0.2%)
C0 0.2ms ( 0.0%)
C1 4.8ms ( 1.7%)
C2 2.8ms ( 0.3%)
C3 0.0ms ( 0.0%)
C4 909.1ms (21.8%)
Wakeups-from-idle per second : 6.1 interval: 4.6s
Top causes for wakeups:
44.4% ( 5.0) <interrupt> : serial idle, serial
24.4% ( 2.8) <interrupt> : prcm
20.0% ( 2.2) <interrupt> : gp timer
4.4% ( 0.5) <kernel core> : schedule_delayed_work_on (delayed_work_timer
2.2% ( 0.2) <kernel core> : neigh_table_init_no_netlink (neigh_periodic_
2.2% ( 0.2) <kernel core> : omap_uart_block_sleep (omap_uart_idle_timer)
Regards,
sriram
>> dont know why MPU/CORE not hitting OFF even though the clocks are off.
>
> It looks like you're primarily testing dynamic idle. Can you check via
> /debug/pm_debug/count whether you're hitting OFF in any powerdomains when
> going into suspend?
>
> Kevin
>
>> With the most of the PM support (Suspend/Resume, Power Domains, CPU
>> Idle) up with minimum config.
>>
>> What else remains to be supported?
>>
>> CPU freq, constraint frame work and individual drivers support to
>> enable power domain transition to OFF/RET?
>> Is this all? do these cover all the pm features of omap3?
>>
>> Is the constraints framework embedded within the TI SRF or is it
>> independently usable?
>>
>> I havent seen too many drivers which specify constraints in the TI
>> sources though.
>>
>>
>> Regards,
>> sriram
>>
>> On Mon, Nov 24, 2008 at 1:02 PM, Högander Jouni
>> <jouni.hogander@nokia.com> wrote:
>>>
>>> "ext Sriram V" <vshrirama@gmail.com> writes:
>>>
>>>> Kevin,
>>>>
>>>> On Fri, Nov 21, 2008 at 9:35 PM, Kevin Hilman
>>>> <khilman@deeprootsystems.com> wrote:
>>>>>
>>>>> "Premi, Sanjeev" <premi@ti.com> writes:
>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: Kevin Hilman [mailto:khilman@deeprootsystems.com]
>>>>>>> Sent: Thursday, November 20, 2008 11:10 PM
>>>>>>> To: Premi, Sanjeev
>>>>>>> Cc: Peter Reid; linux-omap@vger.kernel.org
>>>>>>> Subject: Re: [ANNOUNCE] new PM branch: pm-20081119
>>>>>>>
>>>>>>> "Premi, Sanjeev" <premi@ti.com> writes:
>>>>>>>
>>>>>>>> These are my observations on OMAP3EVM:
>>>>>>>>
>>>>>>>> 1) Very frequently I see these messages:
>>>>>>>>
>>>>>>>> <4>__ratelimit: 6736 callbacks suppressed
>>>>>>>> __ratelimit: 6736 callbacks suppressed <3>omapfb omapfb: irq error
>>>>>>>> status 00c2 omapfb omapfb: irq error status 00c2 <3>omapfb
>>>>>>>
>>>>>>> omapfb: irq
>>>>>>>>
>>>>>>>> error status 0060 omapfb omapfb: irq error status 0060 <3>omapfb
>>>>>>>> omapfb: irq error status 00c2 omapfb omapfb: irq error status 00c2
>>>>>>>> <3>omapfb omapfb: irq error status 0060 omapfb omapfb: irq error
>>>>>>>> status 0060 <3>omapfb omapfb: irq error status 00e2 omapfb
>>>>>>>
>>>>>>> omapfb: irq
>>>>>>>>
>>>>>>>> error status 00e2 <3>omapfb omapfb: irq error status 00c2 omapfb
>>>>>>>> omapfb: irq error status 00c2 <3>omapfb omapfb: irq error
>>>>>>>
>>>>>>> status 0060
>>>>>>>>
>>>>>>>> omapfb omapfb: irq error status 0060 <3>omapfb omapfb: irq error
>>>>>>>> status 00e2 omapfb omapfb: irq error status 00e2 <3>omapfb
>>>>>>>
>>>>>>> omapfb: irq
>>>>>>>>
>>>>>>>> error status 00c2 omapfb omapfb: irq error status 00c2 <3>omapfb
>>>>>>>> omapfb: irq error status 0060 omapfb omapfb: irq error status 0060
>>>>>>>
>>>>>>> Sanjeev,
>>>>>>>
>>>>>>> For starters can you try with a minimal kernel (no drivers,
>>>>>>> no framebuffer, etc.)
>>>>>>>
>>>>>>> The first goal is to hit retention and off with no drivers
>>>>>>> than start moving out to address driver issues from there.
>>>>>>>
>>>>>>> Kevin
>>>>>>>
>>>>>> Here is what I was able to see with the minimal config (attached).
>>>>>>
>>>>>> [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.01 seconds) (elapsed 0.01 seconds) done.done.
>>>>>>
>>>>>> Suspending console(s) (use no_console_suspend to debug)
>>>>>> Suspending console(s) (use no_console_suspend to debug)
>>>>>>
>>>>>> <snip>un-printable characters<snip>
>>>>>>
>>>>>> Powerdomain (per_pwrdm) didn't enter target state 1
>>>>>> Could not enter target state in pm_suspend
>>>>>> Restarting tasks ... Restarting tasks ... done.
>>>>>> done.
>>>>>
>>>>> This is what I see on Beagle as well (PER is not entering retention.)
>>>>>
>>>>> At this point, the current PM debug code doesn't help further in
>>>>> determining exactly why a powerdomain did not hit its target state.
>>>>> Some device in the domain may still have its clocks enabled, or its
>>>>> idle state not set correctly. Or, a given module may have been
>>>>> initialized by the bootloader in a way which prevents it from going
>>>>> idle.
>>>>>
>>>> True. I have observed on omap3evm with minimum configuration, and
>>>> booting out of ramdisk:
>>>> with nand booting: only per powerdomain does not enter
>>>> retention
>>>> with mmc boot: core and per dont enter retention
>>>>
>>>> it could do with clocks set the bootloaders that is preventing it from
>>>> entering ret/off.
>>>
>>> To tackle this you should have CONFIG_OMAP_RESET_CLOCKS enabled in
>>> config.
>>>
>>>> what do you mean by idle state not set correctly? are you referring
>>>> to auto-idle bit?
>>>
>>> Not sure what Kevin meant there, but if the problem was in the
>>> autoidle bit in *_SYSCONFIG, I would expect also CORE pwrdm to
>>> fail. Anyway it's also worth of checking the statuses of PER modules
>>> *_SYSCONFIG registers.
>>>
>>>>
>>>>> We need some improved PM debug capabilities in the kernel to pinpoint
>>>>> exactly the module that is causing the problem.
>>>>>
>>>> Apart from PM debug, are you using any other module/methods to
>>>> debug?
>>>
>>> State of PRCM registers can be quickly checked from
>>> /sys/kernel/debug/pm_debug/registers/current (assuming you have mount
>>> debugfs in /sys/kernel/debug and PM_DEBUG is enabled in config).
>>>
>>> --
>>> Jouni Högander
>>>
>>>
>
>
--
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
^ permalink raw reply [flat|nested] 19+ messages in thread
end of thread, other threads:[~2008-12-03 14:29 UTC | newest]
Thread overview: 19+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-11-20 0:53 [ANNOUNCE] new PM branch: pm-20081119 Kevin Hilman
2008-11-20 8:45 ` Peter Reid
2008-11-20 14:13 ` Premi, Sanjeev
2008-11-20 14:48 ` Koen Kooi
2008-11-20 15:25 ` Premi, Sanjeev
2008-11-21 7:29 ` Kalle Jokiniemi
2008-11-20 16:00 ` Premi, Sanjeev
2008-11-20 17:40 ` Kevin Hilman
2008-11-21 15:46 ` Premi, Sanjeev
2008-11-21 16:05 ` Kevin Hilman
2008-11-23 7:57 ` Sriram V
2008-11-24 7:32 ` Högander Jouni
2008-12-01 16:22 ` Sriram V
2008-12-02 5:17 ` Kevin Hilman
2008-12-03 14:23 ` Sriram V
2008-11-21 7:20 ` Kalle Jokiniemi
2008-11-20 17:38 ` Kevin Hilman
2008-11-20 17:44 ` Kevin Hilman
2008-11-20 17:53 ` Koen Kooi
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox