Re: OMAP baseline test results for v3.9

2013-05-16 Thread Paul Walmsley 
On Tue, 14 May 2013, Tony Lindgren wrote:

 Thanks that explains. BTW, the PM off naming might make some
 people think that CONFIG_PM is not set :)

That's a good point.  Will rename that and probably split the 3730 Beagle 
XM into its own testing category.


- Paul
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: OMAP baseline test results for v3.9

2013-05-14 Thread Tony Lindgren 
Hi,

* Paul Walmsley p...@pwsan.com [130508 12:45]:
 
 PM off, dynamic idle:
 FAIL ( 2/ 5): 4430es2panda, 4460pandaes
 Pass ( 3/ 5): 3530es3beagle, 3730beaglexm, 37xxevm

Looking at your pm logs, 3730beaglexm won't hit off-idle.
I've pasted the relevant lines from your logs below.

Is this a known issue?

Regards,

Tony


3530es3beagle hits OFF:
core_pwrdm 
(ON),OFF:24,RET:41,INA:0,ON:66,RET-LOGIC-OFF:0,RET-MEMBANK1-OFF:0,RET-MEMBANK2-OFF:0

3730beaglexm won't hit OFF:
core_pwrdm 
(ON),OFF:0,RET:88,INA:0,ON:89,RET-LOGIC-OFF:0,RET-MEMBANK1-OFF:0,RET-MEMBANK2-OFF:0

37xxevm hits OFF:
core_pwrdm 
(ON),OFF:8,RET:10,INA:0,ON:19,RET-LOGIC-OFF:0,RET-MEMBANK1-OFF:0,RET-MEMBANK2-OFF:0
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: OMAP baseline test results for v3.9

2013-05-14 Thread Paul Walmsley 
On Tue, 14 May 2013, Tony Lindgren wrote:

 Hi,
 
 * Paul Walmsley p...@pwsan.com [130508 12:45]:
  
  PM off, dynamic idle:
  FAIL ( 2/ 5): 4430es2panda, 4460pandaes
  Pass ( 3/ 5): 3530es3beagle, 3730beaglexm, 37xxevm
 
 Looking at your pm logs, 3730beaglexm won't hit off-idle.
 I've pasted the relevant lines from your logs below.
 
 Is this a known issue?

Yes, the Beagle XM in my testbed is a 3630ES1.0.  From the PM logs:

[   63.154418] omap3_pm_off_mode_enable: Core OFF disabled due to errata 
i583

I should probably clarify how this is reported in the test results.


- Paul
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: OMAP baseline test results for v3.9

2013-05-14 Thread Tony Lindgren 
* Paul Walmsley p...@pwsan.com [130514 14:24]:
 On Tue, 14 May 2013, Tony Lindgren wrote:
 
  Hi,
  
  * Paul Walmsley p...@pwsan.com [130508 12:45]:
   
   PM off, dynamic idle:
   FAIL ( 2/ 5): 4430es2panda, 4460pandaes
   Pass ( 3/ 5): 3530es3beagle, 3730beaglexm, 37xxevm
  
  Looking at your pm logs, 3730beaglexm won't hit off-idle.
  I've pasted the relevant lines from your logs below.
  
  Is this a known issue?
 
 Yes, the Beagle XM in my testbed is a 3630ES1.0.  From the PM logs:
 
 [   63.154418] omap3_pm_off_mode_enable: Core OFF disabled due to errata 
 i583
 
 I should probably clarify how this is reported in the test results.

Thanks that explains. BTW, the PM off naming might make some
people think that CONFIG_PM is not set :)

Regards,

Tony
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

OMAP baseline test results for v3.9-rc8

2013-05-08 Thread Paul Walmsley 


Here are some basic OMAP test results for Linux v3.9-rc8.
Logs and other details at:

http://www.pwsan.com/omap/testlogs/test_v3.9-rc8/20130422154921/


Test summary


Build:
FAIL ( 2/16): am33xx_only, omap2plus_defconfig_2430sdp_only
Pass (14/16): n800_multi_omap2xxx, n800_only_a, omap1_defconfig, 
  omap1_defconfig_1510innovator_only, 
  omap1_defconfig_5912osk_only, omap2plus_defconfig, 
  omap2plus_defconfig_cpupm, omap2plus_defconfig_no_pm, 
  omap2plus_defconfig_omap2_4_only, 
  omap2plus_defconfig_omap3_4_only, 
  rmk_omap3430_ldp_allnoconfig, 
  rmk_omap3430_ldp_oldconfig, 
  rmk_omap4430_sdp_allnoconfig, 
  rmk_omap4430_sdp_oldconfig

Boot to userspace:
FAIL ( 1/11): am335xbone
Pass (10/11): 2420n800, 2430sdp, 3517evm, 3530es3beagle,
  3730beaglexm, 37xxevm, 4430es2panda, 4460pandaes,
  5912osk, cmt3517

PM ret, suspend:
FAIL ( 2/ 6): 2430sdp, 4430es2panda
Pass ( 4/ 6): 3530es3beagle, 3730beaglexm, 37xxevm, 4460pandaes

PM ret, dynamic idle:
FAIL ( 3/ 6): 2430sdp, 4430es2panda, 4460pandaes
Pass ( 3/ 6): 3530es3beagle, 3730beaglexm, 37xxevm

PM off, suspend:
FAIL ( 2/ 5): 4430es2panda, 4460pandaes
Pass ( 3/ 5): 3530es3beagle, 3730beaglexm, 37xxevm

PM off, dynamic idle:
FAIL ( 2/ 5): 4430es2panda, 4460pandaes
Pass ( 3/ 5): 3530es3beagle, 3730beaglexm, 37xxevm



Failing tests: fixed by posted patches
--

Build:

* am33xx_only, omap2plus_defconfig_2430sdp_only: omap-{smp,hotplug}.c link 
errors
  - Discussion  RFC patch: 
http://www.spinics.net/lists/arm-kernel/msg230017.html
  - Still needs revision of the patch


Failing tests: needing investigation


Boot tests:

* 3517EVM  CM-T3517: boot hangs with NFS root
  - Likely some Kconfig, board file, and PM issues with EMAC
  - Longstanding bug
  - Not currently part of the automated test suite

Boot warnings:

* CM-T3517: L3 in-band error with IPSS during boot
  - Cause unknown but see http://marc.info/?l=linux-omapm=134833869730129w=2
  - Longstanding issue; does not occur on the 3517EVM

PM tests:

* 2430sdp: power domains not entering retention
  - Cause unknown

* 4430es2panda, 4460pandaes: pwrdm state mismatch on CAM, DSS, ABE

* 4460pandaes: pwrdm state mismatch on IVAHD, TESLA 

* 4430es2panda: CORE, TESLA, IVAHD, L3INIT didn't enter target state
  - Probably due to lack of reset code for M3, DSP, SL2IF, FSUSB
per discussion with Tero Kristo
  - Likely dependent on the bootloader version
- fails with 2012.07-00136-g755de79
  - http://marc.info/?l=linux-arm-kernelm=136432340618226w=2

* 4460pandaes: chip not entering retention in dynamic idle
  - Presumably 4430es2panda also fails this
  - Suspend-to-RAM enters full chip retention

* 3730 Beagle XM: does not serial wake from off-idle suspend when console
  UART doesn't clock-gate (debug ignore_loglevel)
  - Cause unknown
  - Not yet part of the automated test suite
  - Re-tested at v3.7; still failing:

http://www.pwsan.com/omap/transcripts/20121211-3730beaglexm-3.7-pm-offmode-fail-debug.txt

Other:

* 4430es2panda: omap_hwmod: l3_instr: _wait_target_disable failed
  - Unknown cause; could be due to the lack of hierarchical enable/disable
in hwmod code
  - Jon Hunter and Santosh Shilimkar report this does not appear with
the same X-loader/bootloader on his 4430ES2.3 Panda, so could be
ES-level dependent


Failing tests: reported by others 
-

- MUSB broken after v3.9-rc6
  - due to commit 92702df3570e1ccfa050e135e50c450502251b79
  - discussion here: http://marc.info/?l=linux-omapm=136544098331552w=2
  - patch pending upstream:
http://marc.info/?l=linux-omapm=136562302329307w=2



vmlinux object size
(delta in bytes from test_v3.9-rc7 
(41ef2d5678d83af030125550329b6ae8b74618fa)):
   text data  bsstotal  kernel
   +408   +80 +416  n800_multi_omap2xxx
   +408   +80 +416  n800_only_a
+54   -80  +46  omap1_defconfig
+58   -80  +50  omap1_defconfig_1510innovator_only
+54  +240  +78  omap1_defconfig_5912osk_only
   +252  +960 +348  omap2plus_defconfig
  +4348  +720+4420  omap2plus_defconfig_cpupm
   +388  +640 +452  omap2plus_defconfig_no_pm
   +252  +720 +324  omap2plus_defconfig_omap2_4_only
  +4236  +800+4316  omap2plus_defconfig_omap3_4_only
   +168  +16  -40 +144  rmk_omap3430_ldp_allnoconfig
  -4040   -80-4048  rmk_omap3430_ldp_oldconfig
   +168  +16  -40 +144  rmk_omap4430_sdp_allnoconfig
   +1920   +8 +200  rmk_omap4430_sdp_oldconfig


--
To unsubscribe from this list: send the line

OMAP baseline test results for v3.9

2013-05-08 Thread Paul Walmsley 

Here are some basic OMAP test results for Linux v3.9.
Logs and other details at:

http://www.pwsan.com/omap/testlogs/test_v3.9/20130429104339/


Test summary


Build:
FAIL ( 2/16): am33xx_only, omap2plus_defconfig_2430sdp_only
Pass (14/16): n800_multi_omap2xxx, n800_only_a, omap1_defconfig, 
  omap1_defconfig_1510innovator_only, 
  omap1_defconfig_5912osk_only, omap2plus_defconfig, 
  omap2plus_defconfig_cpupm, omap2plus_defconfig_no_pm, 
  omap2plus_defconfig_omap2_4_only, 
  omap2plus_defconfig_omap3_4_only, 
  rmk_omap3430_ldp_allnoconfig, 
  rmk_omap3430_ldp_oldconfig, 
  rmk_omap4430_sdp_allnoconfig, 
  rmk_omap4430_sdp_oldconfig

Boot to userspace:
FAIL ( 1/11): am335xbone
Pass (10/11): 2420n800, 2430sdp, 3517evm, 3530es3beagle,
  3730beaglexm, 37xxevm, 4430es2panda, 4460pandaes,
  5912osk, cmt3517

PM ret, suspend:
FAIL ( 2/ 6): 2430sdp, 4430es2panda
Pass ( 4/ 6): 3530es3beagle, 3730beaglexm, 37xxevm, 4460pandaes

PM ret, dynamic idle:
FAIL ( 3/ 6): 2430sdp, 4430es2panda, 4460pandaes
Pass ( 3/ 6): 3530es3beagle, 3730beaglexm, 37xxevm

PM off, suspend:
FAIL ( 2/ 5): 4430es2panda, 4460pandaes
Pass ( 3/ 5): 3530es3beagle, 3730beaglexm, 37xxevm

PM off, dynamic idle:
FAIL ( 2/ 5): 4430es2panda, 4460pandaes
Pass ( 3/ 5): 3530es3beagle, 3730beaglexm, 37xxevm



Failing tests: fixed by posted patches
--

Build:

* am33xx_only, omap2plus_defconfig_2430sdp_only: omap-{smp,hotplug}.c link 
errors
  - Discussion  RFC patch: 
http://www.spinics.net/lists/arm-kernel/msg230017.html
  - Still needs revision of the patch


Failing tests: needing investigation


Boot tests:

* 3517EVM  CM-T3517: boot hangs with NFS root
  - Likely some Kconfig, board file, and PM issues with EMAC
  - Longstanding bug
  - Not currently part of the automated test suite

Boot warnings:

* CM-T3517: L3 in-band error with IPSS during boot
  - Cause unknown but see http://marc.info/?l=linux-omapm=134833869730129w=2
  - Longstanding issue; does not occur on the 3517EVM

PM tests:

* 2430sdp: power domains not entering retention
  - Cause unknown

* 4430es2panda, 4460pandaes: pwrdm state mismatch on CAM, DSS, ABE

* 4460pandaes: pwrdm state mismatch on IVAHD, TESLA 

* 4430es2panda: CORE, TESLA, IVAHD, L3INIT didn't enter target state
  - Probably due to lack of reset code for M3, DSP, SL2IF, FSUSB
per discussion with Tero Kristo
  - Likely dependent on the bootloader version
- fails with 2012.07-00136-g755de79
  - http://marc.info/?l=linux-arm-kernelm=136432340618226w=2

* 4460pandaes: chip not entering retention in dynamic idle
  - Presumably 4430es2panda also fails this
  - Suspend-to-RAM enters full chip retention

* 3730 Beagle XM: does not serial wake from off-idle suspend when console
  UART doesn't clock-gate (debug ignore_loglevel)
  - Cause unknown
  - Not yet part of the automated test suite
  - Re-tested at v3.7; still failing:

http://www.pwsan.com/omap/transcripts/20121211-3730beaglexm-3.7-pm-offmode-fail-debug.txt

Other:

* 4430es2panda: omap_hwmod: l3_instr: _wait_target_disable failed
  - Unknown cause; could be due to the lack of hierarchical enable/disable
in hwmod code
  - Jon Hunter and Santosh Shilimkar report this does not appear with
the same X-loader/bootloader on his 4430ES2.3 Panda, so could be
ES-level dependent


vmlinux object size
(delta in bytes from test_v3.9-rc8 
(60d509fa6a9c4653a86ad830e4c4b30360b23f0e)):
   text data  bsstotal  kernel
   +176   +80 +184  n800_multi_omap2xxx
   +160   +80 +168  n800_only_a
   +120   +80 +128  omap1_defconfig
   +136   +80 +144  omap1_defconfig_1510innovator_only
   +152  -240 +128  omap1_defconfig_5912osk_only
   +20400 +204  omap2plus_defconfig
   +20400 +204  omap2plus_defconfig_cpupm
   +20400 +204  omap2plus_defconfig_no_pm
   +20400 +204  omap2plus_defconfig_omap2_4_only
   +20400 +204  omap2plus_defconfig_omap3_4_only
   +13200 +132  rmk_omap3430_ldp_allnoconfig
+8000  +80  rmk_omap3430_ldp_oldconfig
   +13200 +132  rmk_omap4430_sdp_allnoconfig
+9600  +96  rmk_omap4430_sdp_oldconfig



vmlinux object size
(delta in bytes from test_v3.8 
(19f949f52599ba7c3f67a5897ac6be14bfcb1200)):
   text data  bsstotal  kernel
-549808   +23520-9184  -535472  n800_multi_omap2xxx
-548359   +27432-9268  -530195  n800_only_a
 +61909+5680 +392   +67981  omap1_defconfig
 +62549+5664 +424   +68637  omap1_defconfig_1510innovator_only
 +63725

OMAP baseline test results for v3.9-rc7

2013-04-14 Thread Paul Walmsley 

Here are some basic OMAP test results for Linux v3.9-rc7.
Logs and other details at:

http://www.pwsan.com/omap/testlogs/test_v3.9-rc7/20130414220303/


Test summary


Build:
FAIL ( 2/16): am33xx_only, omap2plus_defconfig_2430sdp_only
Pass (14/16): n800_multi_omap2xxx, n800_only_a, omap1_defconfig, 
  omap1_defconfig_1510innovator_only, 
  omap1_defconfig_5912osk_only, omap2plus_defconfig, 
  omap2plus_defconfig_cpupm, omap2plus_defconfig_no_pm, 
  omap2plus_defconfig_omap2_4_only, 
  omap2plus_defconfig_omap3_4_only, 
  rmk_omap3430_ldp_allnoconfig, 
  rmk_omap3430_ldp_oldconfig, 
  rmk_omap4430_sdp_allnoconfig, 
  rmk_omap4430_sdp_oldconfig

Boot to userspace:
FAIL ( 1/11): am335xbone
Pass (10/11): 2420n800, 2430sdp, 3517evm, 3530es3beagle,
  3730beaglexm, 37xxevm, 4430es2panda, 4460pandaes,
  5912osk, cmt3517

PM ret, suspend:
FAIL ( 2/ 6): 2430sdp, 4430es2panda
Pass ( 4/ 6): 3530es3beagle, 3730beaglexm, 37xxevm, 4460pandaes

PM ret, dynamic idle:
FAIL ( 3/ 6): 2430sdp, 4430es2panda, 4460pandaes
Pass ( 3/ 6): 3530es3beagle, 3730beaglexm, 37xxevm

PM off, suspend:
FAIL ( 2/ 5): 4430es2panda, 4460pandaes
Pass ( 3/ 5): 3530es3beagle, 3730beaglexm, 37xxevm

PM off, dynamic idle:
FAIL ( 2/ 5): 4430es2panda, 4460pandaes
Pass ( 3/ 5): 3530es3beagle, 3730beaglexm, 37xxevm



Failing tests: fixed by posted patches
--

Build:

* am33xx_only, omap2plus_defconfig_2430sdp_only: omap-{smp,hotplug}.c link 
errors
  - Discussion  RFC patch: 
http://www.spinics.net/lists/arm-kernel/msg230017.html
  - Still needs revision of the patch


Failing tests: needing investigation


Boot tests:

* 3517EVM  CM-T3517: boot hangs with NFS root
  - Likely some Kconfig, board file, and PM issues with EMAC
  - Longstanding bug
  - Not currently part of the automated test suite

Boot warnings:

* CM-T3517: L3 in-band error with IPSS during boot
  - Cause unknown but see http://marc.info/?l=linux-omapm=134833869730129w=2
  - Longstanding issue; does not occur on the 3517EVM

PM tests:

* 2430sdp: pwrdm state mismatch(dsp_pwrdm) 0 != 3
  - need to doublecheck wakeup dependencies
  - (am assuming it's still there; userspace problems prevent the test
 from running, probably due to the lock warning)

* 2430sdp: power domains not entering retention
  - Cause unknown
  - (am assuming it's still there; userspace problems prevent the test
 from running, probably due to the lock warning)

* 4430es2panda, 4460pandaes: pwrdm state mismatch on CAM, DSS, ABE

* 4460pandaes: pwrdm state mismatch on IVAHD, TESLA 

* 4430es2panda: CORE, TESLA, IVAHD, L3INIT didn't enter target state
  - Probably due to lack of reset code for M3, DSP, SL2IF, FSUSB
per discussion with Tero Kristo
  - Likely dependent on the bootloader version
- fails with 2012.07-00136-g755de79
  - http://marc.info/?l=linux-arm-kernelm=136432340618226w=2

* 4460pandaes: chip not entering retention in dynamic idle
  - Presumably 4430es2panda also fails this
  - Suspend-to-RAM enters full chip retention

* 3730 Beagle XM: does not serial wake from off-idle suspend when console
  UART doesn't clock-gate (debug ignore_loglevel)
  - Cause unknown
  - Not yet part of the automated test suite
  - Re-tested at v3.7; still failing:

http://www.pwsan.com/omap/transcripts/20121211-3730beaglexm-3.7-pm-offmode-fail-debug.txt

Other:

* 4430es2panda: omap_hwmod: l3_instr: _wait_target_disable failed
  - Unknown cause; could be due to the lack of hierarchical enable/disable
in hwmod code
  - Jon Hunter and Santosh Shilimkar report this does not appear with
the same X-loader/bootloader on his 4430ES2.3 Panda, so could be
ES-level dependent


Failing tests: reported by others 
-

- MUSB broken after v3.9-rc6
  - due to commit 92702df3570e1ccfa050e135e50c450502251b79
  - discussion here: http://marc.info/?l=linux-omapm=136544098331552w=2
  - patch pending upstream:
http://marc.info/?l=linux-omapm=136562302329307w=2

vmlinux object size
(delta in bytes from test_v3.9-rc6 
(31880c37c11e28cb81c70757e38392b42e695dc6)):
   text data  bsstotal  kernel
  +506700+5067  n800_multi_omap2xxx
   +97500 +975  n800_only_a
  +113500+1135  omap1_defconfig
  +111900+1119  omap1_defconfig_1510innovator_only
  +113500+1135  omap1_defconfig_5912osk_only
  +125100+1251  omap2plus_defconfig
  +1271   -80+1263  omap2plus_defconfig_cpupm
  +1255  +240+1279  omap2plus_defconfig_no_pm
  +1255   -80+1247  omap2plus_defconfig_omap2_4_only
  +135900+1359

OMAP baseline test results for v3.9-rc6

2013-04-10 Thread Paul Walmsley 

Here are some basic OMAP test results for Linux v3.9-rc6.
Logs and other details at:

http://www.pwsan.com/omap/testlogs/test_v3.9-rc6/20130410123059/


Test summary


Build:
FAIL ( 2/16): am33xx_only, omap2plus_defconfig_2430sdp_only
Pass (14/16): n800_multi_omap2xxx, n800_only_a, omap1_defconfig,
  omap1_defconfig_1510innovator_only, 
  omap1_defconfig_5912osk_only,
  omap2plus_defconfig, omap2plus_defconfig_cpupm,
  omap2plus_defconfig_no_pm,
  omap2plus_defconfig_omap2_4_only,
  omap2plus_defconfig_omap3_4_only,
  rmk_omap3430_ldp_allnoconfig,
  rmk_omap3430_ldp_oldconfig,
  rmk_omap4430_sdp_allnoconfig
  rmk_omap4430_sdp_oldconfig

Boot to userspace:
FAIL ( 1/11): am335xbone
Pass (10/11): 2420n800, 2430sdp, 3517evm, 3530es3beagle,
  3730beaglexm, 37xxevm, 4430es2panda, 4460pandaes,
  5912osk, cmt3517

PM ret, suspend:
FAIL ( 3/ 6): 2430sdp, 37xxevm, 4430es2panda
Pass ( 3/ 6): 3530es3beagle, 3730beaglexm, 4460pandaes

PM ret, dynamic idle:
FAIL ( 4/ 6): 2430sdp, 37xxevm, 4430es2panda, 4460pandaes
Pass ( 2/ 6): 3530es3beagle, 3730beaglexm

PM off, suspend:
FAIL ( 3/ 5): 37xxevm, 4430es2panda, 4460pandaes
Pass ( 2/ 5): 3530es3beagle, 3730beaglexm

PM off, dynamic idle:
FAIL ( 3/ 5): 37xxevm, 4430es2panda, 4460pandaes
Pass ( 2/ 5): 3530es3beagle, 3730beaglexm


