From: Guenter Roeck <linux@roeck-us.net>
To: Guru Das Srinagesh <gurus@codeaurora.org>
Cc: linux-pwm@vger.kernel.org,
"Thierry Reding" <thierry.reding@gmail.com>,
"Uwe Kleine-König" <uwe@kleine-koenig.org>,
"Subbaraman Narayanamurthy" <subbaram@codeaurora.org>,
linux-kernel@vger.kernel.org, "Kamil Debski" <kamil@wypas.org>,
"Bartlomiej Zolnierkiewicz" <b.zolnierkie@samsung.com>,
"Jean Delvare" <jdelvare@suse.com>,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Mark Brown" <broonie@kernel.org>,
linux-hwmon@vger.kernel.org
Subject: Re: [PATCH v7 03/13] hwmon: pwm-fan: Use 64-bit division macros for period and duty cycle
Date: Mon, 9 Mar 2020 14:48:22 -0700 [thread overview]
Message-ID: <20200309214822.GA19773@roeck-us.net> (raw)
In-Reply-To: <b503833e0f58bd6dd9fe84d866124e7c457e099e.1583782035.git.gurus@codeaurora.org>
On Mon, Mar 09, 2020 at 12:35:06PM -0700, Guru Das Srinagesh wrote:
> 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
>
There is no explanation why this is necessary. What is the use case ?
It is hard to imagine a real-world use case with a duty cycle of more
than 2 seconds.
Guenter
next prev parent reply other threads:[~2020-03-09 21:48 UTC|newest]
Thread overview: 33+ 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 ` [Intel-gfx] " Guru Das Srinagesh
2020-03-09 19:35 ` 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 [this message]
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 ` [PATCH v7 05/13] pwm: clps711x: " Guru Das Srinagesh
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-09 19:35 ` Guru Das Srinagesh
2020-03-26 16:37 ` Palmer Dabbelt
2020-03-26 16:37 ` Palmer Dabbelt
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-09 19:35 ` Guru Das Srinagesh
2020-03-09 19:35 ` Guru Das Srinagesh
2020-03-10 14:34 ` Daniel Thompson
2020-03-10 14:34 ` Daniel Thompson
2020-03-10 14:34 ` Daniel Thompson
2020-03-10 18:12 ` Guru Das Srinagesh
2020-03-10 18:12 ` Guru Das Srinagesh
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=20200309214822.GA19773@roeck-us.net \
--to=linux@roeck-us.net \
--cc=b.zolnierkie@samsung.com \
--cc=broonie@kernel.org \
--cc=gurus@codeaurora.org \
--cc=jdelvare@suse.com \
--cc=kamil@wypas.org \
--cc=lgirdwood@gmail.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.