Gerard Marull-Paretas ae91933c4a drivers: pwm: always use nanoseconds for set ... In order to be consistent with what is possible in Devicetree, always take a period in nanoseconds. Other scales or units may be specified by using, e.g., the PWM_MSEC() macros (all of them converting down to nanoseconds). This change then deletes the "_nsec" and "_usec" versions of the pwm_set call. Note that this change limits the period to UINT32_MAX nanoseconds, ~4.3s. PWM is, in generali, used with periods below the second so it should not be a problem. Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>		2022-04-28 11:29:38 +02:00
..
blinky	doc: Fix links to Zephyr include directory on Github	2022-04-21 18:35:16 -04:00
blinky_pwm	drivers: pwm: always use nanoseconds for set	2022-04-28 11:29:38 +02:00
button	cmake: increase minimal required version to 3.20.0	2021-08-20 09:47:34 +02:00
fade_led	drivers: pwm: always use nanoseconds for set	2022-04-28 11:29:38 +02:00
minimal	samples: Take into account PINCTRL in minimal configurations	2021-12-21 18:30:35 +01:00
rgb_led	drivers: pwm: always use nanoseconds for set	2022-04-28 11:29:38 +02:00
servo_motor	drivers: pwm: always use nanoseconds for set	2022-04-28 11:29:38 +02:00
threads	cmake: increase minimal required version to 3.20.0	2021-08-20 09:47:34 +02:00
basic.rst