Failing tests: fixed by posted patches
--

Build:

* am33xx_only, omap2plus_defconfig_2430sdp_only: omap-{smp,hotplug}.c link 
errors
  - Discussion  RFC patch: 
http://www.spinics.net/lists/arm-kernel/msg230017.html
  - Still needs revision of the patch


Failing tests: needing investigation


Boot tests:

* 3517EVM  CM-T3517: boot hangs with NFS root
  - Likely some Kconfig, board file, and PM issues with EMAC
  - Longstanding bug
  - Not currently part of the automated test suite

Boot warnings:

* CM-T3517: L3 in-band error with IPSS during boot
  - Cause unknown but see 
http://marc.info/?l=linux-omapm=134833869730129w=2
  - Longstanding issue; does not occur on the 3517EVM

PM tests:

* 2430sdp: pwrdm state mismatch(dsp_pwrdm) 0 != 3
  - need to doublecheck wakeup dependencies
  - (am assuming it's still there; userspace problems prevent the test
 from running, probably due to the lock warning)

* 2430sdp: power domains not entering retention
  - Cause unknown
  - (am assuming it's still there; userspace problems prevent the test
 from running, probably due to the lock warning)

* 4430es2panda, 4460pandaes: pwrdm state mismatch on CAM, DSS, ABE

* 4460pandaes: pwrdm state mismatch on IVAHD, TESLA 

* 4430es2panda: CORE, TESLA, IVAHD, L3INIT didn't enter target state
  - Probably due to lack of reset code for M3, DSP, SL2IF, FSUSB
per discussion with Tero Kristo
  - Likely dependent on the bootloader version
- fails with 2012.07-00136-g755de79
  - http://marc.info/?l=linux-arm-kernelm=136432340618226w=2

* 4460pandaes: chip not entering retention in dynamic idle
  - Presumably 4430es2panda also fails this
  - Suspend-to-RAM enters full chip retention

* 3730 Beagle XM: does not serial wake from off-idle suspend when console
  UART doesn't clock-gate (debug ignore_loglevel)
  - Cause unknown
  - Not yet part of the automated test suite
  - Re-tested at v3.7; still failing:

http://www.pwsan.com/omap/transcripts/20121211-3730beaglexm-3.7-pm-offmode-fail-debug.txt

Other:

* 4430es2panda: omap_hwmod: l3_instr: _wait_target_disable failed
  - Unknown cause; could be due to the lack of hierarchical enable/disable
in hwmod code
  - Jon Hunter and Santosh Shilimkar report this does not appear with
the same X-loader/bootloader on his 4430ES2.3 Panda, so could be
ES-level dependent


Failing tests: reported by others 
-

- MUSB broken after v3.9-rc6
  - due to commit 92702df3570e1ccfa050e135e50c450502251b79
  - discussion here: http://marc.info/?l=linux-omapm=136544098331552w=2
  - patch here but needs work:
http://marc.info/?l=linux-kernelm=136554118002341w=2


vmlinux object size
(delta in bytes from test_v3.9-rc5 
(07961ac7c0ee8b546658717034fe692fd12eefa9)):
   text data  bsstotal  kernel
   +579 +104  +64 +747  n800_multi_omap2xxx
   +503  +880 +591  n800_only_a
  +  -400+1071  omap1_defconfig
  +1123  -720+1051  omap1_defconfig_1510innovator_only
  +1107  -320+1075  omap1_defconfig_5912osk_only
  +1291 +2480+1539  omap2plus_defconfig
  +1223 +2160+1439  omap2plus_defconfig_cpupm
  +1287 +1840+1471  omap2plus_defconfig_no_pm
  +1015 +184  +64+1263  omap2plus_defconfig_omap2_4_only
  +1159 +184  +64

Re: OMAP baseline test results for v3.9-rc3

2013-04-02 Thread Paul Walmsley 
Hi

On Wed, 27 Mar 2013, Tero Kristo wrote:

 On Tue, 2013-03-26 at 18:43 +, Paul Walmsley wrote:

  So what I'd like you to do is:
  
  1. Determine what devices are remaining to be reset and idled on OMAP4 
 with the bootloader that I use.  As far as I know, there are only four 
 that block full-chip idle: M3, DSP, SL2IF, FSUSB
  
  2. Determine what's needed to reset and idle them.  For the M3 and DSP, 
 I'd assume this involves pointing the reset vector for those 
 processors at a few lines of code that basically enter WFI or the C64x 
 equivalent.
 
 This is the nasty part. We need firmware support for the blocks to do
 this, and this is imo a complete overkill for the task at hand, as it
 will duplicate the DSP + M3 firmware and drivers at least partially.

Why can't the DSP  M3 go straight from the reset vector to WFI (or the 
C64x equivalent?)  The M3s might need a couple of additional instructions 
to program DEEPSLEEP mode.  What other significant additional code is 
needed for those processors?

 If there was a simple way to do this, don't you think this would have
 been done already a year back when we started to discuss this first
 time? 

No, I don't think it has anything to do with the simplicity of the task.  
My sense is that no one at TI wants to work on it.  I can sympathize, but 
all of us who work on upstream Linux do things that we'd rather not do, 
for a more stable or more maintainable kernel.

So the first thing that should be done is to figure out whether the 
situation is really as bad as was suggested above.  Doesn't it seem 
unlikely that it would be necessary to duplicate the firmware -- which 
does much more than just idle the DSP  M3 -- just to put those subsystems 
into idle?

There's also the reset of the FSUSB IP block, which shouldn't need any 
firmware.  Who's going to work on that one?


- Paul
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: OMAP baseline test results for v3.9-rc3

2013-04-01 Thread Tony Lindgren 
* Tero Kristo t-kri...@ti.com [130327 02:15]:
 On Tue, 2013-03-26 at 18:43 +, Paul Walmsley wrote:
  
  So what I'd like you to do is:
  
  1. Determine what devices are remaining to be reset and idled on OMAP4 
 with the bootloader that I use.  As far as I know, there are only four 
 that block full-chip idle: M3, DSP, SL2IF, FSUSB
  
  2. Determine what's needed to reset and idle them.  For the M3 and DSP, 
 I'd assume this involves pointing the reset vector for those 
 processors at a few lines of code that basically enter WFI or the C64x 
 equivalent.
 
 This is the nasty part. We need firmware support for the blocks to do
 this, and this is imo a complete overkill for the task at hand, as it
 will duplicate the DSP + M3 firmware and drivers at least partially. On
 OMAP3, it was easy as you could just setup the boot mode for IVA and get
 over with it. We don't have similar luxury on OMAP4.
 
 If there was a simple way to do this, don't you think this would have
 been done already a year back when we started to discuss this first
 time? And, a year old bootloader is ancient seeing we didn't have any
 kind of support for OMAP4 core idle in mainline back then and this
 feature was essentially completely untested nobody cared about the
 upstream u-boot PM compatibility before that.

You may be able to have an inline function in the DSP and M3 headers
that idles those modules that can also be called from the reset and idle
function in the hwmod code. That way the driver related code stays in
the driver, but can be called from hwmod reset if the driver is not
compiled in.

Of course if the reset and idle of DSP and M3 gets more complex than
just a few lines of code, then we should just determine that the PM is
broken without those drivers and print out a warning.

Regards,

Tony
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

OMAP baseline test results for v3.9-rc5

2013-03-31 Thread Paul Walmsley 

Here are some basic OMAP test results for Linux v3.9-rc5.
Logs and other details at:

http://www.pwsan.com/omap/testlogs/test_v3.9-rc5/20130331205513/


Test summary


Build:
FAIL ( 2/16): am33xx_only, omap2plus_defconfig_2430sdp_only
Pass (14/16): n800_multi_omap2xxx, n800_only_a, omap1_defconfig,
  omap1_defconfig_1510innovator_only, 
  omap1_defconfig_5912osk_only,
  omap2plus_defconfig, omap2plus_defconfig_cpupm,
  omap2plus_defconfig_no_pm,
  omap2plus_defconfig_omap2_4_only,
  omap2plus_defconfig_omap3_4_only,
  rmk_omap3430_ldp_allnoconfig,
  rmk_omap3430_ldp_oldconfig,
  rmk_omap4430_sdp_allnoconfig
  rmk_omap4430_sdp_oldconfig

Boot to userspace:
FAIL ( 1/11): am335xbone
Pass (10/11): 2420n800, 2430sdp, 3517evm, 3530es3beagle,
  3730beaglexm, 37xxevm, 4430es2panda, 4460pandaes,
  5912osk, cmt3517

PM ret, suspend:
FAIL ( 4/ 6): 2430sdp, 37xxevm, 4430es2panda, 4460pandaes
Pass ( 2/ 6): 3530es3beagle, 3730beaglexm

PM ret, dynamic idle:
FAIL ( 4/ 6): 2430sdp, 37xxevm, 4430es2panda, 4460pandaes
Pass ( 2/ 6): 3530es3beagle, 3730beaglexm

PM off, suspend:
FAIL ( 3/ 5): 37xxevm, 4430es2panda, 4460pandaes
Pass ( 2/ 5): 3530es3beagle, 3730beaglexm

PM off, dynamic idle:
FAIL ( 3/ 5): 37xxevm, 4430es2panda, 4460pandaes
Pass ( 2/ 5): 3530es3beagle, 3730beaglexm


Failing tests: fixed by posted patches
--

Build:

* am33xx_only, omap2plus_defconfig_2430sdp_only: omap-{smp,hotplug}.c link 
errors
  - Discussion  RFC patch: 
http://www.spinics.net/lists/arm-kernel/msg230017.html

PM:

* 37xx EVM: UART sluggishness causes timeouts
  - Caused by commit 1776fd059c40907297d6c26c51876575d63fd9e2 
  - http://marc.info/?l=linux-omapm=136479391601254w=2

* 4460pandaes: CORE, L3INIT didn't enter target state
  - Caused by 17b7e7d33530e2bbd3bdc90f4db09b91cfdde2bb
(ARM: OMAP4: clock/hwmod data: start to remove some IP block control
 clocks)
  - Fixed by ARM: OMAP4: PM: fix PM regression introduced by recent clock
cleanup
- http://www.spinics.net/lists/arm-kernel/msg224419.html


Failing tests: needing investigation


Boot tests:

* 3517EVM  CM-T3517: boot hangs with NFS root
  - Likely some Kconfig, board file, and PM issues with EMAC
  - Longstanding bug
  - Not currently part of the automated test suite

Boot warnings:

* CM-T3517: L3 in-band error with IPSS during boot
  - Cause unknown but see http://marc.info/?l=linux-omapm=134833869730129w=2
  - Longstanding issue; does not occur on the 3517EVM

PM tests:

* 2430sdp: pwrdm state mismatch(dsp_pwrdm) 0 != 3
  - need to doublecheck wakeup dependencies
  - (am assuming it's still there; userspace problems prevent the test
 from running, probably due to the lock warning)

* 2430sdp: power domains not entering retention
  - Cause unknown
  - (am assuming it's still there; userspace problems prevent the test
 from running, probably due to the lock warning)

* 4430es2panda, 4460pandaes: pwrdm state mismatch on CAM, DSS, ABE

* 4460pandaes: pwrdm state mismatch on IVAHD, TESLA 

* 4430es2panda: CORE, TESLA, IVAHD, L3INIT didn't enter target state
  - Probably due to lack of reset code for M3, DSP, SL2IF, FSUSB
per discussion with Tero Kristo
  - Likely dependent on the bootloader version
- fails with 2012.07-00136-g755de79
  - http://marc.info/?l=linux-arm-kernelm=136432340618226w=2

* 4460pandaes: chip not entering retention in dynamic idle
  - Presumably 4430es2panda also fails this
  - Suspend-to-RAM enters full chip retention

* 3730 Beagle XM: does not serial wake from off-idle suspend when console
  UART doesn't clock-gate (debug ignore_loglevel)
  - Cause unknown
  - Not yet part of the automated test suite
  - Re-tested at v3.7; still failing:

http://www.pwsan.com/omap/transcripts/20121211-3730beaglexm-3.7-pm-offmode-fail-debug.txt

Other:

* 4430es2panda: omap_hwmod: l3_instr: _wait_target_disable failed
  - Unknown cause; could be due to the lack of hierarchical enable/disable
in hwmod code
  - Jon Hunter and Santosh Shilimkar report this does not appear with
the same X-loader/bootloader on his 4430ES2.3 Panda, so could be
ES-level dependent


vmlinux object size
(delta in bytes from test_v3.9-rc4 (8bb9660418e05bb1845ac1a2428444d78e322cc7)):
   text data  bsstotal  kernel
   +71100 +711  n800_multi_omap2xxx
   +69500 +695  n800_only_a
   +80900 +809  omap1_defconfig
   +81300 +813  omap1_defconfig_1510innovator_only
+5583029  +312636  +117376  +6013041  omap1_defconfig_5912osk_only
  +4419  -160+4403  omap2plus_defconfig
   +323   -80 +315  omap2plus_defconfig_cpupm

Re: OMAP baseline test results for v3.9-rc3

2013-03-27 Thread Tero Kristo 
On Tue, 2013-03-26 at 18:43 +, Paul Walmsley wrote:
 Hi.
 
 On Tue, 19 Mar 2013, Tero Kristo wrote:
 
  I think you should definitely upgrade your bootloader, the old one you
  are using is prone to cause trouble due to bugs it has, and we have no
  simple way to workaround the issues it causes on kernel side.
 
 So, the kernel should be independent of the bootloader that's used.  Many 
 of the rest of us have taken great care to ensure that devices get reset 
 to do this.  We've got pretty good coverage on OMAP3 and most of the other 
 OMAP4 IP blocks.
 
 You mention that there's no simple way to do it, but as far as I know, no 
 one has assessed what's needed to reset the remaining devices.  Or if 
 someone has this information, it hasn't been shared here - please do so.
 
 So what I'd like you to do is:
 
 1. Determine what devices are remaining to be reset and idled on OMAP4 
with the bootloader that I use.  As far as I know, there are only four 
that block full-chip idle: M3, DSP, SL2IF, FSUSB
 
 2. Determine what's needed to reset and idle them.  For the M3 and DSP, 
I'd assume this involves pointing the reset vector for those 
processors at a few lines of code that basically enter WFI or the C64x 
equivalent.

This is the nasty part. We need firmware support for the blocks to do
this, and this is imo a complete overkill for the task at hand, as it
will duplicate the DSP + M3 firmware and drivers at least partially. On
OMAP3, it was easy as you could just setup the boot mode for IVA and get
over with it. We don't have similar luxury on OMAP4.

If there was a simple way to do this, don't you think this would have
been done already a year back when we started to discuss this first
time? And, a year old bootloader is ancient seeing we didn't have any
kind of support for OMAP4 core idle in mainline back then and this
feature was essentially completely untested nobody cared about the
upstream u-boot PM compatibility before that.

-Tero

 
 3. At this point, we can determine the difficulty level of the task.
 
 4. Then, assuming it's of the level described in step 2, that reset/idle 
code should be implemented.
 
 This process will ensure both that users with old OMAP4 bootloaders -- 
 really, u-boot versions distributed less than a year ago, so not very old 
 at all -- will be able to successfully enter chip low power states.  It 
 will also ensure that users who boot to new kernels with kexec will be 
 able to do so successfully, with a minimum of interference from other 
 devices.
 
 
 - Paul
 --
 To unsubscribe from this list: send the line unsubscribe linux-omap in
 the body of a message to majord...@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 majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

OMAP baseline test results for v3.9-rc4

2013-03-26 Thread Paul Walmsley 

Here are some basic OMAP test results for Linux v3.9-rc4.
Logs and other details at:

http://www.pwsan.com/omap/testlogs/test_v3.9-rc4/20130324120244/


Test summary


Build:
FAIL ( 3/16): am33xx_only, omap1_defconfig_5912osk_only,
  omap2plus_defconfig_2430sdp_only
Pass (13/16): n800_multi_omap2xxx, n800_only_a, omap1_defconfig,
  omap1_defconfig_1510innovator_only, 
  omap2plus_defconfig, omap2plus_defconfig_cpupm,
  omap2plus_defconfig_no_pm,
  omap2plus_defconfig_omap2_4_only,
  omap2plus_defconfig_omap3_4_only,
  rmk_omap3430_ldp_allnoconfig,
  rmk_omap3430_ldp_oldconfig,
  rmk_omap4430_sdp_allnoconfig
  rmk_omap4430_sdp_oldconfig

Boot to userspace:
FAIL ( 1/11): am335xbone
Pass (10/11): 2420n800, 2430sdp, 3517evm, 3530es3beagle,
  3730beaglexm, 37xxevm, 4430es2panda, 4460pandaes,
  5912osk, cmt3517

PM ret, suspend:
FAIL ( 4/ 6): 2430sdp, 37xxevm, 4430es2panda, 4460pandaes
Pass ( 2/ 6): 3530es3beagle, 3730beaglexm

PM ret, dynamic idle:
FAIL ( 4/ 6): 2430sdp, 37xxevm, 4430es2panda, 4460pandaes
Pass ( 2/ 6): 3530es3beagle, 3730beaglexm

PM off, suspend:
FAIL ( 3/ 5): 37xxevm, 4430es2panda, 4460pandaes
Pass ( 2/ 5): 3530es3beagle, 3730beaglexm

PM off, dynamic idle:
FAIL ( 3/ 5): 37xxevm, 4430es2panda, 4460pandaes
Pass ( 2/ 5): 3530es3beagle, 3730beaglexm


Failing tests: fixed by posted patches
--

Build:

* omap1_defconfig_5912osk_only: implicit declaration of function 
'cpu_is_omap15xx'
  - Fixed by Aaro: http://www.spinics.net/lists/linux-omap/msg87523.html

* am33xx_only, omap2plus_defconfig_2430sdp_only: omap-{smp,hotplug}.c link 
errors
  - Discussion  RFC patch: 
http://www.spinics.net/lists/arm-kernel/msg230017.html
  
PM:

* 4460pandaes: CORE, L3INIT didn't enter target state
  - Caused by 17b7e7d33530e2bbd3bdc90f4db09b91cfdde2bb
(ARM: OMAP4: clock/hwmod data: start to remove some IP block control
 clocks)
  - Fixed by ARM: OMAP4: PM: fix PM regression introduced by recent clock
cleanup
- http://www.spinics.net/lists/arm-kernel/msg224419.html


Failing tests: needing investigation


Boot tests:

* 3517EVM  CM-T3517: boot hangs with NFS root
  - Likely some Kconfig, board file, and PM issues with EMAC
  - Longstanding bug

Boot warnings:

* 2430sdp  37xxevm: nasty lock warning due to NFS root
  - Cause unknown
  - Breaks most remaining tests

* CM-T3517: L3 in-band error with IPSS during boot
  - Cause unknown but see http://marc.info/?l=linux-omapm=134833869730129w=2
  - Longstanding issue; does not occur on the 3517EVM

PM tests:

* 2430sdp: pwrdm state mismatch(dsp_pwrdm) 0 != 3
  - need to doublecheck wakeup dependencies
  - (am assuming it's still there; userspace problems prevent the test
 from running, probably due to the lock warning)

* 2430sdp: power domains not entering retention
  - Cause unknown
  - (am assuming it's still there; userspace problems prevent the test
 from running, probably due to the lock warning)

* 4430es2panda, 4460pandaes: pwrdm state mismatch on CAM, DSS, ABE

* 4460pandaes: pwrdm state mismatch on IVAHD, TESLA 

* 4430es2panda: CORE, TESLA, IVAHD, L3INIT didn't enter target state
  - Probably due to lack of reset code for M3, DSP, SL2IF, FSUSB
per discussion with Tero Kristo
  - Likely dependent on the bootloader version
- fails with 2012.07-00136-g755de79

* 4460pandaes: chip not entering retention in dynamic idle
  - Presumably 4430es2panda also fails this
  - Suspend-to-RAM enters full chip retention

* 3730 Beagle XM: does not serial wake from off-idle suspend when console
  UART doesn't clock-gate (debug ignore_loglevel)
  - Cause unknown
  - Not yet part of the automated test suite
  - Re-tested at v3.7; still failing:

http://www.pwsan.com/omap/transcripts/20121211-3730beaglexm-3.7-pm-offmode-fail-debug.txt

Other:

* 4430es2panda: omap_hwmod: l3_instr: _wait_target_disable failed
  - Unknown cause; could be due to the lack of hierarchical enable/disable
in hwmod code
  - Jon Hunter and Santosh Shilimkar report this does not appear with
the same X-loader/bootloader on his 4430ES2.3 Panda, so could be
ES-level dependent


vmlinux object size
(delta in bytes from test_v3.9-rc3 
(a937536b868b8369b98967929045f1df54234323)):
   text data  bsstotal  kernel
   +188  +640 +252  n800_multi_omap2xxx
   +188  +640 +252  n800_only_a
   +972  +640+1036  omap1_defconfig
   +956  +640+1020  omap1_defconfig_1510innovator_only
  +225600+2256  omap2plus_defconfig
  +225600+2256  omap2plus_defconfig_cpupm
  +2192  +640+2256  omap2plus_defconfig_no_pm
  +2320  +64

Re: OMAP baseline test results for v3.9-rc3

2013-03-26 Thread Paul Walmsley 
Hi

On Tue, 19 Mar 2013, Santosh Shilimkar wrote:

 On Monday 18 March 2013 09:08 PM, Paul Walmsley wrote:

  Test summary
  
  
 Thanks for the summary Paul. A usual, it is quite exhaustive.

Would that it were true.  These tests are really only very superficial.  
Here are some major missing areas:

- other devices (audio, video, etc.)
- stability testing - does the board hang or freeze across 24 hours to 
  a week of uptime?
- CPU DVFS
- current consumption during active, ret idle, off idle
- multiple bootloaders
- multiple rootfs originations (across boards that support several) -- 
  e.g., NFS, MMC, etc.

If I were basing anything off the mainline kernel, that's the minimum I'd 
like to see.

  
  * 4430es2panda, 4460pandaes: pwrdm state mismatch on CAM, DSS, ABE
  
 I thought we discussed about boot-loader dependency already. 
 
  * 4460pandaes: pwrdm state mismatch on IVAHD, TESLA 
  
 Same here.

Have these issues been confirmed to be bootloader-related?

If so, then we can mark these as cases where the kernel isn't resetting 
devices properly.

  * 4430es2panda: CORE, TESLA, IVAHD, L3INIT didn't enter target state
- Probably due to lack of reset code for M3, DSP, SL2IF, FSUSB
  per discussion with Tero Kristo
- Likely dependent on the bootloader version
  - fails with 2012.07-00136-g755de79
  
 Do you still see the issue after upgrading the boot-loader version ?

Haven't tried yet.

  * 4460pandaes: chip not entering retention in dynamic idle
- Presumably 4430es2panda also fails this
- Suspend-to-RAM enters full chip retention
  
 Assuming dynmic idle is CPUIdle, core retention isn't supported
 in CPUDILE so it is expected

No, it's not CPUIdle.  It's simply echoing a power management timeout to 
the UART autosuspend sysfs entries.  You can see exactly what's done by 
checking the pm/ directory in the test logs, for example:

http://www.pwsan.com/omap/testlogs/test_v3.9-rc4/20130324120244/pm/

OMAP4 should be able to enter full-chip retention idle without CPUIdle, as 
OMAP3 does.  If the current kernel depends on CPUIdle to do this on OMAP4, 
that's a bug.

  Other:
  
  * 4430es2panda: omap_hwmod: l3_instr: _wait_target_disable failed
- Unknown cause; could be due to the lack of hierarchical enable/disable
  in hwmod code
- Jon Hunter reports this does not appear with the same 
  X-loader/bootloader
  on his 4430ES2.3 Panda, so could be ES-level dependent
 I confirm Jon's observation even on my OMAP4430 ES2.3 SDP.

Thanks, I put this in the v3.9-rc4 README.


- Paul
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: OMAP baseline test results for v3.9-rc3

2013-03-26 Thread Paul Walmsley 
Hi.

On Tue, 19 Mar 2013, Tero Kristo wrote:

 I think you should definitely upgrade your bootloader, the old one you
 are using is prone to cause trouble due to bugs it has, and we have no
 simple way to workaround the issues it causes on kernel side.

So, the kernel should be independent of the bootloader that's used.  Many 
of the rest of us have taken great care to ensure that devices get reset 
to do this.  We've got pretty good coverage on OMAP3 and most of the other 
OMAP4 IP blocks.

You mention that there's no simple way to do it, but as far as I know, no 
one has assessed what's needed to reset the remaining devices.  Or if 
someone has this information, it hasn't been shared here - please do so.

So what I'd like you to do is:

1. Determine what devices are remaining to be reset and idled on OMAP4 
   with the bootloader that I use.  As far as I know, there are only four 
   that block full-chip idle: M3, DSP, SL2IF, FSUSB

2. Determine what's needed to reset and idle them.  For the M3 and DSP, 
   I'd assume this involves pointing the reset vector for those 
   processors at a few lines of code that basically enter WFI or the C64x 
   equivalent.

3. At this point, we can determine the difficulty level of the task.

4. Then, assuming it's of the level described in step 2, that reset/idle 
   code should be implemented.

This process will ensure both that users with old OMAP4 bootloaders -- 
really, u-boot versions distributed less than a year ago, so not very old 
at all -- will be able to successfully enter chip low power states.  It 
will also ensure that users who boot to new kernels with kexec will be 
able to do so successfully, with a minimum of interference from other 
devices.


- Paul
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

RE: OMAP baseline test results for v3.9-rc1

2013-03-26 Thread Paul Walmsley 
Hi,

On Thu, 14 Mar 2013, Hiremath, Vaibhav wrote:

  -Original Message-
  From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
  ow...@vger.kernel.org] On Behalf Of Paul Walmsley
  Sent: Tuesday, March 12, 2013 10:10 PM
  To: linux-omap@vger.kernel.org
  Cc: linux-arm-ker...@lists.infradead.org
  Subject: OMAP baseline test results for v3.9-rc1
  
  
  Here are some basic OMAP test results for Linux v3.9-rc1.
  Logs and other details at:
  
  http://www.pwsan.com/omap/testlogs/test_v3.9-rc1/20130312100243/
  
  
  Test summary
  
  
  Build:
  FAIL ( 4/16): am33xx_only, omap1_defconfig,
 This requires some cleanup in Makefile and Kconfig handling,
 
 Either you disable SMP support for non-SMP devices like AM33xx 
 
 OR
 
 Fix the Makefile to resolve the build dependencies (may not be trivial)
 
 OR
 
 Make functions __weak so that build will go through.
 
 
 
 I have created below patch, if it is ok with you then I can
 Submit patch for the same (build tested with am33xx_only and 
 omap2plus_defconfig).

Santosh's suggestion seems the right way to go.  Care to implement a patch 
for #2 above?


- Paul
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: OMAP baseline test results for v3.9-rc3

2013-03-19 Thread Santosh Shilimkar 
+ Tero,

On Monday 18 March 2013 09:08 PM, Paul Walmsley wrote:
 
 Here are some basic OMAP test results for Linux v3.9-rc3.
 Logs and other details at:
 
 http://www.pwsan.com/omap/testlogs/test_v3.9-rc3/20130314094808/
 
 
 Test summary
 
 
Thanks for the summary Paul. A usual, it is quite exhaustive. Few
questions and comments below.

[..]

 Failing tests: needing investigation
 
 

[..]

 PM tests:
 
[..]

 
 * 4430es2panda, 4460pandaes: pwrdm state mismatch on CAM, DSS, ABE
 
I thought we discussed about boot-loader dependency already. 

 * 4460pandaes: pwrdm state mismatch on IVAHD, TESLA 
 
Same here.

 * 4430es2panda: CORE, TESLA, IVAHD, L3INIT didn't enter target state
   - Probably due to lack of reset code for M3, DSP, SL2IF, FSUSB
 per discussion with Tero Kristo
   - Likely dependent on the bootloader version
 - fails with 2012.07-00136-g755de79
 
Do you still see the issue after upgrading the boot-loader version ?

 * 4460pandaes: chip not entering retention in dynamic idle
   - Presumably 4430es2panda also fails this
   - Suspend-to-RAM enters full chip retention
 
Assuming dynmic idle is CPUIdle, core retention isn't supported
in CPUDILE so it is expected

 
 Other:
 
 * 4430es2panda: omap_hwmod: l3_instr: _wait_target_disable failed
   - Unknown cause; could be due to the lack of hierarchical enable/disable
 in hwmod code
   - Jon Hunter reports this does not appear with the same X-loader/bootloader
 on his 4430ES2.3 Panda, so could be ES-level dependent
I confirm Jon's observation even on my OMAP4430 ES2.3 SDP.

Regards,
Santosh

--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: OMAP baseline test results for v3.9-rc3

2013-03-19 Thread Tero Kristo 
On Tue, 2013-03-19 at 14:21 +0530, Santosh Shilimkar wrote:
 + Tero,
 
 On Monday 18 March 2013 09:08 PM, Paul Walmsley wrote:
  
  Here are some basic OMAP test results for Linux v3.9-rc3.
  Logs and other details at:
  
  http://www.pwsan.com/omap/testlogs/test_v3.9-rc3/20130314094808/
  
  
  Test summary
  
  
 Thanks for the summary Paul. A usual, it is quite exhaustive. Few
 questions and comments below.
 
 [..]
 
  Failing tests: needing investigation
  
  
 
 [..]
 
  PM tests:
  
 [..]
 
  
  * 4430es2panda, 4460pandaes: pwrdm state mismatch on CAM, DSS, ABE
  
 I thought we discussed about boot-loader dependency already. 
 
  * 4460pandaes: pwrdm state mismatch on IVAHD, TESLA 
  
 Same here.
 
  * 4430es2panda: CORE, TESLA, IVAHD, L3INIT didn't enter target state
- Probably due to lack of reset code for M3, DSP, SL2IF, FSUSB
  per discussion with Tero Kristo
- Likely dependent on the bootloader version
  - fails with 2012.07-00136-g755de79
  
 Do you still see the issue after upgrading the boot-loader version ?

I think you should definitely upgrade your bootloader, the old one you
are using is prone to cause trouble due to bugs it has, and we have no
simple way to workaround the issues it causes on kernel side.

-Tero


--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

OMAP baseline test results for v3.9-rc3

2013-03-18 Thread Paul Walmsley 

Here are some basic OMAP test results for Linux v3.9-rc3.
Logs and other details at:

http://www.pwsan.com/omap/testlogs/test_v3.9-rc3/20130314094808/


Test summary


Build:
FAIL ( 3/16): am33xx_only, omap1_defconfig_5912osk_only,
  omap2plus_defconfig_2430sdp_only
Pass (13/16): n800_multi_omap2xxx, n800_only_a, omap1_defconfig,
  omap1_defconfig_1510innovator_only, 
  omap2plus_defconfig, omap2plus_defconfig_cpupm,
  omap2plus_defconfig_no_pm,
  omap2plus_defconfig_omap2_4_only,
  omap2plus_defconfig_omap3_4_only,
  rmk_omap3430_ldp_allnoconfig,
  rmk_omap3430_ldp_oldconfig,
  rmk_omap4430_sdp_allnoconfig
  rmk_omap4430_sdp_oldconfig

Boot to userspace:
FAIL ( 1/11): am335xbone
Pass (10/11): 2420n800, 2430sdp, 3517evm, 3530es3beagle,
  3730beaglexm, 37xxevm, 4430es2panda, 4460pandaes,
  5912osk, cmt3517

PM ret, suspend:
FAIL ( 4/ 6): 2430sdp, 37xxevm, 4430es2panda, 4460pandaes
Pass ( 2/ 6): 3530es3beagle, 3730beaglexm

PM ret, dynamic idle:
FAIL ( 4/ 6): 2430sdp, 37xxevm, 4430es2panda, 4460pandaes
Pass ( 2/ 6): 3530es3beagle, 3730beaglexm

PM off, suspend:
FAIL ( 3/ 5): 37xxevm, 4430es2panda, 4460pandaes
Pass ( 2/ 5): 3530es3beagle, 3730beaglexm

PM off, dynamic idle:
FAIL ( 3/ 5): 37xxevm, 4430es2panda, 4460pandaes
Pass ( 2/ 5): 3530es3beagle, 3730beaglexm


Failing tests: fixed by posted patches
--

Build:

* omap1_defconfig_5912osk_only: implicit declaration of function 
'cpu_is_omap15xx'
  - Fixed by Aaro: http://www.spinics.net/lists/linux-omap/msg87523.html

PM:

* 4460pandaes: CORE, L3INIT didn't enter target state
  - Caused by 17b7e7d33530e2bbd3bdc90f4db09b91cfdde2bb
(ARM: OMAP4: clock/hwmod data: start to remove some IP block control
 clocks)
  - Fixed by ARM: OMAP4: PM: fix PM regression introduced by recent clock
cleanup
- http://www.spinics.net/lists/arm-kernel/msg224419.html

Failing tests: needing investigation


Build:

* am33xx_only, omap2plus_defconfig_2430sdp_only: omap-{smp,hotplug}.c link 
errors

Boot tests:

* 3517EVM  CM-T3517: boot hangs with NFS root
  - Likely some Kconfig, board file, and PM issues with EMAC
  - Longstanding bug

Boot warnings:

* 2430sdp  37xxevm: nasty lock warning due to NFS root
  - Cause unknown
  - Breaks most remaining tests

* CM-T3517: L3 in-band error with IPSS during boot
  - Cause unknown but see http://marc.info/?l=linux-omapm=134833869730129w=2
  - Longstanding issue; does not occur on the 3517EVM

PM tests:

* 2430sdp: pwrdm state mismatch(dsp_pwrdm) 0 != 3
  - need to doublecheck wakeup dependencies
  - (am assuming it's still there; userspace problems prevent the test
 from running, probably due to the lock warning)

* 2430sdp: power domains not entering retention
  - Cause unknown
  - (am assuming it's still there; userspace problems prevent the test
 from running, probably due to the lock warning)

* 4430es2panda, 4460pandaes: pwrdm state mismatch on CAM, DSS, ABE

* 4460pandaes: pwrdm state mismatch on IVAHD, TESLA 

* 4430es2panda: CORE, TESLA, IVAHD, L3INIT didn't enter target state
  - Probably due to lack of reset code for M3, DSP, SL2IF, FSUSB
per discussion with Tero Kristo
  - Likely dependent on the bootloader version
- fails with 2012.07-00136-g755de79

* 4460pandaes: chip not entering retention in dynamic idle
  - Presumably 4430es2panda also fails this
  - Suspend-to-RAM enters full chip retention

* 3730 Beagle XM: does not serial wake from off-idle suspend when console
  UART doesn't clock-gate (debug ignore_loglevel)
  - Cause unknown
  - Not yet part of the automated test suite
  - Re-tested at v3.7; still failing:

http://www.pwsan.com/omap/transcripts/20121211-3730beaglexm-3.7-pm-offmode-fail-debug.txt

Other:

* 4430es2panda: omap_hwmod: l3_instr: _wait_target_disable failed
  - Unknown cause; could be due to the lack of hierarchical enable/disable
in hwmod code
  - Jon Hunter reports this does not appear with the same X-loader/bootloader
on his 4430ES2.3 Panda, so could be ES-level dependent


vmlinux object size
(delta in bytes from test_v3.9-rc2 
(f6161aa153581da4a3867a2d1a7caf4be19b6ec9)):
   text data  bsstotal  kernel
+72  -640   +8  n800_multi_omap2xxx
+56  -640   -8  n800_only_a
+5606576  +359420  +121728  +6087724  omap1_defconfig
   +108+25920+2700  omap1_defconfig_1510innovator_only
   +640+25680+3208  omap2plus_defconfig
   +704+25600+3264  omap2plus_defconfig_cpupm
   +704+25600+3264  omap2plus_defconfig_no_pm
   +640+25600+3200  omap2plus_defconfig_omap2_4_only
   +628+25760+3204

Re: OMAP baseline test results for v3.9-rc3

2013-03-18 Thread Anca Emanuel 
You are not planning any resources to solve this ?
You are listing this for a number of months now. It is time to solve them.

On Mon, Mar 18, 2013 at 5:38 PM, Paul Walmsley p...@pwsan.com wrote:

 Here are some basic OMAP test results for Linux v3.9-rc3.
 Logs and other details at:

 http://www.pwsan.com/omap/testlogs/test_v3.9-rc3/20130314094808/


 Test summary
 

 Build:
 FAIL ( 3/16): am33xx_only, omap1_defconfig_5912osk_only,
   omap2plus_defconfig_2430sdp_only
 Pass (13/16): n800_multi_omap2xxx, n800_only_a, omap1_defconfig,
   omap1_defconfig_1510innovator_only,
   omap2plus_defconfig, omap2plus_defconfig_cpupm,
   omap2plus_defconfig_no_pm,
   omap2plus_defconfig_omap2_4_only,
   omap2plus_defconfig_omap3_4_only,
   rmk_omap3430_ldp_allnoconfig,
   rmk_omap3430_ldp_oldconfig,
   rmk_omap4430_sdp_allnoconfig
   rmk_omap4430_sdp_oldconfig

 Boot to userspace:
 FAIL ( 1/11): am335xbone
 Pass (10/11): 2420n800, 2430sdp, 3517evm, 3530es3beagle,
   3730beaglexm, 37xxevm, 4430es2panda, 4460pandaes,
   5912osk, cmt3517

 PM ret, suspend:
 FAIL ( 4/ 6): 2430sdp, 37xxevm, 4430es2panda, 4460pandaes
 Pass ( 2/ 6): 3530es3beagle, 3730beaglexm

 PM ret, dynamic idle:
 FAIL ( 4/ 6): 2430sdp, 37xxevm, 4430es2panda, 4460pandaes
 Pass ( 2/ 6): 3530es3beagle, 3730beaglexm

 PM off, suspend:
 FAIL ( 3/ 5): 37xxevm, 4430es2panda, 4460pandaes
 Pass ( 2/ 5): 3530es3beagle, 3730beaglexm

 PM off, dynamic idle:
 FAIL ( 3/ 5): 37xxevm, 4430es2panda, 4460pandaes
 Pass ( 2/ 5): 3530es3beagle, 3730beaglexm


 Failing tests: fixed by posted patches
 --

 Build:

 * omap1_defconfig_5912osk_only: implicit declaration of function 
 'cpu_is_omap15xx'
   - Fixed by Aaro: http://www.spinics.net/lists/linux-omap/msg87523.html

 PM:

 * 4460pandaes: CORE, L3INIT didn't enter target state
   - Caused by 17b7e7d33530e2bbd3bdc90f4db09b91cfdde2bb
 (ARM: OMAP4: clock/hwmod data: start to remove some IP block control
  clocks)
   - Fixed by ARM: OMAP4: PM: fix PM regression introduced by recent clock
 cleanup
 - http://www.spinics.net/lists/arm-kernel/msg224419.html

 Failing tests: needing investigation
 

 Build:

 * am33xx_only, omap2plus_defconfig_2430sdp_only: omap-{smp,hotplug}.c link 
 errors

 Boot tests:

 * 3517EVM  CM-T3517: boot hangs with NFS root
   - Likely some Kconfig, board file, and PM issues with EMAC
   - Longstanding bug

 Boot warnings:

 * 2430sdp  37xxevm: nasty lock warning due to NFS root
   - Cause unknown
   - Breaks most remaining tests

 * CM-T3517: L3 in-band error with IPSS during boot
   - Cause unknown but see http://marc.info/?l=linux-omapm=134833869730129w=2
   - Longstanding issue; does not occur on the 3517EVM

 PM tests:

 * 2430sdp: pwrdm state mismatch(dsp_pwrdm) 0 != 3
   - need to doublecheck wakeup dependencies
   - (am assuming it's still there; userspace problems prevent the test
  from running, probably due to the lock warning)

 * 2430sdp: power domains not entering retention
   - Cause unknown
   - (am assuming it's still there; userspace problems prevent the test
  from running, probably due to the lock warning)

 * 4430es2panda, 4460pandaes: pwrdm state mismatch on CAM, DSS, ABE

 * 4460pandaes: pwrdm state mismatch on IVAHD, TESLA

 * 4430es2panda: CORE, TESLA, IVAHD, L3INIT didn't enter target state
   - Probably due to lack of reset code for M3, DSP, SL2IF, FSUSB
 per discussion with Tero Kristo
   - Likely dependent on the bootloader version
 - fails with 2012.07-00136-g755de79

 * 4460pandaes: chip not entering retention in dynamic idle
   - Presumably 4430es2panda also fails this
   - Suspend-to-RAM enters full chip retention

 * 3730 Beagle XM: does not serial wake from off-idle suspend when console
   UART doesn't clock-gate (debug ignore_loglevel)
   - Cause unknown
   - Not yet part of the automated test suite
   - Re-tested at v3.7; still failing:
 
 http://www.pwsan.com/omap/transcripts/20121211-3730beaglexm-3.7-pm-offmode-fail-debug.txt

 Other:

 * 4430es2panda: omap_hwmod: l3_instr: _wait_target_disable failed
   - Unknown cause; could be due to the lack of hierarchical enable/disable
 in hwmod code
   - Jon Hunter reports this does not appear with the same X-loader/bootloader
 on his 4430ES2.3 Panda, so could be ES-level dependent


 vmlinux object size
 (delta in bytes from test_v3.9-rc2
 (f6161aa153581da4a3867a2d1a7caf4be19b6ec9)):
text data  bsstotal  kernel
 +72  -640   +8  n800_multi_omap2xxx
 +56  -640   -8  n800_only_a
 +5606576  +359420  +121728  +6087724  omap1_defconfig
+108+25920+2700  omap1_defconfig_1510innovator_only

Re: OMAP baseline test results for v3.9-rc3

2013-03-18 Thread Paul Walmsley 
On Mon, 18 Mar 2013, Anca Emanuel wrote:

 You are not planning any resources to solve this ?
 You are listing this for a number of months now. It is time to solve them.

Absolutely, thanks for volunteering!  Patches welcome.


- Paul
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: OMAP baseline test results for v3.9-rc3

2013-03-18 Thread Paul Walmsley 
On Mon, 18 Mar 2013, Paul Walmsley wrote:

 On Mon, 18 Mar 2013, Anca Emanuel wrote:
 
  You are not planning any resources to solve this ?
  You are listing this for a number of months now. It is time to solve them.
 
 Absolutely, thanks for volunteering!  Patches welcome.

Also, if you are a TI customer, you can probably contact your TI rep and 
put pressure on them to put more resources into their upstream kernel 
support.


- Paul
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: OMAP baseline test results for v3.9-rc2

2013-03-18 Thread Paul Walmsley 
Hi,

restating these to reflect some bugfixes in the test log parsing scripts.

On Thu, 14 Mar 2013, Paul Walmsley wrote:

 vmlinux object size
 (delta in bytes from test_v3.9-rc1 
 (6dbe51c251a327e012439c4772097a13df43c5b8)):
text data  bsstotal  kernel
  +13528  +640   +13592  omap1_defconfig
   +9440 +1200+9560  omap2plus_defconfig
  +13472 +1280   +13600  omap2plus_defconfig_cpupm
  +13472 +1280   +13600  omap2plus_defconfig_omap2_4_only
   +9756 +1200+9876  omap2plus_defconfig_omap3_4_only
+704  -64 -188 +452  rmk_omap3430_ldp_allnoconfig
+556  -640 +492  rmk_omap4430_sdp_oldconfig

The correct and complete delta should be:

vmlinux object size
(delta in bytes from test_v3.9-rc1 
(6dbe51c251a327e012439c4772097a13df43c5b8)):
   text data  bsstotal  kernel
   +620  -72   +4 +552  n800_multi_omap2xxx
  +5860 +648  +12+6520  n800_only_a
  +9180  +880+9268  omap1_defconfig_1510innovator_only
  +9440 +1200+9560  omap2plus_defconfig
 +13472 +1280   +13600  omap2plus_defconfig_cpupm
 +13528  +640   +13592  omap2plus_defconfig_no_pm
 +13472 +1280   +13600  omap2plus_defconfig_omap2_4_only
  +9756 +1200+9876  omap2plus_defconfig_omap3_4_only
   +704  -64 -188 +452  rmk_omap3430_ldp_allnoconfig
   +656  -640 +592  rmk_omap3430_ldp_oldconfig
   +704  -64 -188 +452  rmk_omap4430_sdp_allnoconfig
   +556  -640 +492  rmk_omap4430_sdp_oldconfig


- Paul
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: OMAP baseline test results for v3.9-rc1

2013-03-18 Thread Paul Walmsley 
Hi,

here's the restated delta from v3.8 - v3.9-rc1, after some script bug 
fixes.

On Tue, 12 Mar 2013, Paul Walmsley wrote:

 vmlinux object size
 (delta in bytes from test_v3.8 (19f949f52599ba7c3f67a5897ac6be14bfcb1200)):
text data  bsstotal  kernel
 +195310   +37968+1364  +234642  omap2plus_defconfig
 +185362   +37128+1364  +223854  omap2plus_defconfig_cpupm
 +186719   +31416+1300  +219435  omap2plus_defconfig_omap2_4_only
 +181125   +41432+1300  +223857  omap2plus_defconfig_omap3_4_only
  +10460   +10272+1184   +21916  rmk_omap3430_ldp_allnoconfig
  +40867   +14672 +972   +56511  rmk_omap4430_sdp_oldconfig
 
 Looks like v3.9 is well on target to exceed even the previous 
 per-release bloat records.
 
 There are some entries missing from the above table; this is probably due 
 to some bug in my scripts that needs to be dealt with.

And here's the correct results.

vmlinux object size
(delta in bytes from test_v3.8 
(19f949f52599ba7c3f67a5897ac6be14bfcb1200)):
   text data  bsstotal  kernel
-557629   +23472-9252  -543409  n800_multi_omap2xxx
-557204   +26680-9280  -539804  n800_only_a
 +49056+2992 +424   +52472  omap1_defconfig_1510innovator_only
+195310   +37968+1364  +234642  omap2plus_defconfig
+185362   +37128+1364  +223854  omap2plus_defconfig_cpupm
+192610   +36304+1364  +230278  omap2plus_defconfig_no_pm
+186719   +31416+1300  +219435  omap2plus_defconfig_omap2_4_only
+181125   +41432+1300  +223857  omap2plus_defconfig_omap3_4_only
 +10460   +10272+1184   +21916  rmk_omap3430_ldp_allnoconfig
 +40004   +27640 +788   +68432  rmk_omap3430_ldp_oldconfig
 +10348   +10272+1296   +21916  rmk_omap4430_sdp_allnoconfig
 +40867   +14672 +972   +56511  rmk_omap4430_sdp_oldconfig

The massive decrease in N800 kernel size is a result of an all-out attempt 
to keep the kernel booting on N800, which has a 2MB kernel size limitation 
in the bootloader.

Same crazy bloat in the OMAP2+ kernels, and it's probably due to the 
CONFIG_ARCH_MULTIPLATFORM changes.  Hey, at least we don't have to worry 
about supporting embedded use-cases any more on ARM ;-)


- Paul
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

RE: OMAP baseline test results for v3.9-rc1

2013-03-14 Thread Hiremath, Vaibhav 

 -Original Message-
 From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
 ow...@vger.kernel.org] On Behalf Of Paul Walmsley
 Sent: Tuesday, March 12, 2013 10:10 PM
 To: linux-omap@vger.kernel.org
 Cc: linux-arm-ker...@lists.infradead.org
 Subject: OMAP baseline test results for v3.9-rc1
 
 
 Here are some basic OMAP test results for Linux v3.9-rc1.
 Logs and other details at:
 
 http://www.pwsan.com/omap/testlogs/test_v3.9-rc1/20130312100243/
 
 
 Test summary
 
 
 Build:
 FAIL ( 4/16): am33xx_only, omap1_defconfig,
This requires some cleanup in Makefile and Kconfig handling,

Either you disable SMP support for non-SMP devices like AM33xx 

OR

Fix the Makefile to resolve the build dependencies (may not be trivial)

OR

Make functions __weak so that build will go through.



I have created below patch, if it is ok with you then I can
Submit patch for the same (build tested with am33xx_only and 
omap2plus_defconfig).




diff --git a/arch/arm/mach-omap2/common.h b/arch/arm/mach-omap2/common.h
index 0a6b9c7..cb0d55d 100644
--- a/arch/arm/mach-omap2/common.h
+++ b/arch/arm/mach-omap2/common.h
@@ -233,9 +233,9 @@ extern void omap_do_wfi(void);
 /* Needed for secondary core boot */
 extern void omap_secondary_startup(void);
 extern void omap_secondary_startup_4460(void);
-extern u32 omap_modify_auxcoreboot0(u32 set_mask, u32 clear_mask);
-extern void omap_auxcoreboot_addr(u32 cpu_addr);
-extern u32 omap_read_auxcoreboot0(void);
+extern u32 __weak omap_modify_auxcoreboot0(u32 set_mask, u32 clear_mask);
+extern void __weak omap_auxcoreboot_addr(u32 cpu_addr);
+extern u32 __weak omap_read_auxcoreboot0(void);

 extern void omap4_cpu_die(unsigned int cpu);

@@ -249,7 +249,7 @@ extern int omap4_mpuss_init(void);
 extern int omap4_enter_lowpower(unsigned int cpu, unsigned int power_state);
 extern int omap4_finish_suspend(unsigned long cpu_state);
 extern void omap4_cpu_resume(void);
-extern int omap4_hotplug_cpu(unsigned int cpu, unsigned int power_state);
+extern int __weak omap4_hotplug_cpu(unsigned int cpu, unsigned int 
power_state);
 extern u32 omap4_mpuss_read_prev_context_state(void);
 #else
 static inline int omap4_enter_lowpower(unsigned int cpu,
diff --git a/arch/arm/mach-omap2/omap-wakeupgen.h 
b/arch/arm/mach-omap2/omap-wakeupgen.h
index b0fd16f..94f5281 100644
--- a/arch/arm/mach-omap2/omap-wakeupgen.h
+++ b/arch/arm/mach-omap2/omap-wakeupgen.h
@@ -33,6 +33,6 @@
 #define OMAP_TIMESTAMPCYCLEHI  0xc0c

 extern int __init omap_wakeupgen_init(void);
-extern void __iomem *omap_get_wakeupgen_base(void);
-extern int omap_secure_apis_support(void);
+extern void __weak __iomem *omap_get_wakeupgen_base(void);
+extern int __weak omap_secure_apis_support(void);
 #endif



Thanks,
Vaibhav
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: OMAP baseline test results for v3.9-rc1

2013-03-14 Thread Santosh Shilimkar 
On Thursday 14 March 2013 04:59 PM, Hiremath, Vaibhav wrote:
 
 -Original Message-
 From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
 ow...@vger.kernel.org] On Behalf Of Paul Walmsley
 Sent: Tuesday, March 12, 2013 10:10 PM
 To: linux-omap@vger.kernel.org
 Cc: linux-arm-ker...@lists.infradead.org
 Subject: OMAP baseline test results for v3.9-rc1


 Here are some basic OMAP test results for Linux v3.9-rc1.
 Logs and other details at:

 http://www.pwsan.com/omap/testlogs/test_v3.9-rc1/20130312100243/


 Test summary
 

 Build:
 FAIL ( 4/16): am33xx_only, omap1_defconfig,
 This requires some cleanup in Makefile and Kconfig handling,
 
 Either you disable SMP support for non-SMP devices like AM33xx 
 
 OR
 
 Fix the Makefile to resolve the build dependencies (may not be trivial)
 
This one... Better things is not to build the OMAP4 files for AM33XX only build.
Even if it is not trivial, its right way of fixing the issue.

Regards,
Santosh
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

OMAP baseline test results for v3.9-rc2

2013-03-14 Thread Paul Walmsley 

Here are some basic OMAP test results for Linux v3.9-rc2.
Logs and other details at:

http://www.pwsan.com/omap/testlogs/test_v3.9-rc2/20130314094808/


Test summary


Build:
FAIL ( 4/16): am33xx_only, omap1_defconfig,
  omap1_defconfig_5912osk_only,
  omap2plus_defconfig_2430sdp_only
Pass (12/16): n800_multi_omap2xxx, n800_only_a,
  omap1_defconfig_1510innovator_only, 
  omap2plus_defconfig, omap2plus_defconfig_cpupm,
  omap2plus_defconfig_no_pm,
  omap2plus_defconfig_omap2_4_only,
  omap2plus_defconfig_omap3_4_only,
  rmk_omap3430_ldp_allnoconfig,
  rmk_omap3430_ldp_oldconfig,
  rmk_omap4430_sdp_allnoconfig
  rmk_omap4430_sdp_oldconfig

Boot to userspace:
FAIL ( 4/11): 2430sdp, 37xxevm, 5912osk, am335xbone
Pass ( 7/11): 2420n800, 3517evm, 3530es3beagle,
  3730beaglexm, 4430es2panda, 4460pandaes,
  cmt3517

PM ret, suspend:
FAIL ( 4/ 6): 2430sdp, 37xxevm, 4430es2panda, 4460pandaes
Pass ( 2/ 6): 3530es3beagle, 3730beaglexm

PM ret, dynamic idle:
FAIL ( 4/ 6): 2430sdp, 37xxevm, 4430es2panda, 4460pandaes
Pass ( 2/ 6): 3530es3beagle, 3730beaglexm

PM off, suspend:
FAIL ( 3/ 5): 37xxevm, 4430es2panda, 4460pandaes
Pass ( 2/ 5): 3530es3beagle, 3730beaglexm

PM off, dynamic idle:
FAIL ( 3/ 5): 37xxevm, 4430es2panda, 4460pandaes
Pass ( 2/ 5): 3530es3beagle, 3730beaglexm


Failing tests: fixed by posted patches
--

Build:

* omap1_defconfig: several problems with mach-omap1/board-h2.c
  - Fixed by Tony: http://www.spinics.net/lists/arm-kernel/msg224133.html

* omap1_defconfig_5912osk_only: implicit declaration of function 
'cpu_is_omap15xx'
  - Fixed by Aaro: http://www.spinics.net/lists/linux-omap/msg87523.html

PM:

* 4460pandaes: CORE, L3INIT didn't enter target state
  - Caused by 17b7e7d33530e2bbd3bdc90f4db09b91cfdde2bb
(ARM: OMAP4: clock/hwmod data: start to remove some IP block control
 clocks)
  - Fixed by ARM: OMAP4: PM: fix PM regression introduced by recent clock
cleanup
- http://www.spinics.net/lists/arm-kernel/msg224419.html

Failing tests: needing investigation


Build:

* am33xx_only, omap2plus_defconfig_2430sdp_only: omap-{smp,hotplug}.c link 
errors

Boot tests:

* 2430sdp  37xxevm: hang during MMC partition probe
  - Cause unknown

* 3517EVM  CM-T3517: boot hangs with NFS root
  - Likely some Kconfig, board file, and PM issues with EMAC
  - Longstanding bug

Boot warnings:

* CM-T3517: L3 in-band error with IPSS during boot
  - Cause unknown but see http://marc.info/?l=linux-omapm=134833869730129w=2
  - Longstanding issue; does not occur on the 3517EVM

PM tests:

* 2430sdp: pwrdm state mismatch(dsp_pwrdm) 0 != 3
  - need to doublecheck wakeup dependencies
  - (am assuming it's still there; does not boot to userspace)

* 2430sdp: power domains not entering retention
  - Cause unknown
  - (am assuming it's still there; does not boot to userspace)

* 4430es2panda, 4460pandaes: pwrdm state mismatch on CAM, DSS, ABE

* 4460pandaes: pwrdm state mismatch on IVAHD, TESLA 

* 4430es2panda: CORE, TESLA, IVAHD, L3INIT didn't enter target state
  - Probably due to lack of reset code for M3, DSP, SL2IF, FSUSB
per discussion with Tero Kristo
  - Likely dependent on the bootloader version
- fails with 2012.07-00136-g755de79

* 4460pandaes: chip not entering retention in dynamic idle
  - Presumably 4430es2panda also fails this
  - Suspend-to-RAM enters full chip retention

* 3730 Beagle XM: does not serial wake from off-idle suspend when console
  UART doesn't clock-gate (debug ignore_loglevel)
  - Cause unknown
  - Not yet part of the automated test suite
  - Re-tested at v3.7; still failing:

http://www.pwsan.com/omap/transcripts/20121211-3730beaglexm-3.7-pm-offmode-fail-debug.txt

Other:

* 4430es2panda: omap_hwmod: l3_instr: _wait_target_disable failed
  - Unknown cause; could be due to the lack of hierarchical enable/disable
in hwmod code
  - Jon Hunter reports this does not appear with the same X-loader/bootloader
on his 4430ES2.3 Panda, so could be ES-level dependent


vmlinux object size
(delta in bytes from test_v3.9-rc1 
(6dbe51c251a327e012439c4772097a13df43c5b8)):
   text data  bsstotal  kernel
 +13528  +640   +13592  omap1_defconfig
  +9440 +1200+9560  omap2plus_defconfig
 +13472 +1280   +13600  omap2plus_defconfig_cpupm
 +13472 +1280   +13600  omap2plus_defconfig_omap2_4_only
  +9756 +1200+9876  omap2plus_defconfig_omap3_4_only
   +704  -64 -188 +452  rmk_omap3430_ldp_allnoconfig
   +556  -640 +492  rmk_omap4430_sdp_oldconfig

Boot-time memory difference
(delta in bytes from test_v3.9-rc1

Re: OMAP baseline test results for v3.9-rc1

2013-03-13 Thread Igor Grinberg 
On 03/12/13 18:40, Paul Walmsley wrote:
 
 Here are some basic OMAP test results for Linux v3.9-rc1.
 Logs and other details at:
 
 http://www.pwsan.com/omap/testlogs/test_v3.9-rc1/20130312100243/

[...]

 Failing tests: needing investigation
 

[...]

 * CM-T3517: boot hangs with MMC root
   - Due to missing MMC setup in board file
   - http://www.spinics.net/lists/arm-kernel/msg211471.html
   - Longstanding bug

This should have been fixed by:
ff95793 (ARM: OMAP3: cm-t3517: add MMC support)

I also can't find the MMC rootfs boot log on your website.


-- 
Regards,
Igor.
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: OMAP baseline test results for v3.9-rc1

2013-03-13 Thread Paul Walmsley 
Hi Aaro,

On Tue, 12 Mar 2013, Aaro Koskinen wrote:

 On Tue, Mar 12, 2013 at 04:40:19PM +, Paul Walmsley wrote:
  * 2420N800: powers down 30 seconds after boot
- Presumably due to missing CBUS patches for watchdog control
- http://lkml.org/lkml/2012/9/3/265
- http://marc.info/?l=linux-omapm=135274739624125w=2
- http://marc.info/?l=linux-omapm=135664195831104w=2
- Should be working in v3.9-rc1 when CONFIG_RETU_WATCHDOG=y ?
 
 Yes, you need also CONFIG_I2C_CBUS_GPIO and CONFIG_MFD_RETU.

OK thanks, will add that in for the v3.9-rc2 test.

Would it make sense to add those dependencies to the Kconfig file for 
CONFIG_RETU_WATCHDOG?


- Paul
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: OMAP baseline test results for v3.9-rc1

2013-03-13 Thread Paul Walmsley 
Hi Igor,

On Wed, 13 Mar 2013, Igor Grinberg wrote:

 This should have been fixed by:
 ff95793 (ARM: OMAP3: cm-t3517: add MMC support)
 
 I also can't find the MMC rootfs boot log on your website.

Hmm, I thought I had switched the CM-T3517 over to use MMC booting, but 
looks like it's still trying to use nfsroot.  Thanks for letting me know.  
Will switch to MMC and try again.


- Paul
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

OMAP baseline test results for v3.9-rc1

2013-03-12 Thread Paul Walmsley 

Here are some basic OMAP test results for Linux v3.9-rc1.
Logs and other details at:

http://www.pwsan.com/omap/testlogs/test_v3.9-rc1/20130312100243/


Test summary


Build:
FAIL ( 4/16): am33xx_only, omap1_defconfig,
  omap1_defconfig_5912osk_only,
  omap2plus_defconfig_2430sdp_only
Pass (12/16): n800_multi_omap2xxx, n800_only_a,
  omap1_defconfig_1510innovator_only, 
  omap2plus_defconfig, omap2plus_defconfig_cpupm,
  omap2plus_defconfig_no_pm,
  omap2plus_defconfig_omap2_4_only,
  omap2plus_defconfig_omap3_4_only,
  rmk_omap3430_ldp_allnoconfig,
  rmk_omap3430_ldp_oldconfig,
  rmk_omap4430_sdp_allnoconfig
  rmk_omap4430_sdp_oldconfig

Boot to userspace:
FAIL ( 4/11): 2430sdp, 37xxevm, am335xbone, cmt3517
Pass ( 7/11): 2420n800, 3517evm, 3530es3beagle,
  3730beaglexm, 4430es2panda, 5912osk,
  4460pandaes
  
PM ret, suspend:
FAIL ( 4/ 6): 2430sdp, 37xxevm, 4430es2panda, 4460pandaes
Pass ( 2/ 6): 3530es3beagle, 3730beaglexm

PM ret, dynamic idle:
FAIL ( 4/ 6): 2430sdp, 37xxevm, 4430es2panda, 4460pandaes
Pass ( 2/ 6): 3530es3beagle, 3730beaglexm

PM off, suspend:
FAIL ( 3/ 5): 37xxevm, 4430es2panda, 4460pandaes
Pass ( 2/ 5): 3530es3beagle, 3730beaglexm

PM off, dynamic idle:
FAIL ( 3/ 5): 37xxevm, 4430es2panda, 4460pandaes
Pass ( 2/ 5): 3530es3beagle, 3730beaglexm


Failing tests: fixed by posted patches
--

Build:

* omap1_defconfig: several problems with mach-omap1/board-h2.c
  - Fixed by Tony: http://www.spinics.net/lists/arm-kernel/msg224133.html

* omap1_defconfig_5912osk_only: implicit declaration of function 
'cpu_is_omap15xx'
  - Fixed by Aaro: http://www.spinics.net/lists/linux-omap/msg87523.html


Failing tests: needing investigation


Build:

* am33xx_only, omap2plus_defconfig_2430sdp_only: omap-{smp,hotplug}.c link 
errors

Boot tests:

* 2430sdp  37xxevm: hang during MMC partition probe
  - Cause unknown

* 3517EVM  CM-T3517: boot hangs with NFS root
  - Likely some Kconfig, board file, and PM issues with EMAC
  - Longstanding bug

* CM-T3517: boot hangs with MMC root
  - Due to missing MMC setup in board file
  - http://www.spinics.net/lists/arm-kernel/msg211471.html
  - Longstanding bug

Boot warnings:

* CM-T3517: L3 in-band error with IPSS during boot
  - Cause unknown but see http://marc.info/?l=linux-omapm=134833869730129w=2
  - Longstanding issue; does not occur on the 3517EVM

PM tests:

* 2430sdp: pwrdm state mismatch(dsp_pwrdm) 0 != 3
  - need to doublecheck wakeup dependencies
  - (am assuming it's still there; does not boot to userspace)

* 2430sdp: power domains not entering retention
  - Cause unknown
  - (am assuming it's still there; does not boot to userspace)

* 4430es2panda, 4460pandaes: pwrdm state mismatch on CAM, DSS, ABE

* 4460pandaes: pwrdm state mismatch on IVAHD, TESLA 

* 4430es2panda: CORE, TESLA, IVAHD, L3INIT didn't enter target state
  - Probably due to lack of reset code for M3, DSP, SL2IF, FSUSB
per discussion with Tero Kristo
  - Likely dependent on the bootloader version
- fails with 2012.07-00136-g755de79

* 4460pandaes: CORE, L3INIT didn't enter target state
  - Cause unknown; appeared with v3.9-rc1

* 4460pandaes: chip not entering retention in dynamic idle
  - Presumably 4430es2panda also fails this

* 3730 Beagle XM: does not serial wake from off-idle suspend when console
  UART doesn't clock-gate (debug ignore_loglevel)
  - Cause unknown
  - Not yet part of the automated test suite
  - Re-tested at v3.7; still failing:

http://www.pwsan.com/omap/transcripts/20121211-3730beaglexm-3.7-pm-offmode-fail-debug.txt

Other:

* 2420N800: powers down 30 seconds after boot
  - Presumably due to missing CBUS patches for watchdog control
  - http://lkml.org/lkml/2012/9/3/265
  - http://marc.info/?l=linux-omapm=135274739624125w=2
  - http://marc.info/?l=linux-omapm=135664195831104w=2
  - Should be working in v3.9-rc1 when CONFIG_RETU_WATCHDOG=y ?

* 4430es2panda: omap_hwmod: l3_instr: _wait_target_disable failed
  - Unknown cause; could be due to the lack of hierarchical enable/disable
in hwmod code
  - Jon Hunter reports this does not appear with the same X-loader/bootloader
on his 4430ES2.3 Panda, so could be ES-level dependent



vmlinux object size
(delta in bytes from test_v3.8 (19f949f52599ba7c3f67a5897ac6be14bfcb1200)):
   text data  bsstotal  kernel
+195310   +37968+1364  +234642  omap2plus_defconfig
+185362   +37128+1364  +223854  omap2plus_defconfig_cpupm
+186719   +31416+1300  +219435  omap2plus_defconfig_omap2_4_only
+181125   +41432+1300  +223857  omap2plus_defconfig_omap3_4_only
 +10460   +10272+1184   +21916  rmk_omap3430_ldp_allnoconfig
 +40867   +14672

Re: OMAP baseline test results for v3.9-rc1

2013-03-12 Thread Paul Walmsley 
On Tue, 12 Mar 2013, Paul Walmsley wrote:

 Here are some basic OMAP test results for Linux v3.9-rc1.
 Logs and other details at:
 
 http://www.pwsan.com/omap/testlogs/test_v3.9-rc1/20130312100243/

...

 Boot to userspace:
 FAIL ( 4/11): 2430sdp, 37xxevm, am335xbone, cmt3517
 Pass ( 7/11): 2420n800, 3517evm, 3530es3beagle,
 3730beaglexm, 4430es2panda, 5912osk,
 4460pandaes

It's not correct that 5912osk booted to userspace, given that the kernel 
didn't build.  Looking at the testlogs, it seems to have inadvertently 
booted a 3.8 kernel.  Something else to fix in the scripts.

This has been fixed in the README copy on the web.


- Paul
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: OMAP baseline test results for v3.9-rc1

2013-03-12 Thread Aaro Koskinen 
Hi,

On Tue, Mar 12, 2013 at 04:40:19PM +, Paul Walmsley wrote:
 * 2420N800: powers down 30 seconds after boot
   - Presumably due to missing CBUS patches for watchdog control
   - http://lkml.org/lkml/2012/9/3/265
   - http://marc.info/?l=linux-omapm=135274739624125w=2
   - http://marc.info/?l=linux-omapm=135664195831104w=2
   - Should be working in v3.9-rc1 when CONFIG_RETU_WATCHDOG=y ?

Yes, you need also CONFIG_I2C_CBUS_GPIO and CONFIG_MFD_RETU.

A.
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html