Android console on openmoko kernel

michael trimarchi at gandalf.sssup.it
Thu Jan 8 20:32:44 CET 2009


Hi,

michael wrote:
> Hi,
>
> Andy Green wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Somebody in the thread at some point said:
>> | Hi all,
>> |
>> | I don't understand the console problem. I have my console set on my
>> | openmoko android version, I just
>> | increase VT terminale to 8. Android switch in graphics mode and select
>> | VT7 like X. It is just a configuration
>> | parameter.
>>
>> Sorry I didn't get the point there... if we set the VTs to 8 the flicker
>> is gone?  Or something else?
> The flicker is not gone. I have flicker with or without console 
> compile in it. I can observe
> the kernel panic during resume (red light flickering). And I have one 
> soft lookup during resume :)
>
> <2>[    1.820000] Regulator neo1973-pm-bt.0-BT_3V2 already enabled^M
> <4>[    1.820000] ------------[ cut here ]------------^M
> <4>[    1.820000] WARNING: at drivers/regulator/core.c:1050 
> regulator_enable+0x4c/0x94()^M
> <4>[    1.820000] Modules linked in:^M
> <4>[    1.820000] [<c0034990>] (dump_stack+0x0/0x14) from [<c0051e30>] 
> (warn_on_slowpath+0x4c/0x68)^M
> <4>[    1.820000] [<c0051de4>] (warn_on_slowpath+0x0/0x68) from 
> [<c02c5e74>] (regulator_enable+0x4c/0x94)^M
> <4>[    1.820000]  r6:00000000 r5:00000001 r4:c79c37e0^M
> <4>[    1.820000] [<c02c5e28>] (regulator_enable+0x0/0x94) from 
> [<c004075c>] (__gta02_pm_bt_toggle_radio+0x74/0xa8)^M
> <4>[    1.820000]  r6:c04d5a18 r5:00000040 r4:c7a36be0^M
> <4>[    1.820000] [<c00406e8>] (__gta02_pm_bt_toggle_radio+0x0/0xa8) 
> from [<c0040b64>] (gta01_bt_resume+0x9c/0xbc)^M
> <4>[    1.820000]  r5:ffffffea r4:00000000^M
> <4>[    1.820000] [<c0040ac8>] (gta01_bt_resume+0x0/0xbc) from 
> [<c01e9d94>] (platform_drv_resume+0x20/0x24)^M
> <4>[    1.820000]  r8:c03b8f4c r7:c04d5b44 r6:00000010 r5:ffffffea 
> r4:c04f237c^M
> <4>[    1.820000] [<c01e9d74>] (platform_drv_resume+0x0/0x24) from 
> [<c01e9e84>] (platform_legacy_resume+0x30/0x3c)^M
> <4>[    1.820000] [<c01e9e54>] (platform_legacy_resume+0x0/0x3c) from 
> [<c01ea010>] (platform_pm_resume+0x4c/0x58)^M
> <4>[    1.820000] [<c01e9fc4>] (platform_pm_resume+0x0/0x58) from 
> [<c01ec334>] (pm_op+0x5c/0x84)^M
> <4>[    1.820000] [<c01ec2d8>] (pm_op+0x0/0x84) from [<c01ed03c>] 
> (resume_device+0x5c/0x1b0)^M
> <4>[    1.820000]  r5:c04d5a18 r4:c04d5b8c^M
> <4>[    1.820000] [<c01ecfe0>] (resume_device+0x0/0x1b0) from 
> [<c01ed1f8>] (dpm_resume+0x68/0x134)^M
> <4>[    1.820000]  r7:00000003 r6:00000010 r5:c04d5a18 r4:c04d5b8c^M
> <4>[    1.820000] [<c01ed190>] (dpm_resume+0x0/0x134) from 
> [<c01ed2ec>] (device_resume+0x28/0x38)^M
> <4>[    1.820000]  r6:00000003 r5:c09b4b58 r4:00000010^M
> <4>[    1.820000] [<c01ed2c4>] (device_resume+0x0/0x38) from 
> [<c007d6f8>] (suspend_devices_and_enter+0xb0/0x10c)^M
> <4>[    1.820000]  r4:00000000^M
> <4>[    1.820000] [<c007d648>] (suspend_devices_and_enter+0x0/0x10c) 
> from [<c007da30>] (enter_state+0x124/0x1dc)^M
> <4>[    1.820000]  r6:00000003 r5:00000000 r4:00000000^M
> <4>[    1.820000] [<c007d90c>] (enter_state+0x0/0x1dc) from 
> [<c007db94>] (state_store+0xac/0xc0)^M
> <4>[    1.820000]  r6:c739b000 r5:00000003 r4:c0460860^M
> <4>[    1.820000] [<c007dae8>] (state_store+0x0/0xc0) from 
> [<c01aa404>] (kobj_attr_store+0x24/0x30)^M
> <4>[    1.820000] [<c01aa3e0>] (kobj_attr_store+0x0/0x30) from 
> [<c00f4fc4>] (flush_write_buffer+0x54/0x68)^M
> <4>[    1.820000] [<c00f4f70>] (flush_write_buffer+0x0/0x68) from 
> [<c00f5370>] (sysfs_write_file+0x58/0x80)^M
Issues:

- Looking at this I don't understand where is implemented is_enable ops 
function of the regulator.
So how does it work the regulator_is_enabled function?

- The rtc_set_time is executed in process context I think, like the 
worker of the pcf50633, how can the
function prevents a race without a mutex?

- I think the flicker is an android issue.

Michael





More information about the openmoko-kernel mailing list