Thierry Reding eac7a92fd0 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>		2012-07-23 13:23:56 +02:00
..
core.c	pwm: Add device tree support	2012-06-15 12:56:57 +02:00
Kconfig	pwm: Conflict with legacy PWM API	2012-07-23 13:23:56 +02:00
Makefile	pwm: add pwm-mxs support	2012-07-02 22:06:34 +02:00
pwm-bfin.c	pwm: Move Blackfin PWM driver to PWM framework	2012-07-02 21:38:59 +02:00
pwm-imx.c	ARM i.MX: Move i.MX pwm driver to pwm framework	2012-07-02 21:39:01 +02:00
pwm-mxs.c	pwm: pwm-mxs: add pinctrl support	2012-07-23 13:23:56 +02:00
pwm-pxa.c	pwm: Move PXA PWM driver to PWM framework	2012-07-02 21:39:00 +02:00
pwm-samsung.c	ARM Samsung: Move s3c pwm driver to pwm framework	2012-07-02 21:39:02 +02:00
pwm-tegra.c	pwm: tegra: Add device tree support	2012-07-02 21:38:59 +02:00
pwm-vt8500.c	ARM vt8500: Move vt8500 pwm driver to pwm framework	2012-07-02 22:06:33 +02:00