Re: Digest for omapdiscuss@googlegroups.com - 1 Message in 1 Topic

6 views
Skip to first unread message

Juan Gutierrez

unread,
Mar 17, 2012, 10:54:08 PM3/17/12
to omapd...@googlegroups.com

Do you know which dmtimer is used by the backlight driver? In p-android dmtimers 3, 4, 9 and 11 are used by the Dual Cortex M3 co-processor. Probably the error is because trying to use one of this. If you are not using M3 you can disable remoteproc driver from menuconfig and that would free the dmtimers.

On Mar 17, 2012 4:44 PM, <omapd...@googlegroups.com> wrote:

Group: http://groups.google.com/group/omapdiscuss/topics

    Kuzemko Alexandr <kuze...@rambler.ru> Mar 17 06:29AM  

    Hello!
    I have a OMAP PWM LED driver, that works on mainline 3.2 kernel (from
    kernel.org), but doesn't work on p-android-omap-3.0 branch.
     
    The source of driver is here:
    http://pastebin.com/LKfNBdMe
     
    I use such driver initialization on board file
    static struct omap_pwm_led_platform_data acclaim4430_disp_backlight_data = {
    .name = "lcd-backlight",
    .intensity_timer = 11,
    .def_on = 0,
    .def_brightness = DEFAULT_BACKLIGHT_BRIGHTNESS,
    .set_power = acclaim4430_disp_backlight_setpower,
    };
     
    static struct platform_device sdp4430_disp_led = {
    .name = "omap_pwm_led",
    .id = -1,
    .dev = {
    .platform_data = &acclaim4430_disp_backlight_data,
    },
    };
     
    static struct platform_device *sdp4430_devices[] __initdata = {
    &sdp4430_disp_led,
    };
     
    On p-android-omap-3.0 branch produce warning
    <4>WARNING: at arch/arm/plat-omap/dmtimer.c:917 omap_dm_timer_read_counter
    +0x150/0x1b0()
     
    As I understand LED PWM driver doesn't correct handle timer enable/disable.
     
    Any idea?

     

You received this message because you are subscribed to the Google Group omapdiscuss.
You can post via email.
To unsubscribe from this group, send an empty message.
For more options, visit this group.

Juan Gutierrez

unread,
Mar 17, 2012, 10:58:35 PM3/17/12
to omapd...@googlegroups.com

I think dmtimer 11 is the one in conflict. This one is used as a watchdog timer for the M3 co-processor. So it is enough to disable the WDT for remoteproc option from device drivers in menuconfig.

Reply all
Reply to author
Forward
0 new messages