pwm: Conflict with legacy PWM API
authorThierry Reding <thierry.reding@avionic-design.de>
Mon, 2 Jul 2012 19:29:45 +0000 (21:29 +0200)
committerThierry Reding <thierry.reding@avionic-design.de>
Mon, 23 Jul 2012 11:23:56 +0000 (13:23 +0200)
commiteac7a92fd0bc5b1edff0f9c7be5dce4f88491fb3
treec924a08d43f180aad4e384a25978da9664ce97f1
parent1112fe88d4ebbb5f46750726b87fb0beb1396835
pwm: Conflict with legacy PWM API

In order to avoid duplicate symbols with legacy PWM API implementations,
the new PWM framework needs to conflict with any of the existing legacy
implementations. This is done in two ways: for implementations provided
by drivers, a conflict is added to the driver to ensure it will have to
be ported to the PWM subsystem before it can coexist with other PWM
providers. For architecture-specific code, the conflict is added to the
PWM symbol to avoid confusion when a previously picked platform or
machine can no longer be selected because of the PWM subsystem being
included.

Signed-off-by: Thierry Reding <thierry.reding@avionic-design.de>
drivers/mfd/Kconfig
drivers/misc/Kconfig
drivers/pwm/Kconfig