Grant Erickson <marathon96@xxxxxxxxx> writes:
> This patch adds support to request and use one or more of the OMAP
> dual-mode timers as a generic PWM device compatible with other generic
> PWM drivers such as the PWM backlight or PWM beeper driver.
How will this co-exist with the PWM on the twl6030 PMIC
(drivers/mfd/twl6030-pwm.c.) Both are exporting the same API.
Regarding multilpe PWM drivers, there has been discussion on the
linux-embedded list[1] regarding a more generic PWM framework, and a few
other projects working on PWM for OMAP[2]. Someone needs to step up and
consolidate/push this work forward as there is a clear need for a more
generic PWM infrastructure on various SoCs. Your work is another
example of similar work that needs to be coordinated with the other projects.
> Boards can register such devices using platform data such as in the following
> example:
>
> static struct omap2_pwm_platform_config pwm_config = {
> .timer_id = 10, // GPT10_PWM_EVT
> .polarity = 1 // Active-high
> };
Board code should not have to know which timers are PWM capable. This
information is fixed at the SoC level.
This information is available and is part of the in-progress conversion
of the timers to use the omap_hwmod infrastructure. There are subsets
of the timers that have various features (1ms timers, PWM capable, etc.)
Using hwmod classes, they can be grouped together such that board code
does not have to know which timers on which SoC are PWM capable. It
can simply request a timer with certain capabilities.
Kevin
[1] http://marc.info/?l=linux-embedded&m=128594628918269&w=2
[2] http://marc.info/?l=linux-embedded&m=128599642406671&w=2
--
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
