On Tuesday 25 November 2008, Grazvydas Ignotas wrote: > Hi, > > TWL4030 and compatibles have 2 pulse-width modulation (PWM) generators > (PWM0 and PWM1). They are used for backlight control and charger LED > in pandora board. I wasn't able to find any drivers for them in > linux-omap tree. Is there anyone working on these? There are actually four PWM signals ... two associated with LEDs (or VIBRA.M, or VIBRA.P; high current) with fast input clocks, then PWM0 and PWM1 with slower input clocks which are alternate GPIO settings. PWM1 can be used as VIBRA.SYNC. The two LED PWMs are used as GPIOs on the Beagle ... so the GPIO driver supports them as output-only GPIOs, setting the LED PWMs up to be "always on" or "always off". In short: all the PWM-equipped pins have "clean" driver support, but only for using them as GPIOs, not as PWM. > If not, what would > be the proper way to expose them? May be as LED driver? > I saw lcd_omap*evm.c just write to LED PWM registers over i2c to > control backlight, I wonder if I should just do the same. Right now, just use LEDA and LEDB as GPIO-19 and GPIO-20, like Beagle does; ditto for PWM-0/GPIO-6 and PWM-1/GPIO-7. Near term, something to support led_classdev.brightness_{set,get} methods would make sense to me, for LEDA and LEDB. The EVMs could set up LEDA devices and hook them up to the "backlight" trigger. The same thing could be done for PWM0 and PWM1. Long term, we may have a PWM framework ... but it's not ready yet, and hasn't even been refreshed recently either. And so far as I know, ALSA has no notion of supporting the VIBRA module hookup options for "audio" output. - Dave > Gražvydas > -- > To unsubscribe from this list: send the line "unsubscribe linux-omap" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > 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@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html