mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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>,
	"Fabrice Gasnier" <fabrice.gasnier@st.com>,
	"Maxime Coquelin" <mcoquelin.stm32@gmail.com>,
	"Alexandre Torgue" <alexandre.torgue@st.com>
Subject: [PATCH v7 10/13] pwm: stm32-lp: Use %llu format specifier for period
Date: Mon,  9 Mar 2020 12:35:13 -0700	[thread overview]
Message-ID: <20ac22dbeb9e41bdcb594ee82f6ccd609c3426c6.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 this driver to handle the switch to u64 period
and duty_cycle by updating the format specifier in this dev_dbg message.
The actual switch to u64 period and duty_cycle follows as a separate
patch.

Cc: Fabrice Gasnier <fabrice.gasnier@st.com>
Cc: Maxime Coquelin <mcoquelin.stm32@gmail.com>
Cc: Alexandre Torgue <alexandre.torgue@st.com>

Signed-off-by: Guru Das Srinagesh <gurus@codeaurora.org>
---
 drivers/pwm/pwm-stm32-lp.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/pwm/pwm-stm32-lp.c b/drivers/pwm/pwm-stm32-lp.c
index 67fca62..134c146 100644
--- a/drivers/pwm/pwm-stm32-lp.c
+++ b/drivers/pwm/pwm-stm32-lp.c
@@ -61,7 +61,7 @@ static int stm32_pwm_lp_apply(struct pwm_chip *chip, struct pwm_device *pwm,
 	do_div(div, NSEC_PER_SEC);
 	if (!div) {
 		/* Clock is too slow to achieve requested period. */
-		dev_dbg(priv->chip.dev, "Can't reach %u ns\n",	state->period);
+		dev_dbg(priv->chip.dev, "Can't reach %llu ns\n", state->period);
 		return -EINVAL;
 	}
 
-- 
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project


  parent reply	other threads:[~2020-03-09 19:35 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 ` [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-26 16:37   ` Palmer Dabbelt
2020-03-09 19:35 ` [PATCH v7 09/13] pwm: sti: " Guru Das Srinagesh
2020-03-09 19:35 ` Guru Das Srinagesh [this message]
2020-03-09 19:35 ` [PATCH v7 11/13] pwm: sun4i: " 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=20ac22dbeb9e41bdcb594ee82f6ccd609c3426c6.1583782035.git.gurus@codeaurora.org \
    --to=gurus@codeaurora.org \
    --cc=alexandre.torgue@st.com \
    --cc=fabrice.gasnier@st.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=mcoquelin.stm32@gmail.com \
    --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®