From: Laxman Dewangan <ldewangan@nvidia.com> To: thierry.reding@gmail.com, robh+dt@kernel.org, mark.rutland@arm.com Cc: jonathanh@nvidia.com, linux-pwm@vger.kernel.org, devicetree@vger.kernel.org, linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org, Laxman Dewangan <ldewangan@nvidia.com> Subject: [PATCH 1/4] pwm: tegra: Use DIV_ROUND_CLOSEST_ULL() instead of local implementation Date: Wed, 5 Apr 2017 19:43:43 +0530 [thread overview] Message-ID: <1491401626-31303-2-git-send-email-ldewangan@nvidia.com> (raw) In-Reply-To: <1491401626-31303-1-git-send-email-ldewangan@nvidia.com> Use macro DIV_ROUND_CLOSEST_ULL() for 64bit division to closet one instead of implementing the same locally. This increase readability. Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com> --- drivers/pwm/pwm-tegra.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/pwm/pwm-tegra.c b/drivers/pwm/pwm-tegra.c index e464784..0a688da 100644 --- a/drivers/pwm/pwm-tegra.c +++ b/drivers/pwm/pwm-tegra.c @@ -85,8 +85,7 @@ static int tegra_pwm_config(struct pwm_chip *chip, struct pwm_device *pwm, * nearest integer during division. */ c *= (1 << PWM_DUTY_WIDTH); - c += period_ns / 2; - do_div(c, period_ns); + c = DIV_ROUND_CLOSEST_ULL(c, period_ns); val = (u32)c << PWM_DUTY_SHIFT; -- 2.1.4
WARNING: multiple messages have this Message-ID (diff)
From: Laxman Dewangan <ldewangan@nvidia.com> To: <thierry.reding@gmail.com>, <robh+dt@kernel.org>, <mark.rutland@arm.com> Cc: <jonathanh@nvidia.com>, <linux-pwm@vger.kernel.org>, <devicetree@vger.kernel.org>, <linux-tegra@vger.kernel.org>, <linux-kernel@vger.kernel.org>, Laxman Dewangan <ldewangan@nvidia.com> Subject: [PATCH 1/4] pwm: tegra: Use DIV_ROUND_CLOSEST_ULL() instead of local implementation Date: Wed, 5 Apr 2017 19:43:43 +0530 [thread overview] Message-ID: <1491401626-31303-2-git-send-email-ldewangan@nvidia.com> (raw) In-Reply-To: <1491401626-31303-1-git-send-email-ldewangan@nvidia.com> Use macro DIV_ROUND_CLOSEST_ULL() for 64bit division to closet one instead of implementing the same locally. This increase readability. Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com> --- drivers/pwm/pwm-tegra.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/pwm/pwm-tegra.c b/drivers/pwm/pwm-tegra.c index e464784..0a688da 100644 --- a/drivers/pwm/pwm-tegra.c +++ b/drivers/pwm/pwm-tegra.c @@ -85,8 +85,7 @@ static int tegra_pwm_config(struct pwm_chip *chip, struct pwm_device *pwm, * nearest integer during division. */ c *= (1 << PWM_DUTY_WIDTH); - c += period_ns / 2; - do_div(c, period_ns); + c = DIV_ROUND_CLOSEST_ULL(c, period_ns); val = (u32)c << PWM_DUTY_SHIFT; -- 2.1.4
next prev parent reply other threads:[~2017-04-05 14:13 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-04-05 14:13 [PATCH 0/4] pwm: tegra: Pin configuration in suspend/resume and cleanups Laxman Dewangan 2017-04-05 14:13 ` Laxman Dewangan 2017-04-05 14:13 ` Laxman Dewangan [this message] 2017-04-05 14:13 ` [PATCH 1/4] pwm: tegra: Use DIV_ROUND_CLOSEST_ULL() instead of local implementation Laxman Dewangan 2017-04-05 14:13 ` [PATCH 2/4] pwm: tegra: Increase precision in pwm rate calculation Laxman Dewangan 2017-04-05 14:13 ` Laxman Dewangan [not found] ` <1491401626-31303-1-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org> 2017-04-05 14:13 ` [PATCH 3/4] pwm: tegra: Add DT binding details to configure pin in suspends/resume Laxman Dewangan 2017-04-05 14:13 ` Laxman Dewangan 2017-04-06 8:57 ` Jon Hunter 2017-04-06 8:57 ` Jon Hunter [not found] ` <33445b27-ae0b-b28e-afca-e7b776b4b7c0-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org> 2017-04-06 13:03 ` Thierry Reding 2017-04-06 13:03 ` Thierry Reding 2017-04-06 13:19 ` Laxman Dewangan 2017-04-06 13:19 ` Laxman Dewangan 2017-04-06 14:03 ` Jon Hunter 2017-04-06 14:03 ` Jon Hunter [not found] ` <58E6405E.5020402-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org> 2017-04-07 10:19 ` Linus Walleij 2017-04-07 10:19 ` Linus Walleij 2017-04-05 14:13 ` [PATCH 4/4] pwm: tegra: Add support to configure pin state " Laxman Dewangan 2017-04-05 14:13 ` Laxman Dewangan
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=1491401626-31303-2-git-send-email-ldewangan@nvidia.com \ --to=ldewangan@nvidia.com \ --cc=devicetree@vger.kernel.org \ --cc=jonathanh@nvidia.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-pwm@vger.kernel.org \ --cc=linux-tegra@vger.kernel.org \ --cc=mark.rutland@arm.com \ --cc=robh+dt@kernel.org \ --cc=thierry.reding@gmail.com \ /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: linkBe 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.