Cindy enable android PM in kernel config and build it.The
android input subsystem accepts and interprets the x,y co-ordinates
reported by the touch-driver (ads7846) properly if and only if the
Power Management support is enabled in Android.  Hence please enable
CONFIG_PM while configuring the kernel for OMAP3 EVM.Then it myt work .

2009/4/24 Rupesh Gujare <rupesh.guj...@embinux.com>

>  Cindy,
>
>   It works for me without any problem. I haven't done any calibration.
> Worked for me out of box.
>
>
> Regards,
>
> --
> Rupesh Gujarehttp://embinux.com
>
>
> cindy_king_1024 wrote:
>
> Hi,Repesh
>  I have add the patch,but it can't work as still.
> And what'about  /sys/module/ads7846/parameters/calibration? Dose it need to
> modify?
>
>
> 在2009-04-23 23:11:02,"Rupesh Gujare" 
> <rupesh.guj...@embinux.com><rupesh.guj...@embinux.com>写道:
>
> Cindy,
>   Get this patch to TS working. :)
>
>
> http://labs.embinux.org/git/cgit.cgi/repo/kernel.git/commit/?id=23a3416e6fef7109c52f9e7723843dc864c524a7
>
> Regards,
>
> --
> Rupesh Gujarehttp://embinux.com
>
>
> cindy_king_1024 wrote:
>
> Thanks.I have got the keymap.
>
>
> 在2009-04-22 16:26:52,"vishal bhoj" 
> <vishalb...@gmail.com><vishalb...@gmail.com>写道:
>
>
> Cindy ,
>
> There are few problem with TS driver with Embinux source . I wud suggest
> first get ur keypad working with Android.
>
> Touchscreen needs calibration patch which you can read it from other
> mailing list . . .
>
> 2009/4/22 cindy_king_1024 <cindy_king_1...@126.com>
>
>> Hi,vishal
>> Thanks ,the color is normal now.
>> But the touch screen didn't work,I can't exit the menu .Any advise?
>>
>>
>> 在2009-04-22 12:46:29,"vishal bhoj" <vishalb...@gmail.com> 写道:
>>
>>  I am pasting the content of the link
>>
>>
>> On Fri, Sep 26, 2008 at 4:20 PM, Daniel Schaeffer
>>
>> <[EMAIL PROTECTED]> wrote:
>> > Has anyone looked into why the LCD display on the OMAP3EVM is always tinted
>>
>> > red? I created a couple of color test images that I cat'ed to /dev/fb and 
>> > it
>> > looks like the blue color channel is completely ignored.  I was testing on
>> > v2.6.26-omap2 but is doesn't look like there have been any changes to the 
>> > fb
>>
>>
>> > driver since then so I'm assuming the issue is also present in the head of
>> > the git tree.
>> >
>> > Regards,
>> >
>> > Daniel Schaeffer
>> >
>>
>> Try the patch below(Remember that you may have to manually edit because
>>
>>
>> this patch is against current HEAD)
>>
>>
>> diff --git a/drivers/video/omap/lcd_omap3evm.c
>> b/drivers/video/omap/lcd_omap3evm.c
>> index a564ca5..821bafe 100644
>> --- a/drivers/video/omap/lcd_omap3evm.c
>> +++ b/drivers/video/omap/lcd_omap3evm.c
>>
>>
>> @@ -44,6 +44,8 @@
>>  #define ENABLE_VDAC_DEV_GRP    0x20
>>  #define ENABLE_VPLL2_DEDICATED 0x05
>>  #define ENABLE_VPLL2_DEV_GRP   0xE0
>> +#define TWL4030_VPLL2_DEV_GRP  0x33
>> +#define TWL4030_VPLL2_DEDICATED        0x36
>>
>>
>>
>>  #define TWL_LED_LEDEN          0x00
>>  #define TWL_PWMA_PWMAON                0x00
>> @@ -86,12 +88,24 @@ static void omap3evm_panel_cleanup(struct lcd_panel 
>> *panel)
>>
>>  static int omap3evm_panel_enable(struct lcd_panel *panel)
>>
>>
>>  {
>> +       if (system_rev > OMAP3430_REV_ES1_0) {
>> +               twl4030_i2c_write_u8(TWL4030_MODULE_PM_RECEIVER,
>> +                       ENABLE_VPLL2_DEDICATED, TWL4030_VPLL2_DEDICATED);
>> +               twl4030_i2c_write_u8(TWL4030_MODULE_PM_RECEIVER,
>>
>>
>> +                       ENABLE_VPLL2_DEV_GRP, TWL4030_VPLL2_DEV_GRP);
>> +       }
>>         omap_set_gpio_dataout(LCD_PANEL_ENABLE_GPIO, 0);
>>         return 0;
>>  }
>>
>>  static void omap3evm_panel_disable(struct lcd_panel *panel)
>>
>>
>>  {
>> +       if (system_rev > OMAP3430_REV_ES1_0) {
>> +               twl4030_i2c_write_u8(TWL4030_MODULE_PM_RECEIVER, 0x0,
>> +                       TWL4030_VPLL2_DEDICATED);
>> +               twl4030_i2c_write_u8(TWL4030_MODULE_PM_RECEIVER, 0x0,
>>
>>
>> +                       TWL4030_VPLL2_DEV_GRP);
>> +       }
>>         omap_set_gpio_dataout(LCD_PANEL_ENABLE_GPIO, 1);
>>  }
>>
>>
>>
>>
>>
>> 2009/4/21 cindy_king_1024 <cindy_king_1...@126.com>
>>
>>>
>>> Thanks.
>>> At the first time I boot up it the graphic was normal,but later the
>>> graphic just look as it was make of green and red,lose the blue color.
>>>
>>> 在2009-04-21 17:29:35,"Nimit Manglick" <nimitandr...@gmail.com> 写道:
>>>
>>> Cindy,
>>>
>>> Change the settings as :-
>>>
>>> menu -->> settings --> sound & display -->> screen timeout
>>>
>>> select "never timeout" option from there.
>>>
>>> Regards
>>> Nimit
>>>
>>> 2009/4/21 cindy_king_1024 <cindy_king_1...@126.com>
>>>
>>>> Hi,Nimit
>>>> Now it can boot up but the system is very unstable.
>>>> and some time the graphic come with red
>>>> And the terminal putout:
>>>>
>>>>  VFS: Mounted root (nfs filesystem).
>>>> VFS: Mounted root (nfs filesystem).
>>>> <6>Freeing init memory: 144K
>>>> Freeing init memory: 144K
>>>> <4>Warning: unable to open an initial console.
>>>> Warning: unable to open an initial console.
>>>> <3>init: cannot open '/initlogo.rle'
>>>> init: cannot open '/initlogo.rle'
>>>>  <3>init: cannot find '/system/bin/playmp3', disabling 'bootsound'
>>>> init: cannot find '/system/bin/playmp3', disabling 'bootsound'
>>>> sh: can't access tty; job control turned off
>>>> # <6>warning: `rild' uses 32-bit capabilities (legacy support in use)
>>>> warning: `rild' uses 32-bit capabilities (legacy support in use)
>>>>  <6>request_suspend_state: wakeup (3->0) at 60751251220 (1970-01-01
>>>> 00:01:00.751251220 UTC)
>>>> request_suspend_state: wakeup (3->0) at 60751251220 (1970-01-01
>>>> 00:01:00.751251220 UTC)
>>>> <6>request_suspend_state: sleep (0->3) at 127989257812 (1970-01-01
>>>> 00:02:07.989257812 UTC)
>>>> request_suspend_state: sleep (0->3) at 127989257812 (1970-01-01
>>>> 00:02:07.989257812 UTC)
>>>> <6>PM: Syncing filesystems ... PM: Syncing filesystems ... done.
>>>> done.
>>>> Freezing user space processes ... Freezing user space processes ...
>>>> (elapsed 0.00 seconds) (elapsed
>>>> 0.00 seconds) done.
>>>> done.
>>>> Freezing remaining freezable tasks ... Freezing remaining freezable
>>>> tasks ... (elapsed 0.00 seconds)
>>>>  (elapsed 0.00 seconds) done.done.
>>>> Suspending console(s) (use no_console_suspend to debug)
>>>> Suspending console(s) (use no_console_suspend to debug)
>>>> <3>omapfb omapfb: timeout waiting for FRAME DONE
>>>> +.瓛 -挧墵F!?涨6拜%F江(?
>>>> ?hk?嫺瞚+4圞?鑝?應?皳?仱妑'
>>>> ?垾畱痵omapfb omapfb: timeout waiting for FRAME DONE
>>>> Powerdomain (core_pwrdm) didn't enter target state 1
>>>> Powerdomain (per_pwrdm) didn't enter target state 1
>>>> Could not enter target state in pm_suspend
>>>> eth0: link down
>>>> Restarting tasks ... Restarting tasks ... <6>wakeup wake lock:
>>>> PowerManagerService
>>>> <6>wakeup wake lock: PowerManagerService
>>>> done.
>>>>
>>>>
>>>>
>>>>
>>>> 在2009-04-21 15:36:15,"Nimit Manglick" <nimitandr...@gmail.com> 写道:
>>>>
>>>>
>>>> Alsa-lib and alsa-sound patch is ONLY needed if you want to have audio
>>>> support.
>>>> and that comes later, firstly android has to boot up.
>>>>
>>>> Cindy,
>>>>
>>>> The kernel mentioned in the
>>>> http://labs.embinux.org/git/cgit.cgi/linux-omap-2.6/commit/?h=evm-android-2.6.27
>>>>
>>>> is for beagle-board and not for 3530 EVM.
>>>>
>>>> So still ur android is not booting ??
>>>>
>>>>
>>>> 2009/4/21 cindy_king_1024 <cindy_king_1...@126.com>
>>>>
>>>>> Thanks,but I have a question :
>>>>> In your answer :
>>>>>  1.when compile android ,dose it need to add alsa-lib and alsa_sound
>>>>> with the patch Alsa_sound-v1.1.patch.
>>>>>  No You do not need this.
>>>>>  You mean I need not add the patch or I need not add alsa-lib and
>>>>> alsa_sound?
>>>>> All of alsa-lib and slsa_sound is not needed?
>>>>>
>>>>>
>>>>> 在2009-04-21 14:41:31,"Rupesh Gujare" <rupesh.guj...@embinux.com> 写道:
>>>>>
>>>>> Cindy,
>>>>>
>>>>> cindy_king_1024 wrote:
>>>>>
>>>>> Hi,Nimit
>>>>> My android source without cupcake baranch that you say above.
>>>>> 1.when compile android ,dose it need to add alsa-lib and alsa_sound
>>>>> with the patch Alsa_sound-v1.1.patch.
>>>>>
>>>>> No You do not need this.
>>>>>
>>>>> 2. In the filesystem ,is it need to patch  
>>>>> Initrc.patch<http://labs.embinux.org/images/6/6c/Initrc.patch> and
>>>>> *Qwerty.patch*
>>>>>
>>>>>  You need apply Initrc.patch,(most probably this patch will solve your
>>>>> current error) Qwerty.patch is of no use to you.
>>>>>
>>>>> 3.Can you show me the config file of you kernel(wersion?),mine
>>>>> reference to the links:
>>>>>
>>>>>
>>>>> http://labs.embinux.org/git/cgit.cgi/linux-omap-2.6/commit/?h=evm-android-2.6.27
>>>>>
>>>>> Above defconfig is working fine. You can go ahead with it.
>>>>>
>>>>> Regards,
>>>>>
>>>>> --
>>>>> Rupesh Gujarehttp://embinux.com
>>>>>
>>>>>
>>>>>
>>>>>  网易邮箱,中国第一大电子邮件服务商 <http://email.163.com/>
>>>>>
>>>>>
>>>>
>>>> 网易邮箱,中国第一大电子邮件服务商 <http://email.163.com/>
>>>>
>>>>
>>>
>>> 网易邮箱,中国第一大电子邮件服务商 <http://email.163.com/>
>>>
>>>
>>
>>
>> --
>>  with regards vishal
>>
>> 网易邮箱,中国第一大电子邮件服务商 <http://email.163.com/>
>>
>>
>
>
> --
> with regards vishal
>
> 网易邮箱,中国第一 大电子邮件服务商 <http://email.163.com/>
>
>
>
>
> 网易邮箱,中国第一大电子邮件 服务商 <http://email.163.com>
>
>
>
>
> >
>


-- 
with regards vishal

--~--~---------~--~----~------------~-------~--~----~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
-~----------~----~----~----~------~----~------~--~---

Reply via email to