| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
include/linux/i2c is not for client devices. Move the header file to a
more appropriate location.
Signed-off-by: Wolfram Sang <[email protected]>
Acked-by: Greg Kroah-Hartman <[email protected]>
Acked-by: Alexandre Belloni <[email protected]>
Acked-by: Mark Brown <[email protected]>
Acked-by: Sebastian Reichel <[email protected]>
Acked-by: Jonathan Cameron <[email protected]>
Acked-by: Dmitry Torokhov <[email protected]>
Acked-by: Kishon Vijay Abraham I <[email protected]>
Acked-by: Bartlomiej Zolnierkiewicz <[email protected]>
Acked-by: Thierry Reding <[email protected]>
Acked-by: Tony Lindgren <[email protected]>
Acked-by: Daniel Thompson <[email protected]>
Acked-by: Linus Walleij <[email protected]>
Acked-by: Guenter Roeck <[email protected]>
Signed-off-by: Lee Jones <[email protected]>
|
|
All PWM devices have been marked as "might sleep" since v4.5, there is
no longer a need to differentiate on a per-chip basis.
Signed-off-by: Thierry Reding <[email protected]>
|
|
The current TWL6030 code for the TWL PWM driver does not reliably disable the
PWM output, as tested with LEDs. The previous commit to that driver introduced
that regression.
However, it does make sense to disable the PWM clock after resetting the PWM,
but for some obscure reason, doing it all at once simply doesn't work.
The TWL6030 datasheet mentions that PWMs have to be disabled in two distinct
steps. However, clearing the clock enable bit in a second step (after issuing a
reset first) does not work.
The only approach that works is the one that was in place before the previous
commit to the driver. It consists in enabling the PWM clock after issuing a
reset. This is what TI kernel trees and production code seem to be using.
However, adding an extra step to disable the PWM clock seems to work reliably,
despite looking quite odd.
Signed-off-by: Paul Kocialkowski <[email protected]>
Acked-by: Peter Ujfalusi <[email protected]>
Signed-off-by: Thierry Reding <[email protected]>
|
|
Current twl6030_pwm_disable() implementation writes TWL6030_TOGGLE3_REG
twice, the second write sets TWL6030_PWMXEN bits so the PWM clock does
not disable.
Signed-off-by: Axel Lin <[email protected]>
Acked-by: Peter Ujfalusi <[email protected]>
Signed-off-by: Thierry Reding <[email protected]>
|
|
'of_match_ptr' is defined in linux/of.h. Include it explicitly.
Signed-off-by: Sachin Kamat <[email protected]>
Signed-off-by: Thierry Reding <[email protected]>
|
|
A few drivers already annotate this properly. Make the same change for
all other OF supporting drivers.
Signed-off-by: Thierry Reding <[email protected]>
Acked-by: Shawn Guo <[email protected]>
Acked-by: Alexandre Pereira da Silva <[email protected]>
Acked-by: Viresh Kumar <[email protected]>
|
|
Return proper error instead of 0 if twl6030_pwm_enable() fails.
Signed-off-by: Axel Lin <[email protected]>
Acked-by: Peter Ujfalusi <[email protected]>
Signed-off-by: Thierry Reding <[email protected]>
|
|
Add missing .owner of struct pwm_ops. This prevents the module from being
removed from underneath its users.
Signed-off-by: Axel Lin <[email protected]>
Acked-by: Peter Ujfalusi <[email protected]>
Signed-off-by: Thierry Reding <[email protected]>
|
|
Always use to_twl() for converting into private data instead of
container_of().
Signed-off-by: Johannes Thumshirn <[email protected]>
Signed-off-by: Thierry Reding <[email protected]>
|
|
Calls to PWM drivers connected through I2C can sleep.
Use the new can_sleep property.
Acked-by: Peter Ujfalusi <[email protected]>
Signed-off-by: Florian Vaussard <[email protected]>
Signed-off-by: Thierry Reding <[email protected]>
|
|
The driver supports the following PWM outputs:
TWL4030 PWM0 and PWM1
TWL6030 PWM1 and PWM2
On TWL4030 the PWM signals are muxed. Upon requesting the PWM the driver
will select the correct mux so the PWM can be used. When the PWM has been
freed the original configuration is going to be restored.
Signed-off-by: Peter Ujfalusi <[email protected]>
Signed-off-by: Thierry Reding <[email protected]>
|