linux-toradex.git/include/linux/pwm.h, branch v5.19-rc8

Merge drm/drm-next into drm-misc-next

2021-11-18T08:36:39+00:00

Backmerging from drm/drm-next for v5.16-rc1.

Signed-off-by: Thomas Zimmermann

pwm: Make it explicit that pwm_apply_state() might sleep

2021-11-05T10:51:41+00:00

At least some implementations sleep. So mark pwm_apply_state() with a
might_sleep() to make callers aware. In the worst case this uncovers a
valid atomic user, then we revert this patch and at least gained some more
knowledge and then can work on a concept similar to
gpio_get_value/gpio_get_value_cansleep.

Signed-off-by: Uwe Kleine-König 
Signed-off-by: Thierry Reding

pwm: Add might_sleep() annotations for !CONFIG_PWM API functions

2021-11-05T10:51:40+00:00

The normal implementations of these functions make use of mutexes. To
make it obvious that these functions might sleep also add annotations to
the dummy implementations in the !CONFIG_PWM case.

Signed-off-by: Uwe Kleine-König 
Signed-off-by: Thierry Reding

pwm: Introduce single-PWM of_xlate function

2021-10-27T15:02:33+00:00

The existing pxa driver and the upcoming addition of PWM support in the
TI sn565dsi86 DSI/eDP bridge driver both has a single PWM channel and
thereby a need for a of_xlate function with the period as its single
argument.

Introduce a common helper function in the core that can be used as
of_xlate by such drivers and migrate the pxa driver to use this.

Signed-off-by: Bjorn Andersson 
Acked-by: Uwe Kleine-König 
Tested-by: Steev Klimaszewski 
Tested-By: Steev Klimaszewski 
Signed-off-by: Robert Foss 
Link: https://patchwork.freedesktop.org/patch/msgid/20211025170925.3096444-1-bjorn.andersson@linaro.org

pwm: Make pwmchip_remove() return void

2021-09-02T19:38:56+00:00

Since some time pwmchip_remove() always returns 0 so the return value
isn't usefull. Now that all callers are converted to ignore its value
the function can be changed to return void.

Signed-off-by: Uwe Kleine-König 
Signed-off-by: Thierry Reding

pwm: core: Remove unused devm_pwm_put()

2021-06-30T17:12:19+00:00

There are no users and seems no will come of the devm_pwm_put().
Remove the function.

While at it, slightly update documentation.

Signed-off-by: Andy Shevchenko 
Reviewed-by: Uwe Kleine-König 
Signed-off-by: Thierry Reding

pwm: Add a device-managed function to add PWM chips

2021-06-28T11:17:48+00:00

This potentially simplifies low-level PWM drivers.

Signed-off-by: Uwe Kleine-König 
Signed-off-by: Thierry Reding

pwm: core: Support new usage_power setting in PWM state

2021-06-04T09:43:52+00:00

If usage_power is set, the PWM driver is only required to maintain
the power output but has more freedom regarding signal form.

If supported, the signal can be optimized, for example to
improve EMI by phase shifting individual channels.

Signed-off-by: Clemens Gruber 
Signed-off-by: Thierry Reding

pwm: Clarify which state pwm_get_state() returns

2021-04-09T12:17:03+00:00

Given that lowlevel drivers usually cannot implement exactly what a
consumer requests with pwm_apply_state() there is some rounding
involved.

pwm_get_state() returns the setting that was requested most recently by
the consumer (opposed to what was actually implemented in hardware in
reply to the last request). Clarify this in the function kerneldoc.

Signed-off-by: Uwe Kleine-König 
Signed-off-by: Thierry Reding

pwm: Drop function pwmchip_add_with_polarity()

2021-03-22T11:31:32+00:00

pwmchip_add() only calls pwmchip_add_with_polarity() and nothing else. All
other users of pwmchip_add_with_polarity() are gone. So drop
pwmchip_add_with_polarity() and move the code instead to pwmchip_add().

The initial assignment to pwm->state.polarity is dropped. In every correct
usage of the PWM API this value is overwritten later anyhow.

Signed-off-by: Uwe Kleine-König 
Signed-off-by: Thierry Reding