drivers: pwm: clarify API details
Clarify the PWM pwm_pin_set_cycles() function API details. The API aims for synchronous (glitch-free) updates of the PWM period and pulse width, but not all PWM controllers support this. Similarly, the API aims for independance between channels on multi-channel PWM controllers, but not all PWM controllers support this. Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
This commit is contained in:
parent
976c5fee28
commit
d2ddd379c9
1 changed files with 12 additions and 0 deletions
|
@ -152,6 +152,18 @@ __subsystem struct pwm_driver_api {
|
|||
/**
|
||||
* @brief Set the period and pulse width for a single PWM output.
|
||||
*
|
||||
* The PWM period and pulse width will synchronously be set to the new values
|
||||
* without glitches in the PWM signal, but the call will not block for the
|
||||
* change to take effect.
|
||||
*
|
||||
* @note Not all PWM controllers support synchronous, glitch-free updates of the
|
||||
* PWM period and pulse width. Depending on the hardware, changing the PWM
|
||||
* period and/or pulse width may cause a glitch in the generated PWM signal.
|
||||
*
|
||||
* @note Some multi-channel PWM controllers share the PWM period across all
|
||||
* channels. Depending on the hardware, changing the PWM period for one channel
|
||||
* may affect the PWM period for the other channels of the same PWM controller.
|
||||
*
|
||||
* Passing 0 as @p pulse will cause the pin to be driven to a constant
|
||||
* inactive level.
|
||||
* Passing a non-zero @p pulse equal to @p period will cause the pin
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue