From: Guru Das Srinagesh <gurus@codeaurora.org>
To: linux-pwm@vger.kernel.org
Cc: "Thierry Reding" <thierry.reding@gmail.com>,
"Uwe Kleine-König" <uwe@kleine-koenig.org>,
"Subbaraman Narayanamurthy" <subbaram@codeaurora.org>,
linux-kernel@vger.kernel.org,
"Guru Das Srinagesh" <gurus@codeaurora.org>,
"Alexander Shiyan" <shc_work@mail.ru>
Subject: [PATCH v7 05/13] pwm: clps711x: Use 64-bit division macros for period and duty cycle
Date: Mon, 9 Mar 2020 12:35:08 -0700 [thread overview]
Message-ID: <3c2c8d50bfba2555e3f94c6aa43ae0ac9a0d3d7d.1583782035.git.gurus@codeaurora.org> (raw)
In-Reply-To: <cover.1583782035.git.gurus@codeaurora.org>
In-Reply-To: <cover.1583782035.git.gurus@codeaurora.org>
Because period and duty cycle are defined in the PWM framework structs
as ints with units of nanoseconds, the maximum time duration that can be
set is limited to ~2.147 seconds. Redefining them as u64 values will
enable larger time durations to be set.
As a first step, prepare drivers to handle the switch to u64 period and
duty_cycle by replacing division operations involving pwm period and duty cycle
with their 64-bit equivalents as appropriate. The actual switch to u64 period
and duty_cycle follows as a separate patch.
Where the dividend is 64-bit but the divisor is 32-bit, use *_ULL
macros:
- DIV_ROUND_UP_ULL
- DIV_ROUND_CLOSEST_ULL
- div_u64
Where the divisor is 64-bit (dividend may be 32-bit or 64-bit), use
DIV64_* macros:
- DIV64_U64_ROUND_CLOSEST
- div64_u64
Cc: Alexander Shiyan <shc_work@mail.ru>
Signed-off-by: Guru Das Srinagesh <gurus@codeaurora.org>
---
drivers/pwm/pwm-clps711x.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/pwm/pwm-clps711x.c b/drivers/pwm/pwm-clps711x.c
index 924d39a..ba9500a 100644
--- a/drivers/pwm/pwm-clps711x.c
+++ b/drivers/pwm/pwm-clps711x.c
@@ -43,7 +43,7 @@ static void clps711x_pwm_update_val(struct clps711x_chip *priv, u32 n, u32 v)
static unsigned int clps711x_get_duty(struct pwm_device *pwm, unsigned int v)
{
/* Duty cycle 0..15 max */
- return DIV_ROUND_CLOSEST(v * 0xf, pwm->args.period);
+ return DIV64_U64_ROUND_CLOSEST(v * 0xf, pwm->args.period);
}
static int clps711x_pwm_request(struct pwm_chip *chip, struct pwm_device *pwm)
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2020-03-09 19:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-09 19:35 [PATCH v7 00/13] Convert period and duty cycle to u64 Guru Das Srinagesh
2020-03-09 19:35 ` [PATCH v7 01/13] clk: pwm: Use 64-bit division macros for period and duty cycle Guru Das Srinagesh
2020-03-09 19:35 ` [PATCH v7 02/13] drm/i915: " Guru Das Srinagesh
2020-03-09 19:35 ` [PATCH v7 03/13] hwmon: pwm-fan: " Guru Das Srinagesh
2020-03-09 21:48 ` Guenter Roeck
2020-03-10 12:08 ` Uwe Kleine-König
2020-03-10 15:05 ` Guenter Roeck
2020-03-10 22:24 ` Guru Das Srinagesh
2020-03-10 22:57 ` Guenter Roeck
2020-03-09 19:35 ` [PATCH v7 04/13] ir-rx51: " Guru Das Srinagesh
2020-03-09 19:35 ` Guru Das Srinagesh [this message]
2020-03-09 19:35 ` [PATCH v7 06/13] pwm: pwm-imx-tpm: " Guru Das Srinagesh
2020-03-09 19:35 ` [PATCH v7 07/13] pwm: imx27: " Guru Das Srinagesh
2020-03-09 19:35 ` [PATCH v7 08/13] pwm: sifive: " Guru Das Srinagesh
2020-03-26 16:37 ` Palmer Dabbelt
2020-03-09 19:35 ` [PATCH v7 09/13] pwm: sti: " Guru Das Srinagesh
2020-03-09 19:35 ` [PATCH v7 10/13] pwm: stm32-lp: Use %llu format specifier for period Guru Das Srinagesh
2020-03-09 19:35 ` [PATCH v7 11/13] pwm: sun4i: Use 64-bit division macros for period and duty cycle Guru Das Srinagesh
2020-03-09 19:35 ` [PATCH v7 12/13] backlight: pwm_bl: " Guru Das Srinagesh
2020-03-10 14:34 ` Daniel Thompson
2020-03-10 18:12 ` Guru Das Srinagesh
2020-03-09 19:35 ` [PATCH v7 13/13] pwm: core: Convert period and duty cycle to u64 Guru Das Srinagesh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3c2c8d50bfba2555e3f94c6aa43ae0ac9a0d3d7d.1583782035.git.gurus@codeaurora.org \
--to=gurus@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=shc_work@mail.ru \
--cc=subbaram@codeaurora.org \
--cc=thierry.reding@gmail.com \
--cc=uwe@kleine-koenig.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®