* Re: new PM branch available @ 2009-03-18 18:56 Nicholas Chen 2009-03-18 19:01 ` Kevin Hilman 0 siblings, 1 reply; 40+ messages in thread From: Nicholas Chen @ 2009-03-18 18:56 UTC (permalink / raw) To: khilman; +Cc: linux-omap Dear Kevin, I recently checked out the latest PM branch from your git repository and put it on the Beagleboard (B5). I have been largely able to reproduce the results others have reported on this PM thread, but I believe my CORE and PER powerdomains are not hitting RET or OFF. I think this based on the following: after I echo 1 > enable_off_mode echo 1 > sleep_while_idle echo mem > state Suspending starts but upon resume I see the following: ... Powerdomain (core_pwrdm) didn't enter target state 0 Powerdomain (per_pwrdm) didn't enter target state 0 Could not enter target state in pm_suspend looking at debug/pm_debug/count/ I see that only the core_pwrdm and per_pwrdm have 0's next to OFF: and RET: Based on the thread, the resolution seems to be to disable USB and upgrade u-boot. I think I have done both. My u-boot is 2009.03-rc2 from Steve Sakoman's tree, and I have disabled USB support in my Kernel build. Is there something that I am overlooking? Also, I'm curious if the two powerdomains linked (i.e. I need to fix PER before CORE will shut off or vice versa). Nick ^ permalink raw reply [flat|nested] 40+ messages in thread
* Re: new PM branch available 2009-03-18 18:56 new PM branch available Nicholas Chen @ 2009-03-18 19:01 ` Kevin Hilman 2009-03-18 19:22 ` Nicholas Chen 0 siblings, 1 reply; 40+ messages in thread From: Kevin Hilman @ 2009-03-18 19:01 UTC (permalink / raw) To: Nicholas Chen; +Cc: linux-omap Nicholas Chen <nchen@cs.umd.edu> writes: > I recently checked out the latest PM branch from your git repository > and put it on the Beagleboard (B5). I have been largely able to > reproduce the results others have reported on this PM thread, ...not sure what "this PM thread" you are referring to? > but I believe my CORE and PER powerdomains are not hitting RET or > OFF. > I think this based on the following: > after I > echo 1 > enable_off_mode > echo 1 > sleep_while_idle > echo mem > state CORE and PER are still on because UART clocks are not being cut in idle: # echo 1 > /sys/power/clocks_off_when_idle And see if that works. Also at least on my Beagle, I am not able to resume from full-chip OFF, so for starters I suggest just testing retention: echo 0 > /sys/power/enable_off_mode > Suspending starts but upon resume I see the following: > ... > Powerdomain (core_pwrdm) didn't enter target state 0 > Powerdomain (per_pwrdm) didn't enter target state 0 > Could not enter target state in pm_suspend > > looking at debug/pm_debug/count/ > I see that only the core_pwrdm and per_pwrdm have 0's next to OFF: and > RET: > > Based on the thread, the resolution seems to be to disable USB and > upgrade u-boot. I think I have done both. My u-boot is 2009.03-rc2 > from Steve Sakoman's tree, and I have disabled USB support in my > Kernel build. Is there something that I am overlooking? Also, I'm > curious if the two powerdomains linked (i.e. I need to fix PER before > CORE will shut off or vice versa). For your problem, they're linked in that they both contain a UART block. UART1,2 are in CORE and UART3 is in PER. Kevin ^ permalink raw reply [flat|nested] 40+ messages in thread
* Re: new PM branch available 2009-03-18 19:01 ` Kevin Hilman @ 2009-03-18 19:22 ` Nicholas Chen 0 siblings, 0 replies; 40+ messages in thread From: Nicholas Chen @ 2009-03-18 19:22 UTC (permalink / raw) To: Kevin Hilman; +Cc: linux-omap On Mar 18, 2009, at 3:01 PM, Kevin Hilman wrote: > Nicholas Chen <nchen@cs.umd.edu> writes: > >> I recently checked out the latest PM branch from your git repository >> and put it on the Beagleboard (B5). I have been largely able to >> reproduce the results others have reported on this PM thread, > > ...not sure what "this PM thread" you are referring to? > >> but I believe my CORE and PER powerdomains are not hitting RET or >> OFF. > >> I think this based on the following: >> after I >> echo 1 > enable_off_mode >> echo 1 > sleep_while_idle >> echo mem > state > > CORE and PER are still on because UART clocks are not being cut in > idle: > > # echo 1 > /sys/power/clocks_off_when_idle > > And see if that works. Also at least on my Beagle, I am not able > to resume from full-chip OFF, so for starters I suggest just testing > retention: echo 0 > /sys/power/enable_off_mode > >> Suspending starts but upon resume I see the following: >> ... >> Powerdomain (core_pwrdm) didn't enter target state 0 >> Powerdomain (per_pwrdm) didn't enter target state 0 >> Could not enter target state in pm_suspend >> >> looking at debug/pm_debug/count/ >> I see that only the core_pwrdm and per_pwrdm have 0's next to OFF: >> and >> RET: >> >> Based on the thread, the resolution seems to be to disable USB and >> upgrade u-boot. I think I have done both. My u-boot is 2009.03-rc2 >> from Steve Sakoman's tree, and I have disabled USB support in my >> Kernel build. Is there something that I am overlooking? Also, I'm >> curious if the two powerdomains linked (i.e. I need to fix PER before >> CORE will shut off or vice versa). > > For your problem, they're linked in that they both contain a UART > block. UART1,2 are in CORE and UART3 is in PER. > > Kevin > -- > 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 Thanks for the assistance. I see everything going into RET now, so I think I'm duplicating what everybody else is seeing. I also have a better understanding what the entries in /sys/power do now. Nick PS Sorry, the thread/message I am referring to is: http://markmail.org/message/4cynvcjzult4c2rj From Feb 4. ^ permalink raw reply [flat|nested] 40+ messages in thread
* new PM branch available
@ 2009-01-13 21:51 Kevin Hilman
2009-01-14 7:35 ` Koen Kooi
` (4 more replies)
0 siblings, 5 replies; 40+ messages in thread
From: Kevin Hilman @ 2009-01-13 21:51 UTC (permalink / raw)
To: linux-omap
Hello,
The latest PM branch is now available[1].
I've done basic testing of retention and off-mode (suspend and dynamic
idle) on Beagle and custom HW. My SDP has something still keeping
CORE active that others have not seen, but I have yet to debug. Any
other reports from SDP testing would be appreciated.
Notable changes/updates
- rebased on latest clock updates and fixes from Paul
- clockfw pre- and post- notifiers
- DVFS for VDD2
Full git shortlog below[2]
Enjoy,
Kevin
[1] See branch 'pm' in my git repo:
git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap-pm.git
which is also mirrored as the branch 'pm' of the normal linux-omap
repo (but will not sync until 03:30 GMT)
[2] git shortlog:
Carlos Chinea (1):
OMAP3:PM: Update SSI omapdev record
Jouni Hogander (5):
OMAP3: PM: Use pwrdm_set_next_pwrst instead of set_pwrdm_state in idle loop
OMAP3: PM: Fix wrong sequence in suspend.
OMAP3: PM: Do not build suspend code if SUSPEND is not enabled
OMAP: PM: Build fails if PM is not enabled
OMAP2: PM: Fix omap2 build
Kalle Jokiniemi (3):
OMAP: PM: sysfs interface for enabling voltage off in idle
OMAP3: PM: Fix cpu idle init sequencing
OMAP: SRF: Fixes to shared resource framework (Ver.3)
Kevin Hilman (4):
OMAP3: PM: CPUidle: obey enable_off_mode flag
OMAP3: PM: CPUidle: restrict C-states on UART activity
OMAP3: PM: decouple PER and CORE context save and restore
OMAP2/3: PM: system_rev -> omap_rev()
Paul Walmsley (29):
OMAP2/3 clock: implement clock notifier infrastructure
OMAP clock: add notifier infrastructure
OMAP2/3 clock: store planned clock rates into temporary rate storage
OMAP2/3 clock: add clk post-rate-change notifiers
OMAP2/3 clock: add clock pre-rate-change notification
OMAP2/3 clock: add clock prepare-rate-change notifications
OMAP2/3 clock: add clock abort-rate-change notifications
OMAP2/3 PM: create the OMAP PM interface and add a default OMAP PM no-op layer.
OMAP2/3 omapdev: add basic omapdev structure
OMAP242x omapdev: add OMAP242x omapdev records
OMAP243x omapdev: add OMAP243x omapdev records
OMAP3xxx omapdev: add OMAP3xxx omapdev records
OMAP2/3 omapdev: add code to walk the omapdev records
ARM: MMU: add a Non-cacheable Normal executable memory type
OMAP3 SRAM: mark OCM RAM as Non-cacheable Normal memory
OMAP3 SRAM: add ARM barriers to omap3_sram_configure_core_dpll
OMAP3 clock: add interconnect barriers to CORE DPLL M2 change
OMAP3 SRAM: clear the SDRC PWRENA bit during SDRC frequency change
OMAP3 SDRC: Add 166MHz, 83MHz SDRC settings for the BeagleBoard
OMAP3 SDRC: initialize SDRC_POWER at boot
OMAP3 SRAM: renumber registers to make space for argument passing
OMAP3 clock: only unlock SDRC DLL if SDRC clk < 83MHz
OMAP3 clock: use pr_debug() rather than pr_info() in some clock change code
OMAP3 clock: remove wait for DPLL3 M2 clock to stabilize
OMAP3 clock: initialize SDRC timings at kernel start
OMAP3 clock: add a short delay when lowering CORE clk rate
OMAP3 clock/SDRC: program SDRC_MR register during SDRC clock change
OMAP3 SRAM: add more comments on the SRAM code
OMAP3 SRAM: convert SRAM code to use macros rather than magic numbers
Peter 'p2' De Schrijver (12):
OMAP: PM counter infrastructure.
OMAP: PM: Hook into PM counters
OMAP: PM: Add closures to clkdm_for_each and pwrdm_for_each.
OMAP: PM: Add pm-debug counters
OMAP: PM debug: make powerdomains use PM-debug counters
OMAP: PM: Add definitions for ETK pads and observability registers
OMAP: Debug observability and ETK padconf implementation
OMAP: Add debug observablity (debobs) Kconfig item
OMAP: PM: Implement get_last_off_on_transaction_id()
Save sram context after changing MPU, DSP or core clocks
Fix omap_getspeed.
Make sure omap cpufreq driver initializes after cpufreq framework and governors
Rajendra Nayak (35):
OMAP3: PM: GPMC context save/restore
OMAP3: PM: GPIO context save/restore
OMAP3: PM: I2C context save/restore
OMAP3: PM: INTC context save/restore
OMAP3: PM: PRCM context save/restore
OMAP3: PM: Populate scratchpad contents
OMAP3: PM: SCM context save/restore
OMAP3: PM: SRAM restore function
OMAP3: PM: handle PER/NEON/CORE in idle
OMAP3: PM: Restore MMU table entry
OMAP3: PM: MPU off-mode support
OMAP3: PM: CORE domain off-mode support
OMAP3: PM: allow runtime enable/disable of OFF mode
OMAP3: 3430SDP minimal kernel defconfig
OMAP3: PM: CPUidle: Basic support for C1-C2
OMAP3: PM: CPUidle: Enables state C4
OMAP3: PM: CPUidle: Enables C3 and C5
OMAP3: PM: CPUidle: Safe-state on bm-activity
OMAP3 SRF: Generic shared resource f/w
OMAP3 SRF: MPU/CORE/PD latency modeling
OMAP3 SRF: omap3 srf driver
OMAP3 SRF: OMAP PM srf implementation
OMAP3 SRF: Add CORE rate table param in OMAP-PM
OMAP3 SRF: Add VDD1/VDD2 rate tables for 3430SDP
OMAP3 SRF: Add virt clk nodes for VDD1/VDD2
OMAP3 SRF: Adds OPP/Freq res's in SRF
OMAP3 SRF: Update OMAP-PM layer
OMAP3 SRF: Voltage scaling support
OMAP3 SRF: VDD2 scaling support
OMAP3 SRF: Adds sysfs control for VDD1/VDD2 OPP's
OMAP3 PM: Replace spinlocks with mutex in SRF
OMAP3 PM: CPUFreq driver for OMAP3
OMAP3 PM: Update the min defconfig for 3430sdp
OMAP3 SRF: Fix crash on non-3430SDP platforms with DVFS/CPUFreq
OMAP3: PM: Scale VDD2 OPP for VDD1 OPP3 and higher
Tero Kristo (26):
OMAP: PM debug: do not print out status for meta powerdomains (dpll*)
OMAP: PM debug: Add PRCM register dump support
OMAP: PM: DMA context save / restore
OMAP: PM: off-mode support for DMA on EMU/HS devices
OMAP3: SRAM size fix for HS/EMU devices
OMAP3 PM: off-mode support for HS/EMU devices
OMAP3: PM: Enable SDRAM auto-refresh during sleep
OMAP: SDRC: Add new register definitions for SDRAM controller
OMAP3: PM: SDRC auto-refresh workaround for off-mode
PM: Added three PLL registers to the PRCM context save
PM: Changed secure RAM storage size from 0x8000 to 0x803F
PM: Added suspend target state control to debugfs for OMAP3
OMAP3: PM: Prevent PER from going OFF when CORE is going INA
PM OMAP3: Change omap3_save_secure_ram to be called only during init
OMAP3: PM: MPU and CORE should stay awake if there is CAM domain ACTIVE
OMAP3: GPIO fixes for off-mode
PM: OMAP3: Refreshed DVFS VDD1 control against latest clock fw
OMAP3: Add support for DPLL3 divisor values higher than 2
OMAP3: PM: Fixed VDD2 control to work from both sysfs and SRF API
OMAP3: PM: Added DVFS OPP locking interface for VDD1 and VDD2
OMAP3: Fix rate calculation bug in omap3_select_table_rate
OMAP3: PM: Prevented DVFS state switches when enabling off-mode
OMAP3: PM: Enable VDD2 OPP1
OMAP3: PM: Fix linker error without CONFIG_PM option
PM: OMAP3: Removed a couple of unused variables from DVFS code
PM: OMAP3: Added support for possibly failing clk_set_rate to DVFS
^ permalink raw reply [flat|nested] 40+ messages in thread* Re: new PM branch available 2009-01-13 21:51 Kevin Hilman @ 2009-01-14 7:35 ` Koen Kooi 2009-01-14 18:09 ` David Brownell 2009-01-14 22:14 ` Kevin Hilman 2009-01-14 12:40 ` Ramesh Gupta Guntha ` (3 subsequent siblings) 4 siblings, 2 replies; 40+ messages in thread From: Koen Kooi @ 2009-01-14 7:35 UTC (permalink / raw) To: linux-omap@vger.kernel.org List [-- Attachment #1: Type: text/plain, Size: 43052 bytes --] Op 13 jan 2009, om 22:51 heeft Kevin Hilman het volgende geschreven: > Hello, > > The latest PM branch is now available[1]. > > I've done basic testing of retention and off-mode (suspend and dynamic > idle) on Beagle and custom HW. My SDP has something still keeping > CORE active that others have not seen, but I have yet to debug. Any > other reports from SDP testing would be appreciated. > > Notable changes/updates > - rebased on latest clock updates and fixes from Paul > - clockfw pre- and post- notifiers > - DVFS for VDD2 The bootlog on my rev C1D beagle looks suspicious: Texas Instruments X-Loader 1.4.2 (Dec 3 2008 - 23:20:13) Reading boot sector Booting from mmc U-Boot 2009.01-rc1-00102-g8ecaab3 (Jan 10 2009 - 13:56:28) OMAP3530-GP rev 2, CPU-OPP2 L3-165MHz OMAP3 Beagle board + LPDDR/NAND DRAM: 256 MB NAND: 256 MiB musb: using high speed In: serial Out: serial Err: serial Board revision: Cx Debug (GPIO6 datain): 0x04800000 Hit any key to stop autoboot: 1 \b\b\b 0 reading boot.scr ** Unable to read "boot.scr" from mmc 0:1 ** reading uImage 2556572 bytes read Booting from mmc ... ## Booting kernel from Legacy Image at 82000000 ... Image Name: Angstrom/2.6.28-pm1+gitrb5d11429 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 2556508 Bytes = 2.4 MB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Uncompressing Linux .................................................................................................................................................................... done , booting the kernel. Linux version 2.6.28-omap1 (koen@dominion) (gcc version 4.2.1) #1 Sun Jan 11 18:52:51 CET 2009 CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), cr=10c5387f CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache Machine: OMAP3 Beagle Board Memory policy: ECC disabled, Data cache writeback On node 0 totalpages: 65536 free_area_init_node: node 0, pgdat c050be14, node_mem_map c0540000 Normal zone: 512 pages used for memmap Normal zone: 0 pages reserved Normal zone: 65024 pages, LIFO batch:15 Movable zone: 0 pages used for memmap OMAP3430 ES3.0 SRAM: Mapped pa 0x40200000 to va 0xd7000000 size: 0x100000 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024 Kernel command line: console=ttyS2,115200n8 video=omapfb:vram:2M,vram: 4M,mode:640x480@60 omapfb.debug=y omap-dss.debug=y loglevel=10 omapfb.vram=4M,4M root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait Unknown boot option `omapfb.debug=y': ignoring Unknown boot option `omap-dss.debug=y': ignoring Unknown boot option `omapfb.vram=4M,4M': ignoring Clocking rate (Crystal/DPLL/ARM core): 26.0/332/500 MHz GPMC revision 5.0 IRQ: Found an INTC at 0xd8200000 (revision 4.0) with 96 interrupts Total of 96 interrupts on 1 active controller OMAP34xx GPIO hardware version 2.5 PID hash table entries: 1024 (order: 10, 4096 bytes) OMAP clockevent source: GPTIMER12 at 32768 Hz Console: colour dummy device 80x30 Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) Memory: 128MB 128MB = 256MB total Memory: 254336KB available (4712K code, 428K data, 188K init) Calibrating delay loop... 478.91 BogoMIPS (lpj=1867776) Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok net_namespace: 532 bytes regulator: core version 0.5 NET: Registered protocol family 16 Found NAND on CS0 Registering NAND on CS0 ------------[ cut here ]------------ WARNING: at arch/arm/mach-omap2/clock.c:1094 omap2_clk_register +0x24/0x3c() Modules linked in: [<c003b824>] (dump_stack+0x0/0x14) from [<c005b180>] (warn_on_slowpath +0x4c/0x68) [<c005b134>] (warn_on_slowpath+0x0/0x68) from [<c00416a8>] (omap2_clk_register+0x24/0x3c) r6:c04de968 r5:c04d82d8 r4:c04d8270 [<c0041684>] (omap2_clk_register+0x0/0x3c) from [<c0048854>] (clk_register+0x44/0xc8) [<c0048810>] (clk_register+0x0/0xc8) from [<c00113ec>] (omap2_mcbsp_init+0xc8/0x130) r7:c0469ded r6:00000008 r5:c04d82d8 r4:c04d8270 [<c0011324>] (omap2_mcbsp_init+0x0/0x130) from [<c00372d4>] (do_one_initcall+0x64/0x198) [<c0037270>] (do_one_initcall+0x0/0x198) from [<c0008718>] (kernel_init +0x70/0xdc) [<c00086a8>] (kernel_init+0x0/0xdc) from [<c005db54>] (do_exit +0x0/0x6b4) r5:00000000 r4:00000000 ---[ end trace 1b75b31a2719ed1c ]--- ------------[ cut here ]------------ WARNING: at arch/arm/mach-omap2/clock.c:1094 omap2_clk_register +0x24/0x3c() Modules linked in: [<c003b824>] (dump_stack+0x0/0x14) from [<c005b180>] (warn_on_slowpath +0x4c/0x68) [<c005b134>] (warn_on_slowpath+0x0/0x68) from [<c00416a8>] (omap2_clk_register+0x24/0x3c) r6:c04de968 r5:c04d8340 r4:c04d82d8 [<c0041684>] (omap2_clk_register+0x0/0x3c) from [<c0048854>] (clk_register+0x44/0xc8) [<c0048810>] (clk_register+0x0/0xc8) from [<c00113ec>] (omap2_mcbsp_init+0xc8/0x130) r7:c0469ded r6:00000008 r5:c04d8340 r4:c04d8270 [<c0011324>] (omap2_mcbsp_init+0x0/0x130) from [<c00372d4>] (do_one_initcall+0x64/0x198) [<c0037270>] (do_one_initcall+0x0/0x198) from [<c0008718>] (kernel_init +0x70/0xdc) [<c00086a8>] (kernel_init+0x0/0xdc) from [<c005db54>] (do_exit +0x0/0x6b4) r5:00000000 r4:00000000 ---[ end trace 1b75b31a2719ed1c ]--- ------------[ cut here ]------------ WARNING: at arch/arm/mach-omap2/clock.c:1094 omap2_clk_register +0x24/0x3c() Modules linked in: [<c003b824>] (dump_stack+0x0/0x14) from [<c005b180>] (warn_on_slowpath +0x4c/0x68) [<c005b134>] (warn_on_slowpath+0x0/0x68) from [<c00416a8>] (omap2_clk_register+0x24/0x3c) r6:c04de968 r5:c04d83a8 r4:c04d8340 [<c0041684>] (omap2_clk_register+0x0/0x3c) from [<c0048854>] (clk_register+0x44/0xc8) [<c0048810>] (clk_register+0x0/0xc8) from [<c00113ec>] (omap2_mcbsp_init+0xc8/0x130) r7:c0469ded r6:00000008 r5:c04d83a8 r4:c04d8270 [<c0011324>] (omap2_mcbsp_init+0x0/0x130) from [<c00372d4>] (do_one_initcall+0x64/0x198) [<c0037270>] (do_one_initcall+0x0/0x198) from [<c0008718>] (kernel_init +0x70/0xdc) [<c00086a8>] (kernel_init+0x0/0xdc) from [<c005db54>] (do_exit +0x0/0x6b4) r5:00000000 r4:00000000 ---[ end trace 1b75b31a2719ed1c ]--- ------------[ cut here ]------------ WARNING: at arch/arm/mach-omap2/clock.c:1094 omap2_clk_register +0x24/0x3c() Modules linked in: [<c003b824>] (dump_stack+0x0/0x14) from [<c005b180>] (warn_on_slowpath +0x4c/0x68) [<c005b134>] (warn_on_slowpath+0x0/0x68) from [<c00416a8>] (omap2_clk_register+0x24/0x3c) r6:c04de968 r5:c04d8410 r4:c04d83a8 [<c0041684>] (omap2_clk_register+0x0/0x3c) from [<c0048854>] (clk_register+0x44/0xc8) [<c0048810>] (clk_register+0x0/0xc8) from [<c00113ec>] (omap2_mcbsp_init+0xc8/0x130) r7:c0469ded r6:00000008 r5:c04d8410 r4:c04d8270 [<c0011324>] (omap2_mcbsp_init+0x0/0x130) from [<c00372d4>] (do_one_initcall+0x64/0x198) [<c0037270>] (do_one_initcall+0x0/0x198) from [<c0008718>] (kernel_init +0x70/0xdc) [<c00086a8>] (kernel_init+0x0/0xdc) from [<c005db54>] (do_exit +0x0/0x6b4) r5:00000000 r4:00000000 ---[ end trace 1b75b31a2719ed1c ]--- ------------[ cut here ]------------ WARNING: at arch/arm/mach-omap2/clock.c:1094 omap2_clk_register +0x24/0x3c() Modules linked in: [<c003b824>] (dump_stack+0x0/0x14) from [<c005b180>] (warn_on_slowpath +0x4c/0x68) [<c005b134>] (warn_on_slowpath+0x0/0x68) from [<c00416a8>] (omap2_clk_register+0x24/0x3c) r6:c04de968 r5:c04d8478 r4:c04d8410 [<c0041684>] (omap2_clk_register+0x0/0x3c) from [<c0048854>] (clk_register+0x44/0xc8) [<c0048810>] (clk_register+0x0/0xc8) from [<c00113ec>] (omap2_mcbsp_init+0xc8/0x130) r7:c0469ded r6:00000008 r5:c04d8478 r4:c04d8270 [<c0011324>] (omap2_mcbsp_init+0x0/0x130) from [<c00372d4>] (do_one_initcall+0x64/0x198) [<c0037270>] (do_one_initcall+0x0/0x198) from [<c0008718>] (kernel_init +0x70/0xdc) [<c00086a8>] (kernel_init+0x0/0xdc) from [<c005db54>] (do_exit +0x0/0x6b4) r5:00000000 r4:00000000 ---[ end trace 1b75b31a2719ed1c ]--- omap-mcbsp omap-mcbsp.1: Invalid clock configuration for McBSP1. omap-mcbsp: probe of omap-mcbsp.1 failed with error -2 omap-mcbsp omap-mcbsp.2: Invalid clock configuration for McBSP2. omap-mcbsp: probe of omap-mcbsp.2 failed with error -2 omap-mcbsp omap-mcbsp.3: Invalid clock configuration for McBSP3. omap-mcbsp: probe of omap-mcbsp.3 failed with error -2 omap-mcbsp omap-mcbsp.4: Invalid clock configuration for McBSP4. omap-mcbsp: probe of omap-mcbsp.4 failed with error -2 omap-mcbsp omap-mcbsp.5: Invalid clock configuration for McBSP5. omap-mcbsp: probe of omap-mcbsp.5 failed with error -2 OMAP DMA hardware revision 4.0 USB: No board-specific platform config found i2c_omap i2c_omap.1: bus 1 rev3.12 at 2600 kHz twl4030: PIH (irq 7) chaining IRQs 368..375 twl4030: power (irq 373) chaining IRQs 376..383 twl4030: gpio (irq 368) chaining IRQs 384..401 i2c_omap i2c_omap.3: bus 3 rev3.12 at 400 kHz SCSI subsystem initialized twl4030_usb twl4030_usb: Initialized TWL4030 USB module usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb musb_hdrc: version 6.0, musb-dma, otg (peripheral+host), debug=0 musb_hdrc: ConfigData=0x33 (UTMI-16, HB-ISO Rx (X), SoftConn) musb_hdrc: MHDRC RTL version 1.400 musb_core_init 1405: reconfigure software for static FIFOs musb_hdrc musb_hdrc: musb_init_controller failed with status -19 regulator: VMMC1: 1850 <--> 3150 mV normal standby regulator: VDAC: 1800 mV normal standby regulator: VUSB1V5: 1500 mV normal standby regulator: VUSB1V8: 1800 mV normal standby regulator: VUSB3V1: 3100 mV normal standby regulator: VSIM: 1800 <--> 3000 mV normal standby Bluetooth: Core ver 2.13 NET: Registered protocol family 31 Bluetooth: HCI device and connection manager initialized Bluetooth: HCI socket layer initialized cfg80211: Using static regulatory domain info cfg80211: Regulatory domain: US (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm) (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm) (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm) (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm) (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm) (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm) cfg80211: Calling CRDA for country: US NET: Registered protocol family 2 Switched to high resolution mode on CPU 0 IP route cache hash table entries: 2048 (order: 1, 8192 bytes) TCP established hash table entries: 8192 (order: 4, 65536 bytes) TCP bind hash table entries: 8192 (order: 3, 32768 bytes) TCP: Hash tables configured (established 8192 bind 8192) TCP reno registered NET: Registered protocol family 1 VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) JFFS2 version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc. msgmni has been set to 497 alg: No test for stdrng (krng) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) Serial: 8250/16550 driver4 ports, IRQ sharing enabled serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654 serial8250.0: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654 serial8250.0: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654 console [ttyS2] enabled brd: module loaded loop: module loaded usbcore: registered new interface driver asix usbcore: registered new interface driver cdc_ether usbcore: registered new interface driver rndis_host usbcore: registered new interface driver zd1211rw usbcore: registered new interface driver rndis_wlan usbcore: registered new interface driver zd1201 usbcore: registered new interface driver usb8xxx usbcore: registered new interface driver rtl8187 usbcore: registered new interface driver rt2500usb usbcore: registered new interface driver rt73usb usbcore: registered new interface driver p54usb i2c /dev entries driver input: triton2-pwrbutton as /class/input/input0 triton2 power button driver initialized Driver 'sd' needs updating - please use bus_type methods Driver 'sr' needs updating - please use bus_type methods omap2-nand driver initializing NAND device: Manufacturer ID: 0x2c, Chip ID: 0xba (Micron NAND 256MiB 1,8V 16-bit) cmdlinepart partition parsing not available Creating 5 MTD partitions on "omap2-nand": 0x00000000-0x00080000 : "X-Loader" 0x00080000-0x00260000 : "U-Boot" 0x00260000-0x00280000 : "U-Boot Env" 0x00280000-0x00680000 : "Kernel" 0x00680000-0x10000000 : "File System" ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver ehci-omap ehci-omap.0: OMAP-EHCI Host Controller ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 1 ehci-omap ehci-omap.0: irq 77, io mem 0x48064800 usb usb1: configuration #1 chosen from 1 choice hub 1-0:1.0: USB hub found hub 1-0:1.0: 3 ports detected Initializing USB Mass Storage driver... usbcore: registered new interface driver usb-storage USB Mass Storage support registered. mice: PS/2 mouse device common for all mice input: gpio-keys as /class/input/input1 twl4030_rtc twl4030_rtc: rtc core: registered twl4030_rtc as rtc0 twl4030_rtc twl4030_rtc: Power up reset detected. twl4030_rtc twl4030_rtc: Enabling TWL4030-RTC. OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec Bluetooth: HCI USB driver ver 2.10 usbcore: registered new interface driver hci_usb Bluetooth: Broadcom Blutonium firmware driver ver 1.2 usbcore: registered new interface driver bcm203x Bluetooth: Digianswer Bluetooth USB driver ver 0.10 usbcore: registered new interface driver bpa10x Bluetooth: Generic Bluetooth SDIO driver ver 0.1 cpuidle: using governor ladder cpuidle: using governor menu mmci-omap-hs mmci-omap-hs.0: Failed to get debounce clock Registered led device: beagleboard::usr0 Registered led device: beagleboard::usr1 Registered led device: beagleboard::pmu_stat usbcore: registered new interface driver usbhid usbhid: v2.6:USB HID core driver Advanced Linux Sound Architecture Driver Version 1.0.18rc3. usbcore: registered new interface driver snd-usb-audio ASoC version 0.13.2 OMAP3 Beagle SoC init TWL4030 Audio Codec init asoc: twl4030 <-> omap-mcbsp-dai-(link_id) mapping ok ALSA device list: #0: omap3beagle (twl4030) oprofile: using arm/armv7 TCP cubic registered NET: Registered protocol family 17 NET: Registered protocol family 15 Bluetooth: L2CAP ver 2.11 Bluetooth: L2CAP socket layer initialized Bluetooth: SCO (Voice Link) ver 0.6 Bluetooth: SCO socket layer initialized Bluetooth: RFCOMM socket layer initialized Bluetooth: RFCOMM TTY layer initialized Bluetooth: RFCOMM ver 1.10 Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Bluetooth: BNEP filters: protocol multicast Bluetooth: HIDP (Human Interface Emulation) ver 1.2 RPC: Registered udp transport module. RPC: Registered tcp transport module. ieee80211: 802.11 data/management/control stack, git-1.1.13 ieee80211: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com > ieee80211_crypt: registered algorithm 'NULL' ieee80211_crypt: registered algorithm 'WEP' ieee80211_crypt: registered algorithm 'CCMP' ieee80211_crypt: registered algorithm 'TKIP' ThumbEE CPU extension supported. Power Management for TI OMAP3. pm_dbg_init() SmartReflex driver initialized Disabling unused clock "sr2_fck" Disabling unused clock "sr1_fck" Disabling unused clock "mcbsp_fck" Disabling unused clock "mcbsp_fck" Disabling unused clock "mcbsp_fck" Disabling unused clock "mcbsp_ick" Disabling unused clock "mcbsp_ick" Disabling unused clock "mcbsp_ick" Disabling unused clock "gpt2_ick" Disabling unused clock "gpt3_ick" Disabling unused clock "gpt4_ick" Disabling unused clock "gpt5_ick" Disabling unused clock "gpt6_ick" Disabling unused clock "gpt7_ick" Disabling unused clock "gpt8_ick" Disabling unused clock "gpt9_ick" Disabling unused clock "wdt3_ick" Disabling unused clock "wdt3_fck" Disabling unused clock "gpio2_dbck" Disabling unused clock "gpio3_dbck" Disabling unused clock "gpio4_dbck" Disabling unused clock "gpio5_dbck" Disabling unused clock "gpio6_dbck" Disabling unused clock "gpt9_fck" Disabling unused clock "gpt8_fck" Disabling unused clock "gpt7_fck" Disabling unused clock "gpt6_fck" Disabling unused clock "gpt5_fck" Disabling unused clock "gpt4_fck" Disabling unused clock "gpt3_fck" Disabling unused clock "gpt2_fck" Disabling unused clock "gpt1_ick" Disabling unused clock "wdt1_ick" Disabling unused clock "wdt2_ick" Disabling unused clock "wdt2_fck" Disabling unused clock "gpio1_dbck" Disabling unused clock "gpt1_fck" Disabling unused clock "cam_ick" Disabling unused clock "cam_mclk" Disabling unused clock "dss_ick" Disabling unused clock "dss_96m_fck" Disabling unused clock "dss1_alwon_fck" Disabling unused clock "des1_ick" Disabling unused clock "sha11_ick" Disabling unused clock "rng_ick" Disabling unused clock "aes1_ick" Disabling unused clock "ssi_ick" Disabling unused clock "mailboxes_ick" Disabling unused clock "mcbsp_ick" Disabling unused clock "mcbsp_ick" Disabling unused clock "gpt10_ick" Disabling unused clock "gpt11_ick" Disabling unused clock "i2c_ick" Disabling unused clock "mcspi_ick" Disabling unused clock "mcspi_ick" Disabling unused clock "mcspi_ick" Disabling unused clock "mcspi_ick" Disabling unused clock "hdq_ick" Disabling unused clock "mspro_ick" Disabling unused clock "des2_ick" Disabling unused clock "sha12_ick" Disabling unused clock "aes2_ick" Disabling unused clock "icr_ick" Disabling unused clock "pka_ick" Disabling unused clock "ssi_ssr_fck" Disabling unused clock "hdq_fck" Disabling unused clock "mcspi_fck" Disabling unused clock "mcspi_fck" Disabling unused clock "mcspi_fck" Disabling unused clock "mcspi_fck" Disabling unused clock "mcbsp_fck" Disabling unused clock "mcbsp_fck" Disabling unused clock "i2c_fck" Disabling unused clock "mspro_fck" Disabling unused clock "gpt11_fck" Disabling unused clock "gpt10_fck" Disabling unused clock "dpll4_m6x2_ck" Disabling unused clock "dpll4_m3x2_ck" Disabling unused clock "dpll3_m3x2_ck" Disabling unused clock "sys_clkout1" VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 1 twl4030_rtc twl4030_rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800) Waiting for root device /dev/mmcblk0p2... mmc0: new high speed SDHC card at address 8fe4 mmcblk0: mmc0:8fe4 SD08G 7.40 GiB mmcblk0: p1 p2 p3 EXT3-fs warning: maximal mount count reached, running e2fsck is recommended EXT3 FS on mmcblk0p2, internal journal EXT3-fs: recovery complete. EXT3-fs: mounted filesystem with ordered data mode. VFS: Mounted root (ext3 filesystem). Freeing init memory: 188K INIT: version 2.86 booting v/rules.d: time stamp 2009-01-13 21:05:30 is 285195917.614868154 s in the future udevd[596]: lookup_group: specified group 'scanner' unknown udevd[596]: lookup_group: specified group 'scanner' unknown udevd[596]: lookup_group: specified group 'scanner' unknown udevd[596]: lookup_group: specified group 'scanner' unknown udevd[596]: lookup_group: specified group 'nvram' unknown udevd[596]: lookup_user: specified user 'tss' unknown udevd[596]: lookup_group: specified group 'tss' unknown udevd[596]: lookup_group: specified group 'fuse' unknown udevd[596]: lookup_group: specified group 'kvm' unknown udevd[596]: lookup_group: specified group 'rdma' unknown udevd[596]: lookup_group: specified group 'rdma' unknown udevd[596]: lookup_group: specified group 'rdma' unknown Adding 160640k swap on /dev/mmcblk0p3. Priority:-1 extents:1 across: 160640k Remounting root file system... uncorrectable error : <3>end_request: I/O error, dev mtdblock0, sector 0 Buffer I/O error on device mtdblock0, logical block 0 end_request: I/O error, dev mtdblock0, sector 8 Buffer I/O error on device mtdblock0, logical block 1 uncorrectable error : <3>end_request: I/O error, dev mtdblock0, sector 16 Buffer I/O error on device mtdblock0, logical block 2 uncorrectable error : <3>uncorrectable error : <3>end_request: I/O error, dev mtdblock0, sector 24 Buffer I/O error on device mtdblock0, logical block 3 uncorrectable error : <3>end_request: I/O error, dev mtdblock0, sector 0 Buffer I/O error on device mtdblock0, logical block 0 WARNING: Couldn't open directory /lib/modules/2.6.28-omap1: No such file or directory FATAL: Could not open /lib/modules/2.6.28-omap1/modules.dep.temp for writing: No such file or directory modprobe: FATAL: Could not load /lib/modules/2.6.28-omap1/modules.dep: No such file or directory Setting up IP spoofing protection: rp_filter. Configuring network interfaces... modprobe: FATAL: Could not load /lib/ modules/2.6.28-omap1/modules.dep: No such file or directory eth0: unknown interface: No such device modprobe: FATAL: Could not load /lib/modules/2.6.28-omap1/modules.dep: No such file or directory modprobe: FATAL: Could not load /lib/modules/2.6.28-omap1/modules.dep: No such file or directory eth0 No such device modprobe: FATAL: Could not load /lib/modules/2.6.28-omap1/modules.dep: No such file or directory udhcpc: SIOCGIFINDEX: No such device done. Tue Jan 13 21:06:00 GMT 2009 INIT: Entering runlevel: 5 Configuring leds: beagleboard::pmu_st: none beagleboard::usr0: heartbeat beagleboard::usr1: mmc0 ALSA: Restoring mixer settings... modprobe: FATAL: Could not load /lib/modules/2.6.28-omap1/modules.dep: No such file or directory dropbear. (failed.) [ ok ] Running ntpdate to synchronize clockError : Temporary failure in name resolution . .-------. | | .-. | | |-----.-----.-----.| | .----..-----.-----. | | | __ | ---'| '--.| .-'| | | | | | | | |--- || --'| | | ' | | | | '---'---'--'--'--. |-----''----''--' '-----'-'-'-' -' | '---' The Angstrom Distribution beagleboard ttyS2 Angstrom 2009.X-test-20090102 beagleboard ttyS2 beagleboard login: root root@beagleboard:~# ls /de\b\b\broot@beagleboard:~# ls /dev/fb\a\b \broot@beagleboard:~# ls /dev/full root@beagleboard:~# ls /dev/full pm- kernel root@beagleboard:~# find /sy\b\b\broot@beagleboard:~# find /sys/| grep CPU root@beagleboard:~# root@beagleboard:~# find /sys/| grep CPU\b \b\b \b\b \bpcu\b \b\b \b\b \bcpu /sys/devices/system/cpu /sys/devices/system/cpu/online /sys/devices/system/cpu/possible /sys/devices/system/cpu/present /sys/devices/system/cpu/cpuidle /sys/devices/system/cpu/cpuidle/current_driver /sys/devices/system/cpu/cpuidle/current_governor_ro /sys/devices/system/cpu/cpu0 /sys/devices/system/cpu/cpu0/crash_notes /sys/devices/system/cpu/cpu0/cpuidle /sys/devices/system/cpu/cpu0/cpuidle/state0 /sys/devices/system/cpu/cpu0/cpuidle/state0/name /sys/devices/system/cpu/cpu0/cpuidle/state0/desc /sys/devices/system/cpu/cpu0/cpuidle/state0/latency /sys/devices/system/cpu/cpu0/cpuidle/state0/power /sys/devices/system/cpu/cpu0/cpuidle/state0/usage /sys/devices/system/cpu/cpu0/cpuidle/state0/time /sys/devices/system/cpu/cpu0/cpuidle/state1 /sys/devices/system/cpu/cpu0/cpuidle/state1/name /sys/devices/system/cpu/cpu0/cpuidle/state1/desc /sys/devices/system/cpu/cpu0/cpuidle/state1/latency /sys/devices/system/cpu/cpu0/cpuidle/state1/power /sys/devices/system/cpu/cpu0/cpuidle/state1/usage /sys/devices/system/cpu/cpu0/cpuidle/state1/time /sys/devices/system/cpu/cpu0/cpuidle/state2 /sys/devices/system/cpu/cpu0/cpuidle/state2/name /sys/devices/system/cpu/cpu0/cpuidle/state2/desc /sys/devices/system/cpu/cpu0/cpuidle/state2/latency /sys/devices/system/cpu/cpu0/cpuidle/state2/power /sys/devices/system/cpu/cpu0/cpuidle/state2/usage /sys/devices/system/cpu/cpu0/cpuidle/state2/time /sys/devices/system/cpu/cpu0/cpuidle/state3 /sys/devices/system/cpu/cpu0/cpuidle/state3/name /sys/devices/system/cpu/cpu0/cpuidle/state3/desc /sys/devices/system/cpu/cpu0/cpuidle/state3/latency /sys/devices/system/cpu/cpu0/cpuidle/state3/power /sys/devices/system/cpu/cpu0/cpuidle/state3/usage /sys/devices/system/cpu/cpu0/cpuidle/state3/time /sys/devices/system/cpu/cpu0/cpuidle/state4 /sys/devices/system/cpu/cpu0/cpuidle/state4/name /sys/devices/system/cpu/cpu0/cpuidle/state4/desc /sys/devices/system/cpu/cpu0/cpuidle/state4/latency /sys/devices/system/cpu/cpu0/cpuidle/state4/power /sys/devices/system/cpu/cpu0/cpuidle/state4/usage /sys/devices/system/cpu/cpu0/cpuidle/state4/time /sys/devices/system/cpu/cpu0/cpuidle/state5 /sys/devices/system/cpu/cpu0/cpuidle/state5/name /sys/devices/system/cpu/cpu0/cpuidle/state5/desc /sys/devices/system/cpu/cpu0/cpuidle/state5/latency /sys/devices/system/cpu/cpu0/cpuidle/state5/power /sys/devices/system/cpu/cpu0/cpuidle/state5/usage /sys/devices/system/cpu/cpu0/cpuidle/state5/time /sys/class/misc/cpu_dma_latency /sys/class/misc/cpu_dma_latency/uevent /sys/class/misc/cpu_dma_latency/dev /sys/class/misc/cpu_dma_latency/subsystem /sys/class/misc/cpu_dma_latency/power /sys/class/misc/cpu_dma_latency/power/wakeup /sys/kernel/uids/0/cpu_share /sys/kernel/uids/1/cpu_share /sys/kernel/uids/46/cpu_share /sys/kernel/uids/47/cpu_share /sys/kernel/uids/42/cpu_share /sys/module/cpufreq /sys/module/cpufreq/parameters /sys/module/cpufreq/parameters/debug_ratelimit /sys/module/cpufreq/parameters/debug root@beagleboard:~# ls /sys/devices/system/cpu/cpu0/ cpuidle crash_notes root@beagleboard:~# cd /me\b\b\broot@beagleboard:~# cd /media/ mm\aroot@beagleboard:~# cd /media/mmcb\aroot@beagleboard:~# cd /media/ mmcblk0p1root@beagleboard:~# cd /media/mmcblk0p1/ root@beagleboard:/media/mmcblk0p1# ls broken picodlp-control_0.1-r1.1_armv7a.ipk uImage working mlo u-boot.bin untested root@beagleboard:/media/mmcblk0p1# cp wo\b\broot@beagleboard:/media/ mmcblk0p1# cp working/uI\b \b\b \b2\aroot@beagleboard:/media/mmcblk0p1# cp working/2.6.2 working/2.6.26 working/2.6.28-ehci working/2.6.27 working/2.6.28rc7 root@beagleboard:/media/mmcblk0p1# cp working/2.6.2 working/2.6.26 working/2.6.28-ehci working/2.6.27 working/2.6.28rc7 root@beagleboard:/media/mmcblk0p1# cp working/2.6.28- eroot@beagleboard:/media/mmcblk0p1# cp working/2.6.28-ehci uI\b\broot@beagleboard:/media/mmcblk0p1# cp working/2.6.28-ehci uImage ; sync ; rebootred new interface driver cdc_ether usbcore: registered new interface driver rndis_host usbcore: registered new interface driver zd1211rw usbcore: registered new interface driver rndis_wlan usbcore: registered new interface driver zd1201 usbcore: registered new interface driver usb8xxx usbcore: registered new interface driver rtl8187 usbcore: registered new interface driver rt2500usb usbcore: registered new interface driver rt73usb usbcore: registered new interface driver p54usb i2c /dev entries driver input: triton2-pwrbutton as /class/input/input0 triton2 power button driver initialized Driver 'sd' needs updating - please use bus_type methods Driver 'sr' needs updating - please use bus_type methods omap2-nand driver initializing NAND device: Manufacturer ID: 0x2c, Chip ID: 0xba (Micron NAND 256MiB 1,8V 16-bit) cmdlinepart partition parsing not available Creating 5 MTD partitions on "omap2-nand": 0x00000000-0x00080000 : "X-Loader" 0x00080000-0x00260000 : "U-Boot" 0x00260000-0x00280000 : "U-Boot Env" 0x00280000-0x00680000 : "Kernel" 0x00680000-0x10000000 : "File System" ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver ehci-omap ehci-omap.0: OMAP-EHCI Host Controller ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 1 ehci-omap ehci-omap.0: irq 77, io mem 0x48064800 usb usb1: configuration #1 chosen from 1 choice hub 1-0:1.0: USB hub found hub 1-0:1.0: 3 ports detected Initializing USB Mass Storage driver... usbcore: registered new interface driver usb-storage USB Mass Storage support registered. mice: PS/2 mouse device common for all mice input: gpio-keys as /class/input/input1 twl4030_rtc twl4030_rtc: rtc core: registered twl4030_rtc as rtc0 OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec Bluetooth: HCI USB driver ver 2.10 usbcore: registered new interface driver hci_usb Bluetooth: Broadcom Blutonium firmware driver ver 1.2 usbcore: registered new interface driver bcm203x Bluetooth: Digianswer Bluetooth USB driver ver 0.10 usbcore: registered new interface driver bpa10x Bluetooth: Generic Bluetooth SDIO driver ver 0.1 mmci-omap-hs mmci-omap-hs.0: Failed to get debounce clock Registered led device: beagleboard::usr0 Registered led device: beagleboard::usr1 leds-gpio: probe of leds-gpio failed with error -22 usbcore: registered new interface driver usbhid usbhid: v2.6:USB HID core driver Advanced Linux Sound Architecture Driver Version 1.0.18rc3. usbcore: registered new interface driver snd-usb-audio ASoC version 0.13.2 OMAP3 Beagle SoC init TWL4030 Audio Codec init asoc: twl4030 <-> omap-mcbsp-dai-(link_id) mapping ok ALSA device list: #0: omap3beagle (twl4030) oprofile: using arm/armv7 TCP cubic registered NET: Registered protocol family 17 NET: Registered protocol family 15 Bluetooth: L2CAP ver 2.11 Bluetooth: L2CAP socket layer initialized Bluetooth: SCO (Voice Link) ver 0.6 Bluetooth: SCO socket layer initialized usb 1-2: new high speed USB device using ehci-omap and address 2 Bluetooth: RFCOMM socket layer initialized Bluetooth: RFCOMM TTY layer initialized Bluetooth: RFCOMM ver 1.10 Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Bluetooth: BNEP filters: protocol multicast Bluetooth: HIDP (Human Interface Emulation) ver 1.2 RPC: Registered udp transport module. RPC: Registered tcp transport module. ieee80211: 802.11 data/management/control stack, git-1.1.13 ieee80211: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com > ieee80211_crypt: registered algorithm 'NULL' ieee80211_crypt: registered algorithm 'WEP' ieee80211_crypt: registered algorithm 'CCMP' ieee80211_crypt: registered algorithm 'TKIP' ThumbEE CPU extension supported. Power Management for TI OMAP3. SmartReflex driver initialized Disabling unused clock "sr2_fck" Disabling unused clock "sr1_fck" Disabling unused clock "mcbsp_fck" Disabling unused clock "mcbsp_fck" Disabling unused clock "mcbsp_fck" Disabling unused clock "mcbsp_ick" Disabling unused clock "mcbsp_ick" Disabling unused clock "mcbsp_ick" Disabling unused clock "gpt2_ick" Disabling unused clock "gpt3_ick" Disabling unused clock "gpt4_ick" Disabling unused clock "gpt5_ick" Disabling unused clock "gpt6_ick" Disabling unused clock "gpt7_ick" Disabling unused clock "gpt8_ick" Disabling unused clock "gpt9_ick" Disabling unused clock "wdt3_ick" Disabling unused clock "wdt3_fck" Disabling unused clock "gpio2_dbck" Disabling unused clock "gpio3_dbck" Disabling unused clock "gpio4_dbck" Disabling unused clock "gpio5_dbck" Disabling unused clock "gpio6_dbck" Disabling unused clock "gpt9_fck" Disabling unused clock "gpt8_fck" Disabling unused clock "gpt7_fck" Disabling unused clock "gpt6_fck" Disabling unused clock "gpt5_fck" Disabling unused clock "gpt4_fck" Disabling unused clock "gpt3_fck" Disabling unused clock "gpt2_fck" Disabling unused clock "gpt1_ick" Disabling unused clock "wdt1_ick" Disabling unused clock "wdt2_ick" Disabling unused clock "wdt2_fck" Disabling unused clock "gpio1_dbck" Disabling unused clock "gpt1_fck" Disabling unused clock "cam_ick" Disabling unused clock "cam_mclk" Disabling unused clock "des1_ick" Disabling unused clock "sha11_ick" Disabling unused clock "rng_ick" Disabling unused clock "aes1_ick" Disabling unused clock "ssi_ick" Disabling unused clock "mailboxes_ick" Disabling unused clock "mcbsp_ick" Disabling unused clock "mcbsp_ick" Disabling unused clock "gpt10_ick" Disabling unused clock "gpt11_ick" Disabling unused clock "i2c_ick" Disabling unused clock "mcspi_ick" Disabling unused clock "mcspi_ick" Disabling unused clock "mcspi_ick" Disabling unused clock "mcspi_ick" Disabling unused clock "hdq_ick" Disabling unused clock "mspro_ick" Disabling unused clock "des2_ick" Disabling unused clock "sha12_ick" Disabling unused clock "aes2_ick" Disabling unused clock "icr_ick" Disabling unused clock "pka_ick" Disabling unused clock "ssi_ssr_fck" Disabling unused clock "hdq_fck" Disabling unused clock "mcspi_fck" Disabling unused clock "mcspi_fck" Disabling unused clock "mcspi_fck" Disabling unused clock "mcspi_fck" Disabling unused clock "mcbsp_fck" Disabling unused clock "mcbsp_fck" Disabling unused clock "i2c_fck" Disabling unused clock "mspro_fck" Disabling unused clock "gpt11_fck" Disabling unused clock "gpt10_fck" Disabling unused clock "iva2_ck" Disabling unused clock "dpll4_m6x2_ck" Disabling unused clock "dpll4_m5x2_ck" Disabling unused clock "dpll3_m3x2_ck" Disabling unused clock "sys_clkout1" VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 1 OMAPFB: omapfb_init OMAPFB: omapfb_probe OMAPFB: create 3 framebuffers OMAPFB: fb_infos allocated param '4M' param '4M' OMAPFB: allocating 4194304 bytes for fb 0 OMAPFB: allocated VRAM paddr 80750000, vaddr d1000000 OMAPFB: allocating 4194304 bytes for fb 1 OMAPFB: allocated VRAM paddr 80b50000, vaddr d1400000 OMAPFB: region0 phys 80750000 virt d1000000 size=4194304 OMAPFB: region1 phys 80b50000 virt d1400000 size=4194304 OMAPFB: region2 phys 00000000 virt 00000000 size=0 OMAPFB: fbmems allocated OMAPFB: check_fb_var 0 OMAPFB: xres = 640, yres = 480, vxres = 640, vyres = 480 OMAPFB: set_fb_fix OMAPFB: check_fb_var 1 OMAPFB: xres = 640, yres = 480, vxres = 640, vyres = 480 OMAPFB: set_fb_fix OMAPFB: check_fb_var 2 OMAPFB: set_fb_fix OMAPFB: fb_infos initialized OMAPFB: set_par(0) OMAPFB: set_fb_fix OMAPFB: apply_changes, fb 0, ovl 0 OMAPFB: setup_overlay 0 omap-dss DISPLAY: omap_dss_mgr_apply(lcd) omap-dss DISPC: dispc_enable_plane 0, 0 omap-dss DISPC: dispc_enable_plane 1, 0 omap-dss DISPC: dispc_enable_plane 2, 0 omap-dss DSS: save context OMAPFB: pan_display(0) OMAPFB: setcmap OMAPFB: setcmap Console: switching to colour frame buffer device 80x30 OMAPFB: pan_display(0) OMAPFB: setcmap OMAPFB: setcmap OMAPFB: framebuffers registered OMAPFB: apply_changes, fb 0, ovl 0 OMAPFB: setup_overlay 0 OMAPFB: apply_changes, fb 1, ovl 1 OMAPFB: setup_overlay 1 OMAPFB: apply_changes, fb 2, ovl 2 OMAPFB: create_framebuffers done omap-dss DISPLAY: omap_dss_mgr_apply(lcd) omap-dss DISPC: dispc_setup_plane 0, 80750000, sw 640, 0,0, 640x480 -> 640x480, (ilace 0) omap-dss DISPC: dispc_enable_plane 0, 1 omap-dss DISPC: dispc_enable_plane 1, 0 omap-dss DISPC: dispc_enable_plane 2, 0 omap-dss DSS: save context omap-dss DISPLAY: omap_dss_mgr_apply(tv) omap-dss DSS: save context omap-dss DISPLAY: omap_dss_mgr_apply_l4(l4) OMAPFB: mgr->apply'ed omap-dss DSI: PLL init omap-dss DISPC: dpll4_m4 = 432000000 omap-dss DISPC: fck = 96000000 (9) omap-dss DISPC: lck = 96000000 (1) omap-dss DISPC: pck = 48000000 (2) clock: new_div = 9, new_rate = 48000000 omap-dss DSI: PLL init done omap-dss DISPC: fifo(0) size 1024, low/high old 960/1023, new 256/960 omap-dss DISPC: fifo(1) size 1024, low/high old 960/1023, new 256/960 omap-dss DISPC: fifo(2) size 1024, low/high old 960/1023, new 256/960 omap-dss DISPC: onoff 0 rf 0 ieo 0 ipc 0 ihs 0 ivs 0 acbi 0 acb 0 omap-dss DSI: dsi_pll_calc omap-dss DSI: dsi_pll_program omap-dss DSI: DSI Fint 1857142 omap-dss DSI: clkin (dss2_fck) rate 13000000, highfreq 0 omap-dss DSI: DSIPHY = 2 * 329 / 7 * 13000000 / 1 = 1222000000 omap-dss DSI: Data rate on 1 DSI lane 611 Mbps omap-dss DSI: Clock lane freq 305500000 Hz omap-dss DSI: regm3 = 13, dsi1_pll_fclk = 94000000 omap-dss DSI: regm4 = 16, dsi2_pll_fclk = 76375000 omap-dss DSI: PLL config done omap-dss DISPC: xres 640 yres 480 omap-dss DISPC: pck 23500 omap-dss DISPC: hsw 32 hfp 48 hbp 80 vsw 4 vfp 3 vbp 7 omap-dss DISPC: hsync 29375Hz, vsync 59Hz OMAPFB: display->updated DISPC IRQ: 0x4024: SYNC_LOST omap-dss DISPC error: dispc irq error status 4024 DISPC IRQ: 0x4000: SYNC_LOST omap-dss DISPC error: dispc irq error status 4000 DISPC IRQ: 0x4000: SYNC_LOST omap-dss DISPC error: dispc irq error status 4000 DISPC IRQ: 0x4022: SYNC_LOST omap-dss DISPC error: dispc irq error status 4022 DISPC IRQ: 0x4000: SYNC_LOST omap-dss DISPC error: dispc irq error status 4000 DISPC IRQ: 0x4022: SYNC_LOST omap-dss DISPC error: dispc irq error status 4022 DISPC IRQ: 0x4000: SYNC_LOST omap-dss DISPC error: dispc irq error status 4000 DISPC IRQ: 0x4022: SYNC_LOST omap-dss DISPC error: dispc irq error status 4022 DISPC IRQ: 0x4000: SYNC_LOST omap-dss DISPC error: dispc irq error status 4000 DISPC IRQ: 0x4002: SYNC_LOST omap-dss DISPC error: dispc irq error status 4002 DISPC IRQ: 0x4020: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4022: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4022: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4022: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4022: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST OMAPFB: sysfs created DISPC IRQ: 0x4022: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4022: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4022: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4022: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4022: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4022: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4022: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4022: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4022: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4022: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4022: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST DISPC IRQ: 0x4000: SYNC_LOST omap-dss DISPC error: Excessive DISPC errors Turning off lcd and digit DISPC IRQ: 0x4022: SYNC_LOST omap-dss DISPC error: Excessive DISPC errors Turning off lcd and digit DISPC IRQ: 0x4000: SYNC_LOST omap-dss DISPC error: Excessive DISPC errors Turning off lcd and digit DISPC IRQ: 0x4003: SYNC_LOST omap-dss DISPC error: Excessive DISPC errors Turning off lcd and digit usb 1-2: configuration #1 chosen from 1 choice twl4030_rtc twl4030_rtc: setting system clock to 2009-01-13 21:11:13 UTC (1231881073) hub 1-2:1.0: USB hub found hub 1-2:1.0: 4 ports detected mmc0: new SDHC card at address 8fe4 mmcblk0: mmc0:8fe4 SD08G 7.40 GiB mmcblk0: p1 p2 p3 EXT3-fs warning: maximal mount count reached, running e2fsck is recommended EXT3 FS on mmcblk0p2, internal journal EXT3-fs: mounted filesystem with ordered data mode. VFS: Mounted root (ext3 filesystem). Freeing init memory: 188K If you have read till down here: still no cpufreq while the board file has the rate tables and the initcall: --- /tmp/board-omap3beagle.c 2009-01-12 15:46:26.000000000 +0100 +++ git/arch/arm/mach-omap2/board-omap3beagle.c 2009-01-12 15:46:28.000000000 +0100 @@ -41,14 +41,73 @@ #include <mach/usb-ehci.h> #include <mach/common.h> #include <mach/gpmc.h> +#include <mach/omap-pm.h> #include <mach/nand.h> #include <mach/mux.h> #include <mach/omapfb.h> #include <mach/display.h> +#include <mach/clock.h> + #include "twl4030-generic-scripts.h" #include "mmc-twl4030.h" +#include "pm.h" + +/* MPU speeds */ +#define S600M 600000000 +#define S550M 550000000 +#define S500M 500000000 +#define S250M 250000000 +#define S125M 125000000 + +/* DSP speeds */ +#define S430M 430000000 +#define S400M 400000000 +#define S360M 360000000 +#define S180M 180000000 +#define S90M 90000000 + +/* L3 speeds */ +#define S83M 83000000 +#define S166M 166000000 + +static struct omap_opp mpu_rate_table[] = { + {0, 0, 0}, + /*OPP1*/ + {S125M, VDD1_OPP1, 0x18}, + /*OPP2*/ + {S250M, VDD1_OPP2, 0x20}, + /*OPP3*/ + {S500M, VDD1_OPP3, 0x30}, + /*OPP4*/ + {S550M, VDD1_OPP4, 0x36}, + /*OPP5*/ + {S600M, VDD1_OPP5, 0x3C}, +}; +static struct omap_opp l3_rate_table[] = { + {0, 0, 0}, + /*OPP1*/ + {0, VDD2_OPP1, 0x18}, + /*OPP2*/ + {S83M, VDD2_OPP2, 0x20}, + /*OPP3*/ + {S166M, VDD2_OPP3, 0x2C}, +}; + +struct omap_opp dsp_rate_table[] = { + {0, 0, 0}, + /*OPP1*/ + {S90M, VDD1_OPP1, 0x18}, + /*OPP2*/ + {S180M, VDD1_OPP2, 0x20}, + /*OPP3*/ + {S360M, VDD1_OPP3, 0x30}, + /*OPP4*/ + {S400M, VDD1_OPP4, 0x36}, + /*OPP5*/ + {S430M, VDD1_OPP5, 0x3C}, +}; #define GPMC_CS0_BASE 0x60 #define GPMC_CS_SIZE 0x30 @@ -227,7 +294,8 @@ static void __init omap3_beagle_init_irq(void) { - omap2_init_common_hw(mt46h32m32lf6_sdrc_params, NULL, NULL, NULL); + omap2_init_common_hw(mt46h32m32lf6_sdrc_params, mpu_rate_table, + dsp_rate_table, l3_rate_table); omap_init_irq(); omap_gpio_init(); } regards, Koen [-- Attachment #2: Dit deel van het bericht is digitaal ondertekend --] [-- Type: application/pgp-signature, Size: 186 bytes --] ^ permalink raw reply [flat|nested] 40+ messages in thread
* Re: new PM branch available 2009-01-14 7:35 ` Koen Kooi @ 2009-01-14 18:09 ` David Brownell 2009-01-14 22:14 ` Kevin Hilman 1 sibling, 0 replies; 40+ messages in thread From: David Brownell @ 2009-01-14 18:09 UTC (permalink / raw) To: Koen Kooi; +Cc: linux-omap@vger.kernel.org List On Tuesday 13 January 2009, Koen Kooi wrote: > ------------[ cut here ]------------ > WARNING: at arch/arm/mach-omap2/clock.c:1094 omap2_clk_register > +0x24/0x3c() > Modules linked in: > [<c003b824>] (dump_stack+0x0/0x14) from [<c005b180>] (warn_on_slowpath > +0x4c/0x68) Just in the cause of better diagnostics ... that looks like maybe if (!clk->clkdm.name) { pr_debug("clock: %s: missing clockdomain", clk->name); WARN_ON(1); return -EINVAL; } triggered. A better way to write that, in recent kernels, is if (WARN(!clk->clkdm.name, "clock: %s missing clockdomain\n", clk->name)) return -EINVAL; Where "better" includes "diagnostic message is always present" and thus "line numbers matter less". (Line 1094 in my kernel is the right bracket above, not the WARN_ON...) - Dave ^ permalink raw reply [flat|nested] 40+ messages in thread
* Re: new PM branch available 2009-01-14 7:35 ` Koen Kooi 2009-01-14 18:09 ` David Brownell @ 2009-01-14 22:14 ` Kevin Hilman 2009-01-15 8:18 ` Koen Kooi 1 sibling, 1 reply; 40+ messages in thread From: Kevin Hilman @ 2009-01-14 22:14 UTC (permalink / raw) To: Koen Kooi; +Cc: linux-omap@vger.kernel.org List Koen Kooi <k.kooi@student.utwente.nl> writes: > Op 13 jan 2009, om 22:51 heeft Kevin Hilman het volgende geschreven: > >> Hello, >> >> The latest PM branch is now available[1]. >> >> I've done basic testing of retention and off-mode (suspend and dynamic >> idle) on Beagle and custom HW. My SDP has something still keeping >> CORE active that others have not seen, but I have yet to debug. Any >> other reports from SDP testing would be appreciated. >> >> Notable changes/updates >> - rebased on latest clock updates and fixes from Paul >> - clockfw pre- and post- notifiers >> - DVFS for VDD2 > > The bootlog on my rev C1D beagle looks suspicious: > Hi Koen, Hmm, it looks like you're tree is missing the McBSP fix from Paul[1]. This patch made it in before v2.6.28-omap1 which the latest PM branch is based on, so I'm guessing you're not testing the latest PM branch. Kevin > Texas Instruments X-Loader 1.4.2 (Dec 3 2008 - 23:20:13) > Reading boot sector > Booting from mmc > > > U-Boot 2009.01-rc1-00102-g8ecaab3 (Jan 10 2009 - 13:56:28) > > OMAP3530-GP rev 2, CPU-OPP2 L3-165MHz > OMAP3 Beagle board + LPDDR/NAND > DRAM: 256 MB > NAND: 256 MiB > musb: using high speed > In: serial > Out: serial > Err: serial > Board revision: Cx > Debug (GPIO6 datain): 0x04800000 > Hit any key to stop autoboot: 1 \b\b\b 0 > reading boot.scr > > ** Unable to read "boot.scr" from mmc 0:1 ** > reading uImage > > 2556572 bytes read > Booting from mmc ... > ## Booting kernel from Legacy Image at 82000000 ... > Image Name: Angstrom/2.6.28-pm1+gitrb5d11429 > Image Type: ARM Linux Kernel Image (uncompressed) > Data Size: 2556508 Bytes = 2.4 MB > Load Address: 80008000 > Entry Point: 80008000 > Verifying Checksum ... OK > Loading Kernel Image ... OK > OK > > > Uncompressing Linux > .................................................................................................................................................................... done > , booting the kernel. > Linux version 2.6.28-omap1 (koen@dominion) (gcc version 4.2.1) #1 Sun > Jan 11 18:52:51 CET 2009 > CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), cr=10c5387f > CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache > Machine: OMAP3 Beagle Board > Memory policy: ECC disabled, Data cache writeback > On node 0 totalpages: 65536 > free_area_init_node: node 0, pgdat c050be14, node_mem_map c0540000 > Normal zone: 512 pages used for memmap > Normal zone: 0 pages reserved > Normal zone: 65024 pages, LIFO batch:15 > Movable zone: 0 pages used for memmap > OMAP3430 ES3.0 > SRAM: Mapped pa 0x40200000 to va 0xd7000000 size: 0x100000 > Built 1 zonelists in Zone order, mobility grouping on. Total pages: > 65024 > Kernel command line: console=ttyS2,115200n8 video=omapfb:vram:2M,vram: > 4M,mode:640x480@60 omapfb.debug=y omap-dss.debug=y loglevel=10 > omapfb.vram=4M,4M root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait > Unknown boot option `omapfb.debug=y': ignoring > Unknown boot option `omap-dss.debug=y': ignoring > Unknown boot option `omapfb.vram=4M,4M': ignoring > Clocking rate (Crystal/DPLL/ARM core): 26.0/332/500 MHz > GPMC revision 5.0 > IRQ: Found an INTC at 0xd8200000 (revision 4.0) with 96 interrupts > Total of 96 interrupts on 1 active controller > OMAP34xx GPIO hardware version 2.5 > PID hash table entries: 1024 (order: 10, 4096 bytes) > OMAP clockevent source: GPTIMER12 at 32768 Hz > Console: colour dummy device 80x30 > Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) > Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) > Memory: 128MB 128MB = 256MB total > Memory: 254336KB available (4712K code, 428K data, 188K init) > Calibrating delay loop... 478.91 BogoMIPS (lpj=1867776) > Mount-cache hash table entries: 512 > CPU: Testing write buffer coherency: ok > net_namespace: 532 bytes > regulator: core version 0.5 > NET: Registered protocol family 16 > Found NAND on CS0 > Registering NAND on CS0 > ------------[ cut here ]------------ > WARNING: at arch/arm/mach-omap2/clock.c:1094 omap2_clk_register > +0x24/0x3c() > Modules linked in: > [<c003b824>] (dump_stack+0x0/0x14) from [<c005b180>] (warn_on_slowpath > +0x4c/0x68) > [<c005b134>] (warn_on_slowpath+0x0/0x68) from [<c00416a8>] > (omap2_clk_register+0x24/0x3c) > r6:c04de968 r5:c04d82d8 r4:c04d8270 > [<c0041684>] (omap2_clk_register+0x0/0x3c) from [<c0048854>] > (clk_register+0x44/0xc8) > [<c0048810>] (clk_register+0x0/0xc8) from [<c00113ec>] > (omap2_mcbsp_init+0xc8/0x130) > r7:c0469ded r6:00000008 r5:c04d82d8 r4:c04d8270 > [<c0011324>] (omap2_mcbsp_init+0x0/0x130) from [<c00372d4>] > (do_one_initcall+0x64/0x198) > [<c0037270>] (do_one_initcall+0x0/0x198) from [<c0008718>] > (kernel_init +0x70/0xdc) > [<c00086a8>] (kernel_init+0x0/0xdc) from [<c005db54>] (do_exit > +0x0/0x6b4) > r5:00000000 r4:00000000 > ---[ end trace 1b75b31a2719ed1c ]--- > ------------[ cut here ]------------ > WARNING: at arch/arm/mach-omap2/clock.c:1094 omap2_clk_register > +0x24/0x3c() > Modules linked in: > [<c003b824>] (dump_stack+0x0/0x14) from [<c005b180>] (warn_on_slowpath > +0x4c/0x68) > [<c005b134>] (warn_on_slowpath+0x0/0x68) from [<c00416a8>] > (omap2_clk_register+0x24/0x3c) > r6:c04de968 r5:c04d8340 r4:c04d82d8 > [<c0041684>] (omap2_clk_register+0x0/0x3c) from [<c0048854>] > (clk_register+0x44/0xc8) > [<c0048810>] (clk_register+0x0/0xc8) from [<c00113ec>] > (omap2_mcbsp_init+0xc8/0x130) > r7:c0469ded r6:00000008 r5:c04d8340 r4:c04d8270 > [<c0011324>] (omap2_mcbsp_init+0x0/0x130) from [<c00372d4>] > (do_one_initcall+0x64/0x198) > [<c0037270>] (do_one_initcall+0x0/0x198) from [<c0008718>] > (kernel_init +0x70/0xdc) > [<c00086a8>] (kernel_init+0x0/0xdc) from [<c005db54>] (do_exit > +0x0/0x6b4) > r5:00000000 r4:00000000 > ---[ end trace 1b75b31a2719ed1c ]--- > ------------[ cut here ]------------ > WARNING: at arch/arm/mach-omap2/clock.c:1094 omap2_clk_register > +0x24/0x3c() > Modules linked in: > [<c003b824>] (dump_stack+0x0/0x14) from [<c005b180>] (warn_on_slowpath > +0x4c/0x68) > [<c005b134>] (warn_on_slowpath+0x0/0x68) from [<c00416a8>] > (omap2_clk_register+0x24/0x3c) > r6:c04de968 r5:c04d83a8 r4:c04d8340 > [<c0041684>] (omap2_clk_register+0x0/0x3c) from [<c0048854>] > (clk_register+0x44/0xc8) > [<c0048810>] (clk_register+0x0/0xc8) from [<c00113ec>] > (omap2_mcbsp_init+0xc8/0x130) > r7:c0469ded r6:00000008 r5:c04d83a8 r4:c04d8270 > [<c0011324>] (omap2_mcbsp_init+0x0/0x130) from [<c00372d4>] > (do_one_initcall+0x64/0x198) > [<c0037270>] (do_one_initcall+0x0/0x198) from [<c0008718>] > (kernel_init +0x70/0xdc) > [<c00086a8>] (kernel_init+0x0/0xdc) from [<c005db54>] (do_exit > +0x0/0x6b4) > r5:00000000 r4:00000000 > ---[ end trace 1b75b31a2719ed1c ]--- > ------------[ cut here ]------------ > WARNING: at arch/arm/mach-omap2/clock.c:1094 omap2_clk_register > +0x24/0x3c() > Modules linked in: > [<c003b824>] (dump_stack+0x0/0x14) from [<c005b180>] (warn_on_slowpath > +0x4c/0x68) > [<c005b134>] (warn_on_slowpath+0x0/0x68) from [<c00416a8>] > (omap2_clk_register+0x24/0x3c) > r6:c04de968 r5:c04d8410 r4:c04d83a8 > [<c0041684>] (omap2_clk_register+0x0/0x3c) from [<c0048854>] > (clk_register+0x44/0xc8) > [<c0048810>] (clk_register+0x0/0xc8) from [<c00113ec>] > (omap2_mcbsp_init+0xc8/0x130) > r7:c0469ded r6:00000008 r5:c04d8410 r4:c04d8270 > [<c0011324>] (omap2_mcbsp_init+0x0/0x130) from [<c00372d4>] > (do_one_initcall+0x64/0x198) > [<c0037270>] (do_one_initcall+0x0/0x198) from [<c0008718>] > (kernel_init +0x70/0xdc) > [<c00086a8>] (kernel_init+0x0/0xdc) from [<c005db54>] (do_exit > +0x0/0x6b4) > r5:00000000 r4:00000000 > ---[ end trace 1b75b31a2719ed1c ]--- > ------------[ cut here ]------------ > WARNING: at arch/arm/mach-omap2/clock.c:1094 omap2_clk_register > +0x24/0x3c() > Modules linked in: > [<c003b824>] (dump_stack+0x0/0x14) from [<c005b180>] (warn_on_slowpath > +0x4c/0x68) > [<c005b134>] (warn_on_slowpath+0x0/0x68) from [<c00416a8>] > (omap2_clk_register+0x24/0x3c) > r6:c04de968 r5:c04d8478 r4:c04d8410 > [<c0041684>] (omap2_clk_register+0x0/0x3c) from [<c0048854>] > (clk_register+0x44/0xc8) > [<c0048810>] (clk_register+0x0/0xc8) from [<c00113ec>] > (omap2_mcbsp_init+0xc8/0x130) > r7:c0469ded r6:00000008 r5:c04d8478 r4:c04d8270 > [<c0011324>] (omap2_mcbsp_init+0x0/0x130) from [<c00372d4>] > (do_one_initcall+0x64/0x198) > [<c0037270>] (do_one_initcall+0x0/0x198) from [<c0008718>] > (kernel_init +0x70/0xdc) > [<c00086a8>] (kernel_init+0x0/0xdc) from [<c005db54>] (do_exit > +0x0/0x6b4) > r5:00000000 r4:00000000 > ---[ end trace 1b75b31a2719ed1c ]--- > omap-mcbsp omap-mcbsp.1: Invalid clock configuration for McBSP1. > omap-mcbsp: probe of omap-mcbsp.1 failed with error -2 > omap-mcbsp omap-mcbsp.2: Invalid clock configuration for McBSP2. > omap-mcbsp: probe of omap-mcbsp.2 failed with error -2 > omap-mcbsp omap-mcbsp.3: Invalid clock configuration for McBSP3. > omap-mcbsp: probe of omap-mcbsp.3 failed with error -2 > omap-mcbsp omap-mcbsp.4: Invalid clock configuration for McBSP4. > omap-mcbsp: probe of omap-mcbsp.4 failed with error -2 > omap-mcbsp omap-mcbsp.5: Invalid clock configuration for McBSP5. > omap-mcbsp: probe of omap-mcbsp.5 failed with error -2 > OMAP DMA hardware revision 4.0 > USB: No board-specific platform config found > i2c_omap i2c_omap.1: bus 1 rev3.12 at 2600 kHz > twl4030: PIH (irq 7) chaining IRQs 368..375 > twl4030: power (irq 373) chaining IRQs 376..383 > twl4030: gpio (irq 368) chaining IRQs 384..401 > i2c_omap i2c_omap.3: bus 3 rev3.12 at 400 kHz > SCSI subsystem initialized > twl4030_usb twl4030_usb: Initialized TWL4030 USB module > usbcore: registered new interface driver usbfs > usbcore: registered new interface driver hub > usbcore: registered new device driver usb > musb_hdrc: version 6.0, musb-dma, otg (peripheral+host), debug=0 > musb_hdrc: ConfigData=0x33 (UTMI-16, HB-ISO Rx (X), SoftConn) > musb_hdrc: MHDRC RTL version 1.400 > musb_core_init 1405: reconfigure software for static FIFOs > musb_hdrc musb_hdrc: musb_init_controller failed with status -19 > regulator: VMMC1: 1850 <--> 3150 mV normal standby > regulator: VDAC: 1800 mV normal standby > regulator: VUSB1V5: 1500 mV normal standby > regulator: VUSB1V8: 1800 mV normal standby > regulator: VUSB3V1: 3100 mV normal standby > regulator: VSIM: 1800 <--> 3000 mV normal standby > Bluetooth: Core ver 2.13 > NET: Registered protocol family 31 > Bluetooth: HCI device and connection manager initialized > Bluetooth: HCI socket layer initialized > cfg80211: Using static regulatory domain info > cfg80211: Regulatory domain: US > (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm) > (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm) > (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm) > (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm) > (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm) > (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm) > cfg80211: Calling CRDA for country: US > NET: Registered protocol family 2 > Switched to high resolution mode on CPU 0 > IP route cache hash table entries: 2048 (order: 1, 8192 bytes) > TCP established hash table entries: 8192 (order: 4, 65536 bytes) > TCP bind hash table entries: 8192 (order: 3, 32768 bytes) > TCP: Hash tables configured (established 8192 bind 8192) > TCP reno registered > NET: Registered protocol family 1 > VFS: Disk quotas dquot_6.5.1 > Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) > JFFS2 version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc. > msgmni has been set to 497 > alg: No test for stdrng (krng) > io scheduler noop registered > io scheduler anticipatory registered > io scheduler deadline registered > io scheduler cfq registered (default) > Serial: 8250/16550 driver4 ports, IRQ sharing enabled > serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654 > serial8250.0: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654 > serial8250.0: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654 > console [ttyS2] enabled > brd: module loaded > loop: module loaded > usbcore: registered new interface driver asix > usbcore: registered new interface driver cdc_ether > usbcore: registered new interface driver rndis_host > usbcore: registered new interface driver zd1211rw > usbcore: registered new interface driver rndis_wlan > usbcore: registered new interface driver zd1201 > usbcore: registered new interface driver usb8xxx > usbcore: registered new interface driver rtl8187 > usbcore: registered new interface driver rt2500usb > usbcore: registered new interface driver rt73usb > usbcore: registered new interface driver p54usb > i2c /dev entries driver > input: triton2-pwrbutton as /class/input/input0 > triton2 power button driver initialized > Driver 'sd' needs updating - please use bus_type methods > Driver 'sr' needs updating - please use bus_type methods > omap2-nand driver initializing > NAND device: Manufacturer ID: 0x2c, Chip ID: 0xba (Micron NAND 256MiB > 1,8V 16-bit) > cmdlinepart partition parsing not available > Creating 5 MTD partitions on "omap2-nand": > 0x00000000-0x00080000 : "X-Loader" > 0x00080000-0x00260000 : "U-Boot" > 0x00260000-0x00280000 : "U-Boot Env" > 0x00280000-0x00680000 : "Kernel" > 0x00680000-0x10000000 : "File System" > ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver > ehci-omap ehci-omap.0: OMAP-EHCI Host Controller > ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 1 > ehci-omap ehci-omap.0: irq 77, io mem 0x48064800 > usb usb1: configuration #1 chosen from 1 choice > hub 1-0:1.0: USB hub found > hub 1-0:1.0: 3 ports detected > Initializing USB Mass Storage driver... > usbcore: registered new interface driver usb-storage > USB Mass Storage support registered. > mice: PS/2 mouse device common for all mice > input: gpio-keys as /class/input/input1 > twl4030_rtc twl4030_rtc: rtc core: registered twl4030_rtc as rtc0 > twl4030_rtc twl4030_rtc: Power up reset detected. > twl4030_rtc twl4030_rtc: Enabling TWL4030-RTC. > OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec > Bluetooth: HCI USB driver ver 2.10 > usbcore: registered new interface driver hci_usb > Bluetooth: Broadcom Blutonium firmware driver ver 1.2 > usbcore: registered new interface driver bcm203x > Bluetooth: Digianswer Bluetooth USB driver ver 0.10 > usbcore: registered new interface driver bpa10x > Bluetooth: Generic Bluetooth SDIO driver ver 0.1 > cpuidle: using governor ladder > cpuidle: using governor menu > mmci-omap-hs mmci-omap-hs.0: Failed to get debounce clock > Registered led device: beagleboard::usr0 > Registered led device: beagleboard::usr1 > Registered led device: beagleboard::pmu_stat > usbcore: registered new interface driver usbhid > usbhid: v2.6:USB HID core driver > Advanced Linux Sound Architecture Driver Version 1.0.18rc3. > usbcore: registered new interface driver snd-usb-audio > ASoC version 0.13.2 > OMAP3 Beagle SoC init > TWL4030 Audio Codec init > asoc: twl4030 <-> omap-mcbsp-dai-(link_id) mapping ok > ALSA device list: > #0: omap3beagle (twl4030) > oprofile: using arm/armv7 > TCP cubic registered > NET: Registered protocol family 17 > NET: Registered protocol family 15 > Bluetooth: L2CAP ver 2.11 > Bluetooth: L2CAP socket layer initialized > Bluetooth: SCO (Voice Link) ver 0.6 > Bluetooth: SCO socket layer initialized > Bluetooth: RFCOMM socket layer initialized > Bluetooth: RFCOMM TTY layer initialized > Bluetooth: RFCOMM ver 1.10 > Bluetooth: BNEP (Ethernet Emulation) ver 1.3 > Bluetooth: BNEP filters: protocol multicast > Bluetooth: HIDP (Human Interface Emulation) ver 1.2 > RPC: Registered udp transport module. > RPC: Registered tcp transport module. > ieee80211: 802.11 data/management/control stack, git-1.1.13 > ieee80211: Copyright (C) 2004-2005 Intel Corporation > <jketreno@linux.intel.com >> > ieee80211_crypt: registered algorithm 'NULL' > ieee80211_crypt: registered algorithm 'WEP' > ieee80211_crypt: registered algorithm 'CCMP' > ieee80211_crypt: registered algorithm 'TKIP' > ThumbEE CPU extension supported. > Power Management for TI OMAP3. > pm_dbg_init() > SmartReflex driver initialized > Disabling unused clock "sr2_fck" > Disabling unused clock "sr1_fck" > Disabling unused clock "mcbsp_fck" > Disabling unused clock "mcbsp_fck" > Disabling unused clock "mcbsp_fck" > Disabling unused clock "mcbsp_ick" > Disabling unused clock "mcbsp_ick" > Disabling unused clock "mcbsp_ick" > Disabling unused clock "gpt2_ick" > Disabling unused clock "gpt3_ick" > Disabling unused clock "gpt4_ick" > Disabling unused clock "gpt5_ick" > Disabling unused clock "gpt6_ick" > Disabling unused clock "gpt7_ick" > Disabling unused clock "gpt8_ick" > Disabling unused clock "gpt9_ick" > Disabling unused clock "wdt3_ick" > Disabling unused clock "wdt3_fck" > Disabling unused clock "gpio2_dbck" > Disabling unused clock "gpio3_dbck" > Disabling unused clock "gpio4_dbck" > Disabling unused clock "gpio5_dbck" > Disabling unused clock "gpio6_dbck" > Disabling unused clock "gpt9_fck" > Disabling unused clock "gpt8_fck" > Disabling unused clock "gpt7_fck" > Disabling unused clock "gpt6_fck" > Disabling unused clock "gpt5_fck" > Disabling unused clock "gpt4_fck" > Disabling unused clock "gpt3_fck" > Disabling unused clock "gpt2_fck" > Disabling unused clock "gpt1_ick" > Disabling unused clock "wdt1_ick" > Disabling unused clock "wdt2_ick" > Disabling unused clock "wdt2_fck" > Disabling unused clock "gpio1_dbck" > Disabling unused clock "gpt1_fck" > Disabling unused clock "cam_ick" > Disabling unused clock "cam_mclk" > Disabling unused clock "dss_ick" > Disabling unused clock "dss_96m_fck" > Disabling unused clock "dss1_alwon_fck" > Disabling unused clock "des1_ick" > Disabling unused clock "sha11_ick" > Disabling unused clock "rng_ick" > Disabling unused clock "aes1_ick" > Disabling unused clock "ssi_ick" > Disabling unused clock "mailboxes_ick" > Disabling unused clock "mcbsp_ick" > Disabling unused clock "mcbsp_ick" > Disabling unused clock "gpt10_ick" > Disabling unused clock "gpt11_ick" > Disabling unused clock "i2c_ick" > Disabling unused clock "mcspi_ick" > Disabling unused clock "mcspi_ick" > Disabling unused clock "mcspi_ick" > Disabling unused clock "mcspi_ick" > Disabling unused clock "hdq_ick" > Disabling unused clock "mspro_ick" > Disabling unused clock "des2_ick" > Disabling unused clock "sha12_ick" > Disabling unused clock "aes2_ick" > Disabling unused clock "icr_ick" > Disabling unused clock "pka_ick" > Disabling unused clock "ssi_ssr_fck" > Disabling unused clock "hdq_fck" > Disabling unused clock "mcspi_fck" > Disabling unused clock "mcspi_fck" > Disabling unused clock "mcspi_fck" > Disabling unused clock "mcspi_fck" > Disabling unused clock "mcbsp_fck" > Disabling unused clock "mcbsp_fck" > Disabling unused clock "i2c_fck" > Disabling unused clock "mspro_fck" > Disabling unused clock "gpt11_fck" > Disabling unused clock "gpt10_fck" > Disabling unused clock "dpll4_m6x2_ck" > Disabling unused clock "dpll4_m3x2_ck" > Disabling unused clock "dpll3_m3x2_ck" > Disabling unused clock "sys_clkout1" > VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 1 > twl4030_rtc twl4030_rtc: setting system clock to 2000-01-01 00:00:00 > UTC (946684800) > Waiting for root device /dev/mmcblk0p2... > mmc0: new high speed SDHC card at address 8fe4 > mmcblk0: mmc0:8fe4 SD08G 7.40 GiB > mmcblk0: p1 p2 p3 > EXT3-fs warning: maximal mount count reached, running e2fsck is > recommended > EXT3 FS on mmcblk0p2, internal journal > EXT3-fs: recovery complete. > EXT3-fs: mounted filesystem with ordered data mode. > VFS: Mounted root (ext3 filesystem). > Freeing init memory: 188K > INIT: version 2.86 booting > v/rules.d: time stamp 2009-01-13 21:05:30 is 285195917.614868154 s in > the future > udevd[596]: lookup_group: specified group 'scanner' unknown > > udevd[596]: lookup_group: specified group 'scanner' unknown > > udevd[596]: lookup_group: specified group 'scanner' unknown > > udevd[596]: lookup_group: specified group 'scanner' unknown > > udevd[596]: lookup_group: specified group 'nvram' unknown > > udevd[596]: lookup_user: specified user 'tss' unknown > > udevd[596]: lookup_group: specified group 'tss' unknown > > udevd[596]: lookup_group: specified group 'fuse' unknown > > udevd[596]: lookup_group: specified group 'kvm' unknown > > udevd[596]: lookup_group: specified group 'rdma' unknown > > udevd[596]: lookup_group: specified group 'rdma' unknown > > udevd[596]: lookup_group: specified group 'rdma' unknown > > > Adding 160640k swap on /dev/mmcblk0p3. Priority:-1 extents:1 across: > 160640k > Remounting root file system... > uncorrectable error : <3>end_request: I/O error, dev mtdblock0, sector 0 > Buffer I/O error on device mtdblock0, logical block 0 > end_request: I/O error, dev mtdblock0, sector 8 > Buffer I/O error on device mtdblock0, logical block 1 > uncorrectable error : <3>end_request: I/O error, dev mtdblock0, sector > 16 > Buffer I/O error on device mtdblock0, logical block 2 > uncorrectable error : <3>uncorrectable error : <3>end_request: I/O > error, dev mtdblock0, sector 24 > Buffer I/O error on device mtdblock0, logical block 3 > uncorrectable error : <3>end_request: I/O error, dev mtdblock0, sector 0 > Buffer I/O error on device mtdblock0, logical block 0 > WARNING: Couldn't open directory /lib/modules/2.6.28-omap1: No such > file or directory > FATAL: Could not open /lib/modules/2.6.28-omap1/modules.dep.temp for > writing: No such file or directory > modprobe: FATAL: Could not load /lib/modules/2.6.28-omap1/modules.dep: > No such file or directory > > Setting up IP spoofing protection: rp_filter. > Configuring network interfaces... modprobe: FATAL: Could not load > /lib/ modules/2.6.28-omap1/modules.dep: No such file or directory > > eth0: unknown interface: No such device > modprobe: FATAL: Could not load /lib/modules/2.6.28-omap1/modules.dep: > No such file or directory > > modprobe: FATAL: Could not load /lib/modules/2.6.28-omap1/modules.dep: > No such file or directory > > eth0 No such device > > modprobe: FATAL: Could not load /lib/modules/2.6.28-omap1/modules.dep: > No such file or directory > > udhcpc: SIOCGIFINDEX: No such device > done. > Tue Jan 13 21:06:00 GMT 2009 > INIT: Entering runlevel: 5 > Configuring leds: > beagleboard::pmu_st: none > beagleboard::usr0: heartbeat > beagleboard::usr1: mmc0 > ALSA: Restoring mixer settings... > > modprobe: FATAL: Could not load /lib/modules/2.6.28-omap1/modules.dep: > No such file or directory > > dropbear. > (failed.) > [ ok ] > Running ntpdate to synchronize clockError : Temporary failure in name > resolution > . > > .-------. > | | .-. > | | |-----.-----.-----.| | .----..-----.-----. > | | | __ | ---'| '--.| .-'| | | > | | | | | |--- || --'| | | ' | | | | > '---'---'--'--'--. |-----''----''--' '-----'-'-'-' > -' | > '---' > > The Angstrom Distribution beagleboard ttyS2 > > Angstrom 2009.X-test-20090102 beagleboard ttyS2 > > beagleboard login: root > root@beagleboard:~# ls /de\b\b\broot@beagleboard:~# ls /dev/fb\a\b > \broot@beagleboard:~# ls /dev/full root@beagleboard:~# ls /dev/full > pm- > kernel > root@beagleboard:~# find /sy\b\b\broot@beagleboard:~# find /sys/| grep CPU > root@beagleboard:~# root@beagleboard:~# find /sys/| grep CPU\b \b\b > \b\b \bpcu\b \b\b \b\b \bcpu > /sys/devices/system/cpu > /sys/devices/system/cpu/online > /sys/devices/system/cpu/possible > /sys/devices/system/cpu/present > /sys/devices/system/cpu/cpuidle > /sys/devices/system/cpu/cpuidle/current_driver > /sys/devices/system/cpu/cpuidle/current_governor_ro > /sys/devices/system/cpu/cpu0 > /sys/devices/system/cpu/cpu0/crash_notes > /sys/devices/system/cpu/cpu0/cpuidle > /sys/devices/system/cpu/cpu0/cpuidle/state0 > /sys/devices/system/cpu/cpu0/cpuidle/state0/name > /sys/devices/system/cpu/cpu0/cpuidle/state0/desc > /sys/devices/system/cpu/cpu0/cpuidle/state0/latency > /sys/devices/system/cpu/cpu0/cpuidle/state0/power > /sys/devices/system/cpu/cpu0/cpuidle/state0/usage > /sys/devices/system/cpu/cpu0/cpuidle/state0/time > /sys/devices/system/cpu/cpu0/cpuidle/state1 > /sys/devices/system/cpu/cpu0/cpuidle/state1/name > /sys/devices/system/cpu/cpu0/cpuidle/state1/desc > /sys/devices/system/cpu/cpu0/cpuidle/state1/latency > /sys/devices/system/cpu/cpu0/cpuidle/state1/power > /sys/devices/system/cpu/cpu0/cpuidle/state1/usage > /sys/devices/system/cpu/cpu0/cpuidle/state1/time > /sys/devices/system/cpu/cpu0/cpuidle/state2 > /sys/devices/system/cpu/cpu0/cpuidle/state2/name > /sys/devices/system/cpu/cpu0/cpuidle/state2/desc > /sys/devices/system/cpu/cpu0/cpuidle/state2/latency > /sys/devices/system/cpu/cpu0/cpuidle/state2/power > /sys/devices/system/cpu/cpu0/cpuidle/state2/usage > /sys/devices/system/cpu/cpu0/cpuidle/state2/time > /sys/devices/system/cpu/cpu0/cpuidle/state3 > /sys/devices/system/cpu/cpu0/cpuidle/state3/name > /sys/devices/system/cpu/cpu0/cpuidle/state3/desc > /sys/devices/system/cpu/cpu0/cpuidle/state3/latency > /sys/devices/system/cpu/cpu0/cpuidle/state3/power > /sys/devices/system/cpu/cpu0/cpuidle/state3/usage > /sys/devices/system/cpu/cpu0/cpuidle/state3/time > /sys/devices/system/cpu/cpu0/cpuidle/state4 > /sys/devices/system/cpu/cpu0/cpuidle/state4/name > /sys/devices/system/cpu/cpu0/cpuidle/state4/desc > /sys/devices/system/cpu/cpu0/cpuidle/state4/latency > /sys/devices/system/cpu/cpu0/cpuidle/state4/power > /sys/devices/system/cpu/cpu0/cpuidle/state4/usage > /sys/devices/system/cpu/cpu0/cpuidle/state4/time > /sys/devices/system/cpu/cpu0/cpuidle/state5 > /sys/devices/system/cpu/cpu0/cpuidle/state5/name > /sys/devices/system/cpu/cpu0/cpuidle/state5/desc > /sys/devices/system/cpu/cpu0/cpuidle/state5/latency > /sys/devices/system/cpu/cpu0/cpuidle/state5/power > /sys/devices/system/cpu/cpu0/cpuidle/state5/usage > /sys/devices/system/cpu/cpu0/cpuidle/state5/time > /sys/class/misc/cpu_dma_latency > /sys/class/misc/cpu_dma_latency/uevent > /sys/class/misc/cpu_dma_latency/dev > /sys/class/misc/cpu_dma_latency/subsystem > /sys/class/misc/cpu_dma_latency/power > /sys/class/misc/cpu_dma_latency/power/wakeup > /sys/kernel/uids/0/cpu_share > /sys/kernel/uids/1/cpu_share > /sys/kernel/uids/46/cpu_share > /sys/kernel/uids/47/cpu_share > /sys/kernel/uids/42/cpu_share > /sys/module/cpufreq > /sys/module/cpufreq/parameters > /sys/module/cpufreq/parameters/debug_ratelimit > /sys/module/cpufreq/parameters/debug > root@beagleboard:~# ls /sys/devices/system/cpu/cpu0/ > cpuidle crash_notes > root@beagleboard:~# cd /me\b\b\broot@beagleboard:~# cd /media/ > mm\aroot@beagleboard:~# cd /media/mmcb\aroot@beagleboard:~# cd /media/ > mmcblk0p1root@beagleboard:~# cd /media/mmcblk0p1/ > root@beagleboard:/media/mmcblk0p1# ls > broken picodlp-control_0.1-r1.1_armv7a.ipk uImage working > mlo u-boot.bin untested > root@beagleboard:/media/mmcblk0p1# cp wo\b\broot@beagleboard:/media/ > mmcblk0p1# cp working/uI\b \b\b > \b2\aroot@beagleboard:/media/mmcblk0p1# cp working/2.6.2 > working/2.6.26 working/2.6.28-ehci > working/2.6.27 working/2.6.28rc7 > root@beagleboard:/media/mmcblk0p1# cp working/2.6.2 > working/2.6.26 working/2.6.28-ehci > working/2.6.27 working/2.6.28rc7 > root@beagleboard:/media/mmcblk0p1# cp working/2.6.28- > eroot@beagleboard:/media/mmcblk0p1# cp working/2.6.28-ehci > uI\b\broot@beagleboard:/media/mmcblk0p1# cp working/2.6.28-ehci uImage > ; sync ; rebootred new interface driver cdc_ether > usbcore: registered new interface driver rndis_host > usbcore: registered new interface driver zd1211rw > usbcore: registered new interface driver rndis_wlan > usbcore: registered new interface driver zd1201 > usbcore: registered new interface driver usb8xxx > usbcore: registered new interface driver rtl8187 > usbcore: registered new interface driver rt2500usb > usbcore: registered new interface driver rt73usb > usbcore: registered new interface driver p54usb > i2c /dev entries driver > input: triton2-pwrbutton as /class/input/input0 > triton2 power button driver initialized > Driver 'sd' needs updating - please use bus_type methods > Driver 'sr' needs updating - please use bus_type methods > omap2-nand driver initializing > NAND device: Manufacturer ID: 0x2c, Chip ID: 0xba (Micron NAND 256MiB > 1,8V 16-bit) > cmdlinepart partition parsing not available > Creating 5 MTD partitions on "omap2-nand": > 0x00000000-0x00080000 : "X-Loader" > 0x00080000-0x00260000 : "U-Boot" > 0x00260000-0x00280000 : "U-Boot Env" > 0x00280000-0x00680000 : "Kernel" > 0x00680000-0x10000000 : "File System" > ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver > ehci-omap ehci-omap.0: OMAP-EHCI Host Controller > ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 1 > ehci-omap ehci-omap.0: irq 77, io mem 0x48064800 > usb usb1: configuration #1 chosen from 1 choice > hub 1-0:1.0: USB hub found > hub 1-0:1.0: 3 ports detected > Initializing USB Mass Storage driver... > usbcore: registered new interface driver usb-storage > USB Mass Storage support registered. > mice: PS/2 mouse device common for all mice > input: gpio-keys as /class/input/input1 > twl4030_rtc twl4030_rtc: rtc core: registered twl4030_rtc as rtc0 > OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec > Bluetooth: HCI USB driver ver 2.10 > usbcore: registered new interface driver hci_usb > Bluetooth: Broadcom Blutonium firmware driver ver 1.2 > usbcore: registered new interface driver bcm203x > Bluetooth: Digianswer Bluetooth USB driver ver 0.10 > usbcore: registered new interface driver bpa10x > Bluetooth: Generic Bluetooth SDIO driver ver 0.1 > mmci-omap-hs mmci-omap-hs.0: Failed to get debounce clock > Registered led device: beagleboard::usr0 > Registered led device: beagleboard::usr1 > leds-gpio: probe of leds-gpio failed with error -22 > usbcore: registered new interface driver usbhid > usbhid: v2.6:USB HID core driver > Advanced Linux Sound Architecture Driver Version 1.0.18rc3. > usbcore: registered new interface driver snd-usb-audio > ASoC version 0.13.2 > OMAP3 Beagle SoC init > TWL4030 Audio Codec init > asoc: twl4030 <-> omap-mcbsp-dai-(link_id) mapping ok > ALSA device list: > #0: omap3beagle (twl4030) > oprofile: using arm/armv7 > TCP cubic registered > NET: Registered protocol family 17 > NET: Registered protocol family 15 > Bluetooth: L2CAP ver 2.11 > Bluetooth: L2CAP socket layer initialized > Bluetooth: SCO (Voice Link) ver 0.6 > Bluetooth: SCO socket layer initialized > usb 1-2: new high speed USB device using ehci-omap and address 2 > Bluetooth: RFCOMM socket layer initialized > Bluetooth: RFCOMM TTY layer initialized > Bluetooth: RFCOMM ver 1.10 > Bluetooth: BNEP (Ethernet Emulation) ver 1.3 > Bluetooth: BNEP filters: protocol multicast > Bluetooth: HIDP (Human Interface Emulation) ver 1.2 > RPC: Registered udp transport module. > RPC: Registered tcp transport module. > ieee80211: 802.11 data/management/control stack, git-1.1.13 > ieee80211: Copyright (C) 2004-2005 Intel Corporation > <jketreno@linux.intel.com >> > ieee80211_crypt: registered algorithm 'NULL' > ieee80211_crypt: registered algorithm 'WEP' > ieee80211_crypt: registered algorithm 'CCMP' > ieee80211_crypt: registered algorithm 'TKIP' > ThumbEE CPU extension supported. > Power Management for TI OMAP3. > SmartReflex driver initialized > Disabling unused clock "sr2_fck" > Disabling unused clock "sr1_fck" > Disabling unused clock "mcbsp_fck" > Disabling unused clock "mcbsp_fck" > Disabling unused clock "mcbsp_fck" > Disabling unused clock "mcbsp_ick" > Disabling unused clock "mcbsp_ick" > Disabling unused clock "mcbsp_ick" > Disabling unused clock "gpt2_ick" > Disabling unused clock "gpt3_ick" > Disabling unused clock "gpt4_ick" > Disabling unused clock "gpt5_ick" > Disabling unused clock "gpt6_ick" > Disabling unused clock "gpt7_ick" > Disabling unused clock "gpt8_ick" > Disabling unused clock "gpt9_ick" > Disabling unused clock "wdt3_ick" > Disabling unused clock "wdt3_fck" > Disabling unused clock "gpio2_dbck" > Disabling unused clock "gpio3_dbck" > Disabling unused clock "gpio4_dbck" > Disabling unused clock "gpio5_dbck" > Disabling unused clock "gpio6_dbck" > Disabling unused clock "gpt9_fck" > Disabling unused clock "gpt8_fck" > Disabling unused clock "gpt7_fck" > Disabling unused clock "gpt6_fck" > Disabling unused clock "gpt5_fck" > Disabling unused clock "gpt4_fck" > Disabling unused clock "gpt3_fck" > Disabling unused clock "gpt2_fck" > Disabling unused clock "gpt1_ick" > Disabling unused clock "wdt1_ick" > Disabling unused clock "wdt2_ick" > Disabling unused clock "wdt2_fck" > Disabling unused clock "gpio1_dbck" > Disabling unused clock "gpt1_fck" > Disabling unused clock "cam_ick" > Disabling unused clock "cam_mclk" > Disabling unused clock "des1_ick" > Disabling unused clock "sha11_ick" > Disabling unused clock "rng_ick" > Disabling unused clock "aes1_ick" > Disabling unused clock "ssi_ick" > Disabling unused clock "mailboxes_ick" > Disabling unused clock "mcbsp_ick" > Disabling unused clock "mcbsp_ick" > Disabling unused clock "gpt10_ick" > Disabling unused clock "gpt11_ick" > Disabling unused clock "i2c_ick" > Disabling unused clock "mcspi_ick" > Disabling unused clock "mcspi_ick" > Disabling unused clock "mcspi_ick" > Disabling unused clock "mcspi_ick" > Disabling unused clock "hdq_ick" > Disabling unused clock "mspro_ick" > Disabling unused clock "des2_ick" > Disabling unused clock "sha12_ick" > Disabling unused clock "aes2_ick" > Disabling unused clock "icr_ick" > Disabling unused clock "pka_ick" > Disabling unused clock "ssi_ssr_fck" > Disabling unused clock "hdq_fck" > Disabling unused clock "mcspi_fck" > Disabling unused clock "mcspi_fck" > Disabling unused clock "mcspi_fck" > Disabling unused clock "mcspi_fck" > Disabling unused clock "mcbsp_fck" > Disabling unused clock "mcbsp_fck" > Disabling unused clock "i2c_fck" > Disabling unused clock "mspro_fck" > Disabling unused clock "gpt11_fck" > Disabling unused clock "gpt10_fck" > Disabling unused clock "iva2_ck" > Disabling unused clock "dpll4_m6x2_ck" > Disabling unused clock "dpll4_m5x2_ck" > Disabling unused clock "dpll3_m3x2_ck" > Disabling unused clock "sys_clkout1" > VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 1 > OMAPFB: omapfb_init > OMAPFB: omapfb_probe > OMAPFB: create 3 framebuffers > OMAPFB: fb_infos allocated > param '4M' > param '4M' > OMAPFB: allocating 4194304 bytes for fb 0 > OMAPFB: allocated VRAM paddr 80750000, vaddr d1000000 > OMAPFB: allocating 4194304 bytes for fb 1 > OMAPFB: allocated VRAM paddr 80b50000, vaddr d1400000 > OMAPFB: region0 phys 80750000 virt d1000000 size=4194304 > OMAPFB: region1 phys 80b50000 virt d1400000 size=4194304 > OMAPFB: region2 phys 00000000 virt 00000000 size=0 > OMAPFB: fbmems allocated > OMAPFB: check_fb_var 0 > OMAPFB: xres = 640, yres = 480, vxres = 640, vyres = 480 > OMAPFB: set_fb_fix > OMAPFB: check_fb_var 1 > OMAPFB: xres = 640, yres = 480, vxres = 640, vyres = 480 > OMAPFB: set_fb_fix > OMAPFB: check_fb_var 2 > OMAPFB: set_fb_fix > OMAPFB: fb_infos initialized > OMAPFB: set_par(0) > OMAPFB: set_fb_fix > OMAPFB: apply_changes, fb 0, ovl 0 > OMAPFB: setup_overlay 0 > omap-dss DISPLAY: omap_dss_mgr_apply(lcd) > omap-dss DISPC: dispc_enable_plane 0, 0 > omap-dss DISPC: dispc_enable_plane 1, 0 > omap-dss DISPC: dispc_enable_plane 2, 0 > omap-dss DSS: save context > OMAPFB: pan_display(0) > OMAPFB: setcmap > OMAPFB: setcmap > Console: switching to colour frame buffer device 80x30 > OMAPFB: pan_display(0) > OMAPFB: setcmap > OMAPFB: setcmap > OMAPFB: framebuffers registered > OMAPFB: apply_changes, fb 0, ovl 0 > OMAPFB: setup_overlay 0 > OMAPFB: apply_changes, fb 1, ovl 1 > OMAPFB: setup_overlay 1 > OMAPFB: apply_changes, fb 2, ovl 2 > OMAPFB: create_framebuffers done > omap-dss DISPLAY: omap_dss_mgr_apply(lcd) > omap-dss DISPC: dispc_setup_plane 0, 80750000, sw 640, 0,0, 640x480 -> > 640x480, (ilace 0) > omap-dss DISPC: dispc_enable_plane 0, 1 > omap-dss DISPC: dispc_enable_plane 1, 0 > omap-dss DISPC: dispc_enable_plane 2, 0 > omap-dss DSS: save context > omap-dss DISPLAY: omap_dss_mgr_apply(tv) > omap-dss DSS: save context > omap-dss DISPLAY: omap_dss_mgr_apply_l4(l4) > OMAPFB: mgr->apply'ed > omap-dss DSI: PLL init > omap-dss DISPC: dpll4_m4 = 432000000 > omap-dss DISPC: fck = 96000000 (9) > omap-dss DISPC: lck = 96000000 (1) > omap-dss DISPC: pck = 48000000 (2) > clock: new_div = 9, new_rate = 48000000 > omap-dss DSI: PLL init done > omap-dss DISPC: fifo(0) size 1024, low/high old 960/1023, new 256/960 > omap-dss DISPC: fifo(1) size 1024, low/high old 960/1023, new 256/960 > omap-dss DISPC: fifo(2) size 1024, low/high old 960/1023, new 256/960 > omap-dss DISPC: onoff 0 rf 0 ieo 0 ipc 0 ihs 0 ivs 0 acbi 0 acb 0 > omap-dss DSI: dsi_pll_calc > omap-dss DSI: dsi_pll_program > omap-dss DSI: DSI Fint 1857142 > omap-dss DSI: clkin (dss2_fck) rate 13000000, highfreq 0 > omap-dss DSI: DSIPHY = 2 * 329 / 7 * 13000000 / 1 = 1222000000 > omap-dss DSI: Data rate on 1 DSI lane 611 Mbps > omap-dss DSI: Clock lane freq 305500000 Hz > omap-dss DSI: regm3 = 13, dsi1_pll_fclk = 94000000 > omap-dss DSI: regm4 = 16, dsi2_pll_fclk = 76375000 > omap-dss DSI: PLL config done > omap-dss DISPC: xres 640 yres 480 > omap-dss DISPC: pck 23500 > omap-dss DISPC: hsw 32 hfp 48 hbp 80 vsw 4 vfp 3 vbp 7 > omap-dss DISPC: hsync 29375Hz, vsync 59Hz > OMAPFB: display->updated > DISPC IRQ: 0x4024: SYNC_LOST > omap-dss DISPC error: dispc irq error status 4024 > DISPC IRQ: 0x4000: SYNC_LOST > omap-dss DISPC error: dispc irq error status 4000 > DISPC IRQ: 0x4000: SYNC_LOST > omap-dss DISPC error: dispc irq error status 4000 > DISPC IRQ: 0x4022: SYNC_LOST > omap-dss DISPC error: dispc irq error status 4022 > DISPC IRQ: 0x4000: SYNC_LOST > omap-dss DISPC error: dispc irq error status 4000 > DISPC IRQ: 0x4022: SYNC_LOST > omap-dss DISPC error: dispc irq error status 4022 > DISPC IRQ: 0x4000: SYNC_LOST > omap-dss DISPC error: dispc irq error status 4000 > DISPC IRQ: 0x4022: SYNC_LOST > omap-dss DISPC error: dispc irq error status 4022 > DISPC IRQ: 0x4000: SYNC_LOST > omap-dss DISPC error: dispc irq error status 4000 > DISPC IRQ: 0x4002: SYNC_LOST > omap-dss DISPC error: dispc irq error status 4002 > DISPC IRQ: 0x4020: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4022: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4022: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4022: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4022: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > OMAPFB: sysfs created > DISPC IRQ: 0x4022: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4022: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4022: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4022: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4022: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4022: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4022: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4022: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4022: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4022: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4022: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > DISPC IRQ: 0x4000: SYNC_LOST > omap-dss DISPC error: Excessive DISPC errors > Turning off lcd and digit > DISPC IRQ: 0x4022: SYNC_LOST > omap-dss DISPC error: Excessive DISPC errors > Turning off lcd and digit > DISPC IRQ: 0x4000: SYNC_LOST > omap-dss DISPC error: Excessive DISPC errors > Turning off lcd and digit > DISPC IRQ: 0x4003: SYNC_LOST > omap-dss DISPC error: Excessive DISPC errors > Turning off lcd and digit > usb 1-2: configuration #1 chosen from 1 choice > twl4030_rtc twl4030_rtc: setting system clock to 2009-01-13 21:11:13 > UTC (1231881073) > hub 1-2:1.0: USB hub found > hub 1-2:1.0: 4 ports detected > mmc0: new SDHC card at address 8fe4 > mmcblk0: mmc0:8fe4 SD08G 7.40 GiB > mmcblk0: p1 p2 p3 > EXT3-fs warning: maximal mount count reached, running e2fsck is > recommended > EXT3 FS on mmcblk0p2, internal journal > EXT3-fs: mounted filesystem with ordered data mode. > VFS: Mounted root (ext3 filesystem). > Freeing init memory: 188K > > If you have read till down here: still no cpufreq while the board file > has the rate tables and the initcall: > > --- /tmp/board-omap3beagle.c 2009-01-12 15:46:26.000000000 +0100 > +++ git/arch/arm/mach-omap2/board-omap3beagle.c 2009-01-12 > 15:46:28.000000000 +0100 > @@ -41,14 +41,73 @@ > #include <mach/usb-ehci.h> > #include <mach/common.h> > #include <mach/gpmc.h> > +#include <mach/omap-pm.h> > #include <mach/nand.h> > #include <mach/mux.h> > #include <mach/omapfb.h> > #include <mach/display.h> > +#include <mach/clock.h> > + > > #include "twl4030-generic-scripts.h" > #include "mmc-twl4030.h" > +#include "pm.h" > + > +/* MPU speeds */ > +#define S600M 600000000 > +#define S550M 550000000 > +#define S500M 500000000 > +#define S250M 250000000 > +#define S125M 125000000 > + > +/* DSP speeds */ > +#define S430M 430000000 > +#define S400M 400000000 > +#define S360M 360000000 > +#define S180M 180000000 > +#define S90M 90000000 > + > +/* L3 speeds */ > +#define S83M 83000000 > +#define S166M 166000000 > + > +static struct omap_opp mpu_rate_table[] = { > + {0, 0, 0}, > + /*OPP1*/ > + {S125M, VDD1_OPP1, 0x18}, > + /*OPP2*/ > + {S250M, VDD1_OPP2, 0x20}, > + /*OPP3*/ > + {S500M, VDD1_OPP3, 0x30}, > + /*OPP4*/ > + {S550M, VDD1_OPP4, 0x36}, > + /*OPP5*/ > + {S600M, VDD1_OPP5, 0x3C}, > +}; > > +static struct omap_opp l3_rate_table[] = { > + {0, 0, 0}, > + /*OPP1*/ > + {0, VDD2_OPP1, 0x18}, > + /*OPP2*/ > + {S83M, VDD2_OPP2, 0x20}, > + /*OPP3*/ > + {S166M, VDD2_OPP3, 0x2C}, > +}; > + > +struct omap_opp dsp_rate_table[] = { > + {0, 0, 0}, > + /*OPP1*/ > + {S90M, VDD1_OPP1, 0x18}, > + /*OPP2*/ > + {S180M, VDD1_OPP2, 0x20}, > + /*OPP3*/ > + {S360M, VDD1_OPP3, 0x30}, > + /*OPP4*/ > + {S400M, VDD1_OPP4, 0x36}, > + /*OPP5*/ > + {S430M, VDD1_OPP5, 0x3C}, > +}; > > #define GPMC_CS0_BASE 0x60 > #define GPMC_CS_SIZE 0x30 > > @@ -227,7 +294,8 @@ > > static void __init omap3_beagle_init_irq(void) > { > - omap2_init_common_hw(mt46h32m32lf6_sdrc_params, NULL, NULL, NULL); > + omap2_init_common_hw(mt46h32m32lf6_sdrc_params, mpu_rate_table, > + dsp_rate_table, l3_rate_table); > omap_init_irq(); > omap_gpio_init(); > } > > > regards, > > Koen [1] http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git;a=commit;h=818862e11bad091dc635baedace58265a126b5c8 -- 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] 40+ messages in thread
* Re: new PM branch available 2009-01-14 22:14 ` Kevin Hilman @ 2009-01-15 8:18 ` Koen Kooi 0 siblings, 0 replies; 40+ messages in thread From: Koen Kooi @ 2009-01-15 8:18 UTC (permalink / raw) To: Kevin Hilman; +Cc: linux-omap@vger.kernel.org List [-- Attachment #1: Type: text/plain, Size: 1127 bytes --] Op 14 jan 2009, om 23:14 heeft Kevin Hilman het volgende geschreven: > Koen Kooi <k.kooi@student.utwente.nl> writes: > >> Op 13 jan 2009, om 22:51 heeft Kevin Hilman het volgende geschreven: >> >>> Hello, >>> >>> The latest PM branch is now available[1]. >>> >>> I've done basic testing of retention and off-mode (suspend and >>> dynamic >>> idle) on Beagle and custom HW. My SDP has something still keeping >>> CORE active that others have not seen, but I have yet to debug. Any >>> other reports from SDP testing would be appreciated. >>> >>> Notable changes/updates >>> - rebased on latest clock updates and fixes from Paul >>> - clockfw pre- and post- notifiers >>> - DVFS for VDD2 >> >> The bootlog on my rev C1D beagle looks suspicious: >> > > Hi Koen, > > Hmm, it looks like you're tree is missing the McBSP fix from Paul[1]. > This patch made it in before v2.6.28-omap1 which the latest PM branch > is based on, so I'm guessing you're not testing the latest PM branch. Indeed: >> Image Name: Angstrom/2.6.28-pm1+gitrb5d11429 The latest is gitr998bd567. I'll test the proper one later today. regards, Koen [-- Attachment #2: Dit deel van het bericht is digitaal ondertekend --] [-- Type: application/pgp-signature, Size: 186 bytes --] ^ permalink raw reply [flat|nested] 40+ messages in thread
* Re: new PM branch available 2009-01-13 21:51 Kevin Hilman 2009-01-14 7:35 ` Koen Kooi @ 2009-01-14 12:40 ` Ramesh Gupta Guntha 2009-01-14 16:35 ` Kevin Hilman 2009-01-14 13:57 ` Sriram V ` (2 subsequent siblings) 4 siblings, 1 reply; 40+ messages in thread From: Ramesh Gupta Guntha @ 2009-01-14 12:40 UTC (permalink / raw) To: Kevin Hilman; +Cc: linux-omap Hi Kevin, On 1/14/09, Kevin Hilman <khilman@deeprootsystems.com> wrote: > Hello, > > The latest PM branch is now available[1]. > > I've done basic testing of retention and off-mode (suspend and dynamic > idle) on Beagle and custom HW. My SDP has something still keeping > CORE active that others have not seen, but I have yet to debug. Any > other reports from SDP testing would be appreciated. I have tested on my SDP, I too observed the similar behaviour, I am seeing both PER and CORE are active. thanks Ramesh Gupta G ^ permalink raw reply [flat|nested] 40+ messages in thread
* Re: new PM branch available 2009-01-14 12:40 ` Ramesh Gupta Guntha @ 2009-01-14 16:35 ` Kevin Hilman 0 siblings, 0 replies; 40+ messages in thread From: Kevin Hilman @ 2009-01-14 16:35 UTC (permalink / raw) To: Ramesh Gupta Guntha; +Cc: linux-omap Ramesh Gupta Guntha wrote: > Hi Kevin, > > On 1/14/09, Kevin Hilman <khilman@deeprootsystems.com> wrote: >> Hello, >> >> The latest PM branch is now available[1]. >> >> I've done basic testing of retention and off-mode (suspend and dynamic >> idle) on Beagle and custom HW. My SDP has something still keeping >> CORE active that others have not seen, but I have yet to debug. Any >> other reports from SDP testing would be appreciated. > > I have tested on my SDP, I too observed the similar behaviour, I am > seeing both PER and CORE are active. > Hmm, if you're seeing both PER and CORE, then UART clocks are probably still active. Please try this: # echo 1 > /sys/power/clocks_off_while_idle then try again. Thanks, Kevin ^ permalink raw reply [flat|nested] 40+ messages in thread
* Re: new PM branch available 2009-01-13 21:51 Kevin Hilman 2009-01-14 7:35 ` Koen Kooi 2009-01-14 12:40 ` Ramesh Gupta Guntha @ 2009-01-14 13:57 ` Sriram V 2009-01-14 16:39 ` Kevin Hilman 2009-01-16 13:49 ` Nayak, Rajendra 2009-02-02 17:45 ` Peter 'p2' De Schrijver 4 siblings, 1 reply; 40+ messages in thread From: Sriram V @ 2009-01-14 13:57 UTC (permalink / raw) To: Kevin Hilman; +Cc: linux-omap@vger.kernel.org Hi, OMAP3EVM. all domains hit retention in suspend. On enabling cpuidle, network and mmc is not stable. network is unable to get an IP address. Regards, sriram On Wed, Jan 14, 2009 at 3:21 AM, Kevin Hilman <khilman@deeprootsystems.com> wrote: > Hello, > > The latest PM branch is now available[1]. > > I've done basic testing of retention and off-mode (suspend and dynamic > idle) on Beagle and custom HW. My SDP has something still keeping > CORE active that others have not seen, but I have yet to debug. Any > other reports from SDP testing would be appreciated. > > Notable changes/updates > - rebased on latest clock updates and fixes from Paul > - clockfw pre- and post- notifiers > - DVFS for VDD2 > > Full git shortlog below[2] > > Enjoy, > > Kevin > > [1] See branch 'pm' in my git repo: > git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap-pm.git > which is also mirrored as the branch 'pm' of the normal linux-omap > repo (but will not sync until 03:30 GMT) > > > [2] git shortlog: > > Carlos Chinea (1): > OMAP3:PM: Update SSI omapdev record > > Jouni Hogander (5): > OMAP3: PM: Use pwrdm_set_next_pwrst instead of set_pwrdm_state in idle loop > OMAP3: PM: Fix wrong sequence in suspend. > OMAP3: PM: Do not build suspend code if SUSPEND is not enabled > OMAP: PM: Build fails if PM is not enabled > OMAP2: PM: Fix omap2 build > > Kalle Jokiniemi (3): > OMAP: PM: sysfs interface for enabling voltage off in idle > OMAP3: PM: Fix cpu idle init sequencing > OMAP: SRF: Fixes to shared resource framework (Ver.3) > > Kevin Hilman (4): > OMAP3: PM: CPUidle: obey enable_off_mode flag > OMAP3: PM: CPUidle: restrict C-states on UART activity > OMAP3: PM: decouple PER and CORE context save and restore > OMAP2/3: PM: system_rev -> omap_rev() > > Paul Walmsley (29): > OMAP2/3 clock: implement clock notifier infrastructure > OMAP clock: add notifier infrastructure > OMAP2/3 clock: store planned clock rates into temporary rate storage > OMAP2/3 clock: add clk post-rate-change notifiers > OMAP2/3 clock: add clock pre-rate-change notification > OMAP2/3 clock: add clock prepare-rate-change notifications > OMAP2/3 clock: add clock abort-rate-change notifications > OMAP2/3 PM: create the OMAP PM interface and add a default OMAP PM no-op layer. > OMAP2/3 omapdev: add basic omapdev structure > OMAP242x omapdev: add OMAP242x omapdev records > OMAP243x omapdev: add OMAP243x omapdev records > OMAP3xxx omapdev: add OMAP3xxx omapdev records > OMAP2/3 omapdev: add code to walk the omapdev records > ARM: MMU: add a Non-cacheable Normal executable memory type > OMAP3 SRAM: mark OCM RAM as Non-cacheable Normal memory > OMAP3 SRAM: add ARM barriers to omap3_sram_configure_core_dpll > OMAP3 clock: add interconnect barriers to CORE DPLL M2 change > OMAP3 SRAM: clear the SDRC PWRENA bit during SDRC frequency change > OMAP3 SDRC: Add 166MHz, 83MHz SDRC settings for the BeagleBoard > OMAP3 SDRC: initialize SDRC_POWER at boot > OMAP3 SRAM: renumber registers to make space for argument passing > OMAP3 clock: only unlock SDRC DLL if SDRC clk < 83MHz > OMAP3 clock: use pr_debug() rather than pr_info() in some clock change code > OMAP3 clock: remove wait for DPLL3 M2 clock to stabilize > OMAP3 clock: initialize SDRC timings at kernel start > OMAP3 clock: add a short delay when lowering CORE clk rate > OMAP3 clock/SDRC: program SDRC_MR register during SDRC clock change > OMAP3 SRAM: add more comments on the SRAM code > OMAP3 SRAM: convert SRAM code to use macros rather than magic numbers > > Peter 'p2' De Schrijver (12): > OMAP: PM counter infrastructure. > OMAP: PM: Hook into PM counters > OMAP: PM: Add closures to clkdm_for_each and pwrdm_for_each. > OMAP: PM: Add pm-debug counters > OMAP: PM debug: make powerdomains use PM-debug counters > OMAP: PM: Add definitions for ETK pads and observability registers > OMAP: Debug observability and ETK padconf implementation > OMAP: Add debug observablity (debobs) Kconfig item > OMAP: PM: Implement get_last_off_on_transaction_id() > Save sram context after changing MPU, DSP or core clocks > Fix omap_getspeed. > Make sure omap cpufreq driver initializes after cpufreq framework and governors > > Rajendra Nayak (35): > OMAP3: PM: GPMC context save/restore > OMAP3: PM: GPIO context save/restore > OMAP3: PM: I2C context save/restore > OMAP3: PM: INTC context save/restore > OMAP3: PM: PRCM context save/restore > OMAP3: PM: Populate scratchpad contents > OMAP3: PM: SCM context save/restore > OMAP3: PM: SRAM restore function > OMAP3: PM: handle PER/NEON/CORE in idle > OMAP3: PM: Restore MMU table entry > OMAP3: PM: MPU off-mode support > OMAP3: PM: CORE domain off-mode support > OMAP3: PM: allow runtime enable/disable of OFF mode > OMAP3: 3430SDP minimal kernel defconfig > OMAP3: PM: CPUidle: Basic support for C1-C2 > OMAP3: PM: CPUidle: Enables state C4 > OMAP3: PM: CPUidle: Enables C3 and C5 > OMAP3: PM: CPUidle: Safe-state on bm-activity > OMAP3 SRF: Generic shared resource f/w > OMAP3 SRF: MPU/CORE/PD latency modeling > OMAP3 SRF: omap3 srf driver > OMAP3 SRF: OMAP PM srf implementation > OMAP3 SRF: Add CORE rate table param in OMAP-PM > OMAP3 SRF: Add VDD1/VDD2 rate tables for 3430SDP > OMAP3 SRF: Add virt clk nodes for VDD1/VDD2 > OMAP3 SRF: Adds OPP/Freq res's in SRF > OMAP3 SRF: Update OMAP-PM layer > OMAP3 SRF: Voltage scaling support > OMAP3 SRF: VDD2 scaling support > OMAP3 SRF: Adds sysfs control for VDD1/VDD2 OPP's > OMAP3 PM: Replace spinlocks with mutex in SRF > OMAP3 PM: CPUFreq driver for OMAP3 > OMAP3 PM: Update the min defconfig for 3430sdp > OMAP3 SRF: Fix crash on non-3430SDP platforms with DVFS/CPUFreq > OMAP3: PM: Scale VDD2 OPP for VDD1 OPP3 and higher > > Tero Kristo (26): > OMAP: PM debug: do not print out status for meta powerdomains (dpll*) > OMAP: PM debug: Add PRCM register dump support > OMAP: PM: DMA context save / restore > OMAP: PM: off-mode support for DMA on EMU/HS devices > OMAP3: SRAM size fix for HS/EMU devices > OMAP3 PM: off-mode support for HS/EMU devices > OMAP3: PM: Enable SDRAM auto-refresh during sleep > OMAP: SDRC: Add new register definitions for SDRAM controller > OMAP3: PM: SDRC auto-refresh workaround for off-mode > PM: Added three PLL registers to the PRCM context save > PM: Changed secure RAM storage size from 0x8000 to 0x803F > PM: Added suspend target state control to debugfs for OMAP3 > OMAP3: PM: Prevent PER from going OFF when CORE is going INA > PM OMAP3: Change omap3_save_secure_ram to be called only during init > OMAP3: PM: MPU and CORE should stay awake if there is CAM domain ACTIVE > OMAP3: GPIO fixes for off-mode > PM: OMAP3: Refreshed DVFS VDD1 control against latest clock fw > OMAP3: Add support for DPLL3 divisor values higher than 2 > OMAP3: PM: Fixed VDD2 control to work from both sysfs and SRF API > OMAP3: PM: Added DVFS OPP locking interface for VDD1 and VDD2 > OMAP3: Fix rate calculation bug in omap3_select_table_rate > OMAP3: PM: Prevented DVFS state switches when enabling off-mode > OMAP3: PM: Enable VDD2 OPP1 > OMAP3: PM: Fix linker error without CONFIG_PM option > PM: OMAP3: Removed a couple of unused variables from DVFS code > PM: OMAP3: Added support for possibly failing clk_set_rate to DVFS > > -- > To unsubscribe from this list: send the line "unsubscribe linux-omap" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > ^ permalink raw reply [flat|nested] 40+ messages in thread
* Re: new PM branch available 2009-01-14 13:57 ` Sriram V @ 2009-01-14 16:39 ` Kevin Hilman 2009-01-15 13:42 ` Premi, Sanjeev ` (2 more replies) 0 siblings, 3 replies; 40+ messages in thread From: Kevin Hilman @ 2009-01-14 16:39 UTC (permalink / raw) To: Sriram V; +Cc: linux-omap@vger.kernel.org Sriram V wrote: > Hi, > OMAP3EVM. all domains hit retention in suspend. > > On enabling cpuidle, network and mmc is not stable. network is > unable to get an IP address. Sriram, Can you send me your .config for omap3evm? I'm trying to get my recently received EVM working but I am getting lots of garbage on the serial console on linux-omap HEAD and PM branch on omap3evm. Do you have any additional patches for EVM that you're using? Kevin > > On Wed, Jan 14, 2009 at 3:21 AM, Kevin Hilman > <khilman@deeprootsystems.com> wrote: >> Hello, >> >> The latest PM branch is now available[1]. >> >> I've done basic testing of retention and off-mode (suspend and dynamic >> idle) on Beagle and custom HW. My SDP has something still keeping >> CORE active that others have not seen, but I have yet to debug. Any >> other reports from SDP testing would be appreciated. >> >> Notable changes/updates >> - rebased on latest clock updates and fixes from Paul >> - clockfw pre- and post- notifiers >> - DVFS for VDD2 >> >> Full git shortlog below[2] >> >> Enjoy, >> >> Kevin >> >> [1] See branch 'pm' in my git repo: >> git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap-pm.git >> which is also mirrored as the branch 'pm' of the normal linux-omap >> repo (but will not sync until 03:30 GMT) >> >> >> [2] git shortlog: >> >> Carlos Chinea (1): >> OMAP3:PM: Update SSI omapdev record >> >> Jouni Hogander (5): >> OMAP3: PM: Use pwrdm_set_next_pwrst instead of set_pwrdm_state in idle loop >> OMAP3: PM: Fix wrong sequence in suspend. >> OMAP3: PM: Do not build suspend code if SUSPEND is not enabled >> OMAP: PM: Build fails if PM is not enabled >> OMAP2: PM: Fix omap2 build >> >> Kalle Jokiniemi (3): >> OMAP: PM: sysfs interface for enabling voltage off in idle >> OMAP3: PM: Fix cpu idle init sequencing >> OMAP: SRF: Fixes to shared resource framework (Ver.3) >> >> Kevin Hilman (4): >> OMAP3: PM: CPUidle: obey enable_off_mode flag >> OMAP3: PM: CPUidle: restrict C-states on UART activity >> OMAP3: PM: decouple PER and CORE context save and restore >> OMAP2/3: PM: system_rev -> omap_rev() >> >> Paul Walmsley (29): >> OMAP2/3 clock: implement clock notifier infrastructure >> OMAP clock: add notifier infrastructure >> OMAP2/3 clock: store planned clock rates into temporary rate storage >> OMAP2/3 clock: add clk post-rate-change notifiers >> OMAP2/3 clock: add clock pre-rate-change notification >> OMAP2/3 clock: add clock prepare-rate-change notifications >> OMAP2/3 clock: add clock abort-rate-change notifications >> OMAP2/3 PM: create the OMAP PM interface and add a default OMAP PM no-op layer. >> OMAP2/3 omapdev: add basic omapdev structure >> OMAP242x omapdev: add OMAP242x omapdev records >> OMAP243x omapdev: add OMAP243x omapdev records >> OMAP3xxx omapdev: add OMAP3xxx omapdev records >> OMAP2/3 omapdev: add code to walk the omapdev records >> ARM: MMU: add a Non-cacheable Normal executable memory type >> OMAP3 SRAM: mark OCM RAM as Non-cacheable Normal memory >> OMAP3 SRAM: add ARM barriers to omap3_sram_configure_core_dpll >> OMAP3 clock: add interconnect barriers to CORE DPLL M2 change >> OMAP3 SRAM: clear the SDRC PWRENA bit during SDRC frequency change >> OMAP3 SDRC: Add 166MHz, 83MHz SDRC settings for the BeagleBoard >> OMAP3 SDRC: initialize SDRC_POWER at boot >> OMAP3 SRAM: renumber registers to make space for argument passing >> OMAP3 clock: only unlock SDRC DLL if SDRC clk < 83MHz >> OMAP3 clock: use pr_debug() rather than pr_info() in some clock change code >> OMAP3 clock: remove wait for DPLL3 M2 clock to stabilize >> OMAP3 clock: initialize SDRC timings at kernel start >> OMAP3 clock: add a short delay when lowering CORE clk rate >> OMAP3 clock/SDRC: program SDRC_MR register during SDRC clock change >> OMAP3 SRAM: add more comments on the SRAM code >> OMAP3 SRAM: convert SRAM code to use macros rather than magic numbers >> >> Peter 'p2' De Schrijver (12): >> OMAP: PM counter infrastructure. >> OMAP: PM: Hook into PM counters >> OMAP: PM: Add closures to clkdm_for_each and pwrdm_for_each. >> OMAP: PM: Add pm-debug counters >> OMAP: PM debug: make powerdomains use PM-debug counters >> OMAP: PM: Add definitions for ETK pads and observability registers >> OMAP: Debug observability and ETK padconf implementation >> OMAP: Add debug observablity (debobs) Kconfig item >> OMAP: PM: Implement get_last_off_on_transaction_id() >> Save sram context after changing MPU, DSP or core clocks >> Fix omap_getspeed. >> Make sure omap cpufreq driver initializes after cpufreq framework and governors >> >> Rajendra Nayak (35): >> OMAP3: PM: GPMC context save/restore >> OMAP3: PM: GPIO context save/restore >> OMAP3: PM: I2C context save/restore >> OMAP3: PM: INTC context save/restore >> OMAP3: PM: PRCM context save/restore >> OMAP3: PM: Populate scratchpad contents >> OMAP3: PM: SCM context save/restore >> OMAP3: PM: SRAM restore function >> OMAP3: PM: handle PER/NEON/CORE in idle >> OMAP3: PM: Restore MMU table entry >> OMAP3: PM: MPU off-mode support >> OMAP3: PM: CORE domain off-mode support >> OMAP3: PM: allow runtime enable/disable of OFF mode >> OMAP3: 3430SDP minimal kernel defconfig >> OMAP3: PM: CPUidle: Basic support for C1-C2 >> OMAP3: PM: CPUidle: Enables state C4 >> OMAP3: PM: CPUidle: Enables C3 and C5 >> OMAP3: PM: CPUidle: Safe-state on bm-activity >> OMAP3 SRF: Generic shared resource f/w >> OMAP3 SRF: MPU/CORE/PD latency modeling >> OMAP3 SRF: omap3 srf driver >> OMAP3 SRF: OMAP PM srf implementation >> OMAP3 SRF: Add CORE rate table param in OMAP-PM >> OMAP3 SRF: Add VDD1/VDD2 rate tables for 3430SDP >> OMAP3 SRF: Add virt clk nodes for VDD1/VDD2 >> OMAP3 SRF: Adds OPP/Freq res's in SRF >> OMAP3 SRF: Update OMAP-PM layer >> OMAP3 SRF: Voltage scaling support >> OMAP3 SRF: VDD2 scaling support >> OMAP3 SRF: Adds sysfs control for VDD1/VDD2 OPP's >> OMAP3 PM: Replace spinlocks with mutex in SRF >> OMAP3 PM: CPUFreq driver for OMAP3 >> OMAP3 PM: Update the min defconfig for 3430sdp >> OMAP3 SRF: Fix crash on non-3430SDP platforms with DVFS/CPUFreq >> OMAP3: PM: Scale VDD2 OPP for VDD1 OPP3 and higher >> >> Tero Kristo (26): >> OMAP: PM debug: do not print out status for meta powerdomains (dpll*) >> OMAP: PM debug: Add PRCM register dump support >> OMAP: PM: DMA context save / restore >> OMAP: PM: off-mode support for DMA on EMU/HS devices >> OMAP3: SRAM size fix for HS/EMU devices >> OMAP3 PM: off-mode support for HS/EMU devices >> OMAP3: PM: Enable SDRAM auto-refresh during sleep >> OMAP: SDRC: Add new register definitions for SDRAM controller >> OMAP3: PM: SDRC auto-refresh workaround for off-mode >> PM: Added three PLL registers to the PRCM context save >> PM: Changed secure RAM storage size from 0x8000 to 0x803F >> PM: Added suspend target state control to debugfs for OMAP3 >> OMAP3: PM: Prevent PER from going OFF when CORE is going INA >> PM OMAP3: Change omap3_save_secure_ram to be called only during init >> OMAP3: PM: MPU and CORE should stay awake if there is CAM domain ACTIVE >> OMAP3: GPIO fixes for off-mode >> PM: OMAP3: Refreshed DVFS VDD1 control against latest clock fw >> OMAP3: Add support for DPLL3 divisor values higher than 2 >> OMAP3: PM: Fixed VDD2 control to work from both sysfs and SRF API >> OMAP3: PM: Added DVFS OPP locking interface for VDD1 and VDD2 >> OMAP3: Fix rate calculation bug in omap3_select_table_rate >> OMAP3: PM: Prevented DVFS state switches when enabling off-mode >> OMAP3: PM: Enable VDD2 OPP1 >> OMAP3: PM: Fix linker error without CONFIG_PM option >> PM: OMAP3: Removed a couple of unused variables from DVFS code >> PM: OMAP3: Added support for possibly failing clk_set_rate to DVFS >> >> -- >> To unsubscribe from this list: send the line "unsubscribe linux-omap" in >> the body of a message to majordomo@vger.kernel.org >> More majordomo info at http://vger.kernel.org/majordomo-info.html >> ^ permalink raw reply [flat|nested] 40+ messages in thread
* RE: new PM branch available 2009-01-14 16:39 ` Kevin Hilman @ 2009-01-15 13:42 ` Premi, Sanjeev 2009-01-15 15:01 ` Kevin Hilman 2009-01-15 15:00 ` Sriram V [not found] ` <8bf247760901150654n78b198f0o5c2270186e9c119e@mail.gmail.com> 2 siblings, 1 reply; 40+ messages in thread From: Premi, Sanjeev @ 2009-01-15 13:42 UTC (permalink / raw) To: 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 Kevin Hilman > Sent: Wednesday, January 14, 2009 10:10 PM > To: Sriram V > Cc: linux-omap@vger.kernel.org > Subject: Re: new PM branch available > > Sriram V wrote: > > Hi, > > OMAP3EVM. all domains hit retention in suspend. > > > > On enabling cpuidle, network and mmc is not stable. network is > > unable to get an IP address. > > Sriram, > > Can you send me your .config for omap3evm? I'm trying to get > my recently received EVM working but I am getting lots of > garbage on the serial console on linux-omap HEAD and PM > branch on omap3evm. Do you have any additional patches for > EVM that you're using? > > Kevin > Hi Kevin, I was able to test against the HEAD 'pm' branch on the EVM. Here are my observations with default configuration: 1) CONFIG_DEBUG_LL=y is set by default. The kernel boots fine. I did not notice any 'garbage' problems you and Koen seem to be getting. 2) Same result when CONFIG_DEBUG_LL is deselcted. 3) With default config, suspend operation fails with this message: <3>omapfb omapfb: timeout waiting for FRAME DONE Here is a sample session from my terminal: [root@OMAP3EVM /]# uname -a Linux OMAP3EVM 2.6.28-omap1-00115-g998bd56 #146 Thu Jan 15 18:47:26 IST 2009 armv7l unknown [root@OMAP3EVM /]# echo 1 > /sys/power/clocks_off_while_idle [root@OMAP3EVM /]# echo 1 > /sys/power/sleep_while_idle [root@OMAP3EVM /]# [root@OMAP3EVM /]# echo mem > /sys/power/state <6>PM: Syncing filesystems ... PM: Syncing filesystems ... done. done. Freezing user space processes ... Freezing user space processes ... (elapsed 0.00 seconds) (elapsed 0.00 seconds) done. done. Freezing remaining freezable tasks ... Freezing remaining freezable tasks ... (elapsed 0.06 seconds) (elapsed 0.06 seconds) done.done. Suspending console(s) (use no_console_suspend to debug) Suspending console(s) (use no_console_suspend to debug) Best regards, Sanjeev > > > > > On Wed, Jan 14, 2009 at 3:21 AM, Kevin Hilman > > <khilman@deeprootsystems.com> wrote: > >> Hello, > >> > >> The latest PM branch is now available[1]. > >> > >> I've done basic testing of retention and off-mode (suspend and > >> dynamic > >> idle) on Beagle and custom HW. My SDP has something still keeping > >> CORE active that others have not seen, but I have yet to > debug. Any > >> other reports from SDP testing would be appreciated. > >> > >> Notable changes/updates > >> - rebased on latest clock updates and fixes from Paul > >> - clockfw pre- and post- notifiers > >> - DVFS for VDD2 > >> > >> Full git shortlog below[2] > >> > >> Enjoy, > >> > >> Kevin > >> > >> [1] See branch 'pm' in my git repo: > >> > git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap-pm.g > >> it which is also mirrored as the branch 'pm' of the normal > linux-omap > >> repo (but will not sync until 03:30 GMT) > >> > >> > >> [2] git shortlog: > >> > >> Carlos Chinea (1): > >> OMAP3:PM: Update SSI omapdev record > >> > >> Jouni Hogander (5): > >> OMAP3: PM: Use pwrdm_set_next_pwrst instead of > set_pwrdm_state in idle loop > >> OMAP3: PM: Fix wrong sequence in suspend. > >> OMAP3: PM: Do not build suspend code if SUSPEND is not enabled > >> OMAP: PM: Build fails if PM is not enabled > >> OMAP2: PM: Fix omap2 build > >> > >> Kalle Jokiniemi (3): > >> OMAP: PM: sysfs interface for enabling voltage off in idle > >> OMAP3: PM: Fix cpu idle init sequencing > >> OMAP: SRF: Fixes to shared resource framework (Ver.3) > >> > >> Kevin Hilman (4): > >> OMAP3: PM: CPUidle: obey enable_off_mode flag > >> OMAP3: PM: CPUidle: restrict C-states on UART activity > >> OMAP3: PM: decouple PER and CORE context save and restore > >> OMAP2/3: PM: system_rev -> omap_rev() > >> > >> Paul Walmsley (29): > >> OMAP2/3 clock: implement clock notifier infrastructure > >> OMAP clock: add notifier infrastructure > >> OMAP2/3 clock: store planned clock rates into > temporary rate storage > >> OMAP2/3 clock: add clk post-rate-change notifiers > >> OMAP2/3 clock: add clock pre-rate-change notification > >> OMAP2/3 clock: add clock prepare-rate-change notifications > >> OMAP2/3 clock: add clock abort-rate-change notifications > >> OMAP2/3 PM: create the OMAP PM interface and add a > default OMAP PM no-op layer. > >> OMAP2/3 omapdev: add basic omapdev structure > >> OMAP242x omapdev: add OMAP242x omapdev records > >> OMAP243x omapdev: add OMAP243x omapdev records > >> OMAP3xxx omapdev: add OMAP3xxx omapdev records > >> OMAP2/3 omapdev: add code to walk the omapdev records > >> ARM: MMU: add a Non-cacheable Normal executable memory type > >> OMAP3 SRAM: mark OCM RAM as Non-cacheable Normal memory > >> OMAP3 SRAM: add ARM barriers to omap3_sram_configure_core_dpll > >> OMAP3 clock: add interconnect barriers to CORE DPLL M2 change > >> OMAP3 SRAM: clear the SDRC PWRENA bit during SDRC > frequency change > >> OMAP3 SDRC: Add 166MHz, 83MHz SDRC settings for the > BeagleBoard > >> OMAP3 SDRC: initialize SDRC_POWER at boot > >> OMAP3 SRAM: renumber registers to make space for > argument passing > >> OMAP3 clock: only unlock SDRC DLL if SDRC clk < 83MHz > >> OMAP3 clock: use pr_debug() rather than pr_info() in > some clock change code > >> OMAP3 clock: remove wait for DPLL3 M2 clock to stabilize > >> OMAP3 clock: initialize SDRC timings at kernel start > >> OMAP3 clock: add a short delay when lowering CORE clk rate > >> OMAP3 clock/SDRC: program SDRC_MR register during > SDRC clock change > >> OMAP3 SRAM: add more comments on the SRAM code > >> OMAP3 SRAM: convert SRAM code to use macros rather than magic > >> numbers > >> > >> Peter 'p2' De Schrijver (12): > >> OMAP: PM counter infrastructure. > >> OMAP: PM: Hook into PM counters > >> OMAP: PM: Add closures to clkdm_for_each and pwrdm_for_each. > >> OMAP: PM: Add pm-debug counters > >> OMAP: PM debug: make powerdomains use PM-debug counters > >> OMAP: PM: Add definitions for ETK pads and > observability registers > >> OMAP: Debug observability and ETK padconf implementation > >> OMAP: Add debug observablity (debobs) Kconfig item > >> OMAP: PM: Implement get_last_off_on_transaction_id() > >> Save sram context after changing MPU, DSP or core clocks > >> Fix omap_getspeed. > >> Make sure omap cpufreq driver initializes after cpufreq > >> framework and governors > >> > >> Rajendra Nayak (35): > >> OMAP3: PM: GPMC context save/restore > >> OMAP3: PM: GPIO context save/restore > >> OMAP3: PM: I2C context save/restore > >> OMAP3: PM: INTC context save/restore > >> OMAP3: PM: PRCM context save/restore > >> OMAP3: PM: Populate scratchpad contents > >> OMAP3: PM: SCM context save/restore > >> OMAP3: PM: SRAM restore function > >> OMAP3: PM: handle PER/NEON/CORE in idle > >> OMAP3: PM: Restore MMU table entry > >> OMAP3: PM: MPU off-mode support > >> OMAP3: PM: CORE domain off-mode support > >> OMAP3: PM: allow runtime enable/disable of OFF mode > >> OMAP3: 3430SDP minimal kernel defconfig > >> OMAP3: PM: CPUidle: Basic support for C1-C2 > >> OMAP3: PM: CPUidle: Enables state C4 > >> OMAP3: PM: CPUidle: Enables C3 and C5 > >> OMAP3: PM: CPUidle: Safe-state on bm-activity > >> OMAP3 SRF: Generic shared resource f/w > >> OMAP3 SRF: MPU/CORE/PD latency modeling > >> OMAP3 SRF: omap3 srf driver > >> OMAP3 SRF: OMAP PM srf implementation > >> OMAP3 SRF: Add CORE rate table param in OMAP-PM > >> OMAP3 SRF: Add VDD1/VDD2 rate tables for 3430SDP > >> OMAP3 SRF: Add virt clk nodes for VDD1/VDD2 > >> OMAP3 SRF: Adds OPP/Freq res's in SRF > >> OMAP3 SRF: Update OMAP-PM layer > >> OMAP3 SRF: Voltage scaling support > >> OMAP3 SRF: VDD2 scaling support > >> OMAP3 SRF: Adds sysfs control for VDD1/VDD2 OPP's > >> OMAP3 PM: Replace spinlocks with mutex in SRF > >> OMAP3 PM: CPUFreq driver for OMAP3 > >> OMAP3 PM: Update the min defconfig for 3430sdp > >> OMAP3 SRF: Fix crash on non-3430SDP platforms with > DVFS/CPUFreq > >> OMAP3: PM: Scale VDD2 OPP for VDD1 OPP3 and higher > >> > >> Tero Kristo (26): > >> OMAP: PM debug: do not print out status for meta > powerdomains (dpll*) > >> OMAP: PM debug: Add PRCM register dump support > >> OMAP: PM: DMA context save / restore > >> OMAP: PM: off-mode support for DMA on EMU/HS devices > >> OMAP3: SRAM size fix for HS/EMU devices > >> OMAP3 PM: off-mode support for HS/EMU devices > >> OMAP3: PM: Enable SDRAM auto-refresh during sleep > >> OMAP: SDRC: Add new register definitions for SDRAM controller > >> OMAP3: PM: SDRC auto-refresh workaround for off-mode > >> PM: Added three PLL registers to the PRCM context save > >> PM: Changed secure RAM storage size from 0x8000 to 0x803F > >> PM: Added suspend target state control to debugfs for OMAP3 > >> OMAP3: PM: Prevent PER from going OFF when CORE is going INA > >> PM OMAP3: Change omap3_save_secure_ram to be called > only during init > >> OMAP3: PM: MPU and CORE should stay awake if there is > CAM domain ACTIVE > >> OMAP3: GPIO fixes for off-mode > >> PM: OMAP3: Refreshed DVFS VDD1 control against latest clock fw > >> OMAP3: Add support for DPLL3 divisor values higher than 2 > >> OMAP3: PM: Fixed VDD2 control to work from both sysfs > and SRF API > >> OMAP3: PM: Added DVFS OPP locking interface for VDD1 and VDD2 > >> OMAP3: Fix rate calculation bug in omap3_select_table_rate > >> OMAP3: PM: Prevented DVFS state switches when > enabling off-mode > >> OMAP3: PM: Enable VDD2 OPP1 > >> OMAP3: PM: Fix linker error without CONFIG_PM option > >> PM: OMAP3: Removed a couple of unused variables from DVFS code > >> PM: OMAP3: Added support for possibly failing clk_set_rate to > >> DVFS > >> > >> -- > >> To unsubscribe from this list: send the line "unsubscribe > linux-omap" > >> in the body of a message to majordomo@vger.kernel.org More > majordomo > >> info at http://vger.kernel.org/majordomo-info.html > >> > > -- > To unsubscribe from this list: send the line "unsubscribe > linux-omap" in the body of a message to > majordomo@vger.kernel.org More majordomo info at > http://vger.kernel.org/majordomo-info.html > > ^ permalink raw reply [flat|nested] 40+ messages in thread
* Re: new PM branch available 2009-01-15 13:42 ` Premi, Sanjeev @ 2009-01-15 15:01 ` Kevin Hilman 2009-01-15 15:17 ` Premi, Sanjeev 0 siblings, 1 reply; 40+ messages in thread From: Kevin Hilman @ 2009-01-15 15:01 UTC (permalink / raw) To: Premi, Sanjeev; +Cc: linux-omap@vger.kernel.org Premi, Sanjeev wrote: >> -----Original Message----- >> From: linux-omap-owner@vger.kernel.org >> [mailto:linux-omap-owner@vger.kernel.org] On Behalf Of Kevin Hilman >> Sent: Wednesday, January 14, 2009 10:10 PM >> To: Sriram V >> Cc: linux-omap@vger.kernel.org >> Subject: Re: new PM branch available >> >> Sriram V wrote: >>> Hi, >>> OMAP3EVM. all domains hit retention in suspend. >>> >>> On enabling cpuidle, network and mmc is not stable. network is >>> unable to get an IP address. >> Sriram, >> >> Can you send me your .config for omap3evm? I'm trying to get >> my recently received EVM working but I am getting lots of >> garbage on the serial console on linux-omap HEAD and PM >> branch on omap3evm. Do you have any additional patches for >> EVM that you're using? >> >> Kevin >> > > Hi Kevin, > > I was able to test against the HEAD 'pm' branch on the EVM. > Here are my observations with default configuration: > > 1) CONFIG_DEBUG_LL=y is set by default. The kernel boots fine. > I did not notice any 'garbage' problems you and Koen seem to > be getting. > > 2) Same result when CONFIG_DEBUG_LL is deselcted. Sanjeev, Is this on an an ES3 EVM? What boot loader revs are you using? > 3) With default config, suspend operation fails with this message: > <3>omapfb omapfb: timeout waiting for FRAME DONE This is not a failure, just a warning from the fb driver. This should not prevent retention. I see this on beagle as well, and it doesn't prevent retention. From the log below, you didn't copy the part which reports whether all domains hit target state. Kevin > Here is a sample session from my terminal: > > [root@OMAP3EVM /]# uname -a > Linux OMAP3EVM 2.6.28-omap1-00115-g998bd56 #146 Thu Jan 15 18:47:26 IST 2009 armv7l unknown > [root@OMAP3EVM /]# echo 1 > /sys/power/clocks_off_while_idle > [root@OMAP3EVM /]# echo 1 > /sys/power/sleep_while_idle > [root@OMAP3EVM /]# > [root@OMAP3EVM /]# echo mem > /sys/power/state > <6>PM: Syncing filesystems ... PM: Syncing filesystems ... done. > done. > Freezing user space processes ... Freezing user space processes ... (elapsed 0.00 seconds) (elapsed 0.00 seconds) done. > done. > Freezing remaining freezable tasks ... Freezing remaining freezable tasks ... (elapsed 0.06 seconds) (elapsed 0.06 seconds) done.done. > > Suspending console(s) (use no_console_suspend to debug) > Suspending console(s) (use no_console_suspend to debug) > > Best regards, > Sanjeev > >>> On Wed, Jan 14, 2009 at 3:21 AM, Kevin Hilman >>> <khilman@deeprootsystems.com> wrote: >>>> Hello, >>>> >>>> The latest PM branch is now available[1]. >>>> >>>> I've done basic testing of retention and off-mode (suspend and >>>> dynamic >>>> idle) on Beagle and custom HW. My SDP has something still keeping >>>> CORE active that others have not seen, but I have yet to >> debug. Any >>>> other reports from SDP testing would be appreciated. >>>> >>>> Notable changes/updates >>>> - rebased on latest clock updates and fixes from Paul >>>> - clockfw pre- and post- notifiers >>>> - DVFS for VDD2 >>>> >>>> Full git shortlog below[2] >>>> >>>> Enjoy, >>>> >>>> Kevin >>>> >>>> [1] See branch 'pm' in my git repo: >>>> >> git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap-pm.g >>>> it which is also mirrored as the branch 'pm' of the normal >> linux-omap >>>> repo (but will not sync until 03:30 GMT) >>>> >>>> >>>> [2] git shortlog: >>>> >>>> Carlos Chinea (1): >>>> OMAP3:PM: Update SSI omapdev record >>>> >>>> Jouni Hogander (5): >>>> OMAP3: PM: Use pwrdm_set_next_pwrst instead of >> set_pwrdm_state in idle loop >>>> OMAP3: PM: Fix wrong sequence in suspend. >>>> OMAP3: PM: Do not build suspend code if SUSPEND is not enabled >>>> OMAP: PM: Build fails if PM is not enabled >>>> OMAP2: PM: Fix omap2 build >>>> >>>> Kalle Jokiniemi (3): >>>> OMAP: PM: sysfs interface for enabling voltage off in idle >>>> OMAP3: PM: Fix cpu idle init sequencing >>>> OMAP: SRF: Fixes to shared resource framework (Ver.3) >>>> >>>> Kevin Hilman (4): >>>> OMAP3: PM: CPUidle: obey enable_off_mode flag >>>> OMAP3: PM: CPUidle: restrict C-states on UART activity >>>> OMAP3: PM: decouple PER and CORE context save and restore >>>> OMAP2/3: PM: system_rev -> omap_rev() >>>> >>>> Paul Walmsley (29): >>>> OMAP2/3 clock: implement clock notifier infrastructure >>>> OMAP clock: add notifier infrastructure >>>> OMAP2/3 clock: store planned clock rates into >> temporary rate storage >>>> OMAP2/3 clock: add clk post-rate-change notifiers >>>> OMAP2/3 clock: add clock pre-rate-change notification >>>> OMAP2/3 clock: add clock prepare-rate-change notifications >>>> OMAP2/3 clock: add clock abort-rate-change notifications >>>> OMAP2/3 PM: create the OMAP PM interface and add a >> default OMAP PM no-op layer. >>>> OMAP2/3 omapdev: add basic omapdev structure >>>> OMAP242x omapdev: add OMAP242x omapdev records >>>> OMAP243x omapdev: add OMAP243x omapdev records >>>> OMAP3xxx omapdev: add OMAP3xxx omapdev records >>>> OMAP2/3 omapdev: add code to walk the omapdev records >>>> ARM: MMU: add a Non-cacheable Normal executable memory type >>>> OMAP3 SRAM: mark OCM RAM as Non-cacheable Normal memory >>>> OMAP3 SRAM: add ARM barriers to omap3_sram_configure_core_dpll >>>> OMAP3 clock: add interconnect barriers to CORE DPLL M2 change >>>> OMAP3 SRAM: clear the SDRC PWRENA bit during SDRC >> frequency change >>>> OMAP3 SDRC: Add 166MHz, 83MHz SDRC settings for the >> BeagleBoard >>>> OMAP3 SDRC: initialize SDRC_POWER at boot >>>> OMAP3 SRAM: renumber registers to make space for >> argument passing >>>> OMAP3 clock: only unlock SDRC DLL if SDRC clk < 83MHz >>>> OMAP3 clock: use pr_debug() rather than pr_info() in >> some clock change code >>>> OMAP3 clock: remove wait for DPLL3 M2 clock to stabilize >>>> OMAP3 clock: initialize SDRC timings at kernel start >>>> OMAP3 clock: add a short delay when lowering CORE clk rate >>>> OMAP3 clock/SDRC: program SDRC_MR register during >> SDRC clock change >>>> OMAP3 SRAM: add more comments on the SRAM code >>>> OMAP3 SRAM: convert SRAM code to use macros rather than magic >>>> numbers >>>> >>>> Peter 'p2' De Schrijver (12): >>>> OMAP: PM counter infrastructure. >>>> OMAP: PM: Hook into PM counters >>>> OMAP: PM: Add closures to clkdm_for_each and pwrdm_for_each. >>>> OMAP: PM: Add pm-debug counters >>>> OMAP: PM debug: make powerdomains use PM-debug counters >>>> OMAP: PM: Add definitions for ETK pads and >> observability registers >>>> OMAP: Debug observability and ETK padconf implementation >>>> OMAP: Add debug observablity (debobs) Kconfig item >>>> OMAP: PM: Implement get_last_off_on_transaction_id() >>>> Save sram context after changing MPU, DSP or core clocks >>>> Fix omap_getspeed. >>>> Make sure omap cpufreq driver initializes after cpufreq >>>> framework and governors >>>> >>>> Rajendra Nayak (35): >>>> OMAP3: PM: GPMC context save/restore >>>> OMAP3: PM: GPIO context save/restore >>>> OMAP3: PM: I2C context save/restore >>>> OMAP3: PM: INTC context save/restore >>>> OMAP3: PM: PRCM context save/restore >>>> OMAP3: PM: Populate scratchpad contents >>>> OMAP3: PM: SCM context save/restore >>>> OMAP3: PM: SRAM restore function >>>> OMAP3: PM: handle PER/NEON/CORE in idle >>>> OMAP3: PM: Restore MMU table entry >>>> OMAP3: PM: MPU off-mode support >>>> OMAP3: PM: CORE domain off-mode support >>>> OMAP3: PM: allow runtime enable/disable of OFF mode >>>> OMAP3: 3430SDP minimal kernel defconfig >>>> OMAP3: PM: CPUidle: Basic support for C1-C2 >>>> OMAP3: PM: CPUidle: Enables state C4 >>>> OMAP3: PM: CPUidle: Enables C3 and C5 >>>> OMAP3: PM: CPUidle: Safe-state on bm-activity >>>> OMAP3 SRF: Generic shared resource f/w >>>> OMAP3 SRF: MPU/CORE/PD latency modeling >>>> OMAP3 SRF: omap3 srf driver >>>> OMAP3 SRF: OMAP PM srf implementation >>>> OMAP3 SRF: Add CORE rate table param in OMAP-PM >>>> OMAP3 SRF: Add VDD1/VDD2 rate tables for 3430SDP >>>> OMAP3 SRF: Add virt clk nodes for VDD1/VDD2 >>>> OMAP3 SRF: Adds OPP/Freq res's in SRF >>>> OMAP3 SRF: Update OMAP-PM layer >>>> OMAP3 SRF: Voltage scaling support >>>> OMAP3 SRF: VDD2 scaling support >>>> OMAP3 SRF: Adds sysfs control for VDD1/VDD2 OPP's >>>> OMAP3 PM: Replace spinlocks with mutex in SRF >>>> OMAP3 PM: CPUFreq driver for OMAP3 >>>> OMAP3 PM: Update the min defconfig for 3430sdp >>>> OMAP3 SRF: Fix crash on non-3430SDP platforms with >> DVFS/CPUFreq >>>> OMAP3: PM: Scale VDD2 OPP for VDD1 OPP3 and higher >>>> >>>> Tero Kristo (26): >>>> OMAP: PM debug: do not print out status for meta >> powerdomains (dpll*) >>>> OMAP: PM debug: Add PRCM register dump support >>>> OMAP: PM: DMA context save / restore >>>> OMAP: PM: off-mode support for DMA on EMU/HS devices >>>> OMAP3: SRAM size fix for HS/EMU devices >>>> OMAP3 PM: off-mode support for HS/EMU devices >>>> OMAP3: PM: Enable SDRAM auto-refresh during sleep >>>> OMAP: SDRC: Add new register definitions for SDRAM controller >>>> OMAP3: PM: SDRC auto-refresh workaround for off-mode >>>> PM: Added three PLL registers to the PRCM context save >>>> PM: Changed secure RAM storage size from 0x8000 to 0x803F >>>> PM: Added suspend target state control to debugfs for OMAP3 >>>> OMAP3: PM: Prevent PER from going OFF when CORE is going INA >>>> PM OMAP3: Change omap3_save_secure_ram to be called >> only during init >>>> OMAP3: PM: MPU and CORE should stay awake if there is >> CAM domain ACTIVE >>>> OMAP3: GPIO fixes for off-mode >>>> PM: OMAP3: Refreshed DVFS VDD1 control against latest clock fw >>>> OMAP3: Add support for DPLL3 divisor values higher than 2 >>>> OMAP3: PM: Fixed VDD2 control to work from both sysfs >> and SRF API >>>> OMAP3: PM: Added DVFS OPP locking interface for VDD1 and VDD2 >>>> OMAP3: Fix rate calculation bug in omap3_select_table_rate >>>> OMAP3: PM: Prevented DVFS state switches when >> enabling off-mode >>>> OMAP3: PM: Enable VDD2 OPP1 >>>> OMAP3: PM: Fix linker error without CONFIG_PM option >>>> PM: OMAP3: Removed a couple of unused variables from DVFS code >>>> PM: OMAP3: Added support for possibly failing clk_set_rate to >>>> DVFS >>>> >>>> -- >>>> To unsubscribe from this list: send the line "unsubscribe >> linux-omap" >>>> in the body of a message to majordomo@vger.kernel.org More >> majordomo >>>> info at http://vger.kernel.org/majordomo-info.html >>>> >> -- >> To unsubscribe from this list: send the line "unsubscribe >> linux-omap" in the body of a message to >> majordomo@vger.kernel.org More majordomo info at >> http://vger.kernel.org/majordomo-info.html >> ^ permalink raw reply [flat|nested] 40+ messages in thread
* RE: new PM branch available 2009-01-15 15:01 ` Kevin Hilman @ 2009-01-15 15:17 ` Premi, Sanjeev 2009-01-15 15:34 ` Kevin Hilman 0 siblings, 1 reply; 40+ messages in thread From: Premi, Sanjeev @ 2009-01-15 15:17 UTC (permalink / raw) To: Kevin Hilman; +Cc: linux-omap@vger.kernel.org > -----Original Message----- > From: Kevin Hilman [mailto:khilman@deeprootsystems.com] > Sent: Thursday, January 15, 2009 8:32 PM > To: Premi, Sanjeev > Cc: linux-omap@vger.kernel.org > Subject: Re: new PM branch available > > Premi, Sanjeev wrote: > >> -----Original Message----- > >> From: linux-omap-owner@vger.kernel.org > >> [mailto:linux-omap-owner@vger.kernel.org] On Behalf Of Kevin Hilman > >> Sent: Wednesday, January 14, 2009 10:10 PM > >> To: Sriram V > >> Cc: linux-omap@vger.kernel.org > >> Subject: Re: new PM branch available > >> > >> Sriram V wrote: > >>> Hi, > >>> OMAP3EVM. all domains hit retention in suspend. > >>> > >>> On enabling cpuidle, network and mmc is not stable. network is > >>> unable to get an IP address. > >> Sriram, > >> > >> Can you send me your .config for omap3evm? I'm trying to get my > >> recently received EVM working but I am getting lots of > garbage on the > >> serial console on linux-omap HEAD and PM branch on > omap3evm. Do you > >> have any additional patches for EVM that you're using? > >> > >> Kevin > >> > > > > Hi Kevin, > > > > I was able to test against the HEAD 'pm' branch on the EVM. > > Here are my observations with default configuration: > > > > 1) CONFIG_DEBUG_LL=y is set by default. The kernel boots fine. > > I did not notice any 'garbage' problems you and Koen seem to > > be getting. > > > > 2) Same result when CONFIG_DEBUG_LL is deselcted. > > Sanjeev, > > Is this on an an ES3 EVM? What boot loader revs are you using? [sp] I am using EVM with ES3.0 while Vaibhav is using one with ES2.1 > > 3) With default config, suspend operation fails with this message: > > <3>omapfb omapfb: timeout waiting for FRAME DONE > > This is not a failure, just a warning from the fb driver. > This should not prevent retention. I see this on beagle as > well, and it doesn't prevent retention. > > From the log below, you didn't copy the part which reports > whether all domains hit target state. [sp] This is where it hangs :( After sending the last mail, I tried the same without enabling "clocks_off_while_idle" and "sleep_while_idle" then: omapfb omapfb: timeout waiting for FRAME DONE Powerdomain (core_pwrdm) didn't enter target state 1 Powerdomain (per_pwrdm) didn't enter target state 1 Could not enter target state in pm_suspend I am building a config without FB. Will update as soon as I can test it. > Kevin > > > Here is a sample session from my terminal: > > > > [root@OMAP3EVM /]# uname -a > > Linux OMAP3EVM 2.6.28-omap1-00115-g998bd56 #146 Thu Jan 15 18:47:26 > > IST 2009 armv7l unknown [root@OMAP3EVM /]# echo 1 > > > /sys/power/clocks_off_while_idle [root@OMAP3EVM /]# echo 1 > > > /sys/power/sleep_while_idle [root@OMAP3EVM /]# > [root@OMAP3EVM /]# echo > > mem > /sys/power/state > > <6>PM: Syncing filesystems ... PM: Syncing filesystems ... done. > > done. > > Freezing user space processes ... Freezing user space > processes ... (elapsed 0.00 seconds) (elapsed 0.00 seconds) done. > > done. > > Freezing remaining freezable tasks ... Freezing remaining > freezable tasks ... (elapsed 0.06 seconds) (elapsed 0.06 > seconds) done.done. > > > > Suspending console(s) (use no_console_suspend to debug) Suspending > > console(s) (use no_console_suspend to debug) > > > > Best regards, > > Sanjeev > > > >>> On Wed, Jan 14, 2009 at 3:21 AM, Kevin Hilman > >>> <khilman@deeprootsystems.com> wrote: > >>>> Hello, > >>>> > >>>> The latest PM branch is now available[1]. > >>>> > >>>> I've done basic testing of retention and off-mode (suspend and > >>>> dynamic > >>>> idle) on Beagle and custom HW. My SDP has something > still keeping > >>>> CORE active that others have not seen, but I have yet to > >> debug. Any > >>>> other reports from SDP testing would be appreciated. > >>>> > >>>> Notable changes/updates > >>>> - rebased on latest clock updates and fixes from Paul > >>>> - clockfw pre- and post- notifiers > >>>> - DVFS for VDD2 > >>>> > >>>> Full git shortlog below[2] > >>>> > >>>> Enjoy, > >>>> > >>>> Kevin > >>>> > >>>> [1] See branch 'pm' in my git repo: > >>>> > >> > git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap-pm.g > >>>> it which is also mirrored as the branch 'pm' of the normal > >> linux-omap > >>>> repo (but will not sync until 03:30 GMT) > >>>> > >>>> > >>>> [2] git shortlog: > >>>> > >>>> Carlos Chinea (1): > >>>> OMAP3:PM: Update SSI omapdev record > >>>> > >>>> Jouni Hogander (5): > >>>> OMAP3: PM: Use pwrdm_set_next_pwrst instead of > >> set_pwrdm_state in idle loop > >>>> OMAP3: PM: Fix wrong sequence in suspend. > >>>> OMAP3: PM: Do not build suspend code if SUSPEND is > not enabled > >>>> OMAP: PM: Build fails if PM is not enabled > >>>> OMAP2: PM: Fix omap2 build > >>>> > >>>> Kalle Jokiniemi (3): > >>>> OMAP: PM: sysfs interface for enabling voltage off in idle > >>>> OMAP3: PM: Fix cpu idle init sequencing > >>>> OMAP: SRF: Fixes to shared resource framework (Ver.3) > >>>> > >>>> Kevin Hilman (4): > >>>> OMAP3: PM: CPUidle: obey enable_off_mode flag > >>>> OMAP3: PM: CPUidle: restrict C-states on UART activity > >>>> OMAP3: PM: decouple PER and CORE context save and restore > >>>> OMAP2/3: PM: system_rev -> omap_rev() > >>>> > >>>> Paul Walmsley (29): > >>>> OMAP2/3 clock: implement clock notifier infrastructure > >>>> OMAP clock: add notifier infrastructure > >>>> OMAP2/3 clock: store planned clock rates into > >> temporary rate storage > >>>> OMAP2/3 clock: add clk post-rate-change notifiers > >>>> OMAP2/3 clock: add clock pre-rate-change notification > >>>> OMAP2/3 clock: add clock prepare-rate-change notifications > >>>> OMAP2/3 clock: add clock abort-rate-change notifications > >>>> OMAP2/3 PM: create the OMAP PM interface and add a > >> default OMAP PM no-op layer. > >>>> OMAP2/3 omapdev: add basic omapdev structure > >>>> OMAP242x omapdev: add OMAP242x omapdev records > >>>> OMAP243x omapdev: add OMAP243x omapdev records > >>>> OMAP3xxx omapdev: add OMAP3xxx omapdev records > >>>> OMAP2/3 omapdev: add code to walk the omapdev records > >>>> ARM: MMU: add a Non-cacheable Normal executable memory type > >>>> OMAP3 SRAM: mark OCM RAM as Non-cacheable Normal memory > >>>> OMAP3 SRAM: add ARM barriers to > omap3_sram_configure_core_dpll > >>>> OMAP3 clock: add interconnect barriers to CORE DPLL > M2 change > >>>> OMAP3 SRAM: clear the SDRC PWRENA bit during SDRC > >> frequency change > >>>> OMAP3 SDRC: Add 166MHz, 83MHz SDRC settings for the > >> BeagleBoard > >>>> OMAP3 SDRC: initialize SDRC_POWER at boot > >>>> OMAP3 SRAM: renumber registers to make space for > >> argument passing > >>>> OMAP3 clock: only unlock SDRC DLL if SDRC clk < 83MHz > >>>> OMAP3 clock: use pr_debug() rather than pr_info() in > >> some clock change code > >>>> OMAP3 clock: remove wait for DPLL3 M2 clock to stabilize > >>>> OMAP3 clock: initialize SDRC timings at kernel start > >>>> OMAP3 clock: add a short delay when lowering CORE clk rate > >>>> OMAP3 clock/SDRC: program SDRC_MR register during > >> SDRC clock change > >>>> OMAP3 SRAM: add more comments on the SRAM code > >>>> OMAP3 SRAM: convert SRAM code to use macros rather > than magic > >>>> numbers > >>>> > >>>> Peter 'p2' De Schrijver (12): > >>>> OMAP: PM counter infrastructure. > >>>> OMAP: PM: Hook into PM counters > >>>> OMAP: PM: Add closures to clkdm_for_each and pwrdm_for_each. > >>>> OMAP: PM: Add pm-debug counters > >>>> OMAP: PM debug: make powerdomains use PM-debug counters > >>>> OMAP: PM: Add definitions for ETK pads and > >> observability registers > >>>> OMAP: Debug observability and ETK padconf implementation > >>>> OMAP: Add debug observablity (debobs) Kconfig item > >>>> OMAP: PM: Implement get_last_off_on_transaction_id() > >>>> Save sram context after changing MPU, DSP or core clocks > >>>> Fix omap_getspeed. > >>>> Make sure omap cpufreq driver initializes after cpufreq > >>>> framework and governors > >>>> > >>>> Rajendra Nayak (35): > >>>> OMAP3: PM: GPMC context save/restore > >>>> OMAP3: PM: GPIO context save/restore > >>>> OMAP3: PM: I2C context save/restore > >>>> OMAP3: PM: INTC context save/restore > >>>> OMAP3: PM: PRCM context save/restore > >>>> OMAP3: PM: Populate scratchpad contents > >>>> OMAP3: PM: SCM context save/restore > >>>> OMAP3: PM: SRAM restore function > >>>> OMAP3: PM: handle PER/NEON/CORE in idle > >>>> OMAP3: PM: Restore MMU table entry > >>>> OMAP3: PM: MPU off-mode support > >>>> OMAP3: PM: CORE domain off-mode support > >>>> OMAP3: PM: allow runtime enable/disable of OFF mode > >>>> OMAP3: 3430SDP minimal kernel defconfig > >>>> OMAP3: PM: CPUidle: Basic support for C1-C2 > >>>> OMAP3: PM: CPUidle: Enables state C4 > >>>> OMAP3: PM: CPUidle: Enables C3 and C5 > >>>> OMAP3: PM: CPUidle: Safe-state on bm-activity > >>>> OMAP3 SRF: Generic shared resource f/w > >>>> OMAP3 SRF: MPU/CORE/PD latency modeling > >>>> OMAP3 SRF: omap3 srf driver > >>>> OMAP3 SRF: OMAP PM srf implementation > >>>> OMAP3 SRF: Add CORE rate table param in OMAP-PM > >>>> OMAP3 SRF: Add VDD1/VDD2 rate tables for 3430SDP > >>>> OMAP3 SRF: Add virt clk nodes for VDD1/VDD2 > >>>> OMAP3 SRF: Adds OPP/Freq res's in SRF > >>>> OMAP3 SRF: Update OMAP-PM layer > >>>> OMAP3 SRF: Voltage scaling support > >>>> OMAP3 SRF: VDD2 scaling support > >>>> OMAP3 SRF: Adds sysfs control for VDD1/VDD2 OPP's > >>>> OMAP3 PM: Replace spinlocks with mutex in SRF > >>>> OMAP3 PM: CPUFreq driver for OMAP3 > >>>> OMAP3 PM: Update the min defconfig for 3430sdp > >>>> OMAP3 SRF: Fix crash on non-3430SDP platforms with > >> DVFS/CPUFreq > >>>> OMAP3: PM: Scale VDD2 OPP for VDD1 OPP3 and higher > >>>> > >>>> Tero Kristo (26): > >>>> OMAP: PM debug: do not print out status for meta > >> powerdomains (dpll*) > >>>> OMAP: PM debug: Add PRCM register dump support > >>>> OMAP: PM: DMA context save / restore > >>>> OMAP: PM: off-mode support for DMA on EMU/HS devices > >>>> OMAP3: SRAM size fix for HS/EMU devices > >>>> OMAP3 PM: off-mode support for HS/EMU devices > >>>> OMAP3: PM: Enable SDRAM auto-refresh during sleep > >>>> OMAP: SDRC: Add new register definitions for SDRAM > controller > >>>> OMAP3: PM: SDRC auto-refresh workaround for off-mode > >>>> PM: Added three PLL registers to the PRCM context save > >>>> PM: Changed secure RAM storage size from 0x8000 to 0x803F > >>>> PM: Added suspend target state control to debugfs for OMAP3 > >>>> OMAP3: PM: Prevent PER from going OFF when CORE is going INA > >>>> PM OMAP3: Change omap3_save_secure_ram to be called > >> only during init > >>>> OMAP3: PM: MPU and CORE should stay awake if there is > >> CAM domain ACTIVE > >>>> OMAP3: GPIO fixes for off-mode > >>>> PM: OMAP3: Refreshed DVFS VDD1 control against > latest clock fw > >>>> OMAP3: Add support for DPLL3 divisor values higher than 2 > >>>> OMAP3: PM: Fixed VDD2 control to work from both sysfs > >> and SRF API > >>>> OMAP3: PM: Added DVFS OPP locking interface for > VDD1 and VDD2 > >>>> OMAP3: Fix rate calculation bug in omap3_select_table_rate > >>>> OMAP3: PM: Prevented DVFS state switches when > >> enabling off-mode > >>>> OMAP3: PM: Enable VDD2 OPP1 > >>>> OMAP3: PM: Fix linker error without CONFIG_PM option > >>>> PM: OMAP3: Removed a couple of unused variables > from DVFS code > >>>> PM: OMAP3: Added support for possibly failing > clk_set_rate to > >>>> DVFS > >>>> > >>>> -- > >>>> To unsubscribe from this list: send the line "unsubscribe > >> linux-omap" > >>>> in the body of a message to majordomo@vger.kernel.org More > >> majordomo > >>>> info at http://vger.kernel.org/majordomo-info.html > >>>> > >> -- > >> To unsubscribe from this list: send the line "unsubscribe > linux-omap" > >> in the body of a message to majordomo@vger.kernel.org More > majordomo > >> info at http://vger.kernel.org/majordomo-info.html > >> > > > ^ permalink raw reply [flat|nested] 40+ messages in thread
* Re: new PM branch available 2009-01-15 15:17 ` Premi, Sanjeev @ 2009-01-15 15:34 ` Kevin Hilman 2009-01-15 16:00 ` Premi, Sanjeev 0 siblings, 1 reply; 40+ messages in thread From: Kevin Hilman @ 2009-01-15 15:34 UTC (permalink / raw) To: Premi, Sanjeev; +Cc: linux-omap@vger.kernel.org Premi, Sanjeev wrote: >> -----Original Message----- >> From: Kevin Hilman [mailto:khilman@deeprootsystems.com] >> Sent: Thursday, January 15, 2009 8:32 PM >> To: Premi, Sanjeev >> Cc: linux-omap@vger.kernel.org >> Subject: Re: new PM branch available >> >> Premi, Sanjeev wrote: >>>> -----Original Message----- >>>> From: linux-omap-owner@vger.kernel.org >>>> [mailto:linux-omap-owner@vger.kernel.org] On Behalf Of Kevin Hilman >>>> Sent: Wednesday, January 14, 2009 10:10 PM >>>> To: Sriram V >>>> Cc: linux-omap@vger.kernel.org >>>> Subject: Re: new PM branch available >>>> >>>> Sriram V wrote: >>>>> Hi, >>>>> OMAP3EVM. all domains hit retention in suspend. >>>>> >>>>> On enabling cpuidle, network and mmc is not stable. network is >>>>> unable to get an IP address. >>>> Sriram, >>>> >>>> Can you send me your .config for omap3evm? I'm trying to get my >>>> recently received EVM working but I am getting lots of >> garbage on the >>>> serial console on linux-omap HEAD and PM branch on >> omap3evm. Do you >>>> have any additional patches for EVM that you're using? >>>> >>>> Kevin >>>> >>> Hi Kevin, >>> >>> I was able to test against the HEAD 'pm' branch on the EVM. >>> Here are my observations with default configuration: >>> >>> 1) CONFIG_DEBUG_LL=y is set by default. The kernel boots fine. >>> I did not notice any 'garbage' problems you and Koen seem to >>> be getting. >>> >>> 2) Same result when CONFIG_DEBUG_LL is deselcted. >> Sanjeev, >> >> Is this on an an ES3 EVM? What boot loader revs are you using? > > [sp] I am using EVM with ES3.0 while Vaibhav is using one with ES2.1 What are your x-loader and u-boot versions? Mine are: Texas Instruments X-Loader 1.41 [...] U-Boot 1.1.4 (Jun 5 2008 - 17:53:37) >>> 3) With default config, suspend operation fails with this message: >>> <3>omapfb omapfb: timeout waiting for FRAME DONE >> This is not a failure, just a warning from the fb driver. >> This should not prevent retention. I see this on beagle as >> well, and it doesn't prevent retention. >> >> From the log below, you didn't copy the part which reports >> whether all domains hit target state. > > [sp] This is where it hangs :( It's not hung. It's just sleeping, but refuses to wakeup (like I should've done this morning.) What are you using as your wakeup source? UART? keypad? I'm not sure how the UARTs are mux'd on this board, but you probably want to check the wake-enable bits in the padconf reg for the UART pins. This is done by arch/arm/mach-omap2/serial.c but assumes the UARTs are mux'd using the default registers. Each UART has a couple possible ways to be mux'd. > After sending the last mail, I tried the same without enabling "clocks_off_while_idle" and "sleep_while_idle" then: > > omapfb omapfb: timeout waiting for FRAME DONE > Powerdomain (core_pwrdm) didn't enter target state 1 > Powerdomain (per_pwrdm) didn't enter target state 1 > Could not enter target state in pm_suspend > I am building a config without FB. Will update as soon as I can test it. > >> Kevin >> >>> Here is a sample session from my terminal: >>> >>> [root@OMAP3EVM /]# uname -a >>> Linux OMAP3EVM 2.6.28-omap1-00115-g998bd56 #146 Thu Jan 15 18:47:26 >>> IST 2009 armv7l unknown [root@OMAP3EVM /]# echo 1 > >>> /sys/power/clocks_off_while_idle [root@OMAP3EVM /]# echo 1 > >>> /sys/power/sleep_while_idle [root@OMAP3EVM /]# >> [root@OMAP3EVM /]# echo >>> mem > /sys/power/state >>> <6>PM: Syncing filesystems ... PM: Syncing filesystems ... done. >>> done. >>> Freezing user space processes ... Freezing user space >> processes ... (elapsed 0.00 seconds) (elapsed 0.00 seconds) done. >>> done. >>> Freezing remaining freezable tasks ... Freezing remaining >> freezable tasks ... (elapsed 0.06 seconds) (elapsed 0.06 >> seconds) done.done. >>> Suspending console(s) (use no_console_suspend to debug) Suspending >>> console(s) (use no_console_suspend to debug) >>> >>> Best regards, >>> Sanjeev >>> >>>>> On Wed, Jan 14, 2009 at 3:21 AM, Kevin Hilman >>>>> <khilman@deeprootsystems.com> wrote: >>>>>> Hello, >>>>>> >>>>>> The latest PM branch is now available[1]. >>>>>> >>>>>> I've done basic testing of retention and off-mode (suspend and >>>>>> dynamic >>>>>> idle) on Beagle and custom HW. My SDP has something >> still keeping >>>>>> CORE active that others have not seen, but I have yet to >>>> debug. Any >>>>>> other reports from SDP testing would be appreciated. >>>>>> >>>>>> Notable changes/updates >>>>>> - rebased on latest clock updates and fixes from Paul >>>>>> - clockfw pre- and post- notifiers >>>>>> - DVFS for VDD2 >>>>>> >>>>>> Full git shortlog below[2] >>>>>> >>>>>> Enjoy, >>>>>> >>>>>> Kevin >>>>>> >>>>>> [1] See branch 'pm' in my git repo: >>>>>> >> git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap-pm.g >>>>>> it which is also mirrored as the branch 'pm' of the normal >>>> linux-omap >>>>>> repo (but will not sync until 03:30 GMT) >>>>>> >>>>>> >>>>>> [2] git shortlog: >>>>>> >>>>>> Carlos Chinea (1): >>>>>> OMAP3:PM: Update SSI omapdev record >>>>>> >>>>>> Jouni Hogander (5): >>>>>> OMAP3: PM: Use pwrdm_set_next_pwrst instead of >>>> set_pwrdm_state in idle loop >>>>>> OMAP3: PM: Fix wrong sequence in suspend. >>>>>> OMAP3: PM: Do not build suspend code if SUSPEND is >> not enabled >>>>>> OMAP: PM: Build fails if PM is not enabled >>>>>> OMAP2: PM: Fix omap2 build >>>>>> >>>>>> Kalle Jokiniemi (3): >>>>>> OMAP: PM: sysfs interface for enabling voltage off in idle >>>>>> OMAP3: PM: Fix cpu idle init sequencing >>>>>> OMAP: SRF: Fixes to shared resource framework (Ver.3) >>>>>> >>>>>> Kevin Hilman (4): >>>>>> OMAP3: PM: CPUidle: obey enable_off_mode flag >>>>>> OMAP3: PM: CPUidle: restrict C-states on UART activity >>>>>> OMAP3: PM: decouple PER and CORE context save and restore >>>>>> OMAP2/3: PM: system_rev -> omap_rev() >>>>>> >>>>>> Paul Walmsley (29): >>>>>> OMAP2/3 clock: implement clock notifier infrastructure >>>>>> OMAP clock: add notifier infrastructure >>>>>> OMAP2/3 clock: store planned clock rates into >>>> temporary rate storage >>>>>> OMAP2/3 clock: add clk post-rate-change notifiers >>>>>> OMAP2/3 clock: add clock pre-rate-change notification >>>>>> OMAP2/3 clock: add clock prepare-rate-change notifications >>>>>> OMAP2/3 clock: add clock abort-rate-change notifications >>>>>> OMAP2/3 PM: create the OMAP PM interface and add a >>>> default OMAP PM no-op layer. >>>>>> OMAP2/3 omapdev: add basic omapdev structure >>>>>> OMAP242x omapdev: add OMAP242x omapdev records >>>>>> OMAP243x omapdev: add OMAP243x omapdev records >>>>>> OMAP3xxx omapdev: add OMAP3xxx omapdev records >>>>>> OMAP2/3 omapdev: add code to walk the omapdev records >>>>>> ARM: MMU: add a Non-cacheable Normal executable memory type >>>>>> OMAP3 SRAM: mark OCM RAM as Non-cacheable Normal memory >>>>>> OMAP3 SRAM: add ARM barriers to >> omap3_sram_configure_core_dpll >>>>>> OMAP3 clock: add interconnect barriers to CORE DPLL >> M2 change >>>>>> OMAP3 SRAM: clear the SDRC PWRENA bit during SDRC >>>> frequency change >>>>>> OMAP3 SDRC: Add 166MHz, 83MHz SDRC settings for the >>>> BeagleBoard >>>>>> OMAP3 SDRC: initialize SDRC_POWER at boot >>>>>> OMAP3 SRAM: renumber registers to make space for >>>> argument passing >>>>>> OMAP3 clock: only unlock SDRC DLL if SDRC clk < 83MHz >>>>>> OMAP3 clock: use pr_debug() rather than pr_info() in >>>> some clock change code >>>>>> OMAP3 clock: remove wait for DPLL3 M2 clock to stabilize >>>>>> OMAP3 clock: initialize SDRC timings at kernel start >>>>>> OMAP3 clock: add a short delay when lowering CORE clk rate >>>>>> OMAP3 clock/SDRC: program SDRC_MR register during >>>> SDRC clock change >>>>>> OMAP3 SRAM: add more comments on the SRAM code >>>>>> OMAP3 SRAM: convert SRAM code to use macros rather >> than magic >>>>>> numbers >>>>>> >>>>>> Peter 'p2' De Schrijver (12): >>>>>> OMAP: PM counter infrastructure. >>>>>> OMAP: PM: Hook into PM counters >>>>>> OMAP: PM: Add closures to clkdm_for_each and pwrdm_for_each. >>>>>> OMAP: PM: Add pm-debug counters >>>>>> OMAP: PM debug: make powerdomains use PM-debug counters >>>>>> OMAP: PM: Add definitions for ETK pads and >>>> observability registers >>>>>> OMAP: Debug observability and ETK padconf implementation >>>>>> OMAP: Add debug observablity (debobs) Kconfig item >>>>>> OMAP: PM: Implement get_last_off_on_transaction_id() >>>>>> Save sram context after changing MPU, DSP or core clocks >>>>>> Fix omap_getspeed. >>>>>> Make sure omap cpufreq driver initializes after cpufreq >>>>>> framework and governors >>>>>> >>>>>> Rajendra Nayak (35): >>>>>> OMAP3: PM: GPMC context save/restore >>>>>> OMAP3: PM: GPIO context save/restore >>>>>> OMAP3: PM: I2C context save/restore >>>>>> OMAP3: PM: INTC context save/restore >>>>>> OMAP3: PM: PRCM context save/restore >>>>>> OMAP3: PM: Populate scratchpad contents >>>>>> OMAP3: PM: SCM context save/restore >>>>>> OMAP3: PM: SRAM restore function >>>>>> OMAP3: PM: handle PER/NEON/CORE in idle >>>>>> OMAP3: PM: Restore MMU table entry >>>>>> OMAP3: PM: MPU off-mode support >>>>>> OMAP3: PM: CORE domain off-mode support >>>>>> OMAP3: PM: allow runtime enable/disable of OFF mode >>>>>> OMAP3: 3430SDP minimal kernel defconfig >>>>>> OMAP3: PM: CPUidle: Basic support for C1-C2 >>>>>> OMAP3: PM: CPUidle: Enables state C4 >>>>>> OMAP3: PM: CPUidle: Enables C3 and C5 >>>>>> OMAP3: PM: CPUidle: Safe-state on bm-activity >>>>>> OMAP3 SRF: Generic shared resource f/w >>>>>> OMAP3 SRF: MPU/CORE/PD latency modeling >>>>>> OMAP3 SRF: omap3 srf driver >>>>>> OMAP3 SRF: OMAP PM srf implementation >>>>>> OMAP3 SRF: Add CORE rate table param in OMAP-PM >>>>>> OMAP3 SRF: Add VDD1/VDD2 rate tables for 3430SDP >>>>>> OMAP3 SRF: Add virt clk nodes for VDD1/VDD2 >>>>>> OMAP3 SRF: Adds OPP/Freq res's in SRF >>>>>> OMAP3 SRF: Update OMAP-PM layer >>>>>> OMAP3 SRF: Voltage scaling support >>>>>> OMAP3 SRF: VDD2 scaling support >>>>>> OMAP3 SRF: Adds sysfs control for VDD1/VDD2 OPP's >>>>>> OMAP3 PM: Replace spinlocks with mutex in SRF >>>>>> OMAP3 PM: CPUFreq driver for OMAP3 >>>>>> OMAP3 PM: Update the min defconfig for 3430sdp >>>>>> OMAP3 SRF: Fix crash on non-3430SDP platforms with >>>> DVFS/CPUFreq >>>>>> OMAP3: PM: Scale VDD2 OPP for VDD1 OPP3 and higher >>>>>> >>>>>> Tero Kristo (26): >>>>>> OMAP: PM debug: do not print out status for meta >>>> powerdomains (dpll*) >>>>>> OMAP: PM debug: Add PRCM register dump support >>>>>> OMAP: PM: DMA context save / restore >>>>>> OMAP: PM: off-mode support for DMA on EMU/HS devices >>>>>> OMAP3: SRAM size fix for HS/EMU devices >>>>>> OMAP3 PM: off-mode support for HS/EMU devices >>>>>> OMAP3: PM: Enable SDRAM auto-refresh during sleep >>>>>> OMAP: SDRC: Add new register definitions for SDRAM >> controller >>>>>> OMAP3: PM: SDRC auto-refresh workaround for off-mode >>>>>> PM: Added three PLL registers to the PRCM context save >>>>>> PM: Changed secure RAM storage size from 0x8000 to 0x803F >>>>>> PM: Added suspend target state control to debugfs for OMAP3 >>>>>> OMAP3: PM: Prevent PER from going OFF when CORE is going INA >>>>>> PM OMAP3: Change omap3_save_secure_ram to be called >>>> only during init >>>>>> OMAP3: PM: MPU and CORE should stay awake if there is >>>> CAM domain ACTIVE >>>>>> OMAP3: GPIO fixes for off-mode >>>>>> PM: OMAP3: Refreshed DVFS VDD1 control against >> latest clock fw >>>>>> OMAP3: Add support for DPLL3 divisor values higher than 2 >>>>>> OMAP3: PM: Fixed VDD2 control to work from both sysfs >>>> and SRF API >>>>>> OMAP3: PM: Added DVFS OPP locking interface for >> VDD1 and VDD2 >>>>>> OMAP3: Fix rate calculation bug in omap3_select_table_rate >>>>>> OMAP3: PM: Prevented DVFS state switches when >>>> enabling off-mode >>>>>> OMAP3: PM: Enable VDD2 OPP1 >>>>>> OMAP3: PM: Fix linker error without CONFIG_PM option >>>>>> PM: OMAP3: Removed a couple of unused variables >> from DVFS code >>>>>> PM: OMAP3: Added support for possibly failing >> clk_set_rate to >>>>>> DVFS >>>>>> >>>>>> -- >>>>>> To unsubscribe from this list: send the line "unsubscribe >>>> linux-omap" >>>>>> in the body of a message to majordomo@vger.kernel.org More >>>> majordomo >>>>>> info at http://vger.kernel.org/majordomo-info.html >>>>>> >>>> -- >>>> To unsubscribe from this list: send the line "unsubscribe >> linux-omap" >>>> in the body of a message to majordomo@vger.kernel.org More >> majordomo >>>> info at http://vger.kernel.org/majordomo-info.html >>>> >> ^ permalink raw reply [flat|nested] 40+ messages in thread
* RE: new PM branch available 2009-01-15 15:34 ` Kevin Hilman @ 2009-01-15 16:00 ` Premi, Sanjeev 0 siblings, 0 replies; 40+ messages in thread From: Premi, Sanjeev @ 2009-01-15 16:00 UTC (permalink / raw) To: Kevin Hilman; +Cc: linux-omap@vger.kernel.org <snip>--<snip> > >>> Hi Kevin, > >>> > >>> I was able to test against the HEAD 'pm' branch on the EVM. > >>> Here are my observations with default configuration: > >>> > >>> 1) CONFIG_DEBUG_LL=y is set by default. The kernel boots fine. > >>> I did not notice any 'garbage' problems you and Koen seem to > >>> be getting. > >>> > >>> 2) Same result when CONFIG_DEBUG_LL is deselcted. > >> Sanjeev, > >> > >> Is this on an an ES3 EVM? What boot loader revs are you using? > > > > [sp] I am using EVM with ES3.0 while Vaibhav is using one with ES2.1 > > What are your x-loader and u-boot versions? Mine are: > > Texas Instruments X-Loader 1.41 > [...] > U-Boot 1.1.4 (Jun 5 2008 - 17:53:37) > > > >>> 3) With default config, suspend operation fails with this message: > >>> <3>omapfb omapfb: timeout waiting for FRAME DONE > >> This is not a failure, just a warning from the fb driver. > >> This should not prevent retention. I see this on beagle > as well, and > >> it doesn't prevent retention. > >> > >> From the log below, you didn't copy the part which > reports whether > >> all domains hit target state. > > > > [sp] This is where it hangs :( > > It's not hung. It's just sleeping, but refuses to wakeup [sp] True. > (like I should've done this morning.) [sp] me too! > > What are you using as your wakeup source? UART? keypad? [sp] I try using both (after a reboot). Also tried the kernel image without FB driver. But observations don't change. Checking further, with: # echo 1 > /sys/power/sleep_while_idle Suspend / resume 'appear' to work fine with these warnings: Powerdomain (core_pwrdm) didn't enter target state 1 Powerdomain (per_pwrdm) didn't enter target state 1 However, after: # echo 1 > /sys/power/clocks_off_while_idle Observation is same as mentioned in prev mail. Best regards, Sanjeev > > I'm not sure how the UARTs are mux'd on this board, but you > probably want to check the wake-enable bits in the padconf > reg for the UART pins. > This is done by arch/arm/mach-omap2/serial.c but assumes > the UARTs are mux'd using the default registers. Each UART > has a couple possible ways to be mux'd. > > > After sending the last mail, I tried the same without > enabling "clocks_off_while_idle" and "sleep_while_idle" then: > > > > omapfb omapfb: timeout waiting for FRAME DONE Powerdomain > (core_pwrdm) > > didn't enter target state 1 Powerdomain (per_pwrdm) didn't enter > > target state 1 Could not enter target state in pm_suspend > > > > I am building a config without FB. Will update as soon as I > can test it. > > > >> Kevin > >> > >>> Here is a sample session from my terminal: > >>> > >>> [root@OMAP3EVM /]# uname -a > >>> Linux OMAP3EVM 2.6.28-omap1-00115-g998bd56 #146 Thu Jan > 15 18:47:26 > >>> IST 2009 armv7l unknown [root@OMAP3EVM /]# echo 1 > > >>> /sys/power/clocks_off_while_idle [root@OMAP3EVM /]# echo 1 > > >>> /sys/power/sleep_while_idle [root@OMAP3EVM /]# > >> [root@OMAP3EVM /]# echo > >>> mem > /sys/power/state > >>> <6>PM: Syncing filesystems ... PM: Syncing filesystems ... done. > >>> done. > >>> Freezing user space processes ... Freezing user space > >> processes ... (elapsed 0.00 seconds) (elapsed 0.00 seconds) done. > >>> done. > >>> Freezing remaining freezable tasks ... Freezing remaining > >> freezable tasks ... (elapsed 0.06 seconds) (elapsed 0.06 > >> seconds) done.done. > >>> Suspending console(s) (use no_console_suspend to debug) Suspending > >>> console(s) (use no_console_suspend to debug) > >>> > >>> Best regards, > >>> Sanjeev > >>> <snip>--<snip> ^ permalink raw reply [flat|nested] 40+ messages in thread
* Re: new PM branch available 2009-01-14 16:39 ` Kevin Hilman 2009-01-15 13:42 ` Premi, Sanjeev @ 2009-01-15 15:00 ` Sriram V [not found] ` <8bf247760901150654n78b198f0o5c2270186e9c119e@mail.gmail.com> 2 siblings, 0 replies; 40+ messages in thread From: Sriram V @ 2009-01-15 15:00 UTC (permalink / raw) To: Kevin Hilman; +Cc: linux-omap@vger.kernel.org Hi, Here are my observations on omap3evm. 1) With default config file, The kernel boots. If youre seeing junk after a certain point while booting. it could be related to your bootargs console options. (console=ttyS0,115200n8) 2) Sometimes i do get the usual omapfb errors. 3) If i enable cpuidle - the ethernet driver is unable to get an IP address. So it is unable to mount NFS. If i give a statically assigned IP in my bootargs. NFS mount also fails. This happens only when cpuidle is enabled. 4) If i enable SMC debug, i see ethernet interrupts happening, for some reason. NFS mount/getting a dhcp address fails. I am not sure if this is a wakeup issue. Sometimes, if i add some debug prints it works. but this does not work every time. 5) If i boot with rootfs on MMC and with cpu idle enabled. i cannot ping. cpuidle is somehow effecting the network stuff. I also see some rx overruns. is this a wakeup issue? Regards, Sriram On Wed, Jan 14, 2009 at 10:09 PM, Kevin Hilman <khilman@deeprootsystems.com> wrote: > > Sriram V wrote: >> >> Hi, >> OMAP3EVM. all domains hit retention in suspend. >> >> On enabling cpuidle, network and mmc is not stable. network is >> unable to get an IP address. > > Sriram, > > Can you send me your .config for omap3evm? I'm trying to get my recently received EVM working but I am getting lots of garbage on the serial console on linux-omap HEAD and PM branch on omap3evm. Do you have any additional patches for EVM that you're using? > > Kevin > > >> >> On Wed, Jan 14, 2009 at 3:21 AM, Kevin Hilman >> <khilman@deeprootsystems.com> wrote: >>> >>> Hello, >>> >>> The latest PM branch is now available[1]. >>> >>> I've done basic testing of retention and off-mode (suspend and dynamic >>> idle) on Beagle and custom HW. My SDP has something still keeping >>> CORE active that others have not seen, but I have yet to debug. Any >>> other reports from SDP testing would be appreciated. >>> >>> Notable changes/updates >>> - rebased on latest clock updates and fixes from Paul >>> - clockfw pre- and post- notifiers >>> - DVFS for VDD2 >>> >>> Full git shortlog below[2] >>> >>> Enjoy, >>> >>> Kevin >>> >>> [1] See branch 'pm' in my git repo: >>> git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap-pm.git >>> which is also mirrored as the branch 'pm' of the normal linux-omap >>> repo (but will not sync until 03:30 GMT) >>> >>> >>> [2] git shortlog: >>> >>> Carlos Chinea (1): >>> OMAP3:PM: Update SSI omapdev record >>> >>> Jouni Hogander (5): >>> OMAP3: PM: Use pwrdm_set_next_pwrst instead of set_pwrdm_state in idle loop >>> OMAP3: PM: Fix wrong sequence in suspend. >>> OMAP3: PM: Do not build suspend code if SUSPEND is not enabled >>> OMAP: PM: Build fails if PM is not enabled >>> OMAP2: PM: Fix omap2 build >>> >>> Kalle Jokiniemi (3): >>> OMAP: PM: sysfs interface for enabling voltage off in idle >>> OMAP3: PM: Fix cpu idle init sequencing >>> OMAP: SRF: Fixes to shared resource framework (Ver.3) >>> >>> Kevin Hilman (4): >>> OMAP3: PM: CPUidle: obey enable_off_mode flag >>> OMAP3: PM: CPUidle: restrict C-states on UART activity >>> OMAP3: PM: decouple PER and CORE context save and restore >>> OMAP2/3: PM: system_rev -> omap_rev() >>> >>> Paul Walmsley (29): >>> OMAP2/3 clock: implement clock notifier infrastructure >>> OMAP clock: add notifier infrastructure >>> OMAP2/3 clock: store planned clock rates into temporary rate storage >>> OMAP2/3 clock: add clk post-rate-change notifiers >>> OMAP2/3 clock: add clock pre-rate-change notification >>> OMAP2/3 clock: add clock prepare-rate-change notifications >>> OMAP2/3 clock: add clock abort-rate-change notifications >>> OMAP2/3 PM: create the OMAP PM interface and add a default OMAP PM no-op layer. >>> OMAP2/3 omapdev: add basic omapdev structure >>> OMAP242x omapdev: add OMAP242x omapdev records >>> OMAP243x omapdev: add OMAP243x omapdev records >>> OMAP3xxx omapdev: add OMAP3xxx omapdev records >>> OMAP2/3 omapdev: add code to walk the omapdev records >>> ARM: MMU: add a Non-cacheable Normal executable memory type >>> OMAP3 SRAM: mark OCM RAM as Non-cacheable Normal memory >>> OMAP3 SRAM: add ARM barriers to omap3_sram_configure_core_dpll >>> OMAP3 clock: add interconnect barriers to CORE DPLL M2 change >>> OMAP3 SRAM: clear the SDRC PWRENA bit during SDRC frequency change >>> OMAP3 SDRC: Add 166MHz, 83MHz SDRC settings for the BeagleBoard >>> OMAP3 SDRC: initialize SDRC_POWER at boot >>> OMAP3 SRAM: renumber registers to make space for argument passing >>> OMAP3 clock: only unlock SDRC DLL if SDRC clk < 83MHz >>> OMAP3 clock: use pr_debug() rather than pr_info() in some clock change code >>> OMAP3 clock: remove wait for DPLL3 M2 clock to stabilize >>> OMAP3 clock: initialize SDRC timings at kernel start >>> OMAP3 clock: add a short delay when lowering CORE clk rate >>> OMAP3 clock/SDRC: program SDRC_MR register during SDRC clock change >>> OMAP3 SRAM: add more comments on the SRAM code >>> OMAP3 SRAM: convert SRAM code to use macros rather than magic numbers >>> >>> Peter 'p2' De Schrijver (12): >>> OMAP: PM counter infrastructure. >>> OMAP: PM: Hook into PM counters >>> OMAP: PM: Add closures to clkdm_for_each and pwrdm_for_each. >>> OMAP: PM: Add pm-debug counters >>> OMAP: PM debug: make powerdomains use PM-debug counters >>> OMAP: PM: Add definitions for ETK pads and observability registers >>> OMAP: Debug observability and ETK padconf implementation >>> OMAP: Add debug observablity (debobs) Kconfig item >>> OMAP: PM: Implement get_last_off_on_transaction_id() >>> Save sram context after changing MPU, DSP or core clocks >>> Fix omap_getspeed. >>> Make sure omap cpufreq driver initializes after cpufreq framework and governors >>> >>> Rajendra Nayak (35): >>> OMAP3: PM: GPMC context save/restore >>> OMAP3: PM: GPIO context save/restore >>> OMAP3: PM: I2C context save/restore >>> OMAP3: PM: INTC context save/restore >>> OMAP3: PM: PRCM context save/restore >>> OMAP3: PM: Populate scratchpad contents >>> OMAP3: PM: SCM context save/restore >>> OMAP3: PM: SRAM restore function >>> OMAP3: PM: handle PER/NEON/CORE in idle >>> OMAP3: PM: Restore MMU table entry >>> OMAP3: PM: MPU off-mode support >>> OMAP3: PM: CORE domain off-mode support >>> OMAP3: PM: allow runtime enable/disable of OFF mode >>> OMAP3: 3430SDP minimal kernel defconfig >>> OMAP3: PM: CPUidle: Basic support for C1-C2 >>> OMAP3: PM: CPUidle: Enables state C4 >>> OMAP3: PM: CPUidle: Enables C3 and C5 >>> OMAP3: PM: CPUidle: Safe-state on bm-activity >>> OMAP3 SRF: Generic shared resource f/w >>> OMAP3 SRF: MPU/CORE/PD latency modeling >>> OMAP3 SRF: omap3 srf driver >>> OMAP3 SRF: OMAP PM srf implementation >>> OMAP3 SRF: Add CORE rate table param in OMAP-PM >>> OMAP3 SRF: Add VDD1/VDD2 rate tables for 3430SDP >>> OMAP3 SRF: Add virt clk nodes for VDD1/VDD2 >>> OMAP3 SRF: Adds OPP/Freq res's in SRF >>> OMAP3 SRF: Update OMAP-PM layer >>> OMAP3 SRF: Voltage scaling support >>> OMAP3 SRF: VDD2 scaling support >>> OMAP3 SRF: Adds sysfs control for VDD1/VDD2 OPP's >>> OMAP3 PM: Replace spinlocks with mutex in SRF >>> OMAP3 PM: CPUFreq driver for OMAP3 >>> OMAP3 PM: Update the min defconfig for 3430sdp >>> OMAP3 SRF: Fix crash on non-3430SDP platforms with DVFS/CPUFreq >>> OMAP3: PM: Scale VDD2 OPP for VDD1 OPP3 and higher >>> >>> Tero Kristo (26): >>> OMAP: PM debug: do not print out status for meta powerdomains (dpll*) >>> OMAP: PM debug: Add PRCM register dump support >>> OMAP: PM: DMA context save / restore >>> OMAP: PM: off-mode support for DMA on EMU/HS devices >>> OMAP3: SRAM size fix for HS/EMU devices >>> OMAP3 PM: off-mode support for HS/EMU devices >>> OMAP3: PM: Enable SDRAM auto-refresh during sleep >>> OMAP: SDRC: Add new register definitions for SDRAM controller >>> OMAP3: PM: SDRC auto-refresh workaround for off-mode >>> PM: Added three PLL registers to the PRCM context save >>> PM: Changed secure RAM storage size from 0x8000 to 0x803F >>> PM: Added suspend target state control to debugfs for OMAP3 >>> OMAP3: PM: Prevent PER from going OFF when CORE is going INA >>> PM OMAP3: Change omap3_save_secure_ram to be called only during init >>> OMAP3: PM: MPU and CORE should stay awake if there is CAM domain ACTIVE >>> OMAP3: GPIO fixes for off-mode >>> PM: OMAP3: Refreshed DVFS VDD1 control against latest clock fw >>> OMAP3: Add support for DPLL3 divisor values higher than 2 >>> OMAP3: PM: Fixed VDD2 control to work from both sysfs and SRF API >>> OMAP3: PM: Added DVFS OPP locking interface for VDD1 and VDD2 >>> OMAP3: Fix rate calculation bug in omap3_select_table_rate >>> OMAP3: PM: Prevented DVFS state switches when enabling off-mode >>> OMAP3: PM: Enable VDD2 OPP1 >>> OMAP3: PM: Fix linker error without CONFIG_PM option >>> PM: OMAP3: Removed a couple of unused variables from DVFS code >>> PM: OMAP3: Added support for possibly failing clk_set_rate to DVFS >>> >>> -- >>> To unsubscribe from this list: send the line "unsubscribe linux-omap" in >>> the body of a message to majordomo@vger.kernel.org >>> More majordomo info at http://vger.kernel.org/majordomo-info.html >>> > ^ permalink raw reply [flat|nested] 40+ messages in thread
[parent not found: <8bf247760901150654n78b198f0o5c2270186e9c119e@mail.gmail.com>]
* Re: new PM branch available [not found] ` <8bf247760901150654n78b198f0o5c2270186e9c119e@mail.gmail.com> @ 2009-01-15 15:07 ` Kevin Hilman 0 siblings, 0 replies; 40+ messages in thread From: Kevin Hilman @ 2009-01-15 15:07 UTC (permalink / raw) To: Sriram V; +Cc: linux-omap@vger.kernel.org Sriram V wrote: > Hi, > Here are my observations on omap3evm. Sriram, Thanks for testing! > 1) With default config file, The kernel boots. If youre seeing junk > after a certain point while booting. it could be related to your > bootargs console options. (console=ttyS0,115200n8) I have the same console= bootargs. Are you testing on an ES3 EVM? What version of the bootloader to you have? Mine reports: Texas Instruments X-Loader 1.41 [...] U-Boot 1.1.4 (Jun 5 2008 - 17:53:37) > 2) Sometimes i do get the usual omapfb errors. These are "normal" > 3) If i enable cpuidle - the ethernet driver is unable to get an IP > address. So it is unable to mount NFS. If i give a statically assigned > IP in my bootargs. NFS mount also fails. This happens only when cpuidle > is enabled. > 4) If i enable SMC debug, i see ethernet interrupts happening, for some > reason. NFS mount/getting a dhcp address fails. > I am not sure if this is a wakeup issue. Sometimes, if i add some > debug prints it works. but this does not work every time. > 5) If i boot with rootfs on MMC and with cpu idle enabled. i cannot > ping. cpuidle is somehow effecting the network stuff. I also see some rx > overruns. is this a wakeup issue? I have not done any testing with ethernet, only initramfs or MMC rootfs. This is indeed a wakeup issue. The GPIO IRQ for smc91x is not currently set as a wakeup source, so ethernet activity will not wakeup the system, thus causing delays and other problems. Can you try with rootfs on MMC, but with no ethernet (add ip=none to cmdline.) Then try suspend/resume etc. Kevin > On Wed, Jan 14, 2009 at 10:09 PM, Kevin Hilman > <khilman@deeprootsystems.com <mailto:khilman@deeprootsystems.com>> wrote: > > Sriram V wrote: > >> > >> Hi, > >> OMAP3EVM. all domains hit retention in suspend. > >> > >> On enabling cpuidle, network and mmc is not stable. network is > >> unable to get an IP address. > > > > Sriram, > > > > Can you send me your .config for omap3evm? I'm trying to get my recently > > received EVM working but I am getting lots of garbage on the serial > console > > on linux-omap HEAD and PM branch on omap3evm. Do you have any additional > > patches for EVM that you're using? > > > > Kevin > > > > > >> > >> On Wed, Jan 14, 2009 at 3:21 AM, Kevin Hilman > >> <khilman@deeprootsystems.com <mailto:khilman@deeprootsystems.com>> > wrote: > >>> > >>> Hello, > >>> > >>> The latest PM branch is now available[1]. > >>> > >>> I've done basic testing of retention and off-mode (suspend and dynamic > >>> idle) on Beagle and custom HW. My SDP has something still keeping > >>> CORE active that others have not seen, but I have yet to debug. Any > >>> other reports from SDP testing would be appreciated. > >>> > >>> Notable changes/updates > >>> - rebased on latest clock updates and fixes from Paul > >>> - clockfw pre- and post- notifiers > >>> - DVFS for VDD2 > >>> > >>> Full git shortlog below[2] > >>> > >>> Enjoy, > >>> > >>> Kevin > >>> > >>> [1] See branch 'pm' in my git repo: > >>> > git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap-pm.git > <http://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap-pm.git> > >>> which is also mirrored as the branch 'pm' of the normal linux-omap > >>> repo (but will not sync until 03:30 GMT) > >>> > >>> > >>> [2] git shortlog: > >>> > >>> Carlos Chinea (1): > >>> OMAP3:PM: Update SSI omapdev record > >>> > >>> Jouni Hogander (5): > >>> OMAP3: PM: Use pwrdm_set_next_pwrst instead of set_pwrdm_state in > >>> idle loop > >>> OMAP3: PM: Fix wrong sequence in suspend. > >>> OMAP3: PM: Do not build suspend code if SUSPEND is not enabled > >>> OMAP: PM: Build fails if PM is not enabled > >>> OMAP2: PM: Fix omap2 build > >>> > >>> Kalle Jokiniemi (3): > >>> OMAP: PM: sysfs interface for enabling voltage off in idle > >>> OMAP3: PM: Fix cpu idle init sequencing > >>> OMAP: SRF: Fixes to shared resource framework (Ver.3) > >>> > >>> Kevin Hilman (4): > >>> OMAP3: PM: CPUidle: obey enable_off_mode flag > >>> OMAP3: PM: CPUidle: restrict C-states on UART activity > >>> OMAP3: PM: decouple PER and CORE context save and restore > >>> OMAP2/3: PM: system_rev -> omap_rev() > >>> > >>> Paul Walmsley (29): > >>> OMAP2/3 clock: implement clock notifier infrastructure > >>> OMAP clock: add notifier infrastructure > >>> OMAP2/3 clock: store planned clock rates into temporary rate > storage > >>> OMAP2/3 clock: add clk post-rate-change notifiers > >>> OMAP2/3 clock: add clock pre-rate-change notification > >>> OMAP2/3 clock: add clock prepare-rate-change notifications > >>> OMAP2/3 clock: add clock abort-rate-change notifications > >>> OMAP2/3 PM: create the OMAP PM interface and add a default OMAP PM > >>> no-op layer. > >>> OMAP2/3 omapdev: add basic omapdev structure > >>> OMAP242x omapdev: add OMAP242x omapdev records > >>> OMAP243x omapdev: add OMAP243x omapdev records > >>> OMAP3xxx omapdev: add OMAP3xxx omapdev records > >>> OMAP2/3 omapdev: add code to walk the omapdev records > >>> ARM: MMU: add a Non-cacheable Normal executable memory type > >>> OMAP3 SRAM: mark OCM RAM as Non-cacheable Normal memory > >>> OMAP3 SRAM: add ARM barriers to omap3_sram_configure_core_dpll > >>> OMAP3 clock: add interconnect barriers to CORE DPLL M2 change > >>> OMAP3 SRAM: clear the SDRC PWRENA bit during SDRC frequency change > >>> OMAP3 SDRC: Add 166MHz, 83MHz SDRC settings for the BeagleBoard > >>> OMAP3 SDRC: initialize SDRC_POWER at boot > >>> OMAP3 SRAM: renumber registers to make space for argument passing > >>> OMAP3 clock: only unlock SDRC DLL if SDRC clk < 83MHz > >>> OMAP3 clock: use pr_debug() rather than pr_info() in some clock > >>> change code > >>> OMAP3 clock: remove wait for DPLL3 M2 clock to stabilize > >>> OMAP3 clock: initialize SDRC timings at kernel start > >>> OMAP3 clock: add a short delay when lowering CORE clk rate > >>> OMAP3 clock/SDRC: program SDRC_MR register during SDRC clock change > >>> OMAP3 SRAM: add more comments on the SRAM code > >>> OMAP3 SRAM: convert SRAM code to use macros rather than magic > numbers > >>> > >>> Peter 'p2' De Schrijver (12): > >>> OMAP: PM counter infrastructure. > >>> OMAP: PM: Hook into PM counters > >>> OMAP: PM: Add closures to clkdm_for_each and pwrdm_for_each. > >>> OMAP: PM: Add pm-debug counters > >>> OMAP: PM debug: make powerdomains use PM-debug counters > >>> OMAP: PM: Add definitions for ETK pads and observability registers > >>> OMAP: Debug observability and ETK padconf implementation > >>> OMAP: Add debug observablity (debobs) Kconfig item > >>> OMAP: PM: Implement get_last_off_on_transaction_id() > >>> Save sram context after changing MPU, DSP or core clocks > >>> Fix omap_getspeed. > >>> Make sure omap cpufreq driver initializes after cpufreq > framework and > >>> governors > >>> > >>> Rajendra Nayak (35): > >>> OMAP3: PM: GPMC context save/restore > >>> OMAP3: PM: GPIO context save/restore > >>> OMAP3: PM: I2C context save/restore > >>> OMAP3: PM: INTC context save/restore > >>> OMAP3: PM: PRCM context save/restore > >>> OMAP3: PM: Populate scratchpad contents > >>> OMAP3: PM: SCM context save/restore > >>> OMAP3: PM: SRAM restore function > >>> OMAP3: PM: handle PER/NEON/CORE in idle > >>> OMAP3: PM: Restore MMU table entry > >>> OMAP3: PM: MPU off-mode support > >>> OMAP3: PM: CORE domain off-mode support > >>> OMAP3: PM: allow runtime enable/disable of OFF mode > >>> OMAP3: 3430SDP minimal kernel defconfig > >>> OMAP3: PM: CPUidle: Basic support for C1-C2 > >>> OMAP3: PM: CPUidle: Enables state C4 > >>> OMAP3: PM: CPUidle: Enables C3 and C5 > >>> OMAP3: PM: CPUidle: Safe-state on bm-activity > >>> OMAP3 SRF: Generic shared resource f/w > >>> OMAP3 SRF: MPU/CORE/PD latency modeling > >>> OMAP3 SRF: omap3 srf driver > >>> OMAP3 SRF: OMAP PM srf implementation > >>> OMAP3 SRF: Add CORE rate table param in OMAP-PM > >>> OMAP3 SRF: Add VDD1/VDD2 rate tables for 3430SDP > >>> OMAP3 SRF: Add virt clk nodes for VDD1/VDD2 > >>> OMAP3 SRF: Adds OPP/Freq res's in SRF > >>> OMAP3 SRF: Update OMAP-PM layer > >>> OMAP3 SRF: Voltage scaling support > >>> OMAP3 SRF: VDD2 scaling support > >>> OMAP3 SRF: Adds sysfs control for VDD1/VDD2 OPP's > >>> OMAP3 PM: Replace spinlocks with mutex in SRF > >>> OMAP3 PM: CPUFreq driver for OMAP3 > >>> OMAP3 PM: Update the min defconfig for 3430sdp > >>> OMAP3 SRF: Fix crash on non-3430SDP platforms with DVFS/CPUFreq > >>> OMAP3: PM: Scale VDD2 OPP for VDD1 OPP3 and higher > >>> > >>> Tero Kristo (26): > >>> OMAP: PM debug: do not print out status for meta powerdomains > (dpll*) > >>> OMAP: PM debug: Add PRCM register dump support > >>> OMAP: PM: DMA context save / restore > >>> OMAP: PM: off-mode support for DMA on EMU/HS devices > >>> OMAP3: SRAM size fix for HS/EMU devices > >>> OMAP3 PM: off-mode support for HS/EMU devices > >>> OMAP3: PM: Enable SDRAM auto-refresh during sleep > >>> OMAP: SDRC: Add new register definitions for SDRAM controller > >>> OMAP3: PM: SDRC auto-refresh workaround for off-mode > >>> PM: Added three PLL registers to the PRCM context save > >>> PM: Changed secure RAM storage size from 0x8000 to 0x803F > >>> PM: Added suspend target state control to debugfs for OMAP3 > >>> OMAP3: PM: Prevent PER from going OFF when CORE is going INA > >>> PM OMAP3: Change omap3_save_secure_ram to be called only during > init > >>> OMAP3: PM: MPU and CORE should stay awake if there is CAM domain > >>> ACTIVE > >>> OMAP3: GPIO fixes for off-mode > >>> PM: OMAP3: Refreshed DVFS VDD1 control against latest clock fw > >>> OMAP3: Add support for DPLL3 divisor values higher than 2 > >>> OMAP3: PM: Fixed VDD2 control to work from both sysfs and SRF API > >>> OMAP3: PM: Added DVFS OPP locking interface for VDD1 and VDD2 > >>> OMAP3: Fix rate calculation bug in omap3_select_table_rate > >>> OMAP3: PM: Prevented DVFS state switches when enabling off-mode > >>> OMAP3: PM: Enable VDD2 OPP1 > >>> OMAP3: PM: Fix linker error without CONFIG_PM option > >>> PM: OMAP3: Removed a couple of unused variables from DVFS code > >>> PM: OMAP3: Added support for possibly failing clk_set_rate to DVFS > >>> > >>> -- > >>> To unsubscribe from this list: send the line "unsubscribe > linux-omap" in > >>> the body of a message to majordomo@vger.kernel.org > <mailto:majordomo@vger.kernel.org> > >>> More majordomo info at http://vger.kernel.org/majordomo-info.html > >>> > > > > > ^ permalink raw reply [flat|nested] 40+ messages in thread
* RE: new PM branch available 2009-01-13 21:51 Kevin Hilman ` (2 preceding siblings ...) 2009-01-14 13:57 ` Sriram V @ 2009-01-16 13:49 ` Nayak, Rajendra 2009-01-16 19:03 ` Kevin Hilman 2009-02-02 17:45 ` Peter 'p2' De Schrijver 4 siblings, 1 reply; 40+ messages in thread From: Nayak, Rajendra @ 2009-01-16 13:49 UTC (permalink / raw) To: Kevin Hilman, linux-omap@vger.kernel.org I did some testing today on my 3.0GP 3430SDP. This is with the omap_3430sdp_min_defconfig. 1) Idle. echo -n 1 > /sys/power/clocks_off_while_idle echo -n 1 > /sys/power/enable_off Could not hit RET. something seems to be still active. Not sure if it could be something to do with this error that's thrown while bootup <6>Disabling unused clock "dpll5_ck" Disabling unused clock "dpll5_ck" <3>clock: dpll5_ck failed transition to 'locked' clock: dpll5_ck failed transition to 'locked' Further doing a echo -n 1 > /sys/power/sleep_while_idle causes a hang after the 5 odd secs of UART inactivity. Is'nt this option supposed to affect only the suspend path behavior? Is CPUidle disabled in the default defconfig now? 2) Suspend echo -n 1 > /sys/power/clocks_off_while_idle Hangs on a echo mem > /sys/power/state Goes into suspend, but cannot recover 3) DVFS Both VDD1 and VDD2 DVFS seem to function fine. > -----Original Message----- > From: linux-omap-owner@vger.kernel.org > [mailto:linux-omap-owner@vger.kernel.org] On Behalf Of Kevin Hilman > Sent: Wednesday, January 14, 2009 3:22 AM > To: linux-omap@vger.kernel.org > Subject: new PM branch available > > Hello, > > The latest PM branch is now available[1]. > > I've done basic testing of retention and off-mode (suspend and dynamic > idle) on Beagle and custom HW. My SDP has something still keeping > CORE active that others have not seen, but I have yet to debug. Any > other reports from SDP testing would be appreciated. > > Notable changes/updates > - rebased on latest clock updates and fixes from Paul > - clockfw pre- and post- notifiers > - DVFS for VDD2 > > Full git shortlog below[2] > > Enjoy, > > Kevin > > [1] See branch 'pm' in my git repo: > git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-om > ap-pm.git > which is also mirrored as the branch 'pm' of the normal linux-omap > repo (but will not sync until 03:30 GMT) > > > [2] git shortlog: > > Carlos Chinea (1): > OMAP3:PM: Update SSI omapdev record > > Jouni Hogander (5): > OMAP3: PM: Use pwrdm_set_next_pwrst instead of > set_pwrdm_state in idle loop > OMAP3: PM: Fix wrong sequence in suspend. > OMAP3: PM: Do not build suspend code if SUSPEND is not enabled > OMAP: PM: Build fails if PM is not enabled > OMAP2: PM: Fix omap2 build > > Kalle Jokiniemi (3): > OMAP: PM: sysfs interface for enabling voltage off in idle > OMAP3: PM: Fix cpu idle init sequencing > OMAP: SRF: Fixes to shared resource framework (Ver.3) > > Kevin Hilman (4): > OMAP3: PM: CPUidle: obey enable_off_mode flag > OMAP3: PM: CPUidle: restrict C-states on UART activity > OMAP3: PM: decouple PER and CORE context save and restore > OMAP2/3: PM: system_rev -> omap_rev() > > Paul Walmsley (29): > OMAP2/3 clock: implement clock notifier infrastructure > OMAP clock: add notifier infrastructure > OMAP2/3 clock: store planned clock rates into temporary > rate storage > OMAP2/3 clock: add clk post-rate-change notifiers > OMAP2/3 clock: add clock pre-rate-change notification > OMAP2/3 clock: add clock prepare-rate-change notifications > OMAP2/3 clock: add clock abort-rate-change notifications > OMAP2/3 PM: create the OMAP PM interface and add a > default OMAP PM no-op layer. > OMAP2/3 omapdev: add basic omapdev structure > OMAP242x omapdev: add OMAP242x omapdev records > OMAP243x omapdev: add OMAP243x omapdev records > OMAP3xxx omapdev: add OMAP3xxx omapdev records > OMAP2/3 omapdev: add code to walk the omapdev records > ARM: MMU: add a Non-cacheable Normal executable memory type > OMAP3 SRAM: mark OCM RAM as Non-cacheable Normal memory > OMAP3 SRAM: add ARM barriers to omap3_sram_configure_core_dpll > OMAP3 clock: add interconnect barriers to CORE DPLL M2 change > OMAP3 SRAM: clear the SDRC PWRENA bit during SDRC > frequency change > OMAP3 SDRC: Add 166MHz, 83MHz SDRC settings for the BeagleBoard > OMAP3 SDRC: initialize SDRC_POWER at boot > OMAP3 SRAM: renumber registers to make space for > argument passing > OMAP3 clock: only unlock SDRC DLL if SDRC clk < 83MHz > OMAP3 clock: use pr_debug() rather than pr_info() in > some clock change code > OMAP3 clock: remove wait for DPLL3 M2 clock to stabilize > OMAP3 clock: initialize SDRC timings at kernel start > OMAP3 clock: add a short delay when lowering CORE clk rate > OMAP3 clock/SDRC: program SDRC_MR register during SDRC > clock change > OMAP3 SRAM: add more comments on the SRAM code > OMAP3 SRAM: convert SRAM code to use macros rather than > magic numbers > > Peter 'p2' De Schrijver (12): > OMAP: PM counter infrastructure. > OMAP: PM: Hook into PM counters > OMAP: PM: Add closures to clkdm_for_each and pwrdm_for_each. > OMAP: PM: Add pm-debug counters > OMAP: PM debug: make powerdomains use PM-debug counters > OMAP: PM: Add definitions for ETK pads and > observability registers > OMAP: Debug observability and ETK padconf implementation > OMAP: Add debug observablity (debobs) Kconfig item > OMAP: PM: Implement get_last_off_on_transaction_id() > Save sram context after changing MPU, DSP or core clocks > Fix omap_getspeed. > Make sure omap cpufreq driver initializes after cpufreq > framework and governors > > Rajendra Nayak (35): > OMAP3: PM: GPMC context save/restore > OMAP3: PM: GPIO context save/restore > OMAP3: PM: I2C context save/restore > OMAP3: PM: INTC context save/restore > OMAP3: PM: PRCM context save/restore > OMAP3: PM: Populate scratchpad contents > OMAP3: PM: SCM context save/restore > OMAP3: PM: SRAM restore function > OMAP3: PM: handle PER/NEON/CORE in idle > OMAP3: PM: Restore MMU table entry > OMAP3: PM: MPU off-mode support > OMAP3: PM: CORE domain off-mode support > OMAP3: PM: allow runtime enable/disable of OFF mode > OMAP3: 3430SDP minimal kernel defconfig > OMAP3: PM: CPUidle: Basic support for C1-C2 > OMAP3: PM: CPUidle: Enables state C4 > OMAP3: PM: CPUidle: Enables C3 and C5 > OMAP3: PM: CPUidle: Safe-state on bm-activity > OMAP3 SRF: Generic shared resource f/w > OMAP3 SRF: MPU/CORE/PD latency modeling > OMAP3 SRF: omap3 srf driver > OMAP3 SRF: OMAP PM srf implementation > OMAP3 SRF: Add CORE rate table param in OMAP-PM > OMAP3 SRF: Add VDD1/VDD2 rate tables for 3430SDP > OMAP3 SRF: Add virt clk nodes for VDD1/VDD2 > OMAP3 SRF: Adds OPP/Freq res's in SRF > OMAP3 SRF: Update OMAP-PM layer > OMAP3 SRF: Voltage scaling support > OMAP3 SRF: VDD2 scaling support > OMAP3 SRF: Adds sysfs control for VDD1/VDD2 OPP's > OMAP3 PM: Replace spinlocks with mutex in SRF > OMAP3 PM: CPUFreq driver for OMAP3 > OMAP3 PM: Update the min defconfig for 3430sdp > OMAP3 SRF: Fix crash on non-3430SDP platforms with DVFS/CPUFreq > OMAP3: PM: Scale VDD2 OPP for VDD1 OPP3 and higher > > Tero Kristo (26): > OMAP: PM debug: do not print out status for meta > powerdomains (dpll*) > OMAP: PM debug: Add PRCM register dump support > OMAP: PM: DMA context save / restore > OMAP: PM: off-mode support for DMA on EMU/HS devices > OMAP3: SRAM size fix for HS/EMU devices > OMAP3 PM: off-mode support for HS/EMU devices > OMAP3: PM: Enable SDRAM auto-refresh during sleep > OMAP: SDRC: Add new register definitions for SDRAM controller > OMAP3: PM: SDRC auto-refresh workaround for off-mode > PM: Added three PLL registers to the PRCM context save > PM: Changed secure RAM storage size from 0x8000 to 0x803F > PM: Added suspend target state control to debugfs for OMAP3 > OMAP3: PM: Prevent PER from going OFF when CORE is going INA > PM OMAP3: Change omap3_save_secure_ram to be called > only during init > OMAP3: PM: MPU and CORE should stay awake if there is > CAM domain ACTIVE > OMAP3: GPIO fixes for off-mode > PM: OMAP3: Refreshed DVFS VDD1 control against latest clock fw > OMAP3: Add support for DPLL3 divisor values higher than 2 > OMAP3: PM: Fixed VDD2 control to work from both sysfs > and SRF API > OMAP3: PM: Added DVFS OPP locking interface for VDD1 and VDD2 > OMAP3: Fix rate calculation bug in omap3_select_table_rate > OMAP3: PM: Prevented DVFS state switches when enabling off-mode > OMAP3: PM: Enable VDD2 OPP1 > OMAP3: PM: Fix linker error without CONFIG_PM option > PM: OMAP3: Removed a couple of unused variables from DVFS code > PM: OMAP3: Added support for possibly failing > clk_set_rate to DVFS > > -- > To unsubscribe from this list: send the line "unsubscribe > linux-omap" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > > ^ permalink raw reply [flat|nested] 40+ messages in thread
* Re: new PM branch available 2009-01-16 13:49 ` Nayak, Rajendra @ 2009-01-16 19:03 ` Kevin Hilman 2009-01-19 15:46 ` Premi, Sanjeev 2009-01-23 10:19 ` Nayak, Rajendra 0 siblings, 2 replies; 40+ messages in thread From: Kevin Hilman @ 2009-01-16 19:03 UTC (permalink / raw) To: Nayak, Rajendra; +Cc: linux-omap@vger.kernel.org "Nayak, Rajendra" <rnayak@ti.com> writes: > I did some testing today on my 3.0GP 3430SDP. This is with the omap_3430sdp_min_defconfig. > > 1) Idle. > echo -n 1 > /sys/power/clocks_off_while_idle > echo -n 1 > /sys/power/enable_off > Could not hit RET. something seems to be still active. Not sure if it could be something > to do with this error that's thrown while bootup > > <6>Disabling unused clock "dpll5_ck" > Disabling unused clock "dpll5_ck" > <3>clock: dpll5_ck failed transition to 'locked' > clock: dpll5_ck failed transition to 'locked' This is the same results I see on my SDP. Looking at the registers, I am pretty sure it is the D2D clockdomain that still has activity, but due to very poor Stacked-mode docs and no responses to the D2D questions asked to TI I have not been able to figure this one out. Help debugging this would be greatly appreciated. > Further doing a > echo -n 1 > /sys/power/sleep_while_idle causes a hang after the 5 odd secs > of UART inactivity. > Is'nt this option supposed to affect only the suspend path behavior? No, this affects the common idle loop, with and without CPUidle. > Is CPUidle disabled in the default defconfig now? > > 2) Suspend > echo -n 1 > /sys/power/clocks_off_while_idle > Hangs on a echo mem > /sys/power/state > Goes into suspend, but cannot recover I'm pretty sure all the hangs going into RET are related. Kevin > 3) DVFS > Both VDD1 and VDD2 DVFS seem to function fine. > >> -----Original Message----- >> From: linux-omap-owner@vger.kernel.org >> [mailto:linux-omap-owner@vger.kernel.org] On Behalf Of Kevin Hilman >> Sent: Wednesday, January 14, 2009 3:22 AM >> To: linux-omap@vger.kernel.org >> Subject: new PM branch available >> >> Hello, >> >> The latest PM branch is now available[1]. >> >> I've done basic testing of retention and off-mode (suspend and dynamic >> idle) on Beagle and custom HW. My SDP has something still keeping >> CORE active that others have not seen, but I have yet to debug. Any >> other reports from SDP testing would be appreciated. >> >> Notable changes/updates >> - rebased on latest clock updates and fixes from Paul >> - clockfw pre- and post- notifiers >> - DVFS for VDD2 >> >> Full git shortlog below[2] >> >> Enjoy, >> >> Kevin >> >> [1] See branch 'pm' in my git repo: >> git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-om >> ap-pm.git >> which is also mirrored as the branch 'pm' of the normal linux-omap >> repo (but will not sync until 03:30 GMT) >> >> >> [2] git shortlog: >> >> Carlos Chinea (1): >> OMAP3:PM: Update SSI omapdev record >> >> Jouni Hogander (5): >> OMAP3: PM: Use pwrdm_set_next_pwrst instead of >> set_pwrdm_state in idle loop >> OMAP3: PM: Fix wrong sequence in suspend. >> OMAP3: PM: Do not build suspend code if SUSPEND is not enabled >> OMAP: PM: Build fails if PM is not enabled >> OMAP2: PM: Fix omap2 build >> >> Kalle Jokiniemi (3): >> OMAP: PM: sysfs interface for enabling voltage off in idle >> OMAP3: PM: Fix cpu idle init sequencing >> OMAP: SRF: Fixes to shared resource framework (Ver.3) >> >> Kevin Hilman (4): >> OMAP3: PM: CPUidle: obey enable_off_mode flag >> OMAP3: PM: CPUidle: restrict C-states on UART activity >> OMAP3: PM: decouple PER and CORE context save and restore >> OMAP2/3: PM: system_rev -> omap_rev() >> >> Paul Walmsley (29): >> OMAP2/3 clock: implement clock notifier infrastructure >> OMAP clock: add notifier infrastructure >> OMAP2/3 clock: store planned clock rates into temporary >> rate storage >> OMAP2/3 clock: add clk post-rate-change notifiers >> OMAP2/3 clock: add clock pre-rate-change notification >> OMAP2/3 clock: add clock prepare-rate-change notifications >> OMAP2/3 clock: add clock abort-rate-change notifications >> OMAP2/3 PM: create the OMAP PM interface and add a >> default OMAP PM no-op layer. >> OMAP2/3 omapdev: add basic omapdev structure >> OMAP242x omapdev: add OMAP242x omapdev records >> OMAP243x omapdev: add OMAP243x omapdev records >> OMAP3xxx omapdev: add OMAP3xxx omapdev records >> OMAP2/3 omapdev: add code to walk the omapdev records >> ARM: MMU: add a Non-cacheable Normal executable memory type >> OMAP3 SRAM: mark OCM RAM as Non-cacheable Normal memory >> OMAP3 SRAM: add ARM barriers to omap3_sram_configure_core_dpll >> OMAP3 clock: add interconnect barriers to CORE DPLL M2 change >> OMAP3 SRAM: clear the SDRC PWRENA bit during SDRC >> frequency change >> OMAP3 SDRC: Add 166MHz, 83MHz SDRC settings for the BeagleBoard >> OMAP3 SDRC: initialize SDRC_POWER at boot >> OMAP3 SRAM: renumber registers to make space for >> argument passing >> OMAP3 clock: only unlock SDRC DLL if SDRC clk < 83MHz >> OMAP3 clock: use pr_debug() rather than pr_info() in >> some clock change code >> OMAP3 clock: remove wait for DPLL3 M2 clock to stabilize >> OMAP3 clock: initialize SDRC timings at kernel start >> OMAP3 clock: add a short delay when lowering CORE clk rate >> OMAP3 clock/SDRC: program SDRC_MR register during SDRC >> clock change >> OMAP3 SRAM: add more comments on the SRAM code >> OMAP3 SRAM: convert SRAM code to use macros rather than >> magic numbers >> >> Peter 'p2' De Schrijver (12): >> OMAP: PM counter infrastructure. >> OMAP: PM: Hook into PM counters >> OMAP: PM: Add closures to clkdm_for_each and pwrdm_for_each. >> OMAP: PM: Add pm-debug counters >> OMAP: PM debug: make powerdomains use PM-debug counters >> OMAP: PM: Add definitions for ETK pads and >> observability registers >> OMAP: Debug observability and ETK padconf implementation >> OMAP: Add debug observablity (debobs) Kconfig item >> OMAP: PM: Implement get_last_off_on_transaction_id() >> Save sram context after changing MPU, DSP or core clocks >> Fix omap_getspeed. >> Make sure omap cpufreq driver initializes after cpufreq >> framework and governors >> >> Rajendra Nayak (35): >> OMAP3: PM: GPMC context save/restore >> OMAP3: PM: GPIO context save/restore >> OMAP3: PM: I2C context save/restore >> OMAP3: PM: INTC context save/restore >> OMAP3: PM: PRCM context save/restore >> OMAP3: PM: Populate scratchpad contents >> OMAP3: PM: SCM context save/restore >> OMAP3: PM: SRAM restore function >> OMAP3: PM: handle PER/NEON/CORE in idle >> OMAP3: PM: Restore MMU table entry >> OMAP3: PM: MPU off-mode support >> OMAP3: PM: CORE domain off-mode support >> OMAP3: PM: allow runtime enable/disable of OFF mode >> OMAP3: 3430SDP minimal kernel defconfig >> OMAP3: PM: CPUidle: Basic support for C1-C2 >> OMAP3: PM: CPUidle: Enables state C4 >> OMAP3: PM: CPUidle: Enables C3 and C5 >> OMAP3: PM: CPUidle: Safe-state on bm-activity >> OMAP3 SRF: Generic shared resource f/w >> OMAP3 SRF: MPU/CORE/PD latency modeling >> OMAP3 SRF: omap3 srf driver >> OMAP3 SRF: OMAP PM srf implementation >> OMAP3 SRF: Add CORE rate table param in OMAP-PM >> OMAP3 SRF: Add VDD1/VDD2 rate tables for 3430SDP >> OMAP3 SRF: Add virt clk nodes for VDD1/VDD2 >> OMAP3 SRF: Adds OPP/Freq res's in SRF >> OMAP3 SRF: Update OMAP-PM layer >> OMAP3 SRF: Voltage scaling support >> OMAP3 SRF: VDD2 scaling support >> OMAP3 SRF: Adds sysfs control for VDD1/VDD2 OPP's >> OMAP3 PM: Replace spinlocks with mutex in SRF >> OMAP3 PM: CPUFreq driver for OMAP3 >> OMAP3 PM: Update the min defconfig for 3430sdp >> OMAP3 SRF: Fix crash on non-3430SDP platforms with DVFS/CPUFreq >> OMAP3: PM: Scale VDD2 OPP for VDD1 OPP3 and higher >> >> Tero Kristo (26): >> OMAP: PM debug: do not print out status for meta >> powerdomains (dpll*) >> OMAP: PM debug: Add PRCM register dump support >> OMAP: PM: DMA context save / restore >> OMAP: PM: off-mode support for DMA on EMU/HS devices >> OMAP3: SRAM size fix for HS/EMU devices >> OMAP3 PM: off-mode support for HS/EMU devices >> OMAP3: PM: Enable SDRAM auto-refresh during sleep >> OMAP: SDRC: Add new register definitions for SDRAM controller >> OMAP3: PM: SDRC auto-refresh workaround for off-mode >> PM: Added three PLL registers to the PRCM context save >> PM: Changed secure RAM storage size from 0x8000 to 0x803F >> PM: Added suspend target state control to debugfs for OMAP3 >> OMAP3: PM: Prevent PER from going OFF when CORE is going INA >> PM OMAP3: Change omap3_save_secure_ram to be called >> only during init >> OMAP3: PM: MPU and CORE should stay awake if there is >> CAM domain ACTIVE >> OMAP3: GPIO fixes for off-mode >> PM: OMAP3: Refreshed DVFS VDD1 control against latest clock fw >> OMAP3: Add support for DPLL3 divisor values higher than 2 >> OMAP3: PM: Fixed VDD2 control to work from both sysfs >> and SRF API >> OMAP3: PM: Added DVFS OPP locking interface for VDD1 and VDD2 >> OMAP3: Fix rate calculation bug in omap3_select_table_rate >> OMAP3: PM: Prevented DVFS state switches when enabling off-mode >> OMAP3: PM: Enable VDD2 OPP1 >> OMAP3: PM: Fix linker error without CONFIG_PM option >> PM: OMAP3: Removed a couple of unused variables from DVFS code >> PM: OMAP3: Added support for possibly failing >> clk_set_rate to DVFS >> >> -- >> To unsubscribe from this list: send the line "unsubscribe >> linux-omap" in >> the body of a message to majordomo@vger.kernel.org >> More majordomo info at http://vger.kernel.org/majordomo-info.html >> >> ^ permalink raw reply [flat|nested] 40+ messages in thread
* RE: new PM branch available 2009-01-16 19:03 ` Kevin Hilman @ 2009-01-19 15:46 ` Premi, Sanjeev 2009-01-19 16:04 ` Premi, Sanjeev 2009-01-23 10:19 ` Nayak, Rajendra 1 sibling, 1 reply; 40+ messages in thread From: Premi, Sanjeev @ 2009-01-19 15:46 UTC (permalink / raw) To: Kevin Hilman, Nayak, Rajendra; +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 Kevin Hilman > Sent: Saturday, January 17, 2009 12:33 AM > To: Nayak, Rajendra > Cc: linux-omap@vger.kernel.org > Subject: Re: new PM branch available > > "Nayak, Rajendra" <rnayak@ti.com> writes: > > > I did some testing today on my 3.0GP 3430SDP. This is with > the omap_3430sdp_min_defconfig. > > > > 1) Idle. > > echo -n 1 > /sys/power/clocks_off_while_idle echo -n 1 > > > /sys/power/enable_off Could not hit RET. something seems to > be still > > active. Not sure if it could be something to do with this > error that's > > thrown while bootup > > > > <6>Disabling unused clock "dpll5_ck" > > Disabling unused clock "dpll5_ck" > > <3>clock: dpll5_ck failed transition to 'locked' > > clock: dpll5_ck failed transition to 'locked' > > This is the same results I see on my SDP. > > Looking at the registers, I am pretty sure it is the D2D > clockdomain that still has activity, but due to very poor > Stacked-mode docs and no responses to the D2D questions asked > to TI I have not been able to figure this one out. > > Help debugging this would be greatly appreciated. > > > Further doing a > > echo -n 1 > /sys/power/sleep_while_idle causes a hang after > the 5 odd > > secs of UART inactivity. > > Is'nt this option supposed to affect only the suspend path behavior? > > No, this affects the common idle loop, with and without CPUidle. > > > Is CPUidle disabled in the default defconfig now? > > > > 2) Suspend > > echo -n 1 > /sys/power/clocks_off_while_idle Hangs on a echo mem > > > /sys/power/state Goes into suspend, but cannot recover > > I'm pretty sure all the hangs going into RET are related. > > Kevin > > > 3) DVFS > > Both VDD1 and VDD2 DVFS seem to function fine. > > [sp] I was trying to test DVFS on the OMAP3EVM. This log from my console illustrates the problems I face: # cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors ondemand performance # # cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies cat: read error: No such device # # cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor performance # # echo -n "ondemand" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor # # cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor Performance Here is snapshot from "menuconfig": [*] CPU Frequency scaling [ ] Enable CPUfreq debugging <*> CPU frequency translation statistics [ ] CPU frequency translation statistics details Default CPUFreq governor (performance) ---> -*- 'performance' governor < > 'powersave' governor < > 'userspace' governor for userspace frequency scaling <*> 'ondemand' cpufreq policy governor < > 'conservative' cpufreq governor Currently building with ondemand as default... Best regards, Sanjeev > >> -----Original Message----- > >> From: linux-omap-owner@vger.kernel.org > >> [mailto:linux-omap-owner@vger.kernel.org] On Behalf Of Kevin Hilman > >> Sent: Wednesday, January 14, 2009 3:22 AM > >> To: linux-omap@vger.kernel.org > >> Subject: new PM branch available > >> > >> Hello, > >> > >> The latest PM branch is now available[1]. > >> <snip>--<snip> ^ permalink raw reply [flat|nested] 40+ messages in thread
* RE: new PM branch available 2009-01-19 15:46 ` Premi, Sanjeev @ 2009-01-19 16:04 ` Premi, Sanjeev 0 siblings, 0 replies; 40+ messages in thread From: Premi, Sanjeev @ 2009-01-19 16:04 UTC (permalink / raw) To: Premi, Sanjeev, Kevin Hilman, Nayak, Rajendra; +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 Premi, Sanjeev > Sent: Monday, January 19, 2009 9:16 PM > To: Kevin Hilman; Nayak, Rajendra > Cc: linux-omap@vger.kernel.org > Subject: RE: new PM branch available > > > > > -----Original Message----- > > From: linux-omap-owner@vger.kernel.org > > [mailto:linux-omap-owner@vger.kernel.org] On Behalf Of Kevin Hilman > > Sent: Saturday, January 17, 2009 12:33 AM > > To: Nayak, Rajendra > > Cc: linux-omap@vger.kernel.org > > Subject: Re: new PM branch available > > > > "Nayak, Rajendra" <rnayak@ti.com> writes: > > > > > I did some testing today on my 3.0GP 3430SDP. This is with > > the omap_3430sdp_min_defconfig. > > > > > > 1) Idle. > > > echo -n 1 > /sys/power/clocks_off_while_idle echo -n 1 > > > > /sys/power/enable_off Could not hit RET. something seems to > > be still > > > active. Not sure if it could be something to do with this > > error that's > > > thrown while bootup > > > > > > <6>Disabling unused clock "dpll5_ck" > > > Disabling unused clock "dpll5_ck" > > > <3>clock: dpll5_ck failed transition to 'locked' > > > clock: dpll5_ck failed transition to 'locked' > > > > This is the same results I see on my SDP. > > > > Looking at the registers, I am pretty sure it is the D2D > clockdomain > > that still has activity, but due to very poor Stacked-mode > docs and no > > responses to the D2D questions asked to TI I have not been able to > > figure this one out. > > > > Help debugging this would be greatly appreciated. > > > > > Further doing a > > > echo -n 1 > /sys/power/sleep_while_idle causes a hang after > > the 5 odd > > > secs of UART inactivity. > > > Is'nt this option supposed to affect only the suspend > path behavior? > > > > No, this affects the common idle loop, with and without CPUidle. > > > > > Is CPUidle disabled in the default defconfig now? > > > > > > 2) Suspend > > > echo -n 1 > /sys/power/clocks_off_while_idle Hangs on a > echo mem > > > > /sys/power/state Goes into suspend, but cannot recover > > > > I'm pretty sure all the hangs going into RET are related. > > > > Kevin > > > > > 3) DVFS > > > Both VDD1 and VDD2 DVFS seem to function fine. > > > > > [sp] I was trying to test DVFS on the OMAP3EVM. This log from > my console illustrates the problems I face: > > # cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors > ondemand performance > # > # cat > /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies > cat: read error: No such device > # > # cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor > performance > # > # echo -n "ondemand" > > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor > # > # cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor > Performance > > Here is snapshot from "menuconfig": > [*] CPU Frequency scaling > [ ] Enable CPUfreq debugging > <*> CPU frequency translation statistics > [ ] CPU frequency translation statistics details > Default CPUFreq governor (performance) ---> > -*- 'performance' governor > < > 'powersave' governor > < > 'userspace' governor for userspace frequency scaling > <*> 'ondemand' cpufreq policy governor > < > 'conservative' cpufreq governor > > Currently building with ondemand as default... > [sp] with ondemand and default governor, I did not see cpufreq getting loaded. Will be looking further tomorrow morning. Any updates till then? > Best regards, > Sanjeev > > > >> -----Original Message----- > > >> From: linux-omap-owner@vger.kernel.org > > >> [mailto:linux-omap-owner@vger.kernel.org] On Behalf Of > Kevin Hilman > > >> Sent: Wednesday, January 14, 2009 3:22 AM > > >> To: linux-omap@vger.kernel.org > > >> Subject: new PM branch available > > >> > > >> Hello, > > >> > > >> The latest PM branch is now available[1]. > > >> > <snip>--<snip> > -- > 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] 40+ messages in thread
* RE: new PM branch available 2009-01-16 19:03 ` Kevin Hilman 2009-01-19 15:46 ` Premi, Sanjeev @ 2009-01-23 10:19 ` Nayak, Rajendra 2009-01-23 11:21 ` Högander Jouni 1 sibling, 1 reply; 40+ messages in thread From: Nayak, Rajendra @ 2009-01-23 10:19 UTC (permalink / raw) To: Kevin Hilman; +Cc: linux-omap@vger.kernel.org > I did some testing today on my 3.0GP 3430SDP. This is with the omap_3430sdp_min_defconfig. > > 1) Idle. > echo -n 1 > /sys/power/clocks_off_while_idle > echo -n 1 > /sys/power/enable_off > Could not hit RET. something seems to be still active. Not sure if it could be something > to do with this error that's thrown while bootup > > <6>Disabling unused clock "dpll5_ck" > Disabling unused clock "dpll5_ck" > <3>clock: dpll5_ck failed transition to 'locked' > clock: dpll5_ck failed transition to 'locked' > > This is the same results I see on my SDP. > > Looking at the registers, I am pretty sure it is the D2D clockdomain > that still has activity, but due to very poor Stacked-mode docs and no > responses to the D2D questions asked to TI I have not been able to > figure this one out. > > Help debugging this would be greatly appreciated. I looked some more into this today and saw that the hang is indeed caused due to some kind of debug console going dead. The system was still looping in the idle thread. I could even do a telnet remotely to my board and take some debug dumps.. I am not too familiar with the debug hooks that exist but from what I understand, IVA seem to be one thing preventng a RET/OFF. This dump I took from a telnet window after the hang on debug console.. # cd pm_debug/ # cat count usbhost_pwrdm (RET),OFF:0,RET:1,INA:0,ON:1 sgx_pwrdm (OFF),OFF:1,RET:0,INA:0,ON:1 per_pwrdm (ON),OFF:0,RET:0,INA:0,ON:1 dss_pwrdm (RET),OFF:0,RET:1,INA:0,ON:1 cam_pwrdm (RET),OFF:0,RET:1,INA:0,ON:1 core_pwrdm (ON),OFF:0,RET:0,INA:0,ON:1 neon_pwrdm (ON),OFF:0,RET:466,INA:3048,ON:3515 mpu_pwrdm (ON),OFF:0,RET:466,INA:3048,ON:3515 iva2_pwrdm (ON),OFF:0,RET:0,INA:0,ON:1 per_clkdm->per_pwrdm (9) usbhost_clkdm->usbhost_pwrdm (0) cam_clkdm->cam_pwrdm (0) dss_clkdm->dss_pwrdm (0) core_l4_clkdm->core_pwrdm (3) core_l3_clkdm->core_pwrdm (4) d2d_clkdm->core_pwrdm (0) sgx_clkdm->sgx_pwrdm (0) iva2_clkdm->iva2_pwrdm (0) neon_clkdm->neon_pwrdm (0) mpu_clkdm->mpu_pwrdm (0) prm_clkdm->wkup_pwrdm (12) cm_clkdm->core_pwrdm (3) # Whats surprsing is that the same image sometimes does hit RET/OFF, though I still see the console hang. I could see the VCORE Led flicker as well. This dump I took from the telnet and here IVA did transition.. # cat count usbhost_pwrdm (OFF),OFF:1,RET:1,INA:0,ON:1 sgx_pwrdm (OFF),OFF:1,RET:0,INA:0,ON:1 per_pwrdm (ON),OFF:131,RET:2980,INA:0,ON:3112 dss_pwrdm (OFF),OFF:1,RET:1,INA:0,ON:1 cam_pwrdm (OFF),OFF:1,RET:1,INA:0,ON:1 core_pwrdm (ON),OFF:0,RET:1840,INA:199,ON:2040 neon_pwrdm (ON),OFF:13,RET:2026,INA:2390,ON:4430 mpu_pwrdm (ON),OFF:13,RET:2026,INA:2390,ON:4430 iva2_pwrdm (OFF),OFF:1,RET:1,INA:0,ON:1 per_clkdm->per_pwrdm (9) usbhost_clkdm->usbhost_pwrdm (0) cam_clkdm->cam_pwrdm (0) dss_clkdm->dss_pwrdm (0) core_l4_clkdm->core_pwrdm (3) core_l3_clkdm->core_pwrdm (4) d2d_clkdm->core_pwrdm (0) sgx_clkdm->sgx_pwrdm (0) iva2_clkdm->iva2_pwrdm (0) neon_clkdm->neon_pwrdm (0) mpu_clkdm->mpu_pwrdm (0) prm_clkdm->wkup_pwrdm (12) cm_clkdm->core_pwrdm (3) # Kevin, after you put the omap3_iva_idle code in there, did you try if that worked on a SDP? ^ permalink raw reply [flat|nested] 40+ messages in thread
* Re: new PM branch available 2009-01-23 10:19 ` Nayak, Rajendra @ 2009-01-23 11:21 ` Högander Jouni 2009-01-23 12:00 ` Nayak, Rajendra 0 siblings, 1 reply; 40+ messages in thread From: Högander Jouni @ 2009-01-23 11:21 UTC (permalink / raw) To: ext Nayak, Rajendra; +Cc: Kevin Hilman, linux-omap@vger.kernel.org "ext Nayak, Rajendra" <rnayak@ti.com> writes: >> I did some testing today on my 3.0GP 3430SDP. This is with the omap_3430sdp_min_defconfig. >> >> 1) Idle. >> echo -n 1 > /sys/power/clocks_off_while_idle >> echo -n 1 > /sys/power/enable_off >> Could not hit RET. something seems to be still active. Not sure if it could be something >> to do with this error that's thrown while bootup >> >> <6>Disabling unused clock "dpll5_ck" >> Disabling unused clock "dpll5_ck" >> <3>clock: dpll5_ck failed transition to 'locked' >> clock: dpll5_ck failed transition to 'locked' >> >> This is the same results I see on my SDP. >> >> Looking at the registers, I am pretty sure it is the D2D clockdomain >> that still has activity, but due to very poor Stacked-mode docs and no >> responses to the D2D questions asked to TI I have not been able to >> figure this one out. >> >> Help debugging this would be greatly appreciated. > > I looked some more into this today and saw that the hang is indeed caused > due to some kind of debug console going dead. The system was still looping in the > idle thread. I could even do a telnet remotely to my board and take > some debug dumps.. This might help you: diff --git a/arch/arm/mach-omap2/pm34xx.c b/arch/arm/mach-omap2/pm34xx.c index b2db0ba..266e4f5 100644 --- a/arch/arm/mach-omap2/pm34xx.c +++ b/arch/arm/mach-omap2/pm34xx.c @@ -401,6 +401,8 @@ void omap_sram_idle(void) omap3_prcm_restore_context(); omap3_sram_restore_context(); } + omap_uart_resume_idle(0); + omap_uart_resume_idle(1); if (core_next_state == PWRDM_POWER_OFF) prm_clear_mod_reg_bits(OMAP3430_AUTO_OFF, OMAP3430_GR_MOD, -- 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 related [flat|nested] 40+ messages in thread
* RE: new PM branch available 2009-01-23 11:21 ` Högander Jouni @ 2009-01-23 12:00 ` Nayak, Rajendra 2009-01-23 12:10 ` Nayak, Rajendra ` (2 more replies) 0 siblings, 3 replies; 40+ messages in thread From: Nayak, Rajendra @ 2009-01-23 12:00 UTC (permalink / raw) To: Högander Jouni; +Cc: Kevin Hilman, linux-omap@vger.kernel.org > -----Original Message----- > From: Högander Jouni [mailto:jouni.hogander@nokia.com] > Sent: Friday, January 23, 2009 4:52 PM > To: Nayak, Rajendra > Cc: Kevin Hilman; linux-omap@vger.kernel.org > Subject: Re: new PM branch available > > "ext Nayak, Rajendra" <rnayak@ti.com> writes: > > >> I did some testing today on my 3.0GP 3430SDP. This is with > the omap_3430sdp_min_defconfig. > >> > >> 1) Idle. > >> echo -n 1 > /sys/power/clocks_off_while_idle > >> echo -n 1 > /sys/power/enable_off > >> Could not hit RET. something seems to be still active. Not > sure if it could be something > >> to do with this error that's thrown while bootup > >> > >> <6>Disabling unused clock "dpll5_ck" > >> Disabling unused clock "dpll5_ck" > >> <3>clock: dpll5_ck failed transition to 'locked' > >> clock: dpll5_ck failed transition to 'locked' > >> > >> This is the same results I see on my SDP. > >> > >> Looking at the registers, I am pretty sure it is the D2D > clockdomain > >> that still has activity, but due to very poor Stacked-mode > docs and no > >> responses to the D2D questions asked to TI I have not been able to > >> figure this one out. > >> > >> Help debugging this would be greatly appreciated. > > > > I looked some more into this today and saw that the hang is > indeed caused > > due to some kind of debug console going dead. The system > was still looping in the > > idle thread. I could even do a telnet remotely to my board and take > > some debug dumps.. > > This might help you: Yup, this does help. There's no hang now either in idle or in suspend. Not sure why this was affecting only the SDP while the pm branch seems to function without this for beagle and other omap3 platforms? > > diff --git a/arch/arm/mach-omap2/pm34xx.c > b/arch/arm/mach-omap2/pm34xx.c > index b2db0ba..266e4f5 100644 > --- a/arch/arm/mach-omap2/pm34xx.c > +++ b/arch/arm/mach-omap2/pm34xx.c > @@ -401,6 +401,8 @@ void omap_sram_idle(void) > omap3_prcm_restore_context(); > omap3_sram_restore_context(); > } > + omap_uart_resume_idle(0); > + omap_uart_resume_idle(1); > if (core_next_state == PWRDM_POWER_OFF) > prm_clear_mod_reg_bits(OMAP3430_AUTO_OFF, > OMAP3430_GR_MOD, > > -- > Jouni Högander > > > ^ permalink raw reply [flat|nested] 40+ messages in thread
* RE: new PM branch available 2009-01-23 12:00 ` Nayak, Rajendra @ 2009-01-23 12:10 ` Nayak, Rajendra 2009-01-23 16:49 ` Kevin Hilman 2009-01-23 12:10 ` Koen Kooi 2009-01-23 17:48 ` Kevin Hilman 2 siblings, 1 reply; 40+ messages in thread From: Nayak, Rajendra @ 2009-01-23 12:10 UTC (permalink / raw) To: Högander Jouni; +Cc: Kevin Hilman, linux-omap@vger.kernel.org > -----Original Message----- > From: linux-omap-owner@vger.kernel.org > [mailto:linux-omap-owner@vger.kernel.org] On Behalf Of Nayak, Rajendra > Sent: Friday, January 23, 2009 5:30 PM > To: Högander Jouni > Cc: Kevin Hilman; linux-omap@vger.kernel.org > Subject: RE: new PM branch available > > > > > -----Original Message----- > > From: Högander Jouni [mailto:jouni.hogander@nokia.com] > > Sent: Friday, January 23, 2009 4:52 PM > > To: Nayak, Rajendra > > Cc: Kevin Hilman; linux-omap@vger.kernel.org > > Subject: Re: new PM branch available > > > > "ext Nayak, Rajendra" <rnayak@ti.com> writes: > > > > >> I did some testing today on my 3.0GP 3430SDP. This is with > > the omap_3430sdp_min_defconfig. > > >> > > >> 1) Idle. > > >> echo -n 1 > /sys/power/clocks_off_while_idle > > >> echo -n 1 > /sys/power/enable_off > > >> Could not hit RET. something seems to be still active. Not > > sure if it could be something > > >> to do with this error that's thrown while bootup > > >> > > >> <6>Disabling unused clock "dpll5_ck" > > >> Disabling unused clock "dpll5_ck" > > >> <3>clock: dpll5_ck failed transition to 'locked' > > >> clock: dpll5_ck failed transition to 'locked' > > >> > > >> This is the same results I see on my SDP. > > >> > > >> Looking at the registers, I am pretty sure it is the D2D > > clockdomain > > >> that still has activity, but due to very poor Stacked-mode > > docs and no > > >> responses to the D2D questions asked to TI I have not > been able to > > >> figure this one out. > > >> > > >> Help debugging this would be greatly appreciated. > > > > > > I looked some more into this today and saw that the hang is > > indeed caused > > > due to some kind of debug console going dead. The system > > was still looping in the > > > idle thread. I could even do a telnet remotely to my > board and take > > > some debug dumps.. > > > > This might help you: > > Yup, this does help. There's no hang now either in idle or in suspend. > Not sure why this was affecting only the SDP while the pm branch seems > to function without this for beagle and other omap3 platforms? Looks like all other platforms use UART3 and SDP is the only one using UART1 for debug console. Would you be sending a patch for this on the pm branch? > > > > > diff --git a/arch/arm/mach-omap2/pm34xx.c > > b/arch/arm/mach-omap2/pm34xx.c > > index b2db0ba..266e4f5 100644 > > --- a/arch/arm/mach-omap2/pm34xx.c > > +++ b/arch/arm/mach-omap2/pm34xx.c > > @@ -401,6 +401,8 @@ void omap_sram_idle(void) > > omap3_prcm_restore_context(); > > omap3_sram_restore_context(); > > } > > + omap_uart_resume_idle(0); > > + omap_uart_resume_idle(1); > > if (core_next_state == PWRDM_POWER_OFF) > > prm_clear_mod_reg_bits(OMAP3430_AUTO_OFF, > > OMAP3430_GR_MOD, > > > > -- > > Jouni Högander > > > > > > \x13 칻\x1c & ~ & \x18 +- ݶ\x17 w ˛ m b h b ^n r z \x1a h & > \x1e G h \x03( 階 ݢj" \x1a ^[m z ޖ f h ~ m ^ permalink raw reply [flat|nested] 40+ messages in thread
* Re: new PM branch available 2009-01-23 12:10 ` Nayak, Rajendra @ 2009-01-23 16:49 ` Kevin Hilman 0 siblings, 0 replies; 40+ messages in thread From: Kevin Hilman @ 2009-01-23 16:49 UTC (permalink / raw) To: Nayak, Rajendra; +Cc: Högander Jouni, linux-omap@vger.kernel.org [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain; charset=utf-8, Size: 3790 bytes --] "Nayak, Rajendra" <rnayak@ti.com> writes: >> -----Original Message----- >> From: linux-omap-owner@vger.kernel.org >> [mailto:linux-omap-owner@vger.kernel.org] On Behalf Of Nayak, Rajendra >> Sent: Friday, January 23, 2009 5:30 PM >> To: Högander Jouni >> Cc: Kevin Hilman; linux-omap@vger.kernel.org >> Subject: RE: new PM branch available >> >> >> >> > -----Original Message----- >> > From: Högander Jouni [mailto:jouni.hogander@nokia.com] >> > Sent: Friday, January 23, 2009 4:52 PM >> > To: Nayak, Rajendra >> > Cc: Kevin Hilman; linux-omap@vger.kernel.org >> > Subject: Re: new PM branch available >> > >> > "ext Nayak, Rajendra" <rnayak@ti.com> writes: >> > >> > >> I did some testing today on my 3.0GP 3430SDP. This is with >> > the omap_3430sdp_min_defconfig. >> > >> >> > >> 1) Idle. >> > >> echo -n 1 > /sys/power/clocks_off_while_idle >> > >> echo -n 1 > /sys/power/enable_off >> > >> Could not hit RET. something seems to be still active. Not >> > sure if it could be something >> > >> to do with this error that's thrown while bootup >> > >> >> > >> <6>Disabling unused clock "dpll5_ck" >> > >> Disabling unused clock "dpll5_ck" >> > >> <3>clock: dpll5_ck failed transition to 'locked' >> > >> clock: dpll5_ck failed transition to 'locked' >> > >> >> > >> This is the same results I see on my SDP. >> > >> >> > >> Looking at the registers, I am pretty sure it is the D2D >> > clockdomain >> > >> that still has activity, but due to very poor Stacked-mode >> > docs and no >> > >> responses to the D2D questions asked to TI I have not >> been able to >> > >> figure this one out. >> > >> >> > >> Help debugging this would be greatly appreciated. >> > > >> > > I looked some more into this today and saw that the hang is >> > indeed caused >> > > due to some kind of debug console going dead. The system >> > was still looping in the >> > > idle thread. I could even do a telnet remotely to my >> board and take >> > > some debug dumps.. >> > >> > This might help you: >> >> Yup, this does help. There's no hang now either in idle or in suspend. >> Not sure why this was affecting only the SDP while the pm branch seems >> to function without this for beagle and other omap3 platforms? > > Looks like all other platforms use UART3 and SDP is the only one using UART1 > for debug console. > > Would you be sending a patch for this on the pm branch? Thanks Jouni. I now have this queued up for pm branch. Indeed beagle and custom hw I'm using are not using UART1, that's why I didn't notice before. This is probably causing the non-wakeup problem on EVM as well. Will try today. Kevin >> >> > >> > diff --git a/arch/arm/mach-omap2/pm34xx.c >> > b/arch/arm/mach-omap2/pm34xx.c >> > index b2db0ba..266e4f5 100644 >> > --- a/arch/arm/mach-omap2/pm34xx.c >> > +++ b/arch/arm/mach-omap2/pm34xx.c >> > @@ -401,6 +401,8 @@ void omap_sram_idle(void) >> > omap3_prcm_restore_context(); >> > omap3_sram_restore_context(); >> > } >> > + omap_uart_resume_idle(0); >> > + omap_uart_resume_idle(1); >> > if (core_next_state == PWRDM_POWER_OFF) >> > prm_clear_mod_reg_bits(OMAP3430_AUTO_OFF, >> > OMAP3430_GR_MOD, >> > >> > -- >> > Jouni Högander >> > >> > >> > . .¹.\x1c & ~ & . +- ݶ. w Ë› m b h b ^n r z . h & >> . G h .( 階 Ý¢j" . .m z Þ– f h ~ m -- 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] 40+ messages in thread
* Re: new PM branch available 2009-01-23 12:00 ` Nayak, Rajendra 2009-01-23 12:10 ` Nayak, Rajendra @ 2009-01-23 12:10 ` Koen Kooi 2009-01-23 17:20 ` Kevin Hilman 2009-01-23 17:48 ` Kevin Hilman 2 siblings, 1 reply; 40+ messages in thread From: Koen Kooi @ 2009-01-23 12:10 UTC (permalink / raw) To: Nayak, Rajendra Cc: Högander Jouni, Kevin Hilman, linux-omap@vger.kernel.org [-- Attachment #1: Type: text/plain, Size: 3021 bytes --] Op 23 jan 2009, om 13:00 heeft Nayak, Rajendra het volgende geschreven: > > >> -----Original Message----- >> From: Högander Jouni [mailto:jouni.hogander@nokia.com] >> Sent: Friday, January 23, 2009 4:52 PM >> To: Nayak, Rajendra >> Cc: Kevin Hilman; linux-omap@vger.kernel.org >> Subject: Re: new PM branch available >> >> "ext Nayak, Rajendra" <rnayak@ti.com> writes: >> >>>> I did some testing today on my 3.0GP 3430SDP. This is with >> the omap_3430sdp_min_defconfig. >>>> >>>> 1) Idle. >>>> echo -n 1 > /sys/power/clocks_off_while_idle >>>> echo -n 1 > /sys/power/enable_off >>>> Could not hit RET. something seems to be still active. Not >> sure if it could be something >>>> to do with this error that's thrown while bootup >>>> >>>> <6>Disabling unused clock "dpll5_ck" >>>> Disabling unused clock "dpll5_ck" >>>> <3>clock: dpll5_ck failed transition to 'locked' >>>> clock: dpll5_ck failed transition to 'locked' >>>> >>>> This is the same results I see on my SDP. >>>> >>>> Looking at the registers, I am pretty sure it is the D2D >> clockdomain >>>> that still has activity, but due to very poor Stacked-mode >> docs and no >>>> responses to the D2D questions asked to TI I have not been able to >>>> figure this one out. >>>> >>>> Help debugging this would be greatly appreciated. >>> >>> I looked some more into this today and saw that the hang is >> indeed caused >>> due to some kind of debug console going dead. The system >> was still looping in the >>> idle thread. I could even do a telnet remotely to my board and take >>> some debug dumps.. >> >> This might help you: > > Yup, this does help. There's no hang now either in idle or in suspend. > Not sure why this was affecting only the SDP while the pm branch seems > to function without this for beagle and other omap3 platforms? I get 'hangs' on the beagle as well with the PM branch. They mostly seem to happen when I boot a fresh rootfs and the packagemanager runs a lot of postinst scripts without any form of user interaction. regards, Koen > > >> >> diff --git a/arch/arm/mach-omap2/pm34xx.c >> b/arch/arm/mach-omap2/pm34xx.c >> index b2db0ba..266e4f5 100644 >> --- a/arch/arm/mach-omap2/pm34xx.c >> +++ b/arch/arm/mach-omap2/pm34xx.c >> @@ -401,6 +401,8 @@ void omap_sram_idle(void) >> omap3_prcm_restore_context(); >> omap3_sram_restore_context(); >> } >> + omap_uart_resume_idle(0); >> + omap_uart_resume_idle(1); >> if (core_next_state == PWRDM_POWER_OFF) >> prm_clear_mod_reg_bits(OMAP3430_AUTO_OFF, >> OMAP3430_GR_MOD, >> >> -- >> 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 >> [-- Attachment #2: Dit deel van het bericht is digitaal ondertekend --] [-- Type: application/pgp-signature, Size: 186 bytes --] ^ permalink raw reply [flat|nested] 40+ messages in thread
* Re: new PM branch available 2009-01-23 12:10 ` Koen Kooi @ 2009-01-23 17:20 ` Kevin Hilman 2009-01-23 18:27 ` Koen Kooi 0 siblings, 1 reply; 40+ messages in thread From: Kevin Hilman @ 2009-01-23 17:20 UTC (permalink / raw) To: Koen Kooi Cc: Nayak, Rajendra, Högander Jouni, linux-omap@vger.kernel.org Koen Kooi <k.kooi@student.utwente.nl> writes: > Op 23 jan 2009, om 13:00 heeft Nayak, Rajendra het volgende geschreven: > >> >> >>> -----Original Message----- >>> From: Högander Jouni [mailto:jouni.hogander@nokia.com] >>> Sent: Friday, January 23, 2009 4:52 PM >>> To: Nayak, Rajendra >>> Cc: Kevin Hilman; linux-omap@vger.kernel.org >>> Subject: Re: new PM branch available >>> >>> "ext Nayak, Rajendra" <rnayak@ti.com> writes: >>> >>>>> I did some testing today on my 3.0GP 3430SDP. This is with >>> the omap_3430sdp_min_defconfig. >>>>> >>>>> 1) Idle. >>>>> echo -n 1 > /sys/power/clocks_off_while_idle >>>>> echo -n 1 > /sys/power/enable_off >>>>> Could not hit RET. something seems to be still active. Not >>> sure if it could be something >>>>> to do with this error that's thrown while bootup >>>>> >>>>> <6>Disabling unused clock "dpll5_ck" >>>>> Disabling unused clock "dpll5_ck" >>>>> <3>clock: dpll5_ck failed transition to 'locked' >>>>> clock: dpll5_ck failed transition to 'locked' >>>>> >>>>> This is the same results I see on my SDP. >>>>> >>>>> Looking at the registers, I am pretty sure it is the D2D >>> clockdomain >>>>> that still has activity, but due to very poor Stacked-mode >>> docs and no >>>>> responses to the D2D questions asked to TI I have not been able to >>>>> figure this one out. >>>>> >>>>> Help debugging this would be greatly appreciated. >>>> >>>> I looked some more into this today and saw that the hang is >>> indeed caused >>>> due to some kind of debug console going dead. The system >>> was still looping in the >>>> idle thread. I could even do a telnet remotely to my board and take >>>> some debug dumps.. >>> >>> This might help you: >> >> Yup, this does help. There's no hang now either in idle or in suspend. >> Not sure why this was affecting only the SDP while the pm branch seems >> to function without this for beagle and other omap3 platforms? > > I get 'hangs' on the beagle as well with the PM branch. They mostly > seem to happen when I boot a fresh rootfs and the packagemanager runs > a lot of postinst scripts without any form of user interaction. > Koen, What are your /sys/power/clocks_off_while_idle and ../sleep_while_idle set to? Do you see the hangs when both of these are zero? Kevin -- 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] 40+ messages in thread
* Re: new PM branch available 2009-01-23 17:20 ` Kevin Hilman @ 2009-01-23 18:27 ` Koen Kooi 0 siblings, 0 replies; 40+ messages in thread From: Koen Kooi @ 2009-01-23 18:27 UTC (permalink / raw) To: Kevin Hilman; +Cc: linux-omap@vger.kernel.org List [-- Attachment #1: Type: text/plain, Size: 2633 bytes --] Op 23 jan 2009, om 18:20 heeft Kevin Hilman het volgende geschreven: > Koen Kooi <k.kooi@student.utwente.nl> writes: > >> Op 23 jan 2009, om 13:00 heeft Nayak, Rajendra het volgende >> geschreven: >> >>> >>> >>>> -----Original Message----- >>>> From: Högander Jouni [mailto:jouni.hogander@nokia.com] >>>> Sent: Friday, January 23, 2009 4:52 PM >>>> To: Nayak, Rajendra >>>> Cc: Kevin Hilman; linux-omap@vger.kernel.org >>>> Subject: Re: new PM branch available >>>> >>>> "ext Nayak, Rajendra" <rnayak@ti.com> writes: >>>> >>>>>> I did some testing today on my 3.0GP 3430SDP. This is with >>>> the omap_3430sdp_min_defconfig. >>>>>> >>>>>> 1) Idle. >>>>>> echo -n 1 > /sys/power/clocks_off_while_idle >>>>>> echo -n 1 > /sys/power/enable_off >>>>>> Could not hit RET. something seems to be still active. Not >>>> sure if it could be something >>>>>> to do with this error that's thrown while bootup >>>>>> >>>>>> <6>Disabling unused clock "dpll5_ck" >>>>>> Disabling unused clock "dpll5_ck" >>>>>> <3>clock: dpll5_ck failed transition to 'locked' >>>>>> clock: dpll5_ck failed transition to 'locked' >>>>>> >>>>>> This is the same results I see on my SDP. >>>>>> >>>>>> Looking at the registers, I am pretty sure it is the D2D >>>> clockdomain >>>>>> that still has activity, but due to very poor Stacked-mode >>>> docs and no >>>>>> responses to the D2D questions asked to TI I have not been able >>>>>> to >>>>>> figure this one out. >>>>>> >>>>>> Help debugging this would be greatly appreciated. >>>>> >>>>> I looked some more into this today and saw that the hang is >>>> indeed caused >>>>> due to some kind of debug console going dead. The system >>>> was still looping in the >>>>> idle thread. I could even do a telnet remotely to my board and >>>>> take >>>>> some debug dumps.. >>>> >>>> This might help you: >>> >>> Yup, this does help. There's no hang now either in idle or in >>> suspend. >>> Not sure why this was affecting only the SDP while the pm branch >>> seems >>> to function without this for beagle and other omap3 platforms? >> >> I get 'hangs' on the beagle as well with the PM branch. They mostly >> seem to happen when I boot a fresh rootfs and the packagemanager runs >> a lot of postinst scripts without any form of user interaction. >> > > Koen, > > What are your /sys/power/clocks_off_while_idle and ../sleep_while_idle > set to? Ehm, the default I guess, I'm not touching to sysfsnodes anywhere :) > Do you see the hangs when both of these are zero? I'll have a look at that later next week. regards, Koen [-- Attachment #2: Dit deel van het bericht is digitaal ondertekend --] [-- Type: application/pgp-signature, Size: 186 bytes --] ^ permalink raw reply [flat|nested] 40+ messages in thread
* Re: new PM branch available 2009-01-23 12:00 ` Nayak, Rajendra 2009-01-23 12:10 ` Nayak, Rajendra 2009-01-23 12:10 ` Koen Kooi @ 2009-01-23 17:48 ` Kevin Hilman 2009-01-27 9:18 ` Nayak, Rajendra 2 siblings, 1 reply; 40+ messages in thread From: Kevin Hilman @ 2009-01-23 17:48 UTC (permalink / raw) To: Nayak, Rajendra; +Cc: Högander Jouni, linux-omap@vger.kernel.org "Nayak, Rajendra" <rnayak@ti.com> writes: > > >> -----Original Message----- >> From: Högander Jouni [mailto:jouni.hogander@nokia.com] >> Sent: Friday, January 23, 2009 4:52 PM >> To: Nayak, Rajendra >> Cc: Kevin Hilman; linux-omap@vger.kernel.org >> Subject: Re: new PM branch available >> >> "ext Nayak, Rajendra" <rnayak@ti.com> writes: >> >> >> I did some testing today on my 3.0GP 3430SDP. This is with >> the omap_3430sdp_min_defconfig. >> >> >> >> 1) Idle. >> >> echo -n 1 > /sys/power/clocks_off_while_idle >> >> echo -n 1 > /sys/power/enable_off >> >> Could not hit RET. something seems to be still active. Not >> sure if it could be something >> >> to do with this error that's thrown while bootup >> >> >> >> <6>Disabling unused clock "dpll5_ck" >> >> Disabling unused clock "dpll5_ck" >> >> <3>clock: dpll5_ck failed transition to 'locked' >> >> clock: dpll5_ck failed transition to 'locked' >> >> >> >> This is the same results I see on my SDP. >> >> >> >> Looking at the registers, I am pretty sure it is the D2D >> clockdomain >> >> that still has activity, but due to very poor Stacked-mode >> docs and no >> >> responses to the D2D questions asked to TI I have not been able to >> >> figure this one out. >> >> >> >> Help debugging this would be greatly appreciated. >> > >> > I looked some more into this today and saw that the hang is >> indeed caused >> > due to some kind of debug console going dead. The system >> was still looping in the >> > idle thread. I could even do a telnet remotely to my board and take >> > some debug dumps.. >> >> This might help you: > > Yup, this does help. There's no hang now either in idle or in suspend. Rajendra, Is CORE hitting retention for you? while UART wakeups are now working, CORE is still not hitting retention. Kevin > Not sure why this was affecting only the SDP while the pm branch seems > to function without this for beagle and other omap3 platforms? > >> >> diff --git a/arch/arm/mach-omap2/pm34xx.c >> b/arch/arm/mach-omap2/pm34xx.c >> index b2db0ba..266e4f5 100644 >> --- a/arch/arm/mach-omap2/pm34xx.c >> +++ b/arch/arm/mach-omap2/pm34xx.c >> @@ -401,6 +401,8 @@ void omap_sram_idle(void) >> omap3_prcm_restore_context(); >> omap3_sram_restore_context(); >> } >> + omap_uart_resume_idle(0); >> + omap_uart_resume_idle(1); >> if (core_next_state == PWRDM_POWER_OFF) >> prm_clear_mod_reg_bits(OMAP3430_AUTO_OFF, >> OMAP3430_GR_MOD, >> >> -- >> 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] 40+ messages in thread
* RE: new PM branch available 2009-01-23 17:48 ` Kevin Hilman @ 2009-01-27 9:18 ` Nayak, Rajendra 0 siblings, 0 replies; 40+ messages in thread From: Nayak, Rajendra @ 2009-01-27 9:18 UTC (permalink / raw) To: Kevin Hilman; +Cc: Högander Jouni, linux-omap@vger.kernel.org > -----Original Message----- > From: Kevin Hilman [mailto:khilman@deeprootsystems.com] > Sent: Friday, January 23, 2009 11:19 PM > To: Nayak, Rajendra > Cc: Högander Jouni; linux-omap@vger.kernel.org > Subject: Re: new PM branch available > > "Nayak, Rajendra" <rnayak@ti.com> writes: > > > > > > >> -----Original Message----- > >> From: Högander Jouni [mailto:jouni.hogander@nokia.com] > >> Sent: Friday, January 23, 2009 4:52 PM > >> To: Nayak, Rajendra > >> Cc: Kevin Hilman; linux-omap@vger.kernel.org > >> Subject: Re: new PM branch available > >> > >> "ext Nayak, Rajendra" <rnayak@ti.com> writes: > >> > >> >> I did some testing today on my 3.0GP 3430SDP. This is with > >> the omap_3430sdp_min_defconfig. > >> >> > >> >> 1) Idle. > >> >> echo -n 1 > /sys/power/clocks_off_while_idle > >> >> echo -n 1 > /sys/power/enable_off > >> >> Could not hit RET. something seems to be still active. Not > >> sure if it could be something > >> >> to do with this error that's thrown while bootup > >> >> > >> >> <6>Disabling unused clock "dpll5_ck" > >> >> Disabling unused clock "dpll5_ck" > >> >> <3>clock: dpll5_ck failed transition to 'locked' > >> >> clock: dpll5_ck failed transition to 'locked' > >> >> > >> >> This is the same results I see on my SDP. > >> >> > >> >> Looking at the registers, I am pretty sure it is the D2D > >> clockdomain > >> >> that still has activity, but due to very poor Stacked-mode > >> docs and no > >> >> responses to the D2D questions asked to TI I have not > been able to > >> >> figure this one out. > >> >> > >> >> Help debugging this would be greatly appreciated. > >> > > >> > I looked some more into this today and saw that the hang is > >> indeed caused > >> > due to some kind of debug console going dead. The system > >> was still looping in the > >> > idle thread. I could even do a telnet remotely to my > board and take > >> > some debug dumps.. > >> > >> This might help you: > > > > Yup, this does help. There's no hang now either in idle or > in suspend. > > Rajendra, > > Is CORE hitting retention for you? while UART wakeups are > now working, > CORE is still not hitting retention. > > Kevin Yes, like I said IVA seemed to have been keeping the system active after bootup. Looks like the errata implementation done as part of the omap3_iva_idle is needed only on silicon rev's 1.0 and 2.0. On my ES3.0 *not* doing that is helping me hit RET/OFF in idle and suspend. Not sure if this is an expected behaviour or some changes are needed in the errata fix sequence. I'll try finding out more on that. But for now, not doing the errata fix helps me hit CORE RET/OFF on my ES3.0SDP. > > > Not sure why this was affecting only the SDP while the pm > branch seems > > to function without this for beagle and other omap3 platforms? > > > >> > >> diff --git a/arch/arm/mach-omap2/pm34xx.c > >> b/arch/arm/mach-omap2/pm34xx.c > >> index b2db0ba..266e4f5 100644 > >> --- a/arch/arm/mach-omap2/pm34xx.c > >> +++ b/arch/arm/mach-omap2/pm34xx.c > >> @@ -401,6 +401,8 @@ void omap_sram_idle(void) > >> omap3_prcm_restore_context(); > >> omap3_sram_restore_context(); > >> } > >> + omap_uart_resume_idle(0); > >> + omap_uart_resume_idle(1); > >> if (core_next_state == PWRDM_POWER_OFF) > >> prm_clear_mod_reg_bits(OMAP3430_AUTO_OFF, > >> OMAP3430_GR_MOD, > >> > >> -- > >> 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] 40+ messages in thread
* Re: new PM branch available 2009-01-13 21:51 Kevin Hilman ` (3 preceding siblings ...) 2009-01-16 13:49 ` Nayak, Rajendra @ 2009-02-02 17:45 ` Peter 'p2' De Schrijver 2009-02-02 19:42 ` Kevin Hilman 4 siblings, 1 reply; 40+ messages in thread From: Peter 'p2' De Schrijver @ 2009-02-02 17:45 UTC (permalink / raw) To: ext Kevin Hilman; +Cc: linux-omap@vger.kernel.org Hi Kevin, > Hello, > > The latest PM branch is now available[1]. > > I've done basic testing of retention and off-mode (suspend and dynamic > idle) on Beagle and custom HW. My SDP has something still keeping > CORE active that others have not seen, but I have yet to debug. Any > other reports from SDP testing would be appreciated. > > Notable changes/updates > - rebased on latest clock updates and fixes from Paul > - clockfw pre- and post- notifiers > - DVFS for VDD2 > I tried it on a beagleboard last night, but couldn't get even static retention to work. Some domains (core, per, dss) stay on, but even mpu and neon don't go to retention. They only go to inactive. So could you send your .config file ? Which rootfs are you using, I'm using debian, so maybe something keeps the CPU busy. Are you using NAND or MMC to store your rootfs ? Which beagle HW rev do you have ? I'm testing on a B5 board. And which u-boot are you using ? Thanks, Peter. -- goa is a state of mind ^ permalink raw reply [flat|nested] 40+ messages in thread
* Re: new PM branch available 2009-02-02 17:45 ` Peter 'p2' De Schrijver @ 2009-02-02 19:42 ` Kevin Hilman 2009-02-02 20:06 ` Kevin Hilman 2009-02-04 0:52 ` Peter 'p2' De Schrijver 0 siblings, 2 replies; 40+ messages in thread From: Kevin Hilman @ 2009-02-02 19:42 UTC (permalink / raw) To: Peter 'p2' De Schrijver; +Cc: linux-omap@vger.kernel.org [-- Attachment #1: Type: text/plain, Size: 2075 bytes --] Hi Peter, "Peter 'p2' De Schrijver" <peter.de-schrijver@nokia.com> writes: > Hi Kevin, > >> Hello, >> >> The latest PM branch is now available[1]. >> >> I've done basic testing of retention and off-mode (suspend and dynamic >> idle) on Beagle and custom HW. My SDP has something still keeping >> CORE active that others have not seen, but I have yet to debug. Any >> other reports from SDP testing would be appreciated. >> >> Notable changes/updates >> - rebased on latest clock updates and fixes from Paul >> - clockfw pre- and post- notifiers >> - DVFS for VDD2 >> > > I tried it on a beagleboard last night, but couldn't get even static > retention to work. Some domains (core, per, dss) stay on, but even mpu > and neon don't go to retention. They only go to inactive. A first guess: this sounds like CONFIG_OMAP_RESET_CLOCKS=y is missing from your .config. The MPU/NEON going active but not RET is an indication to me that some fclk is active so that the fclk check in omap3_can_sleep() fails, so a WFI is never attempted. That's shy Personally, I'm thinking we should totally drop this fclk check. I see no reason not to attempt a WFI, even if there are active fclks. > So could you send your .config file ? Attached. > Which rootfs are you using, I'm using debian, so maybe something > keeps the CPU busy. Are you using NAND or MMC to store your rootfs ? I'm using rootfs on MMC and have tested with busybox-only, debian and OE rootfs. With debian and OE, I usually boot a minimal rootfs, before a full userland comes up. With debian, I changed my /etc/init.d/rcS to start initlevel 1 instead of 'S'. > Which beagle HW rev do you have ? I'm testing on a B5 board. I have a rev B4. > And which u-boot are you using ? I'm using the u-boot from Steve Sakoman's tree[1]. That helped a lot in my initial Beagle testing, but I think the kernel should reset the IVA and D2D now which is the domains that I was having problems with before, so I think that the out of the box u-boot should work fine. Kevin [1] http://elinux.org/BeagleBoard#U-Boot [-- Attachment #2: beagle.config --] [-- Type: text/plain, Size: 51690 bytes --] # # Automatically generated make config: don't edit # Linux kernel version: 2.6.28-omap1 # Mon Feb 2 11:17:18 2009 # 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_OPROFILE_ARMV7=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_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=y CONFIG_IKCONFIG_PROC=y 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 is not set CONFIG_HOTPLUG=y CONFIG_PRINTK=y CONFIG_BUG=y # CONFIG_ELF_CORE is not set # CONFIG_COMPAT_BRK is not set 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=y # CONFIG_MARKERS is not set CONFIG_OPROFILE=y 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=y CONFIG_MODVERSIONS=y CONFIG_MODULE_SRCVERSION_ALL=y CONFIG_KMOD=y CONFIG_BLOCK=y CONFIG_LBD=y # CONFIG_BLK_DEV_IO_TRACE is not set CONFIG_LSF=y # 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 is not set # CONFIG_DEFAULT_DEADLINE is not set CONFIG_DEFAULT_CFQ=y # CONFIG_DEFAULT_NOOP is not set CONFIG_DEFAULT_IOSCHED="cfq" CONFIG_CLASSIC_RCU=y CONFIG_FREEZER=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_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=y # CONFIG_OMAP_SMARTREFLEX_TESTING 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=y # 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_TICK_GPTIMER=12 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 is not set CONFIG_OMAP_PM_SRF=y 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=y # CONFIG_MACH_OVERO is not set # CONFIG_MACH_OMAP3_PANDORA is not set # # 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=y # 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 is not set CONFIG_HZ=128 CONFIG_AEABI=y # CONFIG_OABI_COMPAT is not set 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=y CONFIG_ALIGNMENT_TRAP=y # # Boot options # CONFIG_ZBOOT_ROM_TEXT=0x0 CONFIG_ZBOOT_ROM_BSS=0x0 CONFIG_CMDLINE=" debug " # CONFIG_XIP_KERNEL is not set CONFIG_KEXEC=y CONFIG_ATAGS_PROC=y # # CPU Power Management # CONFIG_CPU_FREQ=y CONFIG_CPU_FREQ_TABLE=y CONFIG_CPU_FREQ_DEBUG=y CONFIG_CPU_FREQ_STAT=y CONFIG_CPU_FREQ_STAT_DETAILS=y CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y # CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set CONFIG_CPU_FREQ_GOV_PERFORMANCE=y CONFIG_CPU_FREQ_GOV_POWERSAVE=y CONFIG_CPU_FREQ_GOV_USERSPACE=y CONFIG_CPU_FREQ_GOV_ONDEMAND=y CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y CONFIG_CPU_IDLE=y CONFIG_CPU_IDLE_GOV_LADDER=y CONFIG_CPU_IDLE_GOV_MENU=y # # Floating point emulation # # # At least one emulation must be selected # CONFIG_VFP=y CONFIG_VFPv3=y CONFIG_NEON=y # # 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_CAN_PM_TRACE=y CONFIG_PM_SLEEP=y CONFIG_SUSPEND=y # CONFIG_PM_TEST_SUSPEND is not set CONFIG_SUSPEND_FREEZER=y # CONFIG_APM_EMULATION is not set CONFIG_ARCH_SUSPEND_POSSIBLE=y CONFIG_NET=y # # Networking options # CONFIG_PACKET=y CONFIG_PACKET_MMAP=y 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=m 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=m # CONFIG_IPV6_PRIVACY is not set # CONFIG_IPV6_ROUTER_PREF is not set # CONFIG_IPV6_OPTIMISTIC_DAD is not set # CONFIG_INET6_AH is not set # CONFIG_INET6_ESP is not set # CONFIG_INET6_IPCOMP is not set # CONFIG_IPV6_MIP6 is not set # CONFIG_INET6_XFRM_TUNNEL is not set # CONFIG_INET6_TUNNEL is not set CONFIG_INET6_XFRM_MODE_TRANSPORT=m CONFIG_INET6_XFRM_MODE_TUNNEL=m CONFIG_INET6_XFRM_MODE_BEET=m # CONFIG_INET6_XFRM_MODE_ROUTEOPTIMIZATION is not set CONFIG_IPV6_SIT=m CONFIG_IPV6_NDISC_NODETYPE=y # CONFIG_IPV6_TUNNEL is not set # CONFIG_IPV6_MULTIPLE_TABLES is not set # CONFIG_IPV6_MROUTE 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=y CONFIG_BT_L2CAP=y CONFIG_BT_SCO=y CONFIG_BT_RFCOMM=y CONFIG_BT_RFCOMM_TTY=y CONFIG_BT_BNEP=y CONFIG_BT_BNEP_MC_FILTER=y CONFIG_BT_BNEP_PROTO_FILTER=y CONFIG_BT_HIDP=y # # Bluetooth device drivers # CONFIG_BT_HCIUSB=m CONFIG_BT_HCIUSB_SCO=y # CONFIG_BT_HCIBTUSB is not set CONFIG_BT_HCIBTSDIO=y # CONFIG_BT_HCIUART is not set CONFIG_BT_HCIBCM203X=m CONFIG_BT_HCIBPA10X=m # CONFIG_BT_HCIBFUSB is not set # CONFIG_BT_HCIBRF6150 is not set # CONFIG_BT_HCIH4P is not set # CONFIG_BT_HCIVHCI is not set # CONFIG_AF_RXRPC is not set # CONFIG_PHONET is not set CONFIG_WIRELESS=y CONFIG_CFG80211=y CONFIG_NL80211=y CONFIG_WIRELESS_OLD_REGULATORY=y CONFIG_WIRELESS_EXT=y CONFIG_WIRELESS_EXT_SYSFS=y CONFIG_MAC80211=y # # Rate control algorithm selection # CONFIG_MAC80211_RC_PID=y # CONFIG_MAC80211_RC_MINSTREL is not set CONFIG_MAC80211_RC_DEFAULT_PID=y # CONFIG_MAC80211_RC_DEFAULT_MINSTREL is not set CONFIG_MAC80211_RC_DEFAULT="pid" # CONFIG_MAC80211_MESH is not set CONFIG_MAC80211_LEDS=y # CONFIG_MAC80211_DEBUGFS is not set # CONFIG_MAC80211_DEBUG_MENU is not set CONFIG_IEEE80211=y # CONFIG_IEEE80211_DEBUG is not set CONFIG_IEEE80211_CRYPT_WEP=y CONFIG_IEEE80211_CRYPT_CCMP=y CONFIG_IEEE80211_CRYPT_TKIP=y # 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=y CONFIG_FIRMWARE_IN_KERNEL=y CONFIG_EXTRA_FIRMWARE="" # 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=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 is not set # 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 is not set # CONFIG_MTD_JEDECPROBE 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_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_PLATRAM is not set # # Self-contained MTD device drivers # # CONFIG_MTD_DATAFLASH is not set # CONFIG_MTD_M25P80 is not set # 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=y # CONFIG_MTD_NAND_VERIFY_WRITE is not set # CONFIG_MTD_NAND_ECC_SMC is not set # CONFIG_MTD_NAND_MUSEUM_IDS is not set # CONFIG_MTD_NAND_GPIO is not set CONFIG_MTD_NAND_OMAP2=y CONFIG_MTD_NAND_IDS=y # CONFIG_MTD_NAND_DISKONCHIP is not set # CONFIG_MTD_NAND_NANDSIM is not set CONFIG_MTD_NAND_PLATFORM=y # CONFIG_MTD_ALAUDA is not set # CONFIG_MTD_ONENAND is not set # # UBI - Unsorted block images # CONFIG_MTD_UBI=y CONFIG_MTD_UBI_WL_THRESHOLD=4096 CONFIG_MTD_UBI_BEB_RESERVE=1 # CONFIG_MTD_UBI_GLUEBI is not set # # UBI debugging options # # CONFIG_MTD_UBI_DEBUG 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=m # CONFIG_BLK_DEV_NBD is not set # CONFIG_BLK_DEV_UB 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=m CONFIG_CDROM_PKTCDVD_BUFFERS=8 # CONFIG_CDROM_PKTCDVD_WCACHE is not set # CONFIG_ATA_OVER_ETH is not set CONFIG_MISC_DEVICES=y CONFIG_EEPROM_93CX6=y # CONFIG_ICS932S401 is not set # CONFIG_OMAP_STI is not set # CONFIG_ENCLOSURE_SERVICES is not set # CONFIG_C2PORT is not set CONFIG_HAVE_IDE=y # CONFIG_IDE is not set # # SCSI device support # CONFIG_RAID_ATTRS=m 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=y CONFIG_BLK_DEV_SR_VENDOR=y CONFIG_CHR_DEV_SG=y CONFIG_CHR_DEV_SCH=m # # Some SCSI devices (e.g. CD jukebox) support multiple LUNs # CONFIG_SCSI_MULTI_LUN=y # 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=m # CONFIG_SCSI_SAS_LIBSAS is not set # CONFIG_SCSI_SRP_ATTRS is not set CONFIG_SCSI_LOWLEVEL=y CONFIG_ISCSI_TCP=m # CONFIG_SCSI_DEBUG is not set # CONFIG_SCSI_DH is not set # CONFIG_ATA is not set CONFIG_MD=y CONFIG_BLK_DEV_MD=m CONFIG_MD_LINEAR=m CONFIG_MD_RAID0=m CONFIG_MD_RAID1=m CONFIG_MD_RAID10=m CONFIG_MD_RAID456=m CONFIG_MD_RAID5_RESHAPE=y CONFIG_MD_MULTIPATH=m CONFIG_MD_FAULTY=m CONFIG_BLK_DEV_DM=m # CONFIG_DM_DEBUG is not set CONFIG_DM_CRYPT=m CONFIG_DM_SNAPSHOT=m CONFIG_DM_MIRROR=m CONFIG_DM_ZERO=m CONFIG_DM_MULTIPATH=m CONFIG_DM_DELAY=m # CONFIG_DM_UEVENT is not set CONFIG_NETDEVICES=y CONFIG_DUMMY=m # CONFIG_BONDING is not set # CONFIG_MACVLAN is not set # CONFIG_EQUALIZER is not set CONFIG_TUN=m # CONFIG_VETH is not set # CONFIG_NET_ETHERNET is not set CONFIG_MII=m # CONFIG_NETDEV_1000 is not set # CONFIG_NETDEV_10000 is not set # # Wireless LAN # # CONFIG_WLAN_PRE80211 is not set CONFIG_WLAN_80211=y CONFIG_LIBERTAS=y CONFIG_LIBERTAS_USB=m # CONFIG_LIBERTAS_SDIO is not set # CONFIG_LIBERTAS_DEBUG is not set # CONFIG_LIBERTAS_THINFIRM is not set CONFIG_USB_ZD1201=m CONFIG_USB_NET_RNDIS_WLAN=m CONFIG_RTL8187=m # CONFIG_MAC80211_HWSIM is not set CONFIG_P54_COMMON=y CONFIG_P54_USB=m # CONFIG_IWLWIFI_LEDS is not set CONFIG_HOSTAP=y CONFIG_HOSTAP_FIRMWARE=y CONFIG_HOSTAP_FIRMWARE_NVRAM=y # CONFIG_B43 is not set # CONFIG_B43LEGACY is not set CONFIG_ZD1211RW=m # CONFIG_ZD1211RW_DEBUG is not set CONFIG_RT2X00=y CONFIG_RT2500USB=m CONFIG_RT73USB=m CONFIG_RT2X00_LIB_USB=m CONFIG_RT2X00_LIB=m CONFIG_RT2X00_LIB_FIRMWARE=y CONFIG_RT2X00_LIB_CRYPTO=y CONFIG_RT2X00_LIB_LEDS=y # CONFIG_RT2X00_DEBUG is not set # # USB Network Adapters # CONFIG_USB_CATC=m CONFIG_USB_KAWETH=m CONFIG_USB_PEGASUS=m CONFIG_USB_RTL8150=m CONFIG_USB_USBNET=m CONFIG_USB_NET_AX8817X=m CONFIG_USB_NET_CDCETHER=m CONFIG_USB_NET_DM9601=m # CONFIG_USB_NET_SMSC95XX is not set CONFIG_USB_NET_GL620A=m CONFIG_USB_NET_NET1080=m CONFIG_USB_NET_PLUSB=m CONFIG_USB_NET_MCS7830=m CONFIG_USB_NET_RNDIS_HOST=m CONFIG_USB_NET_CDC_SUBSET=m CONFIG_USB_ALI_M5632=y CONFIG_USB_AN2720=y CONFIG_USB_BELKIN=y CONFIG_USB_ARMLINUX=y CONFIG_USB_EPSON2888=y CONFIG_USB_KC2190=y CONFIG_USB_NET_ZAURUS=m # CONFIG_WAN is not set CONFIG_PPP=m CONFIG_PPP_MULTILINK=y CONFIG_PPP_FILTER=y CONFIG_PPP_ASYNC=m CONFIG_PPP_SYNC_TTY=m CONFIG_PPP_DEFLATE=m CONFIG_PPP_BSDCOMP=m CONFIG_PPP_MPPE=m CONFIG_PPPOE=m CONFIG_PPPOL2TP=m # CONFIG_SLIP is not set CONFIG_SLHC=m # CONFIG_NETCONSOLE is not set # CONFIG_NETPOLL is not set # CONFIG_NET_POLL_CONTROLLER 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=y CONFIG_INPUT_MOUSEDEV_PSAUX=y CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024 CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768 # CONFIG_INPUT_JOYDEV is not set CONFIG_INPUT_EVDEV=y # CONFIG_INPUT_EVBUG is not set # # Input Device Drivers # CONFIG_INPUT_KEYBOARD=y # CONFIG_KEYBOARD_ATKBD is not set # CONFIG_KEYBOARD_SUNKBD is not set # CONFIG_KEYBOARD_LKKBD is not set # CONFIG_KEYBOARD_XTKBD is not set # CONFIG_KEYBOARD_NEWTON is not set # CONFIG_KEYBOARD_STOWAWAY is not set # CONFIG_KEYBOARD_TWL4030 is not set # CONFIG_KEYBOARD_LM8323 is not set CONFIG_KEYBOARD_GPIO=y CONFIG_INPUT_MOUSE=y CONFIG_MOUSE_PS2=y CONFIG_MOUSE_PS2_ALPS=y CONFIG_MOUSE_PS2_LOGIPS2PP=y CONFIG_MOUSE_PS2_SYNAPTICS=y CONFIG_MOUSE_PS2_LIFEBOOK=y CONFIG_MOUSE_PS2_TRACKPOINT=y # CONFIG_MOUSE_PS2_ELANTECH is not set # CONFIG_MOUSE_PS2_TOUCHKIT is not set # CONFIG_MOUSE_SERIAL is not set # CONFIG_MOUSE_APPLETOUCH is not set # CONFIG_MOUSE_BCM5974 is not set # CONFIG_MOUSE_VSXXXAA is not set # CONFIG_MOUSE_GPIO 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=y CONFIG_SERIO_SERPORT=y CONFIG_SERIO_LIBPS2=y # CONFIG_SERIO_RAW 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=y 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=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 # CONFIG_I2C_TINY_USB 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=y # CONFIG_SENSORS_PCF8574 is not set # CONFIG_PCF8575 is not set # CONFIG_SENSORS_PCA9539 is not set # CONFIG_SENSORS_PCF8591 is not set # CONFIG_TPS65010 is not set CONFIG_TWL4030_MADC=m CONFIG_TWL4030_PWRBUTTON=y CONFIG_TWL4030_POWEROFF=y # CONFIG_SENSORS_MAX6875 is not set # CONFIG_SENSORS_TSL2550 is not set # CONFIG_SENSORS_TSL2563 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=y # CONFIG_SPI_DEBUG is not set CONFIG_SPI_MASTER=y # # SPI Master Controller Drivers # # CONFIG_SPI_BITBANG is not set # CONFIG_SPI_OMAP24XX is not set # # SPI Protocol Masters # # CONFIG_SPI_AT25 is not set # CONFIG_SPI_TSC210X is not set # CONFIG_SPI_TSC2301 is not set # CONFIG_SPI_SPIDEV is not set # CONFIG_SPI_TLE62X0 is not set CONFIG_ARCH_REQUIRE_GPIOLIB=y CONFIG_GPIOLIB=y # CONFIG_DEBUG_GPIO is not set CONFIG_GPIO_SYSFS=y # # 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_GPIO_MAX7301 is not set # CONFIG_GPIO_MCP23S08 is not set # CONFIG_W1 is not set CONFIG_POWER_SUPPLY=m # CONFIG_POWER_SUPPLY_DEBUG is not set # CONFIG_PDA_POWER is not set # CONFIG_BATTERY_DS2760 is not set # CONFIG_TWL4030_BCI_BATTERY is not set # CONFIG_BATTERY_BQ27x00 is not set CONFIG_HWMON=y # CONFIG_HWMON_VID is not set # CONFIG_SENSORS_AD7414 is not set # CONFIG_SENSORS_AD7418 is not set # CONFIG_SENSORS_ADCXX is not set # CONFIG_SENSORS_ADM1021 is not set # CONFIG_SENSORS_ADM1025 is not set # CONFIG_SENSORS_ADM1026 is not set # CONFIG_SENSORS_ADM1029 is not set # CONFIG_SENSORS_ADM1031 is not set # CONFIG_SENSORS_ADM9240 is not set # CONFIG_SENSORS_ADT7462 is not set # CONFIG_SENSORS_ADT7470 is not set # CONFIG_SENSORS_ADT7473 is not set # CONFIG_SENSORS_ATXP1 is not set # CONFIG_SENSORS_DS1621 is not set # CONFIG_SENSORS_F71805F is not set # CONFIG_SENSORS_F71882FG is not set # CONFIG_SENSORS_F75375S is not set # CONFIG_SENSORS_GL518SM is not set # CONFIG_SENSORS_GL520SM is not set # CONFIG_SENSORS_IT87 is not set # CONFIG_SENSORS_LM63 is not set # CONFIG_SENSORS_LM70 is not set # CONFIG_SENSORS_LM75 is not set # CONFIG_SENSORS_LM77 is not set # CONFIG_SENSORS_LM78 is not set # CONFIG_SENSORS_LM80 is not set # CONFIG_SENSORS_LM83 is not set # CONFIG_SENSORS_LM85 is not set # CONFIG_SENSORS_LM87 is not set # CONFIG_SENSORS_LM90 is not set # CONFIG_SENSORS_LM92 is not set # CONFIG_SENSORS_LM93 is not set # CONFIG_SENSORS_MAX1111 is not set # CONFIG_SENSORS_MAX1619 is not set # CONFIG_SENSORS_MAX6650 is not set # CONFIG_SENSORS_PC87360 is not set # CONFIG_SENSORS_PC87427 is not set # CONFIG_SENSORS_DME1737 is not set # CONFIG_SENSORS_SMSC47M1 is not set # CONFIG_SENSORS_SMSC47M192 is not set # CONFIG_SENSORS_SMSC47B397 is not set # CONFIG_SENSORS_ADS7828 is not set # CONFIG_SENSORS_THMC50 is not set # CONFIG_SENSORS_VT1211 is not set # CONFIG_SENSORS_W83781D is not set # CONFIG_SENSORS_W83791D is not set # CONFIG_SENSORS_W83792D is not set # CONFIG_SENSORS_W83793 is not set # CONFIG_SENSORS_W83L785TS is not set # CONFIG_SENSORS_W83L786NG is not set # CONFIG_SENSORS_W83627HF is not set # CONFIG_SENSORS_W83627EHF is not set # CONFIG_SENSORS_TSC210X is not set CONFIG_SENSORS_OMAP34XX=y # CONFIG_HWMON_DEBUG_CHIP is not set # CONFIG_THERMAL is not set # CONFIG_THERMAL_HWMON is not set CONFIG_WATCHDOG=y CONFIG_WATCHDOG_NOWAYOUT=y # # Watchdog Device Drivers # # CONFIG_SOFT_WATCHDOG is not set CONFIG_OMAP_WATCHDOG=y # # USB-based Watchdog Cards # # CONFIG_USBPCWATCHDOG 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=m CONFIG_VIDEO_V4L2_COMMON=m CONFIG_VIDEO_ALLOW_V4L1=y CONFIG_VIDEO_V4L1_COMPAT=y CONFIG_DVB_CORE=m CONFIG_VIDEO_MEDIA=m # # Multimedia drivers # CONFIG_MEDIA_ATTACH=y CONFIG_MEDIA_TUNER=m # CONFIG_MEDIA_TUNER_CUSTOMIZE is not set CONFIG_MEDIA_TUNER_SIMPLE=m CONFIG_MEDIA_TUNER_TDA8290=m CONFIG_MEDIA_TUNER_TDA827X=m CONFIG_MEDIA_TUNER_TDA18271=m CONFIG_MEDIA_TUNER_TDA9887=m CONFIG_MEDIA_TUNER_TEA5761=m CONFIG_MEDIA_TUNER_TEA5767=m CONFIG_MEDIA_TUNER_MT20XX=m CONFIG_MEDIA_TUNER_MT2060=m CONFIG_MEDIA_TUNER_MT2266=m CONFIG_MEDIA_TUNER_QT1010=m CONFIG_MEDIA_TUNER_XC2028=m CONFIG_MEDIA_TUNER_XC5000=m CONFIG_MEDIA_TUNER_MXL5005S=m CONFIG_VIDEO_V4L2=m CONFIG_VIDEO_V4L1=m CONFIG_VIDEO_TVEEPROM=m CONFIG_VIDEO_TUNER=m CONFIG_VIDEO_CAPTURE_DRIVERS=y # CONFIG_VIDEO_ADV_DEBUG is not set # CONFIG_VIDEO_FIXED_MINOR_RANGES is not set CONFIG_VIDEO_HELPER_CHIPS_AUTO=y CONFIG_VIDEO_MSP3400=m CONFIG_VIDEO_CS53L32A=m CONFIG_VIDEO_WM8775=m CONFIG_VIDEO_SAA711X=m CONFIG_VIDEO_CX25840=m CONFIG_VIDEO_CX2341X=m # CONFIG_VIDEO_VIVI is not set # CONFIG_VIDEO_CPIA is not set # CONFIG_VIDEO_CPIA2 is not set # CONFIG_VIDEO_SAA5246A is not set # CONFIG_VIDEO_SAA5249 is not set # CONFIG_VIDEO_AU0828 is not set # CONFIG_SOC_CAMERA is not set CONFIG_V4L_USB_DRIVERS=y CONFIG_USB_VIDEO_CLASS=m CONFIG_USB_VIDEO_CLASS_INPUT_EVDEV=y CONFIG_USB_GSPCA=m CONFIG_USB_M5602=m CONFIG_USB_GSPCA_CONEX=m CONFIG_USB_GSPCA_ETOMS=m CONFIG_USB_GSPCA_FINEPIX=m CONFIG_USB_GSPCA_MARS=m CONFIG_USB_GSPCA_OV519=m CONFIG_USB_GSPCA_PAC207=m CONFIG_USB_GSPCA_PAC7311=m CONFIG_USB_GSPCA_SONIXB=m CONFIG_USB_GSPCA_SONIXJ=m CONFIG_USB_GSPCA_SPCA500=m CONFIG_USB_GSPCA_SPCA501=m CONFIG_USB_GSPCA_SPCA505=m CONFIG_USB_GSPCA_SPCA506=m CONFIG_USB_GSPCA_SPCA508=m CONFIG_USB_GSPCA_SPCA561=m CONFIG_USB_GSPCA_STK014=m CONFIG_USB_GSPCA_SUNPLUS=m CONFIG_USB_GSPCA_T613=m CONFIG_USB_GSPCA_TV8532=m CONFIG_USB_GSPCA_VC032X=m CONFIG_USB_GSPCA_ZC3XX=m CONFIG_VIDEO_PVRUSB2=m CONFIG_VIDEO_PVRUSB2_SYSFS=y CONFIG_VIDEO_PVRUSB2_DVB=y # CONFIG_VIDEO_PVRUSB2_DEBUGIFC is not set # CONFIG_VIDEO_EM28XX is not set CONFIG_VIDEO_USBVISION=m CONFIG_VIDEO_USBVIDEO=m CONFIG_USB_VICAM=m CONFIG_USB_IBMCAM=m CONFIG_USB_KONICAWC=m CONFIG_USB_QUICKCAM_MESSENGER=m # CONFIG_USB_ET61X251 is not set CONFIG_VIDEO_OVCAMCHIP=m CONFIG_USB_W9968CF=m CONFIG_USB_OV511=m CONFIG_USB_SE401=m CONFIG_USB_SN9C102=m CONFIG_USB_STV680=m # CONFIG_USB_ZC0301 is not set CONFIG_USB_PWC=m # CONFIG_USB_PWC_DEBUG is not set CONFIG_USB_ZR364XX=m # CONFIG_USB_STKWEBCAM is not set # CONFIG_USB_S2255 is not set CONFIG_RADIO_ADAPTERS=y # CONFIG_USB_DSBR is not set # CONFIG_USB_SI470X is not set # CONFIG_USB_MR800 is not set CONFIG_DVB_CAPTURE_DRIVERS=y # CONFIG_TTPCI_EEPROM is not set # # Supported USB Adapters # CONFIG_DVB_USB=m # CONFIG_DVB_USB_DEBUG is not set CONFIG_DVB_USB_A800=m CONFIG_DVB_USB_DIBUSB_MB=m # CONFIG_DVB_USB_DIBUSB_MB_FAULTY is not set CONFIG_DVB_USB_DIBUSB_MC=m CONFIG_DVB_USB_DIB0700=m CONFIG_DVB_USB_UMT_010=m CONFIG_DVB_USB_CXUSB=m CONFIG_DVB_USB_M920X=m CONFIG_DVB_USB_GL861=m CONFIG_DVB_USB_AU6610=m CONFIG_DVB_USB_DIGITV=m CONFIG_DVB_USB_VP7045=m CONFIG_DVB_USB_VP702X=m CONFIG_DVB_USB_GP8PSK=m CONFIG_DVB_USB_NOVA_T_USB2=m CONFIG_DVB_USB_TTUSB2=m CONFIG_DVB_USB_DTT200U=m CONFIG_DVB_USB_OPERA1=m CONFIG_DVB_USB_AF9005=m CONFIG_DVB_USB_AF9005_REMOTE=m CONFIG_DVB_USB_DW2102=m CONFIG_DVB_USB_CINERGY_T2=m CONFIG_DVB_USB_ANYSEE=m CONFIG_DVB_USB_DTV5100=m CONFIG_DVB_USB_AF9015=m CONFIG_DVB_TTUSB_BUDGET=m CONFIG_DVB_TTUSB_DEC=m CONFIG_DVB_SIANO_SMS1XXX=m CONFIG_DVB_SIANO_SMS1XXX_SMS_IDS=y # # Supported FlexCopII (B2C2) Adapters # # CONFIG_DVB_B2C2_FLEXCOP is not set # # Supported DVB Frontends # # # Customise DVB Frontends # # CONFIG_DVB_FE_CUSTOMISE is not set # # DVB-S (satellite) frontends # CONFIG_DVB_CX24110=m CONFIG_DVB_CX24123=m CONFIG_DVB_MT312=m CONFIG_DVB_S5H1420=m CONFIG_DVB_STV0288=m CONFIG_DVB_STB6000=m CONFIG_DVB_STV0299=m CONFIG_DVB_TDA8083=m CONFIG_DVB_TDA10086=m CONFIG_DVB_VES1X93=m CONFIG_DVB_TUNER_ITD1000=m CONFIG_DVB_TDA826X=m CONFIG_DVB_TUA6100=m CONFIG_DVB_CX24116=m CONFIG_DVB_SI21XX=m # # DVB-T (terrestrial) frontends # CONFIG_DVB_SP8870=m CONFIG_DVB_SP887X=m CONFIG_DVB_CX22700=m CONFIG_DVB_CX22702=m # CONFIG_DVB_DRX397XD is not set CONFIG_DVB_L64781=m CONFIG_DVB_TDA1004X=m CONFIG_DVB_NXT6000=m CONFIG_DVB_MT352=m CONFIG_DVB_ZL10353=m CONFIG_DVB_DIB3000MB=m CONFIG_DVB_DIB3000MC=m CONFIG_DVB_DIB7000M=m CONFIG_DVB_DIB7000P=m CONFIG_DVB_TDA10048=m # # DVB-C (cable) frontends # CONFIG_DVB_VES1820=m CONFIG_DVB_TDA10021=m CONFIG_DVB_TDA10023=m CONFIG_DVB_STV0297=m # # ATSC (North American/Korean Terrestrial/Cable DTV) frontends # CONFIG_DVB_NXT200X=m # CONFIG_DVB_OR51211 is not set # CONFIG_DVB_OR51132 is not set CONFIG_DVB_BCM3510=m CONFIG_DVB_LGDT330X=m CONFIG_DVB_S5H1409=m CONFIG_DVB_AU8522=m CONFIG_DVB_S5H1411=m # # Digital terrestrial only tuners/PLL # CONFIG_DVB_PLL=m CONFIG_DVB_TUNER_DIB0070=m # # SEC control devices for DVB-S # CONFIG_DVB_LNBP21=m # CONFIG_DVB_ISL6405 is not set CONFIG_DVB_ISL6421=m # CONFIG_DVB_LGS8GL5 is not set # # Tools to develop new frontends # # CONFIG_DVB_DUMMY_FE is not set CONFIG_DVB_AF9013=m # CONFIG_DAB is not set # # Graphics support # # CONFIG_VGASTATE is not set # CONFIG_VIDEO_OUTPUT_CONTROL is not set CONFIG_FB=y # CONFIG_FIRMWARE_EDID is not set # CONFIG_FB_DDC is not set # CONFIG_FB_BOOT_VESA_SUPPORT is not set CONFIG_FB_CFB_FILLRECT=y CONFIG_FB_CFB_COPYAREA=y CONFIG_FB_CFB_IMAGEBLIT=y # CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set # CONFIG_FB_SYS_FILLRECT is not set # CONFIG_FB_SYS_COPYAREA is not set # CONFIG_FB_SYS_IMAGEBLIT is not set # CONFIG_FB_FOREIGN_ENDIAN is not set # CONFIG_FB_SYS_FOPS is not set # CONFIG_FB_SVGALIB is not set # CONFIG_FB_MACMODES is not set # CONFIG_FB_BACKLIGHT is not set # CONFIG_FB_MODE_HELPERS is not set # CONFIG_FB_TILEBLITTING is not set # # Frame buffer hardware drivers # # CONFIG_FB_S1D13XXX is not set # CONFIG_FB_VIRTUAL is not set # CONFIG_FB_METRONOME is not set # CONFIG_FB_MB862XX is not set CONFIG_FB_OMAP=y # CONFIG_FB_OMAP_LCDC_EXTERNAL is not set # CONFIG_FB_OMAP_BOOTLOADER_INIT is not set CONFIG_FB_OMAP_CONSISTENT_DMA_SIZE=2 # CONFIG_BACKLIGHT_LCD_SUPPORT is not set # # Display device support # CONFIG_DISPLAY_SUPPORT=y # # Display hardware drivers # # # Console display driver support # # CONFIG_VGA_CONSOLE is not set CONFIG_DUMMY_CONSOLE=y CONFIG_FRAMEBUFFER_CONSOLE=y # CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY is not set CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y # CONFIG_FONTS is not set CONFIG_FONT_8x8=y CONFIG_FONT_8x16=y CONFIG_LOGO=y CONFIG_LOGO_LINUX_MONO=y CONFIG_LOGO_LINUX_VGA16=y CONFIG_LOGO_LINUX_CLUT224=y CONFIG_SOUND=y CONFIG_SOUND_OSS_CORE=y CONFIG_SND=y CONFIG_SND_TIMER=y CONFIG_SND_PCM=y CONFIG_SND_HWDEP=m CONFIG_SND_RAWMIDI=m CONFIG_SND_SEQUENCER=m # CONFIG_SND_SEQ_DUMMY is not set CONFIG_SND_OSSEMUL=y CONFIG_SND_MIXER_OSS=y CONFIG_SND_PCM_OSS=y CONFIG_SND_PCM_OSS_PLUGINS=y CONFIG_SND_SEQUENCER_OSS=y # CONFIG_SND_DYNAMIC_MINORS is not set CONFIG_SND_SUPPORT_OLD_API=y CONFIG_SND_VERBOSE_PROCFS=y # CONFIG_SND_VERBOSE_PRINTK is not set # CONFIG_SND_DEBUG is not set CONFIG_SND_DRIVERS=y # CONFIG_SND_DUMMY is not set # CONFIG_SND_VIRMIDI is not set # CONFIG_SND_MTPAV is not set # CONFIG_SND_SERIAL_U16550 is not set # CONFIG_SND_MPU401 is not set CONFIG_SND_ARM=y CONFIG_SND_SPI=y CONFIG_SND_USB=y CONFIG_SND_USB_AUDIO=m CONFIG_SND_USB_CAIAQ=m CONFIG_SND_USB_CAIAQ_INPUT=y CONFIG_SND_SOC=y CONFIG_SND_OMAP_SOC=y CONFIG_SND_OMAP_SOC_MCBSP=y CONFIG_SND_OMAP_SOC_OMAP3_BEAGLE=y # CONFIG_SND_SOC_ALL_CODECS is not set CONFIG_SND_SOC_TWL4030=y # CONFIG_SOUND_PRIME is not set CONFIG_HID_SUPPORT=y CONFIG_HID=y CONFIG_HID_DEBUG=y # CONFIG_HIDRAW is not set # # USB Input Devices # CONFIG_USB_HID=m # CONFIG_HID_PID is not set # CONFIG_USB_HIDDEV is not set # # USB HID Boot Protocol drivers # # CONFIG_USB_KBD is not set # CONFIG_USB_MOUSE is not set # # Special HID drivers # CONFIG_HID_COMPAT=y CONFIG_HID_A4TECH=m CONFIG_HID_APPLE=y CONFIG_HID_BELKIN=m CONFIG_HID_BRIGHT=m CONFIG_HID_CHERRY=m CONFIG_HID_CHICONY=m CONFIG_HID_CYPRESS=m CONFIG_HID_DELL=m CONFIG_HID_EZKEY=m CONFIG_HID_GYRATION=m CONFIG_HID_LOGITECH=m # CONFIG_LOGITECH_FF is not set # CONFIG_LOGIRUMBLEPAD2_FF is not set CONFIG_HID_MICROSOFT=m CONFIG_HID_MONTEREY=m CONFIG_HID_PANTHERLORD=m # CONFIG_PANTHERLORD_FF is not set CONFIG_HID_PETALYNX=m CONFIG_HID_SAMSUNG=m CONFIG_HID_SONY=m CONFIG_HID_SUNPLUS=m # CONFIG_THRUSTMASTER_FF is not set # CONFIG_ZEROPLUS_FF is not set CONFIG_USB_SUPPORT=y CONFIG_USB_ARCH_HAS_HCD=y CONFIG_USB_ARCH_HAS_OHCI=y CONFIG_USB_ARCH_HAS_EHCI=y CONFIG_USB=y # CONFIG_USB_DEBUG is not set # CONFIG_USB_ANNOUNCE_NEW_DEVICES is not set # # Miscellaneous USB options # CONFIG_USB_DEVICEFS=y CONFIG_USB_DEVICE_CLASS=y # CONFIG_USB_DYNAMIC_MINORS is not set CONFIG_USB_SUSPEND=y CONFIG_USB_OTG=y # CONFIG_USB_OTG_WHITELIST is not set # CONFIG_USB_OTG_BLACKLIST_HUB is not set CONFIG_USB_MON=y # CONFIG_USB_WUSB is not set # CONFIG_USB_WUSB_CBAF is not set # # USB Host Controller Drivers # # CONFIG_USB_C67X00_HCD is not set CONFIG_USB_EHCI_HCD=m CONFIG_OMAP_EHCI_PHY_MODE=y # CONFIG_OMAP_EHCI_TLL_MODE is not set CONFIG_USB_EHCI_ROOT_HUB_TT=y # CONFIG_USB_EHCI_TT_NEWSCHED is not set # CONFIG_USB_ISP116X_HCD is not set # CONFIG_USB_OHCI_HCD is not set # CONFIG_USB_SL811_HCD is not set # CONFIG_USB_R8A66597_HCD is not set # CONFIG_USB_HWA_HCD is not set CONFIG_USB_MUSB_HDRC=y CONFIG_USB_MUSB_SOC=y # # OMAP 343x high speed USB support # # CONFIG_USB_MUSB_HOST is not set # CONFIG_USB_MUSB_PERIPHERAL is not set CONFIG_USB_MUSB_OTG=y CONFIG_USB_GADGET_MUSB_HDRC=y CONFIG_USB_MUSB_HDRC_HCD=y # CONFIG_MUSB_PIO_ONLY is not set CONFIG_USB_INVENTRA_DMA=y # CONFIG_USB_TI_CPPI_DMA is not set # CONFIG_USB_MUSB_DEBUG is not set # # USB Device Class drivers # CONFIG_USB_ACM=m CONFIG_USB_PRINTER=m CONFIG_USB_WDM=m # CONFIG_USB_TMC is not set # # NOTE: USB_STORAGE depends on SCSI but BLK_DEV_SD may also be needed; # # # see USB_STORAGE Help for more information # CONFIG_USB_STORAGE=m # CONFIG_USB_STORAGE_DEBUG is not set # CONFIG_USB_STORAGE_DATAFAB is not set # CONFIG_USB_STORAGE_FREECOM is not set # CONFIG_USB_STORAGE_ISD200 is not set # CONFIG_USB_STORAGE_DPCM is not set # CONFIG_USB_STORAGE_USBAT is not set # CONFIG_USB_STORAGE_SDDR09 is not set # CONFIG_USB_STORAGE_SDDR55 is not set # CONFIG_USB_STORAGE_JUMPSHOT is not set # CONFIG_USB_STORAGE_ALAUDA is not set # CONFIG_USB_STORAGE_ONETOUCH is not set # CONFIG_USB_STORAGE_KARMA is not set # CONFIG_USB_STORAGE_CYPRESS_ATACB is not set # CONFIG_USB_LIBUSUAL is not set # # USB Imaging devices # # CONFIG_USB_MDC800 is not set # CONFIG_USB_MICROTEK is not set # # USB port drivers # CONFIG_USB_SERIAL=m CONFIG_USB_EZUSB=y CONFIG_USB_SERIAL_GENERIC=y CONFIG_USB_SERIAL_AIRCABLE=m CONFIG_USB_SERIAL_ARK3116=m CONFIG_USB_SERIAL_BELKIN=m CONFIG_USB_SERIAL_CH341=m CONFIG_USB_SERIAL_WHITEHEAT=m CONFIG_USB_SERIAL_DIGI_ACCELEPORT=m CONFIG_USB_SERIAL_CP2101=m CONFIG_USB_SERIAL_CYPRESS_M8=m CONFIG_USB_SERIAL_EMPEG=m CONFIG_USB_SERIAL_FTDI_SIO=m CONFIG_USB_SERIAL_FUNSOFT=m CONFIG_USB_SERIAL_VISOR=m CONFIG_USB_SERIAL_IPAQ=m CONFIG_USB_SERIAL_IR=m CONFIG_USB_SERIAL_EDGEPORT=m CONFIG_USB_SERIAL_EDGEPORT_TI=m CONFIG_USB_SERIAL_GARMIN=m CONFIG_USB_SERIAL_IPW=m CONFIG_USB_SERIAL_IUU=m CONFIG_USB_SERIAL_KEYSPAN_PDA=m CONFIG_USB_SERIAL_KEYSPAN=m CONFIG_USB_SERIAL_KEYSPAN_MPR=y CONFIG_USB_SERIAL_KEYSPAN_USA28=y CONFIG_USB_SERIAL_KEYSPAN_USA28X=y CONFIG_USB_SERIAL_KEYSPAN_USA28XA=y CONFIG_USB_SERIAL_KEYSPAN_USA28XB=y CONFIG_USB_SERIAL_KEYSPAN_USA19=y CONFIG_USB_SERIAL_KEYSPAN_USA18X=y CONFIG_USB_SERIAL_KEYSPAN_USA19W=y CONFIG_USB_SERIAL_KEYSPAN_USA19QW=y CONFIG_USB_SERIAL_KEYSPAN_USA19QI=y CONFIG_USB_SERIAL_KEYSPAN_USA49W=y CONFIG_USB_SERIAL_KEYSPAN_USA49WLC=y CONFIG_USB_SERIAL_KLSI=m CONFIG_USB_SERIAL_KOBIL_SCT=m CONFIG_USB_SERIAL_MCT_U232=m CONFIG_USB_SERIAL_MOS7720=m CONFIG_USB_SERIAL_MOS7840=m CONFIG_USB_SERIAL_MOTOROLA=m CONFIG_USB_SERIAL_NAVMAN=m CONFIG_USB_SERIAL_PL2303=m CONFIG_USB_SERIAL_OTI6858=m CONFIG_USB_SERIAL_SPCP8X5=m CONFIG_USB_SERIAL_HP4X=m CONFIG_USB_SERIAL_SAFE=m # CONFIG_USB_SERIAL_SAFE_PADDED is not set CONFIG_USB_SERIAL_SIERRAWIRELESS=m CONFIG_USB_SERIAL_TI=m CONFIG_USB_SERIAL_CYBERJACK=m CONFIG_USB_SERIAL_XIRCOM=m CONFIG_USB_SERIAL_OPTION=m CONFIG_USB_SERIAL_OMNINET=m CONFIG_USB_SERIAL_DEBUG=m # # USB Miscellaneous drivers # CONFIG_USB_EMI62=m CONFIG_USB_EMI26=m # CONFIG_USB_ADUTUX is not set # CONFIG_USB_SEVSEG is not set # CONFIG_USB_RIO500 is not set CONFIG_USB_LEGOTOWER=m CONFIG_USB_LCD=m # CONFIG_USB_BERRY_CHARGE is not set CONFIG_USB_LED=m # CONFIG_USB_CYPRESS_CY7C63 is not set # CONFIG_USB_CYTHERM is not set # CONFIG_USB_PHIDGET is not set # CONFIG_USB_IDMOUSE is not set # CONFIG_USB_FTDI_ELAN is not set # CONFIG_USB_APPLEDISPLAY is not set # CONFIG_USB_SISUSBVGA is not set # CONFIG_USB_LD is not set # CONFIG_USB_TRANCEVIBRATOR is not set # CONFIG_USB_IOWARRIOR is not set # CONFIG_USB_TEST is not set # CONFIG_USB_ISIGHTFW is not set # CONFIG_USB_VST is not set CONFIG_USB_GADGET=y # CONFIG_USB_GADGET_DEBUG is not set # CONFIG_USB_GADGET_DEBUG_FILES is not set CONFIG_USB_GADGET_DEBUG_FS=y CONFIG_USB_GADGET_VBUS_DRAW=2 CONFIG_USB_GADGET_SELECTED=y # CONFIG_USB_GADGET_AT91 is not set # CONFIG_USB_GADGET_ATMEL_USBA is not set # CONFIG_USB_GADGET_FSL_USB2 is not set # CONFIG_USB_GADGET_LH7A40X is not set # CONFIG_USB_GADGET_OMAP is not set # CONFIG_USB_GADGET_PXA25X is not set # CONFIG_USB_GADGET_PXA27X is not set # CONFIG_USB_GADGET_S3C2410 is not set # CONFIG_USB_GADGET_M66592 is not set # CONFIG_USB_GADGET_AMD5536UDC is not set # CONFIG_USB_GADGET_FSL_QE is not set # CONFIG_USB_GADGET_NET2280 is not set # CONFIG_USB_GADGET_GOKU is not set # CONFIG_USB_GADGET_DUMMY_HCD is not set CONFIG_USB_GADGET_DUALSPEED=y # CONFIG_USB_ZERO is not set CONFIG_USB_ETH=y CONFIG_USB_ETH_RNDIS=y # CONFIG_USB_GADGETFS is not set # CONFIG_USB_FILE_STORAGE is not set # CONFIG_USB_G_SERIAL is not set # CONFIG_USB_MIDI_GADGET is not set # CONFIG_USB_G_PRINTER is not set # CONFIG_USB_CDC_COMPOSITE is not set # # OTG and related infrastructure # CONFIG_USB_OTG_UTILS=y CONFIG_USB_GPIO_VBUS=y # CONFIG_ISP1301_OMAP is not set CONFIG_TWL4030_USB=y CONFIG_MMC=y # CONFIG_MMC_DEBUG is not set CONFIG_MMC_UNSAFE_RESUME=y # # MMC/SD/SDIO Card Drivers # CONFIG_MMC_BLOCK=y CONFIG_MMC_BLOCK_BOUNCE=y CONFIG_SDIO_UART=y # CONFIG_MMC_TEST is not set # # MMC/SD/SDIO Host Controller Drivers # # CONFIG_MMC_SDHCI is not set CONFIG_MMC_OMAP_HS=y CONFIG_MMC_SPI=m # CONFIG_MEMSTICK is not set # CONFIG_ACCESSIBILITY is not set CONFIG_NEW_LEDS=y CONFIG_LEDS_CLASS=y # # LED drivers # # CONFIG_LEDS_OMAP_DEBUG is not set # CONFIG_LEDS_OMAP is not set # CONFIG_LEDS_OMAP_PWM is not set # CONFIG_LEDS_PCA9532 is not set CONFIG_LEDS_GPIO=y # CONFIG_LEDS_PCA955X is not set # # LED Triggers # CONFIG_LEDS_TRIGGERS=y CONFIG_LEDS_TRIGGER_TIMER=y CONFIG_LEDS_TRIGGER_HEARTBEAT=y # CONFIG_LEDS_TRIGGER_BACKLIGHT is not set # CONFIG_LEDS_TRIGGER_DEFAULT_ON 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=y # CONFIG_RTC_DRV_S35390A is not set # CONFIG_RTC_DRV_FM3130 is not set # CONFIG_RTC_DRV_RX8581 is not set # # SPI RTC drivers # # CONFIG_RTC_DRV_M41T94 is not set # CONFIG_RTC_DRV_DS1305 is not set # CONFIG_RTC_DRV_DS1390 is not set # CONFIG_RTC_DRV_MAX6902 is not set # CONFIG_RTC_DRV_R9701 is not set # CONFIG_RTC_DRV_RS5C348 is not set # CONFIG_RTC_DRV_DS3234 is not set # # 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=y # CONFIG_REGULATOR_DEBUG is not set # CONFIG_REGULATOR_FIXED_VOLTAGE is not set # CONFIG_REGULATOR_VIRTUAL_CONSUMER is not set # CONFIG_REGULATOR_BQ24022 is not set CONFIG_REGULATOR_TWL4030=y # 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=m # CONFIG_EXT4DEV_COMPAT is not set CONFIG_EXT4_FS_XATTR=y # CONFIG_EXT4_FS_POSIX_ACL is not set # CONFIG_EXT4_FS_SECURITY is not set CONFIG_JBD=y # CONFIG_JBD_DEBUG is not set CONFIG_JBD2=m # CONFIG_JBD2_DEBUG is not set CONFIG_FS_MBCACHE=m # CONFIG_REISERFS_FS is not set # CONFIG_JFS_FS is not set CONFIG_FS_POSIX_ACL=y CONFIG_FILE_LOCKING=y CONFIG_XFS_FS=m # CONFIG_XFS_QUOTA is not set # CONFIG_XFS_POSIX_ACL is not set # CONFIG_XFS_RT is not set # CONFIG_XFS_DEBUG is not set # CONFIG_GFS2_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=m # # CD-ROM/DVD Filesystems # CONFIG_ISO9660_FS=m CONFIG_JOLIET=y CONFIG_ZISOFS=y CONFIG_UDF_FS=m CONFIG_UDF_NLS=y # # 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_JFFS2_FS=y CONFIG_JFFS2_FS_DEBUG=0 CONFIG_JFFS2_FS_WRITEBUFFER=y # CONFIG_JFFS2_FS_WBUF_VERIFY is not set CONFIG_JFFS2_SUMMARY=y CONFIG_JFFS2_FS_XATTR=y CONFIG_JFFS2_FS_POSIX_ACL=y CONFIG_JFFS2_FS_SECURITY=y CONFIG_JFFS2_COMPRESSION_OPTIONS=y CONFIG_JFFS2_ZLIB=y CONFIG_JFFS2_LZO=y CONFIG_JFFS2_RTIME=y CONFIG_JFFS2_RUBIN=y # CONFIG_JFFS2_CMODE_NONE is not set # CONFIG_JFFS2_CMODE_PRIORITY is not set # CONFIG_JFFS2_CMODE_SIZE is not set CONFIG_JFFS2_CMODE_FAVOURLZO=y CONFIG_UBIFS_FS=y # CONFIG_UBIFS_FS_XATTR is not set # CONFIG_UBIFS_FS_ADVANCED_COMPR is not set CONFIG_UBIFS_FS_LZO=y CONFIG_UBIFS_FS_ZLIB=y # CONFIG_UBIFS_FS_DEBUG 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=y CONFIG_TIMER_STATS=y # 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 is not set # 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_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 is not set # 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_XOR_BLOCKS=m CONFIG_ASYNC_CORE=m CONFIG_ASYNC_MEMCPY=m CONFIG_ASYNC_XOR=m CONFIG_CRYPTO=y # # Crypto core or helper # # CONFIG_CRYPTO_FIPS is not set CONFIG_CRYPTO_ALGAPI=y CONFIG_CRYPTO_ALGAPI2=y CONFIG_CRYPTO_AEAD2=y CONFIG_CRYPTO_BLKCIPHER=y CONFIG_CRYPTO_BLKCIPHER2=y CONFIG_CRYPTO_HASH=m CONFIG_CRYPTO_HASH2=y CONFIG_CRYPTO_RNG2=y CONFIG_CRYPTO_MANAGER=y CONFIG_CRYPTO_MANAGER2=y CONFIG_CRYPTO_GF128MUL=m CONFIG_CRYPTO_NULL=m CONFIG_CRYPTO_CRYPTD=m # CONFIG_CRYPTO_AUTHENC is not set CONFIG_CRYPTO_TEST=m # # 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=y CONFIG_CRYPTO_LRW=m CONFIG_CRYPTO_PCBC=m # CONFIG_CRYPTO_XTS is not set # # Hash modes # CONFIG_CRYPTO_HMAC=m CONFIG_CRYPTO_XCBC=m # # Digest # CONFIG_CRYPTO_CRC32C=m CONFIG_CRYPTO_MD4=m CONFIG_CRYPTO_MD5=y CONFIG_CRYPTO_MICHAEL_MIC=y # 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=m CONFIG_CRYPTO_SHA256=m CONFIG_CRYPTO_SHA512=m CONFIG_CRYPTO_TGR192=m CONFIG_CRYPTO_WP512=m # # Ciphers # CONFIG_CRYPTO_AES=y CONFIG_CRYPTO_ANUBIS=m CONFIG_CRYPTO_ARC4=y CONFIG_CRYPTO_BLOWFISH=m CONFIG_CRYPTO_CAMELLIA=m CONFIG_CRYPTO_CAST5=m CONFIG_CRYPTO_CAST6=m CONFIG_CRYPTO_DES=y CONFIG_CRYPTO_FCRYPT=m CONFIG_CRYPTO_KHAZAD=m # CONFIG_CRYPTO_SALSA20 is not set # CONFIG_CRYPTO_SEED is not set CONFIG_CRYPTO_SERPENT=m CONFIG_CRYPTO_TEA=m CONFIG_CRYPTO_TWOFISH=m CONFIG_CRYPTO_TWOFISH_COMMON=m # # Compression # CONFIG_CRYPTO_DEFLATE=y CONFIG_CRYPTO_LZO=y # # 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=y CONFIG_CRC_T10DIF=y CONFIG_CRC_ITU_T=y CONFIG_CRC32=y CONFIG_CRC7=y CONFIG_LIBCRC32C=y CONFIG_ZLIB_INFLATE=y CONFIG_ZLIB_DEFLATE=y CONFIG_LZO_COMPRESS=y CONFIG_LZO_DECOMPRESS=y CONFIG_PLIST=y CONFIG_HAS_IOMEM=y CONFIG_HAS_IOPORT=y CONFIG_HAS_DMA=y ^ permalink raw reply [flat|nested] 40+ messages in thread
* Re: new PM branch available 2009-02-02 19:42 ` Kevin Hilman @ 2009-02-02 20:06 ` Kevin Hilman 2009-02-04 0:52 ` Peter 'p2' De Schrijver 1 sibling, 0 replies; 40+ messages in thread From: Kevin Hilman @ 2009-02-02 20:06 UTC (permalink / raw) To: Peter 'p2' De Schrijver; +Cc: linux-omap@vger.kernel.org Kevin Hilman <khilman@deeprootsystems.com> writes: > Hi Peter, > > "Peter 'p2' De Schrijver" <peter.de-schrijver@nokia.com> writes: > >> Hi Kevin, >> >>> Hello, >>> >>> The latest PM branch is now available[1]. >>> >>> I've done basic testing of retention and off-mode (suspend and dynamic >>> idle) on Beagle and custom HW. My SDP has something still keeping >>> CORE active that others have not seen, but I have yet to debug. Any >>> other reports from SDP testing would be appreciated. >>> >>> Notable changes/updates >>> - rebased on latest clock updates and fixes from Paul >>> - clockfw pre- and post- notifiers >>> - DVFS for VDD2 >>> >> >> I tried it on a beagleboard last night, but couldn't get even static >> retention to work. Some domains (core, per, dss) stay on, but even mpu >> and neon don't go to retention. They only go to inactive. > > A first guess: this sounds like CONFIG_OMAP_RESET_CLOCKS=y is missing > from your .config. > > The MPU/NEON going active but not RET is an indication to me that some > fclk is active so that the fclk check in omap3_can_sleep() fails, so a > WFI is never attempted. That's shy > > Personally, I'm thinking we should totally drop this fclk check. I see > no reason not to attempt a WFI, even if there are active fclks. > >> So could you send your .config file ? > > Attached. > >> Which rootfs are you using, I'm using debian, so maybe something >> keeps the CPU busy. Are you using NAND or MMC to store your rootfs ? > > I'm using rootfs on MMC and have tested with busybox-only, debian and > OE rootfs. With debian and OE, I usually boot a minimal rootfs, > before a full userland comes up. With debian, I changed my > /etc/init.d/rcS to start initlevel 1 instead of 'S'. > >> Which beagle HW rev do you have ? I'm testing on a B5 board. > > I have a rev B4. > >> And which u-boot are you using ? > > I'm using the u-boot from Steve Sakoman's tree[1]. That helped a lot > in my initial Beagle testing, but I think the kernel should reset the > IVA and D2D now which is the domains that I was having problems with > before, so I think that the out of the box u-boot should work fine. > > Kevin > > [1] http://elinux.org/BeagleBoard#U-Boot One other thing... to fix the noise about unbalanced IRQs upon GPIO resume, you also need my patch posted to l-o recently: [PATCH omap-fixes] OMAP2/3: GPIO: remove recursion in IRQ wakeup path Kevin ^ permalink raw reply [flat|nested] 40+ messages in thread
* Re: new PM branch available 2009-02-02 19:42 ` Kevin Hilman 2009-02-02 20:06 ` Kevin Hilman @ 2009-02-04 0:52 ` Peter 'p2' De Schrijver 2009-02-04 16:04 ` Kevin Hilman 1 sibling, 1 reply; 40+ messages in thread From: Peter 'p2' De Schrijver @ 2009-02-04 0:52 UTC (permalink / raw) To: ext Kevin Hilman; +Cc: linux-omap@vger.kernel.org Hi Kevin, > Hi Peter, > > "Peter 'p2' De Schrijver" <peter.de-schrijver@nokia.com> writes: > > > A first guess: this sounds like CONFIG_OMAP_RESET_CLOCKS=y is missing > from your .config. > > The MPU/NEON going active but not RET is an indication to me that some > fclk is active so that the fclk check in omap3_can_sleep() fails, so a > WFI is never attempted. That's shy > Ok. I did enable CONFIG_OMAP_RESET_CLOCKS. But with your config file only PER and CORE did not go to retention. One difference is that I did not enable smartreflex, but as B5 (and B4) are using OMAP3s without proper efuse values, smartreflex shouldn't matter I assume ? I upgrade my u-boot to the latest version, and then PER went to retention as well. The only way to get core to retention was to force idle USBOTG and disable the USBOTG driver. Dynamic retention seems to work only once the system has been in static retention once. Static off mode seems to work, but resume from off kills the UART. The system seems to run though, at least LED0 flickers as usual when the system runs. Sometimes it hangs and I have seen one reboot. > > > Which rootfs are you using, I'm using debian, so maybe something > > keeps the CPU busy. Are you using NAND or MMC to store your rootfs ? > > I'm using rootfs on MMC and have tested with busybox-only, debian and > OE rootfs. With debian and OE, I usually boot a minimal rootfs, > before a full userland comes up. With debian, I changed my > /etc/init.d/rcS to start initlevel 1 instead of 'S'. > Ok. I tried with both the small OE ramdisk image and rather minimal debian install. I didn't see a difference in behaviour between both. > > And which u-boot are you using ? > > I'm using the u-boot from Steve Sakoman's tree[1]. That helped a lot > in my initial Beagle testing, but I think the kernel should reset the > IVA and D2D now which is the domains that I was having problems with > before, so I think that the out of the box u-boot should work fine. > I upgraded to this u-boot and it resolved at least one issue. Cheers, Peter. -- goa is a state of mind ^ permalink raw reply [flat|nested] 40+ messages in thread
* Re: new PM branch available 2009-02-04 0:52 ` Peter 'p2' De Schrijver @ 2009-02-04 16:04 ` Kevin Hilman 2009-02-04 16:15 ` Koen Kooi 2009-02-04 16:38 ` Peter 'p2' De Schrijver 0 siblings, 2 replies; 40+ messages in thread From: Kevin Hilman @ 2009-02-04 16:04 UTC (permalink / raw) To: Peter 'p2' De Schrijver; +Cc: linux-omap@vger.kernel.org "Peter 'p2' De Schrijver" <peter.de-schrijver@nokia.com> writes: > Hi Kevin, > >> Hi Peter, >> >> "Peter 'p2' De Schrijver" <peter.de-schrijver@nokia.com> writes: >> >> >> A first guess: this sounds like CONFIG_OMAP_RESET_CLOCKS=y is missing >> from your .config. >> >> The MPU/NEON going active but not RET is an indication to me that some >> fclk is active so that the fclk check in omap3_can_sleep() fails, so a >> WFI is never attempted. That's shy >> > > Ok. I did enable CONFIG_OMAP_RESET_CLOCKS. But with your config file > only PER and CORE did not go to retention. One difference is that I did > not enable smartreflex, but as B5 (and B4) are using OMAP3s without > proper efuse values, smartreflex shouldn't matter I assume ? > > I upgrade my u-boot to the latest version, and then PER went to > retention as well. Did you happen to notice what was keeping PER out of retention before the u-boot upgrade? Looks like we might still need some init-time reset code to compensate for bootloaders. > The only way to get core to retention was to force idle USBOTG and > disable the USBOTG driver. This is the same issue on 3430SDP. The PM branch code does the force-idle, and I usually have USB built as modules and not loaded when I do the tests. I'm guessing this is a result of u-boot configuring/using USB. > Dynamic retention seems to work only once the system has been in static > retention once. > > Static off mode seems to work, but resume from off kills the UART. The > system seems to run though, at least LED0 flickers as usual when the > system runs. Sometimes it hangs and I have seen one reboot. I have noticed this as well. I haven't looked at all at the T2 scripts being used on Beagle. Do you think some of these issues may be related to those scripts? Kevin >> >> > Which rootfs are you using, I'm using debian, so maybe something >> > keeps the CPU busy. Are you using NAND or MMC to store your rootfs ? >> >> I'm using rootfs on MMC and have tested with busybox-only, debian and >> OE rootfs. With debian and OE, I usually boot a minimal rootfs, >> before a full userland comes up. With debian, I changed my >> /etc/init.d/rcS to start initlevel 1 instead of 'S'. >> > > Ok. I tried with both the small OE ramdisk image and rather minimal debian > install. I didn't see a difference in behaviour between both. > >> > And which u-boot are you using ? >> >> I'm using the u-boot from Steve Sakoman's tree[1]. That helped a lot >> in my initial Beagle testing, but I think the kernel should reset the >> IVA and D2D now which is the domains that I was having problems with >> before, so I think that the out of the box u-boot should work fine. >> > > I upgraded to this u-boot and it resolved at least one issue. > > Cheers, > > Peter. > > -- > goa is a state of mind ^ permalink raw reply [flat|nested] 40+ messages in thread
* Re: new PM branch available 2009-02-04 16:04 ` Kevin Hilman @ 2009-02-04 16:15 ` Koen Kooi 2009-02-04 16:38 ` Peter 'p2' De Schrijver 1 sibling, 0 replies; 40+ messages in thread From: Koen Kooi @ 2009-02-04 16:15 UTC (permalink / raw) To: Kevin Hilman; +Cc: Peter 'p2' De Schrijver, linux-omap@vger.kernel.org [-- Attachment #1: Type: text/plain, Size: 736 bytes --] Op 4 feb 2009, om 17:04 heeft Kevin Hilman het volgende geschreven: > "Peter 'p2' De Schrijver" <peter.de-schrijver@nokia.com> writes: > >> Dynamic retention seems to work only once the system has been in >> static >> retention once. >> >> Static off mode seems to work, but resume from off kills the UART. >> The >> system seems to run though, at least LED0 flickers as usual when the >> system runs. Sometimes it hangs and I have seen one reboot. > > I have noticed this as well. > > I haven't looked at all at the T2 scripts being used on Beagle. Do > you think some of these issues may be related to those scripts? The scripts prevent 'reboot' from working, disabling them makes it work again (on beagle). regards, Koen [-- Attachment #2: Dit deel van het bericht is digitaal ondertekend --] [-- Type: application/pgp-signature, Size: 186 bytes --] ^ permalink raw reply [flat|nested] 40+ messages in thread
* Re: new PM branch available 2009-02-04 16:04 ` Kevin Hilman 2009-02-04 16:15 ` Koen Kooi @ 2009-02-04 16:38 ` Peter 'p2' De Schrijver 1 sibling, 0 replies; 40+ messages in thread From: Peter 'p2' De Schrijver @ 2009-02-04 16:38 UTC (permalink / raw) To: ext Kevin Hilman; +Cc: linux-omap@vger.kernel.org Hi Kevin, > > Did you happen to notice what was keeping PER out of retention before > the u-boot upgrade? Looks like we might still need some init-time > reset code to compensate for bootloaders. > No. I still have the old u-boot version though, so I can reproduce the problem. After fosdem :) > > The only way to get core to retention was to force idle USBOTG and > > disable the USBOTG driver. > > This is the same issue on 3430SDP. The PM branch code does the > force-idle, and I usually have USB built as modules and not loaded > when I do the tests. > Ok. > I'm guessing this is a result of u-boot configuring/using USB. > > > Dynamic retention seems to work only once the system has been in static > > retention once. > > > > Static off mode seems to work, but resume from off kills the UART. The > > system seems to run though, at least LED0 flickers as usual when the > > system runs. Sometimes it hangs and I have seen one reboot. > > I have noticed this as well. > > I haven't looked at all at the T2 scripts being used on Beagle. Do > you think some of these issues may be related to those scripts? > It might be. They are very basic compared to some others I have seen. I will have a look at those tonight. Cheers, Peter. -- goa is a state of mind ^ permalink raw reply [flat|nested] 40+ messages in thread
end of thread, other threads:[~2009-03-18 19:32 UTC | newest]
Thread overview: 40+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-03-18 18:56 new PM branch available Nicholas Chen
2009-03-18 19:01 ` Kevin Hilman
2009-03-18 19:22 ` Nicholas Chen
-- strict thread matches above, loose matches on Subject: below --
2009-01-13 21:51 Kevin Hilman
2009-01-14 7:35 ` Koen Kooi
2009-01-14 18:09 ` David Brownell
2009-01-14 22:14 ` Kevin Hilman
2009-01-15 8:18 ` Koen Kooi
2009-01-14 12:40 ` Ramesh Gupta Guntha
2009-01-14 16:35 ` Kevin Hilman
2009-01-14 13:57 ` Sriram V
2009-01-14 16:39 ` Kevin Hilman
2009-01-15 13:42 ` Premi, Sanjeev
2009-01-15 15:01 ` Kevin Hilman
2009-01-15 15:17 ` Premi, Sanjeev
2009-01-15 15:34 ` Kevin Hilman
2009-01-15 16:00 ` Premi, Sanjeev
2009-01-15 15:00 ` Sriram V
[not found] ` <8bf247760901150654n78b198f0o5c2270186e9c119e@mail.gmail.com>
2009-01-15 15:07 ` Kevin Hilman
2009-01-16 13:49 ` Nayak, Rajendra
2009-01-16 19:03 ` Kevin Hilman
2009-01-19 15:46 ` Premi, Sanjeev
2009-01-19 16:04 ` Premi, Sanjeev
2009-01-23 10:19 ` Nayak, Rajendra
2009-01-23 11:21 ` Högander Jouni
2009-01-23 12:00 ` Nayak, Rajendra
2009-01-23 12:10 ` Nayak, Rajendra
2009-01-23 16:49 ` Kevin Hilman
2009-01-23 12:10 ` Koen Kooi
2009-01-23 17:20 ` Kevin Hilman
2009-01-23 18:27 ` Koen Kooi
2009-01-23 17:48 ` Kevin Hilman
2009-01-27 9:18 ` Nayak, Rajendra
2009-02-02 17:45 ` Peter 'p2' De Schrijver
2009-02-02 19:42 ` Kevin Hilman
2009-02-02 20:06 ` Kevin Hilman
2009-02-04 0:52 ` Peter 'p2' De Schrijver
2009-02-04 16:04 ` Kevin Hilman
2009-02-04 16:15 ` Koen Kooi
2009-02-04 16:38 ` Peter 'p2' De Schrijver
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox