* State of SDP4430 platform @ 2011-01-16 1:09 Russell King - ARM Linux 2011-01-16 6:06 ` Paul Walmsley 2011-02-07 8:18 ` Gulati, Shweta 0 siblings, 2 replies; 16+ messages in thread From: Russell King - ARM Linux @ 2011-01-16 1:09 UTC (permalink / raw) To: linux-omap It's probably best if I just quote the boot log, and people see about fixing the masses of WARN_ON()s. Notice that it completely obliterates the early part of the boot log due to the number of WARN_ON()s triggered. Other stuff that shows in this boot log: - There's a couple of complaints about missing clock domains for some clocks - Bunch of regulators are returning errors (is this a problem?) - I2C timeouts which add quite a bit to the boot-time - missing vdd_mpu/vdd_iva? (with additional blank lines emitted) Uncompressing Linux... done, booting the kernel. 060768>] (warn_slowpath_common+0x0/0x70) from [<c006087c>] (warn_slowpath_fmt+0x38/0x40) r8:c0359a10 r7:00000000 r6:00000060 r5:00000000 r4:00000000 [<c0060844>] (warn_slowpath_fmt+0x0/0x40) from [<c004c84c>] (clkdm_clear_all_wkdeps+0x80/0x90) r3:00002502 r2:c030688d [<c004c7cc>] (clkdm_clear_all_wkdeps+0x0/0x90) from [<c004cf60>] (clkdm_init+0x14c/0x17c) r5:c0359a10 r4:c0359b4c [<c004ce14>] (clkdm_init+0x0/0x17c) from [<c0011758>] (omap44xx_clockdomains_init+0x18/0x20) [<c0011740>] (omap44xx_clockdomains_init+0x0/0x20) from [<c000f0b0>] (omap2_init_common_infrastructure+0x28/0xa4) [<c000f088>] (omap2_init_common_infrastructure+0x0/0xa4) from [<c0011d78>] (omap_4430sdp_init_irq+0x2c/0x54) r4:00000001 [<c0011d4c>] (omap_4430sdp_init_irq+0x0/0x54) from [<c000b87c>] (init_IRQ+0x1c/0x24) r4:bfffffff [<c000b860>] (init_IRQ+0x0/0x24) from [<c0008a78>] (start_kernel+0x194/0x314) [<c00088e4>] (start_kernel+0x0/0x314) from [<80008040>] (0x80008040) r8:80000000 r7:c0357c84 r6:c0028678 r5:c0354b70 r4:10c53c7d ---[ end trace 1b75b31a2719ed2d ]--- ------------[ cut here ]------------ WARNING: at /home/rmk/git/linux-2.6-rmk/arch/arm/mach-omap2/prm2xxx_3xxx.h:264 clkdm_clear_all_wkdeps+0x80/0x90() prm: omap2xxx/omap3xxx specific function and not suppose to be used on omap4 Modules linked in: Backtrace: [<c003ec64>] (dump_backtrace+0x0/0x10c) from [<c0288be0>] (dump_stack+0x18/0x1c) r7:c0347f08 r6:c004c84c r5:c030684e r4:00000108 [<c0288bc8>] (dump_stack+0x0/0x1c) from [<c00607c0>] (warn_slowpath_common+0x58/0x70) [<c0060768>] (warn_slowpath_common+0x0/0x70) from [<c006087c>] (warn_slowpath_fmt+0x38/0x40) r8:c0359a10 r7:00000000 r6:00000060 r5:00000000 r4:00000000 [<c0060844>] (warn_slowpath_fmt+0x0/0x40) from [<c004c84c>] (clkdm_clear_all_wkdeps+0x80/0x90) r3:004cff02 r2:c030688d [<c004c7cc>] (clkdm_clear_all_wkdeps+0x0/0x90) from [<c004cf60>] (clkdm_init+0x14c/0x17c) r5:c0359a10 r4:c0359b20 [<c004ce14>] (clkdm_init+0x0/0x17c) from [<c0011758>] (omap44xx_clockdomains_init+0x18/0x20) [<c0011740>] (omap44xx_clockdomains_init+0x0/0x20) from [<c000f0b0>] (omap2_init_common_infrastructure+0x28/0xa4) [<c000f088>] (omap2_init_common_infrastructure+0x0/0xa4) from [<c0011d78>] (omap_4430sdp_init_irq+0x2c/0x54) r4:00000001 [<c0011d4c>] (omap_4430sdp_init_irq+0x0/0x54) from [<c000b87c>] (init_IRQ+0x1c/0x24) r4:bfffffff [<c000b860>] (init_IRQ+0x0/0x24) from [<c0008a78>] (start_kernel+0x194/0x314) [<c00088e4>] (start_kernel+0x0/0x314) from [<80008040>] (0x80008040) r8:80000000 r7:c0357c84 r6:c0028678 r5:c0354b70 r4:10c53c7d ---[ end trace 1b75b31a2719ed2e ]--- ------------[ cut here ]------------ WARNING: at /home/rmk/git/linux-2.6-rmk/arch/arm/mach-omap2/prm2xxx_3xxx.h:264 clkdm_clear_all_wkdeps+0x80/0x90() prm: omap2xxx/omap3xxx specific function and not suppose to be used on omap4 Modules linked in: Backtrace: [<c003ec64>] (dump_backtrace+0x0/0x10c) from [<c0288be0>] (dump_stack+0x18/0x1c) r7:c0347f08 r6:c004c84c r5:c030684e r4:00000108 [<c0288bc8>] (dump_stack+0x0/0x1c) from [<c00607c0>] (warn_slowpath_common+0x58/0x70) [<c0060768>] (warn_slowpath_common+0x0/0x70) from [<c006087c>] (warn_slowpath_fmt+0x38/0x40) r8:c0359a10 r7:00000000 r6:00000060 r5:00000000 r4:00000000 [<c0060844>] (warn_slowpath_fmt+0x0/0x40) from [<c004c84c>] (clkdm_clear_all_wkdeps+0x80/0x90) r3:00000002 r2:c030688d [<c004c7cc>] (clkdm_clear_all_wkdeps+0x0/0x90) from [<c004cf60>] (clkdm_init+0x14c/0x17c) r5:c0359a10 r4:c0359af4 [<c004ce14>] (clkdm_init+0x0/0x17c) from [<c0011758>] (omap44xx_clockdomains_init+0x18/0x20) [<c0011740>] (omap44xx_clockdomains_init+0x0/0x20) from [<c000f0b0>] (omap2_init_common_infrastructure+0x28/0xa4) [<c000f088>] (omap2_init_common_infrastructure+0x0/0xa4) from [<c0011d78>] (omap_4430sdp_init_irq+0x2c/0x54) r4:00000001 [<c0011d4c>] (omap_4430sdp_init_irq+0x0/0x54) from [<c000b87c>] (init_IRQ+0x1c/0x24) r4:bfffffff [<c000b860>] (init_IRQ+0x0/0x24) from [<c0008a78>] (start_kernel+0x194/0x314) [<c00088e4>] (start_kernel+0x0/0x314) from [<80008040>] (0x80008040) r8:80000000 r7:c0357c84 r6:c0028678 r5:c0354b70 r4:10c53c7d ---[ end trace 1b75b31a2719ed2f ]--- ------------[ cut here ]------------ WARNING: at /home/rmk/git/linux-2.6-rmk/arch/arm/mach-omap2/prm2xxx_3xxx.h:264 clkdm_clear_all_wkdeps+0x80/0x90() prm: omap2xxx/omap3xxx specific function and not suppose to be used on omap4 Modules linked in: Backtrace: [<c003ec64>] (dump_backtrace+0x0/0x10c) from [<c0288be0>] (dump_stack+0x18/0x1c) r7:c0347f08 r6:c004c84c r5:c030684e r4:00000108 [<c0288bc8>] (dump_stack+0x0/0x1c) from [<c00607c0>] (warn_slowpath_common+0x58/0x70) [<c0060768>] (warn_slowpath_common+0x0/0x70) from [<c006087c>] (warn_slowpath_fmt+0x38/0x40) r8:c0359a10 r7:00000000 r6:00000060 r5:00000000 r4:00000000 [<c0060844>] (warn_slowpath_fmt+0x0/0x40) from [<c004c84c>] (clkdm_clear_all_wkdeps+0x80/0x90) r3:00000102 r2:c030688d [<c004c7cc>] (clkdm_clear_all_wkdeps+0x0/0x90) from [<c004cf60>] (clkdm_init+0x14c/0x17c) r5:c0359a10 r4:c0359ac8 [<c004ce14>] (clkdm_init+0x0/0x17c) from [<c0011758>] (omap44xx_clockdomains_init+0x18/0x20) [<c0011740>] (omap44xx_clockdomains_init+0x0/0x20) from [<c000f0b0>] (omap2_init_common_infrastructure+0x28/0xa4) [<c000f088>] (omap2_init_common_infrastructure+0x0/0xa4) from [<c0011d78>] (omap_4430sdp_init_irq+0x2c/0x54) r4:00000001 [<c0011d4c>] (omap_4430sdp_init_irq+0x0/0x54) from [<c000b87c>] (init_IRQ+0x1c/0x24) r4:bfffffff [<c000b860>] (init_IRQ+0x0/0x24) from [<c0008a78>] (start_kernel+0x194/0x314) [<c00088e4>] (start_kernel+0x0/0x314) from [<80008040>] (0x80008040) r8:80000000 r7:c0357c84 r6:c0028678 r5:c0354b70 r4:10c53c7d ---[ end trace 1b75b31a2719ed30 ]--- ------------[ cut here ]------------ WARNING: at /home/rmk/git/linux-2.6-rmk/arch/arm/mach-omap2/prm2xxx_3xxx.h:264 clkdm_clear_all_wkdeps+0x80/0x90() prm: omap2xxx/omap3xxx specific function and not suppose to be used on omap4 Modules linked in: Backtrace: [<c003ec64>] (dump_backtrace+0x0/0x10c) from [<c0288be0>] (dump_stack+0x18/0x1c) r7:c0347f08 r6:c004c84c r5:c030684e r4:00000108 [<c0288bc8>] (dump_stack+0x0/0x1c) from [<c00607c0>] (warn_slowpath_common+0x58/0x70) [<c0060768>] (warn_slowpath_common+0x0/0x70) from [<c006087c>] (warn_slowpath_fmt+0x38/0x40) r8:c0359a10 r7:00000000 r6:00000060 r5:00000000 r4:00000000 [<c0060844>] (warn_slowpath_fmt+0x0/0x40) from [<c004c84c>] (clkdm_clear_all_wkdeps+0x80/0x90) r3:00000302 r2:c030688d [<c004c7cc>] (clkdm_clear_all_wkdeps+0x0/0x90) from [<c004cf60>] (clkdm_init+0x14c/0x17c) r5:c0359a10 r4:c0359a9c [<c004ce14>] (clkdm_init+0x0/0x17c) from [<c0011758>] (omap44xx_clockdomains_init+0x18/0x20) [<c0011740>] (omap44xx_clockdomains_init+0x0/0x20) from [<c000f0b0>] (omap2_init_common_infrastructure+0x28/0xa4) [<c000f088>] (omap2_init_common_infrastructure+0x0/0xa4) from [<c0011d78>] (omap_4430sdp_init_irq+0x2c/0x54) r4:00000001 [<c0011d4c>] (omap_4430sdp_init_irq+0x0/0x54) from [<c000b87c>] (init_IRQ+0x1c/0x24) r4:bfffffff [<c000b860>] (init_IRQ+0x0/0x24) from [<c0008a78>] (start_kernel+0x194/0x314) [<c00088e4>] (start_kernel+0x0/0x314) from [<80008040>] (0x80008040) r8:80000000 r7:c0357c84 r6:c0028678 r5:c0354b70 r4:10c53c7d ---[ end trace 1b75b31a2719ed31 ]--- ------------[ cut here ]------------ WARNING: at /home/rmk/git/linux-2.6-rmk/arch/arm/mach-omap2/prm2xxx_3xxx.h:264 clkdm_clear_all_wkdeps+0x80/0x90() prm: omap2xxx/omap3xxx specific function and not suppose to be used on omap4 Modules linked in: Backtrace: [<c003ec64>] (dump_backtrace+0x0/0x10c) from [<c0288be0>] (dump_stack+0x18/0x1c) r7:c0347f08 r6:c004c84c r5:c030684e r4:00000108 [<c0288bc8>] (dump_stack+0x0/0x1c) from [<c00607c0>] (warn_slowpath_common+0x58/0x70) [<c0060768>] (warn_slowpath_common+0x0/0x70) from [<c006087c>] (warn_slowpath_fmt+0x38/0x40) r8:c0359a10 r7:00000000 r6:00000060 r5:00000000 r4:00000000 [<c0060844>] (warn_slowpath_fmt+0x0/0x40) from [<c004c84c>] (clkdm_clear_all_wkdeps+0x80/0x90) r3:00000102 r2:c030688d [<c004c7cc>] (clkdm_clear_all_wkdeps+0x0/0x90) from [<c004cf60>] (clkdm_init+0x14c/0x17c) r5:c0359a10 r4:c0359a70 [<c004ce14>] (clkdm_init+0x0/0x17c) from [<c0011758>] (omap44xx_clockdomains_init+0x18/0x20) [<c0011740>] (omap44xx_clockdomains_init+0x0/0x20) from [<c000f0b0>] (omap2_init_common_infrastructure+0x28/0xa4) [<c000f088>] (omap2_init_common_infrastructure+0x0/0xa4) from [<c0011d78>] (omap_4430sdp_init_irq+0x2c/0x54) r4:00000001 [<c0011d4c>] (omap_4430sdp_init_irq+0x0/0x54) from [<c000b87c>] (init_IRQ+0x1c/0x24) r4:bfffffff [<c000b860>] (init_IRQ+0x0/0x24) from [<c0008a78>] (start_kernel+0x194/0x314) [<c00088e4>] (start_kernel+0x0/0x314) from [<80008040>] (0x80008040) r8:80000000 r7:c0357c84 r6:c0028678 r5:c0354b70 r4:10c53c7d ---[ end trace 1b75b31a2719ed32 ]--- ------------[ cut here ]------------ WARNING: at /home/rmk/git/linux-2.6-rmk/arch/arm/mach-omap2/prm2xxx_3xxx.h:264 clkdm_clear_all_wkdeps+0x80/0x90() prm: omap2xxx/omap3xxx specific function and not suppose to be used on omap4 Modules linked in: Backtrace: [<c003ec64>] (dump_backtrace+0x0/0x10c) from [<c0288be0>] (dump_stack+0x18/0x1c) r7:c0347f08 r6:c004c84c r5:c030684e r4:00000108 [<c0288bc8>] (dump_stack+0x0/0x1c) from [<c00607c0>] (warn_slowpath_common+0x58/0x70) [<c0060768>] (warn_slowpath_common+0x0/0x70) from [<c006087c>] (warn_slowpath_fmt+0x38/0x40) r8:c0359a10 r7:00000000 r6:00000060 r5:00000000 r4:00000000 [<c0060844>] (warn_slowpath_fmt+0x0/0x40) from [<c004c84c>] (clkdm_clear_all_wkdeps+0x80/0x90) r3:00000001 r2:c030688d [<c004c7cc>] (clkdm_clear_all_wkdeps+0x0/0x90) from [<c004cf60>] (clkdm_init+0x14c/0x17c) r5:c0359a10 r4:c0359a44 [<c004ce14>] (clkdm_init+0x0/0x17c) from [<c0011758>] (omap44xx_clockdomains_init+0x18/0x20) [<c0011740>] (omap44xx_clockdomains_init+0x0/0x20) from [<c000f0b0>] (omap2_init_common_infrastructure+0x28/0xa4) [<c000f088>] (omap2_init_common_infrastructure+0x0/0xa4) from [<c0011d78>] (omap_4430sdp_init_irq+0x2c/0x54) r4:00000001 [<c0011d4c>] (omap_4430sdp_init_irq+0x0/0x54) from [<c000b87c>] (init_IRQ+0x1c/0x24) r4:bfffffff [<c000b860>] (init_IRQ+0x0/0x24) from [<c0008a78>] (start_kernel+0x194/0x314) [<c00088e4>] (start_kernel+0x0/0x314) from [<80008040>] (0x80008040) r8:80000000 r7:c0357c84 r6:c0028678 r5:c0354b70 r4:10c53c7d ---[ end trace 1b75b31a2719ed33 ]--- ------------[ cut here ]------------ WARNING: at /home/rmk/git/linux-2.6-rmk/arch/arm/mach-omap2/prm2xxx_3xxx.h:264 clkdm_clear_all_wkdeps+0x80/0x90() prm: omap2xxx/omap3xxx specific function and not suppose to be used on omap4 Modules linked in: Backtrace: [<c003ec64>] (dump_backtrace+0x0/0x10c) from [<c0288be0>] (dump_stack+0x18/0x1c) r7:c0347f08 r6:c004c84c r5:c030684e r4:00000108 [<c0288bc8>] (dump_stack+0x0/0x1c) from [<c00607c0>] (warn_slowpath_common+0x58/0x70) [<c0060768>] (warn_slowpath_common+0x0/0x70) from [<c006087c>] (warn_slowpath_fmt+0x38/0x40) r8:c0359a10 r7:00000000 r6:00000060 r5:00000000 r4:00000000 [<c0060844>] (warn_slowpath_fmt+0x0/0x40) from [<c004c84c>] (clkdm_clear_all_wkdeps+0x80/0x90) r3:00000002 r2:c030688d [<c004c7cc>] (clkdm_clear_all_wkdeps+0x0/0x90) from [<c004cf60>] (clkdm_init+0x14c/0x17c) r5:c0359a10 r4:c0359a18 [<c004ce14>] (clkdm_init+0x0/0x17c) from [<c0011758>] (omap44xx_clockdomains_init+0x18/0x20) [<c0011740>] (omap44xx_clockdomains_init+0x0/0x20) from [<c000f0b0>] (omap2_init_common_infrastructure+0x28/0xa4) [<c000f088>] (omap2_init_common_infrastructure+0x0/0xa4) from [<c0011d78>] (omap_4430sdp_init_irq+0x2c/0x54) r4:00000001 [<c0011d4c>] (omap_4430sdp_init_irq+0x0/0x54) from [<c000b87c>] (init_IRQ+0x1c/0x24) r4:bfffffff [<c000b860>] (init_IRQ+0x0/0x24) from [<c0008a78>] (start_kernel+0x194/0x314) [<c00088e4>] (start_kernel+0x0/0x314) from [<80008040>] (0x80008040) r8:80000000 r7:c0357c84 r6:c0028678 r5:c0354b70 r4:10c53c7d ---[ end trace 1b75b31a2719ed34 ]--- omap_hwmod: l3_div_ck: missing clockdomain for l3_div_ck. omap_hwmod: dpll_mpu_m2_ck: missing clockdomain for dpll_mpu_m2_ck. GPMC revision 6.0 OMAP clockevent source: GPTIMER1 at 32768 Hz sched_clock: 32 bits at 32kHz, resolution 30517ns, wraps every 131071999ms Console: colour dummy device 80x30 Calibrating delay loop... 2013.49 BogoMIPS (lpj=7864320) pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok L310 cache controller enabled l2x0: 16 ways, CACHE_ID 0x410000c2, AUX_CTRL 0x0e050000, Cache size: 524288 B CPU1: Booted secondary processor CPU1: Unknown IPI message 0x1 Brought up 2 CPUs SMP: Total of 2 processors activated (4026.98 BogoMIPS). print_constraints: dummy: NET: Registered protocol family 16 OMAP GPIO hardware version 0.1 OMAP GPIO hardware version 0.1 OMAP GPIO hardware version 0.1 OMAP GPIO hardware version 0.1 OMAP GPIO hardware version 0.1 OMAP GPIO hardware version 0.1 omap_mux_init: Add partition: #1: core, flags: 2 omap_mux_init: Add partition: #2: wkup, flags: 2 omap_device: omap_uart.1: new worst case deactivate latency 0: 30517 omap_device: omap_uart.3: new worst case activate latency 0: 30517 pm_dbg_init: only OMAP3 supported OMAP DMA hardware revision 0.0 bio: create slab <bio-0> at 0 omap_i2c omap_i2c.1: bus 1 rev4.0 at 400 kHz Skipping twl internal clock init and using bootloader value (unknown osc rate) twl6030: PIH (irq 39) chaining IRQs 368..387 print_constraints: VMMC: 1200 <--> 3000 mV at 3000 mV normal standby print_constraints: VPP: 1800 <--> 2500 mV at 1900 mV normal standby print_constraints: VUSIM: 1200 <--> 2900 mV at 1800 mV normal standby machine_constraints_voltage: VANA: failed to apply 2100000uV constraint twl_reg twl_reg.43: can't register VANA, -22 twl_reg: probe of twl_reg.43 failed with error -22 machine_constraints_voltage: VCXIO: failed to apply 1800000uV constraint twl_reg twl_reg.44: can't register VCXIO, -22 twl_reg: probe of twl_reg.44 failed with error -22 machine_constraints_voltage: VDAC: failed to apply 1800000uV constraint twl_reg twl_reg.45: can't register VDAC, -22 twl_reg: probe of twl_reg.45 failed with error -22 print_constraints: VAUX1_6030: 1000 <--> 3000 mV at 2800 mV normal standby print_constraints: VAUX2_6030: 1200 <--> 2800 mV at 1800 mV normal standby print_constraints: VAUX3_6030: 1000 <--> 3000 mV at 1200 mV normal standby omap_i2c omap_i2c.2: bus 2 rev4.0 at 400 kHz omap_i2c omap_i2c.3: bus 3 rev4.0 at 400 kHz omap_i2c omap_i2c.4: bus 4 rev4.0 at 400 kHz DMA-API: preallocated 4096 debug entries DMA-API: debugging enabled by kernel config Switching to clocksource 32k_counter NET: Registered protocol family 2 IP route cache hash table entries: 1024 (order: 0, 4096 bytes) TCP established hash table entries: 1024 (order: 1, 8192 bytes) TCP bind hash table entries: 1024 (order: 1, 12288 bytes) TCP: Hash tables configured (established 1024 bind 1024) TCP reno registered UDP hash table entries: 128 (order: 0, 4096 bytes) UDP-Lite hash table entries: 128 (order: 0, 4096 bytes) NET: Registered protocol family 1 RPC: Registered udp transport module. RPC: Registered tcp transport module. RPC: Registered tcp NFSv4.1 backchannel transport module. NetWinder Floating Point Emulator V0.97 (double precision) highmem bounce pool size: 64 pages VFS: Disk quotas dquot_6.5.2 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) msgmni has been set to 48 io scheduler noop registered io scheduler deadline registered io scheduler cfq registered (default) Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled omap_uart.0: ttyO0 at MMIO 0x4806a000 (irq = 104) is a OMAP UART0 omap_uart.1: ttyO1 at MMIO 0x4806c000 (irq = 105) is a OMAP UART1 omap_uart.2: ttyO2 at MMIO 0x48020000 (irq = 106) is a OMAP UART2 console [ttyO2] enabled omap_uart.3: ttyO3 at MMIO 0x4806e000 (irq = 102) is a OMAP UART3 brd: module loaded loop: module loaded ks8851 spi1.0: message enable is 0 ks8851 spi1.0: eth0: revision 0, MAC ce:9f:77:f1:2c:21, IRQ 194 input: gpio-keys as /devices/platform/gpio-keys/input/input0 twl_rtc twl_rtc: rtc core: registered twl_rtc as rtc0 twl_rtc twl_rtc: Power up reset detected. omap_device: omap_i2c.1: new worst case deactivate latency 0: 30517 twl_rtc twl_rtc: Enabling TWL-RTC. i2c /dev entries driver omap_device: omap_i2c.3: new worst case activate latency 0: 30517 lm75 3-0048: hwmon0: sensor 'tmp105' omap_i2c omap_i2c.1: controller timed out omap_i2c omap_i2c.1: controller timed out omap_i2c omap_i2c.2: controller timed out omap_i2c omap_i2c.2: controller timed out omap_i2c omap_i2c.2: controller timed out omap_i2c omap_i2c.2: controller timed out omap_i2c omap_i2c.3: controller timed out omap_i2c omap_i2c.3: controller timed out omap_i2c omap_i2c.3: controller timed out omap_i2c omap_i2c.4: controller timed out omap_i2c omap_i2c.4: controller timed out omap_i2c omap_i2c.4: controller timed out omap_i2c omap_i2c.4: controller timed out TCP cubic registered NET: Registered protocol family 17 VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 0 omap2_set_init_voltage: unable to find boot up OPP for vdd_mpu omap2_set_init_voltage: Unable to put vdd_mpu to its init voltage omap2_set_init_voltage: unable to find boot up OPP for vdd_iva omap2_set_init_voltage: Unable to put vdd_iva to its init voltage Power Management for TI OMAP4. regulator_init_complete: VAUX3_6030: incomplete constraints, leaving on regulator_init_complete: VAUX2_6030: incomplete constraints, leaving on regulator_init_complete: VUSIM: incomplete constraints, leaving on regulator_init_complete: VPP: incomplete constraints, leaving on mmc0: host does not support reading read-only switch. assuming write-enable. mmc0: new high speed SD card at address 0002 mmcblk0: mmc0:0002 00000 971 MiB mmcblk0: p1 p2 omap_i2c omap_i2c.1: controller timed out twl: i2c_read failed to transfer all messages twl_rtc twl_rtc: rtc_read_time error -110 twl_rtc twl_rtc: hctosys: unable to read the hardware clock Waiting 2sec before mounting root device... mmc1: new high speed MMC card at address 0001 mmcblk1: mmc1:0001 MMC32G 29.8 GiB mmcblk1: p1 EXT3-fs: barriers not enabled EXT3-fs (mmcblk0p2): warning: maximal mount count reached, running e2fsck is recommended kjournald starting. Commit interval 5 seconds EXT3-fs (mmcblk0p2): using internal journal EXT3-fs (mmcblk0p2): recovery complete EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode VFS: Mounted root (ext3 filesystem) on device 179:2. Freeing init memory: 156K ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: State of SDP4430 platform 2011-01-16 1:09 State of SDP4430 platform Russell King - ARM Linux @ 2011-01-16 6:06 ` Paul Walmsley 2011-01-16 6:25 ` Santosh Shilimkar 2011-02-07 8:18 ` Gulati, Shweta 1 sibling, 1 reply; 16+ messages in thread From: Paul Walmsley @ 2011-01-16 6:06 UTC (permalink / raw) To: Russell King - ARM Linux; +Cc: linux-omap [-- Attachment #1: Type: TEXT/PLAIN, Size: 5160 bytes --] On Sun, 16 Jan 2011, Russell King - ARM Linux wrote: > It's probably best if I just quote the boot log, and people see about > fixing the masses of WARN_ON()s. Notice that it completely obliterates > the early part of the boot log due to the number of WARN_ON()s > triggered. These come from the clockdomain code, which is missing quite a bit of OMAP4 implementation. Some patches to add that code in have been posted for the 2.6.39 timeframe[1][2], so it should be reasonable to use something like the following patch for 2.6.38, which converts those backtraces to pr_err()s. > Other stuff that shows in this boot log: ... > - Bunch of regulators are returning errors (is this a problem?) > - I2C timeouts which add quite a bit to the boot-time These two are probably related. Looks like something is wrong with communication with the TWL/TPS PMIC on that board. Those problems don't show up on the OMAP4430ES2 Panda here, so they are probably 4430SDP-specific. - Paul 1. Nayak, Rajendra. _[PATCH 0/5] Clockdomain split series_. Posted to the linux-omap@vger.kernel.org mailing list on 5 January 2011. http://www.mail-archive.com/linux-omap@vger.kernel.org/msg41748.html 2. Nayak, Rajendra. _[RFC 0/3] OMAP4 static dependency support_. Posted to the linux-omap@vger.kernel.org mailing list on 12 January 2011. http://www.mail-archive.com/linux-omap@vger.kernel.org/msg42222.html --- [PATCH] OMAP4: clockdomain: bypass unimplemented wake-up dependency functions on OMAP4 Clockdomain functions that manipulate wake-up dependencies are not implemented yet on OMAP4 for 2.6.38. This patch bypasses the OMAP2/3 functions on OMAP4, which in turn avoids the warnings when the functions would attempt to call the underlying OMAP2/3 PRCM functions. A clockdomain wake-up and sleep dependency implementation for OMAP4 from Rajendra should be possible to merge during the 2.6.39 merge window: http://www.mail-archive.com/linux-omap@vger.kernel.org/msg41748.html http://www.mail-archive.com/linux-omap@vger.kernel.org/msg42222.html Reported-by: Russell King <rmk+kernel@arm.linux.org.uk> Cc: Rajendra Nayak <rnayak@ti.com> Cc: Santosh Shilimkar <santosh.shilimkar@ti.com> Cc: Benoît Cousson <b-cousson@ti.com> Signed-off-by: Paul Walmsley <paul@pwsan.com> --- arch/arm/mach-omap2/clockdomain.c | 30 ++++++++++++++++++++++++++---- 1 files changed, 26 insertions(+), 4 deletions(-) diff --git a/arch/arm/mach-omap2/clockdomain.c b/arch/arm/mach-omap2/clockdomain.c index e20b986..58e42f7 100644 --- a/arch/arm/mach-omap2/clockdomain.c +++ b/arch/arm/mach-omap2/clockdomain.c @@ -423,6 +423,12 @@ int clkdm_add_wkdep(struct clockdomain *clkdm1, struct clockdomain *clkdm2) { struct clkdm_dep *cd; + if (!cpu_is_omap24xx() && !cpu_is_omap34xx()) { + pr_err("clockdomain: %s/%s: %s: not yet implemented\n", + clkdm1->name, clkdm2->name, __func__); + return -EINVAL; + } + if (!clkdm1 || !clkdm2) return -EINVAL; @@ -458,6 +464,12 @@ int clkdm_del_wkdep(struct clockdomain *clkdm1, struct clockdomain *clkdm2) { struct clkdm_dep *cd; + if (!cpu_is_omap24xx() && !cpu_is_omap34xx()) { + pr_err("clockdomain: %s/%s: %s: not yet implemented\n", + clkdm1->name, clkdm2->name, __func__); + return -EINVAL; + } + if (!clkdm1 || !clkdm2) return -EINVAL; @@ -500,6 +512,12 @@ int clkdm_read_wkdep(struct clockdomain *clkdm1, struct clockdomain *clkdm2) if (!clkdm1 || !clkdm2) return -EINVAL; + if (!cpu_is_omap24xx() && !cpu_is_omap34xx()) { + pr_err("clockdomain: %s/%s: %s: not yet implemented\n", + clkdm1->name, clkdm2->name, __func__); + return -EINVAL; + } + cd = _clkdm_deps_lookup(clkdm2, clkdm1->wkdep_srcs); if (IS_ERR(cd)) { pr_debug("clockdomain: hardware cannot set/clear wake up of " @@ -527,6 +545,12 @@ int clkdm_clear_all_wkdeps(struct clockdomain *clkdm) struct clkdm_dep *cd; u32 mask = 0; + if (!cpu_is_omap24xx() && !cpu_is_omap34xx()) { + pr_err("clockdomain: %s: %s: not yet implemented\n", + clkdm->name, __func__); + return -EINVAL; + } + if (!clkdm) return -EINVAL; @@ -830,8 +854,7 @@ void omap2_clkdm_allow_idle(struct clockdomain *clkdm) * dependency code and data for OMAP4. */ if (cpu_is_omap44xx()) { - WARN_ONCE(1, "clockdomain: OMAP4 wakeup/sleep dependency " - "support is not yet implemented\n"); + pr_err("clockdomain: %s: OMAP4 wakeup/sleep dependency support: not yet implemented\n", clkdm->name); } else { if (atomic_read(&clkdm->usecount) > 0) _clkdm_add_autodeps(clkdm); @@ -872,8 +895,7 @@ void omap2_clkdm_deny_idle(struct clockdomain *clkdm) * dependency code and data for OMAP4. */ if (cpu_is_omap44xx()) { - WARN_ONCE(1, "clockdomain: OMAP4 wakeup/sleep dependency " - "support is not yet implemented\n"); + pr_err("clockdomain: %s: OMAP4 wakeup/sleep dependency support: not yet implemented\n", clkdm->name); } else { if (atomic_read(&clkdm->usecount) > 0) _clkdm_del_autodeps(clkdm); -- 1.7.2.3 ^ permalink raw reply related [flat|nested] 16+ messages in thread
* RE: State of SDP4430 platform 2011-01-16 6:06 ` Paul Walmsley @ 2011-01-16 6:25 ` Santosh Shilimkar 2011-01-17 10:07 ` Santosh Shilimkar 0 siblings, 1 reply; 16+ messages in thread From: Santosh Shilimkar @ 2011-01-16 6:25 UTC (permalink / raw) To: Paul Walmsley, Russell King - ARM Linux; +Cc: linux-omap > -----Original Message----- > From: linux-omap-owner@vger.kernel.org [mailto:linux-omap- > owner@vger.kernel.org] On Behalf Of Paul Walmsley > Sent: Sunday, January 16, 2011 11:37 AM > To: Russell King - ARM Linux > Cc: linux-omap@vger.kernel.org > Subject: Re: State of SDP4430 platform > > On Sun, 16 Jan 2011, Russell King - ARM Linux wrote: > > > It's probably best if I just quote the boot log, and people see > about > > fixing the masses of WARN_ON()s. Notice that it completely > obliterates > > the early part of the boot log due to the number of WARN_ON()s > > triggered. > > These come from the clockdomain code, which is missing quite a bit > of > OMAP4 implementation. Some patches to add that code in have been > posted > for the 2.6.39 timeframe[1][2], so it should be reasonable to use > something like the following patch for 2.6.38, which converts those > backtraces to pr_err()s. > I was just typing the same about clockdomain WARNS(). Till the clockdomain split series is ready for merge, I guess your below patch can be merged. > > Other stuff that shows in this boot log: > > ... > > > - Bunch of regulators are returning errors (is this a problem?) > > - I2C timeouts which add quite a bit to the boot-time > > These two are probably related. Looks like something is wrong with > communication with the TWL/TPS PMIC on that board. Those problems > don't > show up on the OMAP4430ES2 Panda here, so they are probably > 4430SDP-specific. > > Actually I don't see these errors which ring a bell. There was an I2C pull related issue with ES1.0 silicon. I guess these timeouts would show up only on ES1.0 OMAP4 boards and not on ES2.0 boards. Monday I will check on my ES1.0 board and if needed send an updated bootloader ( setting up right pull values) or a patch to kernel. [....] > > [PATCH] OMAP4: clockdomain: bypass unimplemented wake-up dependency > functions on OMAP4 > > Clockdomain functions that manipulate wake-up dependencies are not > implemented yet on OMAP4 for 2.6.38. This patch bypasses the > OMAP2/3 > functions on OMAP4, which in turn avoids the warnings when the > functions would attempt to call the underlying OMAP2/3 PRCM > functions. > > A clockdomain wake-up and sleep dependency implementation for OMAP4 > from Rajendra should be possible to merge during the 2.6.39 merge > window: > > http://www.mail-archive.com/linux- > omap@vger.kernel.org/msg41748.html > > http://www.mail-archive.com/linux- > omap@vger.kernel.org/msg42222.html > > > Reported-by: Russell King <rmk+kernel@arm.linux.org.uk> > Cc: Rajendra Nayak <rnayak@ti.com> > Cc: Santosh Shilimkar <santosh.shilimkar@ti.com> > Cc: Benoīt Cousson <b-cousson@ti.com> > Signed-off-by: Paul Walmsley <paul@pwsan.com> > --- Have tried similar fix to remove WARNS() but since Rajendra's split series was addressing it correctly, I dropped that patch. Anyways... Acked-by: Santosh Shilimkar <santosh.shilimkar@ti.com> Regards, Santosh -- 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] 16+ messages in thread
* RE: State of SDP4430 platform 2011-01-16 6:25 ` Santosh Shilimkar @ 2011-01-17 10:07 ` Santosh Shilimkar 2011-01-17 23:19 ` Paul Walmsley 2011-02-06 9:49 ` Russell King - ARM Linux 0 siblings, 2 replies; 16+ messages in thread From: Santosh Shilimkar @ 2011-01-17 10:07 UTC (permalink / raw) To: Paul Walmsley, Russell King - ARM Linux; +Cc: linux-omap > -----Original Message----- > From: Santosh Shilimkar [mailto:santosh.shilimkar@ti.com] > Sent: Sunday, January 16, 2011 11:56 AM > To: Paul Walmsley; Russell King - ARM Linux > Cc: linux-omap@vger.kernel.org > Subject: RE: State of SDP4430 platform > > > -----Original Message----- > > From: linux-omap-owner@vger.kernel.org [mailto:linux-omap- > > owner@vger.kernel.org] On Behalf Of Paul Walmsley > > Sent: Sunday, January 16, 2011 11:37 AM > > To: Russell King - ARM Linux > > Cc: linux-omap@vger.kernel.org > > Subject: Re: State of SDP4430 platform > > [.....] > > > Other stuff that shows in this boot log: > > > > ... > > > > > - Bunch of regulators are returning errors (is this a problem?) > > > - I2C timeouts which add quite a bit to the boot-time > > > > These two are probably related. Looks like something is wrong > with > > communication with the TWL/TPS PMIC on that board. Those problems > > don't > > show up on the OMAP4430ES2 Panda here, so they are probably > > 4430SDP-specific. > > > > > Actually I don't see these errors which ring a bell. There was an > I2C pull related issue with ES1.0 silicon. I guess these timeouts > would show up only on ES1.0 OMAP4 boards and not on ES2.0 boards. > > Monday I will check on my ES1.0 board and if needed send an updated > bootloader ( setting up right pull values) or a patch to kernel. > The I2C timeout issue I could reproduce on my ES1.0 board. It's ES1.0 specific issue because I2C burst mode wasn't fuctional on it. Twl RTC driver uses I2C burst mode and hence it times out. Other TWL I2C module has no such issue. The pull work-around we tried was not reliable hence it was dropped. In short the TWL RTC driver won't function on ES1.0. Apart from that rest of the I2C clients should work as usual. Regards, Santosh ^ permalink raw reply [flat|nested] 16+ messages in thread
* RE: State of SDP4430 platform 2011-01-17 10:07 ` Santosh Shilimkar @ 2011-01-17 23:19 ` Paul Walmsley 2011-01-18 6:53 ` Santosh Shilimkar 2011-01-19 15:26 ` Krishnamoorthy, Balaji T 2011-02-06 9:49 ` Russell King - ARM Linux 1 sibling, 2 replies; 16+ messages in thread From: Paul Walmsley @ 2011-01-17 23:19 UTC (permalink / raw) To: Santosh Shilimkar; +Cc: Russell King - ARM Linux, linux-omap On Mon, 17 Jan 2011, Santosh Shilimkar wrote: > The I2C timeout issue I could reproduce on my ES1.0 board. It's ES1.0 > specific issue because I2C burst mode wasn't fuctional on it. Twl RTC > driver uses I2C burst mode and hence it times out. Other TWL I2C > module has no such issue. > The pull work-around we tried was not reliable hence it was dropped. > > In short the TWL RTC driver won't function on ES1.0. Apart from that > rest of the I2C clients should work as usual. Looks like the IRQ handling code uses it too: $ egrep -r 'twl_i2c_(write|read)\(' drivers/ | egrep -v twl-core | egrep -v 4030 drivers/mfd/twl6030-irq.c: ret = twl_i2c_read(TWL_MODULE_PIH, sts.bytes, drivers/mfd/twl6030-irq.c: ret = twl_i2c_write(TWL_MODULE_PIH, sts.bytes, drivers/mfd/twl6030-irq.c: ret = twl_i2c_write(TWL_MODULE_PIH, &mask[0], drivers/mfd/twl6030-irq.c: ret = twl_i2c_write(TWL_MODULE_PIH, &mask[0], drivers/mfd/twl6030-irq.c: ret = twl_i2c_write(TWL_MODULE_PIH, &mask[0], drivers/rtc/rtc-twl.c: ret = twl_i2c_read(TWL_MODULE_RTC, rtc_data, drivers/rtc/rtc-twl.c: ret = twl_i2c_write(TWL_MODULE_RTC, rtc_data, drivers/rtc/rtc-twl.c: ret = twl_i2c_read(TWL_MODULE_RTC, rtc_data, drivers/rtc/rtc-twl.c: ret = twl_i2c_write(TWL_MODULE_RTC, alarm_data, $ I'd assume this also would affect other, non-TWL, I2C endpoints, no? Sounds like a platform_data flag should be passed into the I2C driver code to indicate that burst transactions are buggy on OMAP4430ES1. - Paul ^ permalink raw reply [flat|nested] 16+ messages in thread
* RE: State of SDP4430 platform 2011-01-17 23:19 ` Paul Walmsley @ 2011-01-18 6:53 ` Santosh Shilimkar 2011-01-19 15:26 ` Krishnamoorthy, Balaji T 1 sibling, 0 replies; 16+ messages in thread From: Santosh Shilimkar @ 2011-01-18 6:53 UTC (permalink / raw) To: Paul Walmsley, Balaji T Krishnamoorthy Cc: Russell King - ARM Linux, linux-omap (+ Balaji TK) > -----Original Message----- > From: Paul Walmsley [mailto:paul@pwsan.com] > Sent: Tuesday, January 18, 2011 4:49 AM > To: Santosh Shilimkar > Cc: Russell King - ARM Linux; linux-omap@vger.kernel.org > Subject: RE: State of SDP4430 platform > > On Mon, 17 Jan 2011, Santosh Shilimkar wrote: > > > The I2C timeout issue I could reproduce on my ES1.0 board. It's > ES1.0 > > specific issue because I2C burst mode wasn't fuctional on it. Twl > RTC > > driver uses I2C burst mode and hence it times out. Other TWL I2C > > module has no such issue. > > The pull work-around we tried was not reliable hence it was > dropped. > > > > In short the TWL RTC driver won't function on ES1.0. Apart from > that > > rest of the I2C clients should work as usual. > > Looks like the IRQ handling code uses it too: > > $ egrep -r 'twl_i2c_(write|read)\(' drivers/ | egrep -v twl-core | > egrep -v 4030 > drivers/mfd/twl6030-irq.c: ret = > twl_i2c_read(TWL_MODULE_PIH, sts.bytes, > drivers/mfd/twl6030-irq.c: ret = > twl_i2c_write(TWL_MODULE_PIH, sts.bytes, > drivers/mfd/twl6030-irq.c: ret = twl_i2c_write(TWL_MODULE_PIH, > &mask[0], > drivers/mfd/twl6030-irq.c: ret = twl_i2c_write(TWL_MODULE_PIH, > &mask[0], > drivers/mfd/twl6030-irq.c: ret = twl_i2c_write(TWL_MODULE_PIH, > &mask[0], > drivers/rtc/rtc-twl.c: ret = twl_i2c_read(TWL_MODULE_RTC, rtc_data, > drivers/rtc/rtc-twl.c: ret = twl_i2c_write(TWL_MODULE_RTC, > rtc_data, > drivers/rtc/rtc-twl.c: ret = twl_i2c_read(TWL_MODULE_RTC, rtc_data, > drivers/rtc/rtc-twl.c: ret = twl_i2c_write(TWL_MODULE_RTC, > alarm_data, > $ > > I'd assume this also would affect other, non-TWL, I2C endpoints, no? > > Sounds like a platform_data flag should be passed into the I2C > driver code > to indicate that burst transactions are buggy on OMAP4430ES1. > As per Balaji other phoenix I2C modules works fine except RTC. In that case RTC needed some patching. Regards, Santosh ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: State of SDP4430 platform 2011-01-17 23:19 ` Paul Walmsley 2011-01-18 6:53 ` Santosh Shilimkar @ 2011-01-19 15:26 ` Krishnamoorthy, Balaji T 2011-01-19 23:26 ` Paul Walmsley 1 sibling, 1 reply; 16+ messages in thread From: Krishnamoorthy, Balaji T @ 2011-01-19 15:26 UTC (permalink / raw) To: Paul Walmsley; +Cc: Santosh Shilimkar, Russell King - ARM Linux, linux-omap On Tue, Jan 18, 2011 at 4:49 AM, Paul Walmsley <paul@pwsan.com> wrote: > On Mon, 17 Jan 2011, Santosh Shilimkar wrote: > >> The I2C timeout issue I could reproduce on my ES1.0 board. It's ES1.0 >> specific issue because I2C burst mode wasn't fuctional on it. Twl RTC >> driver uses I2C burst mode and hence it times out. Other TWL I2C >> module has no such issue. >> The pull work-around we tried was not reliable hence it was dropped. >> >> In short the TWL RTC driver won't function on ES1.0. Apart from that >> rest of the I2C clients should work as usual. > > Looks like the IRQ handling code uses it too: > > $ egrep -r 'twl_i2c_(write|read)\(' drivers/ | egrep -v twl-core | egrep -v 4030 > drivers/mfd/twl6030-irq.c: ret = twl_i2c_read(TWL_MODULE_PIH, sts.bytes, > drivers/mfd/twl6030-irq.c: ret = twl_i2c_write(TWL_MODULE_PIH, sts.bytes, > drivers/mfd/twl6030-irq.c: ret = twl_i2c_write(TWL_MODULE_PIH, &mask[0], > drivers/mfd/twl6030-irq.c: ret = twl_i2c_write(TWL_MODULE_PIH, &mask[0], > drivers/mfd/twl6030-irq.c: ret = twl_i2c_write(TWL_MODULE_PIH, &mask[0], > drivers/rtc/rtc-twl.c: ret = twl_i2c_read(TWL_MODULE_RTC, rtc_data, > drivers/rtc/rtc-twl.c: ret = twl_i2c_write(TWL_MODULE_RTC, rtc_data, > drivers/rtc/rtc-twl.c: ret = twl_i2c_read(TWL_MODULE_RTC, rtc_data, > drivers/rtc/rtc-twl.c: ret = twl_i2c_write(TWL_MODULE_RTC, alarm_data, > $ > > I'd assume this also would affect other, non-TWL, I2C endpoints, no? > in ES1, timeouts were observed only with RTC. I2C burst access to IRQ registers and bq24156 were OK > Sounds like a platform_data flag should be passed into the I2C driver code > to indicate that burst transactions are buggy on OMAP4430ES1. > > > - Paul > -- > 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] 16+ messages in thread
* Re: State of SDP4430 platform 2011-01-19 15:26 ` Krishnamoorthy, Balaji T @ 2011-01-19 23:26 ` Paul Walmsley 2011-01-19 23:27 ` Paul Walmsley 0 siblings, 1 reply; 16+ messages in thread From: Paul Walmsley @ 2011-01-19 23:26 UTC (permalink / raw) To: Krishnamoorthy, Balaji T Cc: Santosh Shilimkar, Russell King - ARM Linux, linux-omap Hi, On Wed, 19 Jan 2011, Krishnamoorthy, Balaji T wrote: > in ES1, timeouts were observed only with RTC. > I2C burst access to IRQ registers and bq24156 were OK Was an errata generated for this bug? - Paul ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: State of SDP4430 platform 2011-01-19 23:26 ` Paul Walmsley @ 2011-01-19 23:27 ` Paul Walmsley 2011-02-07 23:49 ` Paul Walmsley 0 siblings, 1 reply; 16+ messages in thread From: Paul Walmsley @ 2011-01-19 23:27 UTC (permalink / raw) To: Krishnamoorthy, Balaji T Cc: Santosh Shilimkar, Russell King - ARM Linux, linux-omap On Wed, 19 Jan 2011, Paul Walmsley wrote: > On Wed, 19 Jan 2011, Krishnamoorthy, Balaji T wrote: > > > in ES1, timeouts were observed only with RTC. > > I2C burst access to IRQ registers and bq24156 were OK > > Was an errata generated for this bug? er, erratum, pardon me... - Paul ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: State of SDP4430 platform 2011-01-19 23:27 ` Paul Walmsley @ 2011-02-07 23:49 ` Paul Walmsley 2011-03-02 18:50 ` Paul Walmsley 0 siblings, 1 reply; 16+ messages in thread From: Paul Walmsley @ 2011-02-07 23:49 UTC (permalink / raw) To: Krishnamoorthy, Balaji T Cc: Santosh Shilimkar, Russell King - ARM Linux, linux-omap Balaji, On Wed, 19 Jan 2011, Paul Walmsley wrote: > On Wed, 19 Jan 2011, Paul Walmsley wrote: > > > On Wed, 19 Jan 2011, Krishnamoorthy, Balaji T wrote: > > > > > in ES1, timeouts were observed only with RTC. > > > I2C burst access to IRQ registers and bq24156 were OK > > > > Was an errata generated for this bug? > > er, erratum, pardon me... Is an erratum present for this bug? Also, will you generate a patch for this to at least warn the user when this situation occurs? - Paul ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: State of SDP4430 platform 2011-02-07 23:49 ` Paul Walmsley @ 2011-03-02 18:50 ` Paul Walmsley 2011-03-03 15:23 ` Krishnamoorthy, Balaji T 0 siblings, 1 reply; 16+ messages in thread From: Paul Walmsley @ 2011-03-02 18:50 UTC (permalink / raw) To: Krishnamoorthy, Balaji T Cc: Santosh Shilimkar, Russell King - ARM Linux, linux-omap Balaji, On Mon, 7 Feb 2011, Paul Walmsley wrote: > On Wed, 19 Jan 2011, Paul Walmsley wrote: > > > On Wed, 19 Jan 2011, Paul Walmsley wrote: > > > > > On Wed, 19 Jan 2011, Krishnamoorthy, Balaji T wrote: > > > > > > > in ES1, timeouts were observed only with RTC. > > > > I2C burst access to IRQ registers and bq24156 were OK > > > > > > Was an errata generated for this bug? > > > > er, erratum, pardon me... > > Is an erratum present for this bug? > > Also, will you generate a patch for this to at least warn the user when > this situation occurs? Still waiting for a response to this. - Paul ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: State of SDP4430 platform 2011-03-02 18:50 ` Paul Walmsley @ 2011-03-03 15:23 ` Krishnamoorthy, Balaji T 0 siblings, 0 replies; 16+ messages in thread From: Krishnamoorthy, Balaji T @ 2011-03-03 15:23 UTC (permalink / raw) To: Paul Walmsley; +Cc: Santosh Shilimkar, Russell King - ARM Linux, linux-omap >> > > > in ES1, timeouts were observed only with RTC. >> > > > I2C burst access to IRQ registers and bq24156 were OK >> > > >> > > Was an errata generated for this bug? >> > >> > er, erratum, pardon me... >> >> Is an erratum present for this bug? >> >> Also, will you generate a patch for this to at least warn the user when >> this situation occurs? > > Still waiting for a response to this. Apologies for the delay Could only find Phoenix TWL6030 - ProDB00107890 for this errata This is not related to I2C module on OMAP4 so fixing in twl-core.c Description: I2C FS burst mode not functional Glitch in the I2C Data line when the I2C controller does a Burst Read Have tried to workaround by using single byte read for Phoenix ES1.0 http://www.mail-archive.com/linux-omap@vger.kernel.org/msg46054.html > > > - Paul > ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: State of SDP4430 platform 2011-01-17 10:07 ` Santosh Shilimkar 2011-01-17 23:19 ` Paul Walmsley @ 2011-02-06 9:49 ` Russell King - ARM Linux 2011-02-07 6:05 ` Santosh Shilimkar 2011-02-07 6:58 ` Krishnamoorthy, Balaji T 1 sibling, 2 replies; 16+ messages in thread From: Russell King - ARM Linux @ 2011-02-06 9:49 UTC (permalink / raw) To: Santosh Shilimkar; +Cc: Paul Walmsley, linux-omap On Mon, Jan 17, 2011 at 03:37:34PM +0530, Santosh Shilimkar wrote: > The I2C timeout issue I could reproduce on my ES1.0 board. It's ES1.0 > specific issue because I2C burst mode wasn't fuctional on it. Twl RTC > driver uses I2C burst mode and hence it times out. Other TWL I2C > module has no such issue. > The pull work-around we tried was not reliable hence it was dropped. > > In short the TWL RTC driver won't function on ES1.0. Apart from that > rest of the I2C clients should work as usual. The ES2.2 OMAP4 arrived on Friday. Fitting it resulted in no change to the I2C timeouts: Linux version 2.6.38-rc3+ (rmk@rmk-PC) (gcc version 4.3.5 (GCC) ) #167 SMP PREEMPT Sat Feb 5 17:56:32 GMT 2011 CPU: ARMv7 Processor [411fc092] revision 2 (ARMv7), cr=10c53c7f CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache Machine: OMAP4430 4430SDP board vmalloc area is too big, limiting to 864MB Memory policy: ECC disabled, Data cache writealloc OMAP4430 ES2.0 SRAM: Mapped pa 0x40300000 to va 0xfe400000 size: 0xe000 FIXME: omap44xx_sram_init not implemented On node 0 totalpages: 131072 free_area_init_node: node 0, pgdat c0374d40, node_mem_map c0396000 Normal zone: 64 pages used for memmap Normal zone: 0 pages reserved Normal zone: 8128 pages, LIFO batch:0 HighMem zone: 960 pages used for memmap HighMem zone: 121920 pages, LIFO batch:31 PERCPU: Embedded 7 pages/cpu @c079b000 s4192 r8192 d16288 u32768 pcpu-alloc: s4192 r8192 d16288 u32768 alloc=8*4096 pcpu-alloc: [0] 0 [0] 1 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048 Kernel command line: root=/dev/mmcblk0p2 rw mem=512M vmalloc=1G console=ttyO2,115200n8 rootdelay=2 PID hash table entries: 128 (order: -3, 512 bytes) Dentry cache hash table entries: 4096 (order: 2, 16384 bytes) Inode-cache hash table entries: 2048 (order: 1, 8192 bytes) Memory: 512MB = 512MB total Memory: 516408k/516408k available, 7880k reserved, 491520K highmem Virtual kernel memory layout: vector : 0xffff0000 - 0xffff1000 ( 4 kB) fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB) DMA : 0xffc00000 - 0xffe00000 ( 2 MB) vmalloc : 0xc2800000 - 0xf8000000 ( 856 MB) lowmem : 0xc0000000 - 0xc2000000 ( 32 MB) pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB) modules : 0xbf000000 - 0xbfe00000 ( 14 MB) .init : 0xc0008000 - 0xc002f000 ( 156 kB) .text : 0xc002f000 - 0xc0347000 (3168 kB) .data : 0xc0348000 - 0xc0375700 ( 182 kB) SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=2, Nodes=1 Preemptable hierarchical RCU implementation. RCU-based detection of stalled CPUs is disabled. Verbose stalled-CPUs detection is disabled. NR_IRQS:402 clockdomain: l3_dma_clkdm: clkdm_clear_all_wkdeps: not yet implemented clockdomain: emu_sys_clkdm: OMAP4 wakeup/sleep dependency support: not yet implemented clockdomain: emu_sys_clkdm: clkdm_clear_all_wkdeps: not yet implemented clockdomain: l4_wkup_clkdm: OMAP4 wakeup/sleep dependency support: not yet implemented clockdomain: l4_wkup_clkdm: clkdm_clear_all_wkdeps: not yet implemented clockdomain: l3_dss_clkdm: clkdm_clear_all_wkdeps: not yet implemented clockdomain: iss_clkdm: clkdm_clear_all_wkdeps: not yet implemented clockdomain: l3_d2d_clkdm: clkdm_clear_all_wkdeps: not yet implemented clockdomain: l3_1_clkdm: OMAP4 wakeup/sleep dependency support: not yet implemented clockdomain: l3_1_clkdm: clkdm_clear_all_wkdeps: not yet implemented clockdomain: l3_2_clkdm: OMAP4 wakeup/sleep dependency support: not yet implemented clockdomain: l3_2_clkdm: clkdm_clear_all_wkdeps: not yet implemented clockdomain: ducati_clkdm: clkdm_clear_all_wkdeps: not yet implemented clockdomain: l4_ao_clkdm: clkdm_clear_all_wkdeps: not yet implemented clockdomain: l3_emif_clkdm: clkdm_clear_all_wkdeps: not yet implemented clockdomain: mpu1_clkdm: clkdm_clear_all_wkdeps: not yet implemented clockdomain: mpu0_clkdm: clkdm_clear_all_wkdeps: not yet implemented clockdomain: mpuss_clkdm: clkdm_clear_all_wkdeps: not yet implemented clockdomain: l3_init_clkdm: clkdm_clear_all_wkdeps: not yet implemented clockdomain: l3_instr_clkdm: clkdm_clear_all_wkdeps: not yet implemented clockdomain: abe_clkdm: clkdm_clear_all_wkdeps: not yet implemented clockdomain: l4_per_clkdm: clkdm_clear_all_wkdeps: not yet implemented clockdomain: l4_secure_clkdm: clkdm_clear_all_wkdeps: not yet implemented clockdomain: ivahd_clkdm: clkdm_clear_all_wkdeps: not yet implemented clockdomain: l3_gfx_clkdm: clkdm_clear_all_wkdeps: not yet implemented clockdomain: tesla_clkdm: clkdm_clear_all_wkdeps: not yet implemented clockdomain: l4_cfg_clkdm: OMAP4 wakeup/sleep dependency support: not yet implemented clockdomain: l4_cfg_clkdm: clkdm_clear_all_wkdeps: not yet implemented clockdomain: l4_cefuse_clkdm: clkdm_clear_all_wkdeps: not yet implemented omap_hwmod: l3_div_ck: missing clockdomain for l3_div_ck. omap_hwmod: dpll_mpu_m2_ck: missing clockdomain for dpll_mpu_m2_ck. GPMC revision 6.0 OMAP clockevent source: GPTIMER1 at 32768 Hz sched_clock: 32 bits at 32kHz, resolution 30517ns, wraps every 131071999ms Console: colour dummy device 80x30 Calibrating delay loop... 2013.49 BogoMIPS (lpj=7864320) pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok L310 cache controller enabled l2x0: 16 ways, CACHE_ID 0x410000c4, AUX_CTRL 0x7e470000, Cache size: 1048576 B CPU1: Booted secondary processor CPU1: Unknown IPI message 0x1 Brought up 2 CPUs SMP: Total of 2 processors activated (4026.98 BogoMIPS). print_constraints: dummy: NET: Registered protocol family 16 OMAP GPIO hardware version 0.1 omap_device: omap_gpio.1: new worst case activate latency 0: 30517 OMAP GPIO hardware version 0.1 OMAP GPIO hardware version 0.1 OMAP GPIO hardware version 0.1 OMAP GPIO hardware version 0.1 OMAP GPIO hardware version 0.1 omap_mux_init: Add partition: #1: core, flags: 2 omap_mux_init: Add partition: #2: wkup, flags: 2 omap_device: omap_uart.2: new worst case activate latency 0: 30517 pm_dbg_init: only OMAP3 supported OMAP DMA hardware revision 0.0 bio: create slab <bio-0> at 0 omap_i2c omap_i2c.1: bus 1 rev4.0 at 400 kHz Skipping twl internal clock init and using bootloader value (unknown osc rate) twl6030: PIH (irq 39) chaining IRQs 368..387 print_constraints: VMMC: 1200 <--> 3000 mV at 3000 mV normal standby print_constraints: VPP: 1800 <--> 2500 mV at 1900 mV normal standby print_constraints: VUSIM: 1200 <--> 2900 mV at 1800 mV normal standby machine_constraints_voltage: VANA: failed to apply 2100000uV constraint twl_reg twl_reg.43: can't register VANA, -22 twl_reg: probe of twl_reg.43 failed with error -22 machine_constraints_voltage: VCXIO: failed to apply 1800000uV constraint twl_reg twl_reg.44: can't register VCXIO, -22 twl_reg: probe of twl_reg.44 failed with error -22 machine_constraints_voltage: VDAC: failed to apply 1800000uV constraint twl_reg twl_reg.45: can't register VDAC, -22 twl_reg: probe of twl_reg.45 failed with error -22 print_constraints: VAUX1_6030: 1000 <--> 3000 mV at 2800 mV normal standby print_constraints: VAUX2_6030: 1200 <--> 2800 mV at 1800 mV normal standby print_constraints: VAUX3_6030: 1000 <--> 3000 mV at 1200 mV normal standby omap_device: omap_i2c.2: new worst case activate latency 0: 30517 omap_i2c omap_i2c.2: bus 2 rev4.0 at 400 kHz omap_i2c omap_i2c.3: bus 3 rev4.0 at 400 kHz omap_i2c omap_i2c.4: bus 4 rev4.0 at 400 kHz omap_device: omap_i2c.4: new worst case deactivate latency 0: 30517 DMA-API: preallocated 4096 debug entries DMA-API: debugging enabled by kernel config Switching to clocksource 32k_counter NET: Registered protocol family 2 IP route cache hash table entries: 1024 (order: 0, 4096 bytes) TCP established hash table entries: 1024 (order: 1, 8192 bytes) TCP bind hash table entries: 1024 (order: 1, 12288 bytes) TCP: Hash tables configured (established 1024 bind 1024) TCP reno registered UDP hash table entries: 128 (order: 0, 4096 bytes) UDP-Lite hash table entries: 128 (order: 0, 4096 bytes) NET: Registered protocol family 1 RPC: Registered udp transport module. RPC: Registered tcp transport module. RPC: Registered tcp NFSv4.1 backchannel transport module. NetWinder Floating Point Emulator V0.97 (double precision) highmem bounce pool size: 64 pages VFS: Disk quotas dquot_6.5.2 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) msgmni has been set to 48 io scheduler noop registered io scheduler deadline registered io scheduler cfq registered (default) Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled omap_uart.0: ttyO0 at MMIO 0x4806a000 (irq = 104) is a OMAP UART0 omap_uart.1: ttyO1 at MMIO 0x4806c000 (irq = 105) is a OMAP UART1 omap_uart.2: ttyO2 at MMIO 0x48020000 (irq = 106) is a OMAP UART2 console [ttyO2] enabled omap_uart.3: ttyO3 at MMIO 0x4806e000 (irq = 102) is a OMAP UART3 brd: module loaded loop: module loaded ks8851 spi1.0: message enable is 0 ks8851 spi1.0: eth0: revision 0, MAC 08:00:28:01:4d:c6, IRQ 194 input: gpio-keys as /devices/platform/gpio-keys/input/input0 twl_rtc twl_rtc: rtc core: registered twl_rtc as rtc0 i2c /dev entries driver lm75 3-0048: hwmon0: sensor 'tmp105' omap_i2c omap_i2c.1: controller timed out omap_i2c omap_i2c.1: controller timed out omap_i2c omap_i2c.2: controller timed out omap_i2c omap_i2c.2: controller timed out omap_i2c omap_i2c.2: controller timed out omap_i2c omap_i2c.2: controller timed out omap_i2c omap_i2c.3: controller timed out omap_i2c omap_i2c.3: controller timed out omap_i2c omap_i2c.3: controller timed out omap_i2c omap_i2c.4: controller timed out omap_i2c omap_i2c.4: controller timed out omap_i2c omap_i2c.4: controller timed out omap_i2c omap_i2c.4: controller timed out Registered led device: omap4:green:debug0 Registered led device: omap4:green:debug1 Registered led device: omap4:green:debug2 Registered led device: omap4:green:debug3 Registered led device: omap4:green:debug4 Registered led device: omap4:blue:user Registered led device: omap4:red:user Registered led device: omap4:green:user TCP cubic registered NET: Registered protocol family 17 VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 1 omap2_set_init_voltage: unable to find boot up OPP for vdd_mpu omap2_set_init_voltage: Unable to put vdd_mpu to its init voltage omap2_set_init_voltage: unable to find boot up OPP for vdd_iva omap2_set_init_voltage: Unable to put vdd_iva to its init voltage Power Management for TI OMAP4. regulator_init_complete: VAUX3_6030: incomplete constraints, leaving on regulator_init_complete: VAUX2_6030: incomplete constraints, leaving on regulator_init_complete: VUSIM: incomplete constraints, leaving on regulator_init_complete: VPP: incomplete constraints, leaving on twl_rtc twl_rtc: setting system clock to 2000-01-01 00:10:18 UTC (946685418) Waiting 2sec before mounting root device... mmc0: host does not support reading read-only switch. assuming write-enable. mmc0: new high speed SD card at address 0002 mmcblk0: mmc0:0002 00000 971 MiB mmcblk0: p1 p2 mmc1: new high speed MMC card at address 0001 mmcblk1: mmc1:0001 SEM08G 7.39 GiB mmcblk1: unknown partition table EXT3-fs: barriers not enabled kjournald starting. Commit interval 5 seconds EXT3-fs (mmcblk0p2): warning: maximal mount count reached, running e2fsck is recommended EXT3-fs (mmcblk0p2): using internal journal EXT3-fs (mmcblk0p2): recovery complete EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode VFS: Mounted root (ext3 filesystem) on device 179:2. Freeing init memory: 156K udevd (471): /proc/471/oom_adj is deprecated, please use /proc/471/oom_score_adj instead. udevd version 124 started EXT3-fs (mmcblk0p2): error: unrecognized mount option "relatime" or missing value ^ permalink raw reply [flat|nested] 16+ messages in thread
* RE: State of SDP4430 platform 2011-02-06 9:49 ` Russell King - ARM Linux @ 2011-02-07 6:05 ` Santosh Shilimkar 2011-02-07 6:58 ` Krishnamoorthy, Balaji T 1 sibling, 0 replies; 16+ messages in thread From: Santosh Shilimkar @ 2011-02-07 6:05 UTC (permalink / raw) To: Russell King - ARM Linux; +Cc: Paul Walmsley, linux-omap > -----Original Message----- > From: Russell King - ARM Linux [mailto:linux@arm.linux.org.uk] > Sent: Sunday, February 06, 2011 3:19 PM > To: Santosh Shilimkar > Cc: Paul Walmsley; linux-omap@vger.kernel.org > Subject: Re: State of SDP4430 platform > > On Mon, Jan 17, 2011 at 03:37:34PM +0530, Santosh Shilimkar wrote: > > The I2C timeout issue I could reproduce on my ES1.0 board. It's > ES1.0 > > specific issue because I2C burst mode wasn't fuctional on it. Twl > RTC > > driver uses I2C burst mode and hence it times out. Other TWL I2C > > module has no such issue. > > The pull work-around we tried was not reliable hence it was > dropped. > > > > In short the TWL RTC driver won't function on ES1.0. Apart from > that > > rest of the I2C clients should work as usual. > > The ES2.2 OMAP4 arrived on Friday. Fitting it resulted in no change > to the I2C timeouts: > Good that finally the tile reached you. Will have somebody look at this. Meanwhile, can you send your .config? With the regular omap2plus defconfig, we didn't see the issue last time. Regards, Santosh ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: State of SDP4430 platform 2011-02-06 9:49 ` Russell King - ARM Linux 2011-02-07 6:05 ` Santosh Shilimkar @ 2011-02-07 6:58 ` Krishnamoorthy, Balaji T 1 sibling, 0 replies; 16+ messages in thread From: Krishnamoorthy, Balaji T @ 2011-02-07 6:58 UTC (permalink / raw) To: Russell King - ARM Linux; +Cc: Santosh Shilimkar, Paul Walmsley, linux-omap On Sun, Feb 6, 2011 at 3:19 PM, Russell King - ARM Linux <linux@arm.linux.org.uk> wrote: > lm75 3-0048: hwmon0: sensor 'tmp105' > omap_i2c omap_i2c.1: controller timed out > omap_i2c omap_i2c.1: controller timed out > omap_i2c omap_i2c.2: controller timed out > omap_i2c omap_i2c.2: controller timed out > omap_i2c omap_i2c.2: controller timed out > omap_i2c omap_i2c.2: controller timed out > omap_i2c omap_i2c.3: controller timed out > omap_i2c omap_i2c.3: controller timed out > omap_i2c omap_i2c.3: controller timed out > omap_i2c omap_i2c.4: controller timed out > omap_i2c omap_i2c.4: controller timed out > omap_i2c omap_i2c.4: controller timed out > omap_i2c omap_i2c.4: controller timed out These timeouts are from tmp105 driver lm75 - temperature sensor is trying to probe all i2c bus and it gets NACK. i2c controller timeout after NACK is due to a bug in omap_i2c driver. Will send a patch for this. Can you disable LM75 untill then. ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: State of SDP4430 platform 2011-01-16 1:09 State of SDP4430 platform Russell King - ARM Linux 2011-01-16 6:06 ` Paul Walmsley @ 2011-02-07 8:18 ` Gulati, Shweta 1 sibling, 0 replies; 16+ messages in thread From: Gulati, Shweta @ 2011-02-07 8:18 UTC (permalink / raw) To: Russell King - ARM Linux; +Cc: linux-omap Hi, On Sun, Jan 16, 2011 at 6:39 AM, Russell King - ARM Linux <linux@arm.linux.org.uk> wrote: > It's probably best if I just quote the boot log, and people see about > fixing the masses of WARN_ON()s. Notice that it completely obliterates > the early part of the boot log due to the number of WARN_ON()s triggered. > > Other stuff that shows in this boot log: > - There's a couple of complaints about missing clock domains for some clocks > - Bunch of regulators are returning errors (is this a problem?) > - I2C timeouts which add quite a bit to the boot-time > - missing vdd_mpu/vdd_iva? (with additional blank lines emitted) The warning coming as : "unable to find boot up OPP for vdd_mpu" and "unable to find boot up OPP for vdd_iva" is due to different OPP definition in voltage layer and OPP layer in current LO codebase. File arch/arm/mach-omap2/opp4xxx_data.c has mismatch in OPP50 and OPP100 voltage levels with those defined in voltage.c. We have discussion going with H/W folks to ensure what voltage level should be used for OPPs(Nominal voltage v/s Max voltage) Once we are finalized on that discussion, we would post patch to fix these warning. > Uncompressing Linux... done, booting the kernel. > 060768>] (warn_slowpath_common+0x0/0x70) from [<c006087c>] (warn_slowpath_fmt+0x38/0x40) > r8:c0359a10 r7:00000000 r6:00000060 r5:00000000 r4:00000000 > [<c0060844>] (warn_slowpath_fmt+0x0/0x40) from [<c004c84c>] (clkdm_clear_all_wkdeps+0x80/0x90) > r3:00002502 r2:c030688d > [<c004c7cc>] (clkdm_clear_all_wkdeps+0x0/0x90) from [<c004cf60>] (clkdm_init+0x14c/0x17c) > r5:c0359a10 r4:c0359b4c > [<c004ce14>] (clkdm_init+0x0/0x17c) from [<c0011758>] (omap44xx_clockdomains_init+0x18/0x20) > [<c0011740>] (omap44xx_clockdomains_init+0x0/0x20) from [<c000f0b0>] (omap2_init_common_infrastructure+0x28/0xa4) > [<c000f088>] (omap2_init_common_infrastructure+0x0/0xa4) from [<c0011d78>] (omap_4430sdp_init_irq+0x2c/0x54) > r4:00000001 > [<c0011d4c>] (omap_4430sdp_init_irq+0x0/0x54) from [<c000b87c>] (init_IRQ+0x1c/0x24) > r4:bfffffff > [<c000b860>] (init_IRQ+0x0/0x24) from [<c0008a78>] (start_kernel+0x194/0x314) > [<c00088e4>] (start_kernel+0x0/0x314) from [<80008040>] (0x80008040) > r8:80000000 r7:c0357c84 r6:c0028678 r5:c0354b70 r4:10c53c7d > ---[ end trace 1b75b31a2719ed2d ]--- > ------------[ cut here ]------------ > WARNING: at /home/rmk/git/linux-2.6-rmk/arch/arm/mach-omap2/prm2xxx_3xxx.h:264 clkdm_clear_all_wkdeps+0x80/0x90() > prm: omap2xxx/omap3xxx specific function and not suppose to be used on omap4 > Modules linked in: > Backtrace: > [<c003ec64>] (dump_backtrace+0x0/0x10c) from [<c0288be0>] (dump_stack+0x18/0x1c) > r7:c0347f08 r6:c004c84c r5:c030684e r4:00000108 > [<c0288bc8>] (dump_stack+0x0/0x1c) from [<c00607c0>] (warn_slowpath_common+0x58/0x70) > [<c0060768>] (warn_slowpath_common+0x0/0x70) from [<c006087c>] (warn_slowpath_fmt+0x38/0x40) > r8:c0359a10 r7:00000000 r6:00000060 r5:00000000 r4:00000000 > [<c0060844>] (warn_slowpath_fmt+0x0/0x40) from [<c004c84c>] (clkdm_clear_all_wkdeps+0x80/0x90) > r3:004cff02 r2:c030688d > [<c004c7cc>] (clkdm_clear_all_wkdeps+0x0/0x90) from [<c004cf60>] (clkdm_init+0x14c/0x17c) > r5:c0359a10 r4:c0359b20 > [<c004ce14>] (clkdm_init+0x0/0x17c) from [<c0011758>] (omap44xx_clockdomains_init+0x18/0x20) > [<c0011740>] (omap44xx_clockdomains_init+0x0/0x20) from [<c000f0b0>] (omap2_init_common_infrastructure+0x28/0xa4) > [<c000f088>] (omap2_init_common_infrastructure+0x0/0xa4) from [<c0011d78>] (omap_4430sdp_init_irq+0x2c/0x54) > r4:00000001 > [<c0011d4c>] (omap_4430sdp_init_irq+0x0/0x54) from [<c000b87c>] (init_IRQ+0x1c/0x24) > r4:bfffffff > [<c000b860>] (init_IRQ+0x0/0x24) from [<c0008a78>] (start_kernel+0x194/0x314) > [<c00088e4>] (start_kernel+0x0/0x314) from [<80008040>] (0x80008040) > r8:80000000 r7:c0357c84 r6:c0028678 r5:c0354b70 r4:10c53c7d > ---[ end trace 1b75b31a2719ed2e ]--- > ------------[ cut here ]------------ > WARNING: at /home/rmk/git/linux-2.6-rmk/arch/arm/mach-omap2/prm2xxx_3xxx.h:264 clkdm_clear_all_wkdeps+0x80/0x90() > prm: omap2xxx/omap3xxx specific function and not suppose to be used on omap4 > Modules linked in: > Backtrace: > [<c003ec64>] (dump_backtrace+0x0/0x10c) from [<c0288be0>] (dump_stack+0x18/0x1c) > r7:c0347f08 r6:c004c84c r5:c030684e r4:00000108 > [<c0288bc8>] (dump_stack+0x0/0x1c) from [<c00607c0>] (warn_slowpath_common+0x58/0x70) > [<c0060768>] (warn_slowpath_common+0x0/0x70) from [<c006087c>] (warn_slowpath_fmt+0x38/0x40) > r8:c0359a10 r7:00000000 r6:00000060 r5:00000000 r4:00000000 > [<c0060844>] (warn_slowpath_fmt+0x0/0x40) from [<c004c84c>] (clkdm_clear_all_wkdeps+0x80/0x90) > r3:00000002 r2:c030688d > [<c004c7cc>] (clkdm_clear_all_wkdeps+0x0/0x90) from [<c004cf60>] (clkdm_init+0x14c/0x17c) > r5:c0359a10 r4:c0359af4 > [<c004ce14>] (clkdm_init+0x0/0x17c) from [<c0011758>] (omap44xx_clockdomains_init+0x18/0x20) > [<c0011740>] (omap44xx_clockdomains_init+0x0/0x20) from [<c000f0b0>] (omap2_init_common_infrastructure+0x28/0xa4) > [<c000f088>] (omap2_init_common_infrastructure+0x0/0xa4) from [<c0011d78>] (omap_4430sdp_init_irq+0x2c/0x54) > r4:00000001 > [<c0011d4c>] (omap_4430sdp_init_irq+0x0/0x54) from [<c000b87c>] (init_IRQ+0x1c/0x24) > r4:bfffffff > [<c000b860>] (init_IRQ+0x0/0x24) from [<c0008a78>] (start_kernel+0x194/0x314) > [<c00088e4>] (start_kernel+0x0/0x314) from [<80008040>] (0x80008040) > r8:80000000 r7:c0357c84 r6:c0028678 r5:c0354b70 r4:10c53c7d > ---[ end trace 1b75b31a2719ed2f ]--- > ------------[ cut here ]------------ > WARNING: at /home/rmk/git/linux-2.6-rmk/arch/arm/mach-omap2/prm2xxx_3xxx.h:264 clkdm_clear_all_wkdeps+0x80/0x90() > prm: omap2xxx/omap3xxx specific function and not suppose to be used on omap4 > Modules linked in: > Backtrace: > [<c003ec64>] (dump_backtrace+0x0/0x10c) from [<c0288be0>] (dump_stack+0x18/0x1c) > r7:c0347f08 r6:c004c84c r5:c030684e r4:00000108 > [<c0288bc8>] (dump_stack+0x0/0x1c) from [<c00607c0>] (warn_slowpath_common+0x58/0x70) > [<c0060768>] (warn_slowpath_common+0x0/0x70) from [<c006087c>] (warn_slowpath_fmt+0x38/0x40) > r8:c0359a10 r7:00000000 r6:00000060 r5:00000000 r4:00000000 > [<c0060844>] (warn_slowpath_fmt+0x0/0x40) from [<c004c84c>] (clkdm_clear_all_wkdeps+0x80/0x90) > r3:00000102 r2:c030688d > [<c004c7cc>] (clkdm_clear_all_wkdeps+0x0/0x90) from [<c004cf60>] (clkdm_init+0x14c/0x17c) > r5:c0359a10 r4:c0359ac8 > [<c004ce14>] (clkdm_init+0x0/0x17c) from [<c0011758>] (omap44xx_clockdomains_init+0x18/0x20) > [<c0011740>] (omap44xx_clockdomains_init+0x0/0x20) from [<c000f0b0>] (omap2_init_common_infrastructure+0x28/0xa4) > [<c000f088>] (omap2_init_common_infrastructure+0x0/0xa4) from [<c0011d78>] (omap_4430sdp_init_irq+0x2c/0x54) > r4:00000001 > [<c0011d4c>] (omap_4430sdp_init_irq+0x0/0x54) from [<c000b87c>] (init_IRQ+0x1c/0x24) > r4:bfffffff > [<c000b860>] (init_IRQ+0x0/0x24) from [<c0008a78>] (start_kernel+0x194/0x314) > [<c00088e4>] (start_kernel+0x0/0x314) from [<80008040>] (0x80008040) > r8:80000000 r7:c0357c84 r6:c0028678 r5:c0354b70 r4:10c53c7d > ---[ end trace 1b75b31a2719ed30 ]--- > ------------[ cut here ]------------ > WARNING: at /home/rmk/git/linux-2.6-rmk/arch/arm/mach-omap2/prm2xxx_3xxx.h:264 clkdm_clear_all_wkdeps+0x80/0x90() > prm: omap2xxx/omap3xxx specific function and not suppose to be used on omap4 > Modules linked in: > Backtrace: > [<c003ec64>] (dump_backtrace+0x0/0x10c) from [<c0288be0>] (dump_stack+0x18/0x1c) > r7:c0347f08 r6:c004c84c r5:c030684e r4:00000108 > [<c0288bc8>] (dump_stack+0x0/0x1c) from [<c00607c0>] (warn_slowpath_common+0x58/0x70) > [<c0060768>] (warn_slowpath_common+0x0/0x70) from [<c006087c>] (warn_slowpath_fmt+0x38/0x40) > r8:c0359a10 r7:00000000 r6:00000060 r5:00000000 r4:00000000 > [<c0060844>] (warn_slowpath_fmt+0x0/0x40) from [<c004c84c>] (clkdm_clear_all_wkdeps+0x80/0x90) > r3:00000302 r2:c030688d > [<c004c7cc>] (clkdm_clear_all_wkdeps+0x0/0x90) from [<c004cf60>] (clkdm_init+0x14c/0x17c) > r5:c0359a10 r4:c0359a9c > [<c004ce14>] (clkdm_init+0x0/0x17c) from [<c0011758>] (omap44xx_clockdomains_init+0x18/0x20) > [<c0011740>] (omap44xx_clockdomains_init+0x0/0x20) from [<c000f0b0>] (omap2_init_common_infrastructure+0x28/0xa4) > [<c000f088>] (omap2_init_common_infrastructure+0x0/0xa4) from [<c0011d78>] (omap_4430sdp_init_irq+0x2c/0x54) > r4:00000001 > [<c0011d4c>] (omap_4430sdp_init_irq+0x0/0x54) from [<c000b87c>] (init_IRQ+0x1c/0x24) > r4:bfffffff > [<c000b860>] (init_IRQ+0x0/0x24) from [<c0008a78>] (start_kernel+0x194/0x314) > [<c00088e4>] (start_kernel+0x0/0x314) from [<80008040>] (0x80008040) > r8:80000000 r7:c0357c84 r6:c0028678 r5:c0354b70 r4:10c53c7d > ---[ end trace 1b75b31a2719ed31 ]--- > ------------[ cut here ]------------ > WARNING: at /home/rmk/git/linux-2.6-rmk/arch/arm/mach-omap2/prm2xxx_3xxx.h:264 clkdm_clear_all_wkdeps+0x80/0x90() > prm: omap2xxx/omap3xxx specific function and not suppose to be used on omap4 > Modules linked in: > Backtrace: > [<c003ec64>] (dump_backtrace+0x0/0x10c) from [<c0288be0>] (dump_stack+0x18/0x1c) > r7:c0347f08 r6:c004c84c r5:c030684e r4:00000108 > [<c0288bc8>] (dump_stack+0x0/0x1c) from [<c00607c0>] (warn_slowpath_common+0x58/0x70) > [<c0060768>] (warn_slowpath_common+0x0/0x70) from [<c006087c>] (warn_slowpath_fmt+0x38/0x40) > r8:c0359a10 r7:00000000 r6:00000060 r5:00000000 r4:00000000 > [<c0060844>] (warn_slowpath_fmt+0x0/0x40) from [<c004c84c>] (clkdm_clear_all_wkdeps+0x80/0x90) > r3:00000102 r2:c030688d > [<c004c7cc>] (clkdm_clear_all_wkdeps+0x0/0x90) from [<c004cf60>] (clkdm_init+0x14c/0x17c) > r5:c0359a10 r4:c0359a70 > [<c004ce14>] (clkdm_init+0x0/0x17c) from [<c0011758>] (omap44xx_clockdomains_init+0x18/0x20) > [<c0011740>] (omap44xx_clockdomains_init+0x0/0x20) from [<c000f0b0>] (omap2_init_common_infrastructure+0x28/0xa4) > [<c000f088>] (omap2_init_common_infrastructure+0x0/0xa4) from [<c0011d78>] (omap_4430sdp_init_irq+0x2c/0x54) > r4:00000001 > [<c0011d4c>] (omap_4430sdp_init_irq+0x0/0x54) from [<c000b87c>] (init_IRQ+0x1c/0x24) > r4:bfffffff > [<c000b860>] (init_IRQ+0x0/0x24) from [<c0008a78>] (start_kernel+0x194/0x314) > [<c00088e4>] (start_kernel+0x0/0x314) from [<80008040>] (0x80008040) > r8:80000000 r7:c0357c84 r6:c0028678 r5:c0354b70 r4:10c53c7d > ---[ end trace 1b75b31a2719ed32 ]--- > ------------[ cut here ]------------ > WARNING: at /home/rmk/git/linux-2.6-rmk/arch/arm/mach-omap2/prm2xxx_3xxx.h:264 clkdm_clear_all_wkdeps+0x80/0x90() > prm: omap2xxx/omap3xxx specific function and not suppose to be used on omap4 > Modules linked in: > Backtrace: > [<c003ec64>] (dump_backtrace+0x0/0x10c) from [<c0288be0>] (dump_stack+0x18/0x1c) > r7:c0347f08 r6:c004c84c r5:c030684e r4:00000108 > [<c0288bc8>] (dump_stack+0x0/0x1c) from [<c00607c0>] (warn_slowpath_common+0x58/0x70) > [<c0060768>] (warn_slowpath_common+0x0/0x70) from [<c006087c>] (warn_slowpath_fmt+0x38/0x40) > r8:c0359a10 r7:00000000 r6:00000060 r5:00000000 r4:00000000 > [<c0060844>] (warn_slowpath_fmt+0x0/0x40) from [<c004c84c>] (clkdm_clear_all_wkdeps+0x80/0x90) > r3:00000001 r2:c030688d > [<c004c7cc>] (clkdm_clear_all_wkdeps+0x0/0x90) from [<c004cf60>] (clkdm_init+0x14c/0x17c) > r5:c0359a10 r4:c0359a44 > [<c004ce14>] (clkdm_init+0x0/0x17c) from [<c0011758>] (omap44xx_clockdomains_init+0x18/0x20) > [<c0011740>] (omap44xx_clockdomains_init+0x0/0x20) from [<c000f0b0>] (omap2_init_common_infrastructure+0x28/0xa4) > [<c000f088>] (omap2_init_common_infrastructure+0x0/0xa4) from [<c0011d78>] (omap_4430sdp_init_irq+0x2c/0x54) > r4:00000001 > [<c0011d4c>] (omap_4430sdp_init_irq+0x0/0x54) from [<c000b87c>] (init_IRQ+0x1c/0x24) > r4:bfffffff > [<c000b860>] (init_IRQ+0x0/0x24) from [<c0008a78>] (start_kernel+0x194/0x314) > [<c00088e4>] (start_kernel+0x0/0x314) from [<80008040>] (0x80008040) > r8:80000000 r7:c0357c84 r6:c0028678 r5:c0354b70 r4:10c53c7d > ---[ end trace 1b75b31a2719ed33 ]--- > ------------[ cut here ]------------ > WARNING: at /home/rmk/git/linux-2.6-rmk/arch/arm/mach-omap2/prm2xxx_3xxx.h:264 clkdm_clear_all_wkdeps+0x80/0x90() > prm: omap2xxx/omap3xxx specific function and not suppose to be used on omap4 > Modules linked in: > Backtrace: > [<c003ec64>] (dump_backtrace+0x0/0x10c) from [<c0288be0>] (dump_stack+0x18/0x1c) > r7:c0347f08 r6:c004c84c r5:c030684e r4:00000108 > [<c0288bc8>] (dump_stack+0x0/0x1c) from [<c00607c0>] (warn_slowpath_common+0x58/0x70) > [<c0060768>] (warn_slowpath_common+0x0/0x70) from [<c006087c>] (warn_slowpath_fmt+0x38/0x40) > r8:c0359a10 r7:00000000 r6:00000060 r5:00000000 r4:00000000 > [<c0060844>] (warn_slowpath_fmt+0x0/0x40) from [<c004c84c>] (clkdm_clear_all_wkdeps+0x80/0x90) > r3:00000002 r2:c030688d > [<c004c7cc>] (clkdm_clear_all_wkdeps+0x0/0x90) from [<c004cf60>] (clkdm_init+0x14c/0x17c) > r5:c0359a10 r4:c0359a18 > [<c004ce14>] (clkdm_init+0x0/0x17c) from [<c0011758>] (omap44xx_clockdomains_init+0x18/0x20) > [<c0011740>] (omap44xx_clockdomains_init+0x0/0x20) from [<c000f0b0>] (omap2_init_common_infrastructure+0x28/0xa4) > [<c000f088>] (omap2_init_common_infrastructure+0x0/0xa4) from [<c0011d78>] (omap_4430sdp_init_irq+0x2c/0x54) > r4:00000001 > [<c0011d4c>] (omap_4430sdp_init_irq+0x0/0x54) from [<c000b87c>] (init_IRQ+0x1c/0x24) > r4:bfffffff > [<c000b860>] (init_IRQ+0x0/0x24) from [<c0008a78>] (start_kernel+0x194/0x314) > [<c00088e4>] (start_kernel+0x0/0x314) from [<80008040>] (0x80008040) > r8:80000000 r7:c0357c84 r6:c0028678 r5:c0354b70 r4:10c53c7d > ---[ end trace 1b75b31a2719ed34 ]--- > omap_hwmod: l3_div_ck: missing clockdomain for l3_div_ck. > omap_hwmod: dpll_mpu_m2_ck: missing clockdomain for dpll_mpu_m2_ck. > GPMC revision 6.0 > OMAP clockevent source: GPTIMER1 at 32768 Hz > sched_clock: 32 bits at 32kHz, resolution 30517ns, wraps every 131071999ms > Console: colour dummy device 80x30 > Calibrating delay loop... 2013.49 BogoMIPS (lpj=7864320) > pid_max: default: 32768 minimum: 301 > Mount-cache hash table entries: 512 > CPU: Testing write buffer coherency: ok > L310 cache controller enabled > l2x0: 16 ways, CACHE_ID 0x410000c2, AUX_CTRL 0x0e050000, Cache size: 524288 B > CPU1: Booted secondary processor > CPU1: Unknown IPI message 0x1 > Brought up 2 CPUs > SMP: Total of 2 processors activated (4026.98 BogoMIPS). > print_constraints: dummy: > NET: Registered protocol family 16 > OMAP GPIO hardware version 0.1 > OMAP GPIO hardware version 0.1 > OMAP GPIO hardware version 0.1 > OMAP GPIO hardware version 0.1 > OMAP GPIO hardware version 0.1 > OMAP GPIO hardware version 0.1 > omap_mux_init: Add partition: #1: core, flags: 2 > omap_mux_init: Add partition: #2: wkup, flags: 2 > omap_device: omap_uart.1: new worst case deactivate latency 0: 30517 > omap_device: omap_uart.3: new worst case activate latency 0: 30517 > pm_dbg_init: only OMAP3 supported > OMAP DMA hardware revision 0.0 > bio: create slab <bio-0> at 0 > omap_i2c omap_i2c.1: bus 1 rev4.0 at 400 kHz > Skipping twl internal clock init and using bootloader value (unknown osc rate) > twl6030: PIH (irq 39) chaining IRQs 368..387 > print_constraints: VMMC: 1200 <--> 3000 mV at 3000 mV normal standby > print_constraints: VPP: 1800 <--> 2500 mV at 1900 mV normal standby > print_constraints: VUSIM: 1200 <--> 2900 mV at 1800 mV normal standby > machine_constraints_voltage: VANA: failed to apply 2100000uV constraint > twl_reg twl_reg.43: can't register VANA, -22 > twl_reg: probe of twl_reg.43 failed with error -22 > machine_constraints_voltage: VCXIO: failed to apply 1800000uV constraint > twl_reg twl_reg.44: can't register VCXIO, -22 > twl_reg: probe of twl_reg.44 failed with error -22 > machine_constraints_voltage: VDAC: failed to apply 1800000uV constraint > twl_reg twl_reg.45: can't register VDAC, -22 > twl_reg: probe of twl_reg.45 failed with error -22 > print_constraints: VAUX1_6030: 1000 <--> 3000 mV at 2800 mV normal standby > print_constraints: VAUX2_6030: 1200 <--> 2800 mV at 1800 mV normal standby > print_constraints: VAUX3_6030: 1000 <--> 3000 mV at 1200 mV normal standby > omap_i2c omap_i2c.2: bus 2 rev4.0 at 400 kHz > omap_i2c omap_i2c.3: bus 3 rev4.0 at 400 kHz > omap_i2c omap_i2c.4: bus 4 rev4.0 at 400 kHz > DMA-API: preallocated 4096 debug entries > DMA-API: debugging enabled by kernel config > Switching to clocksource 32k_counter > NET: Registered protocol family 2 > IP route cache hash table entries: 1024 (order: 0, 4096 bytes) > TCP established hash table entries: 1024 (order: 1, 8192 bytes) > TCP bind hash table entries: 1024 (order: 1, 12288 bytes) > TCP: Hash tables configured (established 1024 bind 1024) > TCP reno registered > UDP hash table entries: 128 (order: 0, 4096 bytes) > UDP-Lite hash table entries: 128 (order: 0, 4096 bytes) > NET: Registered protocol family 1 > RPC: Registered udp transport module. > RPC: Registered tcp transport module. > RPC: Registered tcp NFSv4.1 backchannel transport module. > NetWinder Floating Point Emulator V0.97 (double precision) > highmem bounce pool size: 64 pages > VFS: Disk quotas dquot_6.5.2 > Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) > msgmni has been set to 48 > io scheduler noop registered > io scheduler deadline registered > io scheduler cfq registered (default) > Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled > omap_uart.0: ttyO0 at MMIO 0x4806a000 (irq = 104) is a OMAP UART0 > omap_uart.1: ttyO1 at MMIO 0x4806c000 (irq = 105) is a OMAP UART1 > omap_uart.2: ttyO2 at MMIO 0x48020000 (irq = 106) is a OMAP UART2 > console [ttyO2] enabled > omap_uart.3: ttyO3 at MMIO 0x4806e000 (irq = 102) is a OMAP UART3 > brd: module loaded > loop: module loaded > ks8851 spi1.0: message enable is 0 > ks8851 spi1.0: eth0: revision 0, MAC ce:9f:77:f1:2c:21, IRQ 194 > input: gpio-keys as /devices/platform/gpio-keys/input/input0 > twl_rtc twl_rtc: rtc core: registered twl_rtc as rtc0 > twl_rtc twl_rtc: Power up reset detected. > omap_device: omap_i2c.1: new worst case deactivate latency 0: 30517 > twl_rtc twl_rtc: Enabling TWL-RTC. > i2c /dev entries driver > omap_device: omap_i2c.3: new worst case activate latency 0: 30517 > lm75 3-0048: hwmon0: sensor 'tmp105' > omap_i2c omap_i2c.1: controller timed out > omap_i2c omap_i2c.1: controller timed out > omap_i2c omap_i2c.2: controller timed out > omap_i2c omap_i2c.2: controller timed out > omap_i2c omap_i2c.2: controller timed out > omap_i2c omap_i2c.2: controller timed out > omap_i2c omap_i2c.3: controller timed out > omap_i2c omap_i2c.3: controller timed out > omap_i2c omap_i2c.3: controller timed out > omap_i2c omap_i2c.4: controller timed out > omap_i2c omap_i2c.4: controller timed out > omap_i2c omap_i2c.4: controller timed out > omap_i2c omap_i2c.4: controller timed out > TCP cubic registered > NET: Registered protocol family 17 > VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 0 > omap2_set_init_voltage: unable to find boot up OPP for vdd_mpu > omap2_set_init_voltage: Unable to put vdd_mpu to its init voltage > > omap2_set_init_voltage: unable to find boot up OPP for vdd_iva > omap2_set_init_voltage: Unable to put vdd_iva to its init voltage > > Power Management for TI OMAP4. > regulator_init_complete: VAUX3_6030: incomplete constraints, leaving on > regulator_init_complete: VAUX2_6030: incomplete constraints, leaving on > regulator_init_complete: VUSIM: incomplete constraints, leaving on > regulator_init_complete: VPP: incomplete constraints, leaving on > mmc0: host does not support reading read-only switch. assuming write-enable. > mmc0: new high speed SD card at address 0002 > mmcblk0: mmc0:0002 00000 971 MiB > mmcblk0: p1 p2 > omap_i2c omap_i2c.1: controller timed out > twl: i2c_read failed to transfer all messages > twl_rtc twl_rtc: rtc_read_time error -110 > twl_rtc twl_rtc: hctosys: unable to read the hardware clock > Waiting 2sec before mounting root device... > mmc1: new high speed MMC card at address 0001 > mmcblk1: mmc1:0001 MMC32G 29.8 GiB > mmcblk1: p1 > EXT3-fs: barriers not enabled > EXT3-fs (mmcblk0p2): warning: maximal mount count reached, running e2fsck is recommended > kjournald starting. Commit interval 5 seconds > EXT3-fs (mmcblk0p2): using internal journal > EXT3-fs (mmcblk0p2): recovery complete > EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode > VFS: Mounted root (ext3 filesystem) on device 179:2. > Freeing init memory: 156K > > -- > 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, Regards, Shweta -- 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] 16+ messages in thread
end of thread, other threads:[~2011-03-03 15:23 UTC | newest] Thread overview: 16+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2011-01-16 1:09 State of SDP4430 platform Russell King - ARM Linux 2011-01-16 6:06 ` Paul Walmsley 2011-01-16 6:25 ` Santosh Shilimkar 2011-01-17 10:07 ` Santosh Shilimkar 2011-01-17 23:19 ` Paul Walmsley 2011-01-18 6:53 ` Santosh Shilimkar 2011-01-19 15:26 ` Krishnamoorthy, Balaji T 2011-01-19 23:26 ` Paul Walmsley 2011-01-19 23:27 ` Paul Walmsley 2011-02-07 23:49 ` Paul Walmsley 2011-03-02 18:50 ` Paul Walmsley 2011-03-03 15:23 ` Krishnamoorthy, Balaji T 2011-02-06 9:49 ` Russell King - ARM Linux 2011-02-07 6:05 ` Santosh Shilimkar 2011-02-07 6:58 ` Krishnamoorthy, Balaji T 2011-02-07 8:18 ` Gulati, Shweta
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.