linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: linus.walleij@linaro.org, brgl@bgdev.pl,
	linux-gpio@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	Ye Zhang <ye.zhang@rock-chips.com>
Cc: linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
	mika.westerberg@linux.intel.com,
	andriy.shevchenko@linux.intel.com, tao.huang@rock-chips.com,
	finley.xiao@rock-chips.com, tim.chen@rock-chips.com,
	elaine.zhang@rock-chips.com, Ye Zhang <ye.zhang@rock-chips.com>
Subject: Re: [PATCH v2] gpio: rockchip: resolve overflow issues
Date: Fri, 23 Aug 2024 11:34:34 +0200	[thread overview]
Message-ID: <2735393.uZKlY2gecq@diego> (raw)
In-Reply-To: <20240823034314.62305-4-ye.zhang@rock-chips.com>

Am Freitag, 23. August 2024, 05:43:06 CEST schrieb Ye Zhang:
> Prevent overflow issues when performing debounce-related calculations.

Please add some more explanation here.
I.e. something about previous max_debounce calculation does overflow
the type of max_debounce

Thanks
Heiko

> Fixes: 3bcbd1a85b68 ("gpio/rockchip: support next version gpio controller")
> Signed-off-by: Ye Zhang <ye.zhang@rock-chips.com>
> ---
>  drivers/gpio/gpio-rockchip.c | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/gpio/gpio-rockchip.c b/drivers/gpio/gpio-rockchip.c
> index 5f60162baaeb..bf22b103b6a2 100644
> --- a/drivers/gpio/gpio-rockchip.c
> +++ b/drivers/gpio/gpio-rockchip.c
> @@ -209,11 +209,12 @@ static int rockchip_gpio_set_debounce(struct gpio_chip *gc,
>  		freq = clk_get_rate(bank->db_clk);
>  		if (!freq)
>  			return -EINVAL;
> -		max_debounce = (GENMASK(23, 0) + 1) * 2 * 1000000 / freq;
> +		div = (u64)(GENMASK(23, 0) + 1) * 2 * 1000000;
> +		max_debounce = DIV_ROUND_CLOSEST_ULL(div, freq);
>  		if (debounce > max_debounce)
>  			return -EINVAL;
>  
> -		div = debounce * freq;
> +		div = (u64)debounce * freq;
>  		div_reg = DIV_ROUND_CLOSEST_ULL(div, 2 * USEC_PER_SEC) - 1;
>  	} else {
>  		div_debounce_support = false;
> 





  reply	other threads:[~2024-08-23  9:33 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-23  3:43 [PATCH v2] gpio: rockchip: Update the GPIO driver Ye Zhang
2024-08-23  3:43 ` [PATCH v2] gpio: rockchip: avoid division by zero Ye Zhang
2024-08-23  9:27   ` Heiko Stübner
2024-08-23 14:45   ` Andy Shevchenko
2024-08-23  3:43 ` [PATCH v2] gpio: rockchip: release reference to device node Ye Zhang
2024-08-23  9:28   ` Heiko Stübner
2024-08-23 10:52   ` Shawn Lin
2024-08-23  3:43 ` [PATCH v2] gpio: rockchip: resolve overflow issues Ye Zhang
2024-08-23  9:34   ` Heiko Stübner [this message]
2024-08-23 10:59   ` Shawn Lin
2024-08-23 14:49     ` Andy Shevchenko
2024-08-23 14:48   ` Andy Shevchenko
2024-08-23  3:43 ` [PATCH v2] gpio: rockchip: resolve underflow issue Ye Zhang
2024-08-23 14:51   ` Andy Shevchenko
2024-08-23  3:43 ` [PATCH v2] gpio: rockchip: fix debounce calculate Ye Zhang
2024-08-23  3:43 ` [PATCH v2] gpio: rockchip: Update debounce config function Ye Zhang
2024-08-23  3:43 ` [PATCH v2] gpio: rockchip: support 'clock-names' from dt nodes Ye Zhang
2024-08-23 14:56   ` Andy Shevchenko
2024-08-23  3:43 ` [PATCH v2] gpio: rockchip: support new version gpio Ye Zhang
2024-08-23 13:32   ` Sebastian Reichel
2024-08-23 15:05   ` Andy Shevchenko
2024-08-23  3:43 ` [PATCH v2] gpio: rockchip: Set input direction when request irq Ye Zhang
2024-08-23 14:59   ` Andy Shevchenko
2024-08-23  3:43 ` [PATCH v2] gpio: rockchip: support ACPI Ye Zhang
2024-08-23  5:27   ` Mika Westerberg
2024-08-23  7:03 ` [PATCH v2] gpio: rockchip: Update the GPIO driver Bartosz Golaszewski
2024-08-23  7:06 ` Dragan Simic
2024-08-23 15:07   ` Andy Shevchenko
2024-08-23  9:33 ` Heiko Stübner

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=2735393.uZKlY2gecq@diego \
    --to=heiko@sntech.de \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=brgl@bgdev.pl \
    --cc=elaine.zhang@rock-chips.com \
    --cc=finley.xiao@rock-chips.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=tao.huang@rock-chips.com \
    --cc=tim.chen@rock-chips.com \
    --cc=ye.zhang@rock-chips.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: 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;
as well as URLs for NNTP newsgroup(s).