From 3140218f56c628ab79cdc7794db1f3e6c655bd0c Mon Sep 17 00:00:00 2001 From: Guy McSwain Date: Fri, 18 Dec 2020 19:41:57 -0600 Subject: [PATCH] PR#413 Update doc: return current PWM dutycycle instead of 0 --- pigpiod_if2.3 | 2 +- pigpiod_if2.h | 3 ++- 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/pigpiod_if2.3 b/pigpiod_if2.3 index e5c79e8..9226593 100644 --- a/pigpiod_if2.3 +++ b/pigpiod_if2.3 @@ -949,7 +949,7 @@ user_gpio: 0-31. .br .br -Returns 0 if OK, otherwise PI_BAD_USER_GPIO or PI_NOT_PWM_GPIO. +Returns current PWM dutycycle if OK, otherwise PI_BAD_USER_GPIO or PI_NOT_PWM_GPIO. .br diff --git a/pigpiod_if2.h b/pigpiod_if2.h index 4e3314d..15efdb3 100644 --- a/pigpiod_if2.h +++ b/pigpiod_if2.h @@ -568,7 +568,8 @@ Return the PWM dutycycle in use on a GPIO. user_gpio: 0-31. . . -Returns 0 if OK, otherwise PI_BAD_USER_GPIO or PI_NOT_PWM_GPIO. +Returns current PWM dutycycle if OK, +otherwise PI_BAD_USER_GPIO or PI_NOT_PWM_GPIO. For normal PWM the dutycycle will be out of the defined range for the GPIO (see [*get_PWM_range*]).