Linux I2C development
 help / color / mirror / Atom feed
From: Andi Shyti <andi.shyti@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
	 Chris Packham <chris.packham@alliedtelesis.co.nz>,
	stable@vger.kernel.org
Subject: Re: [PATCH v1 1/1] i2c: mpc: Fix timeout calculations
Date: Tue, 23 Jun 2026 17:37:19 +0200	[thread overview]
Message-ID: <ajqmNOky98RWB989@zenone.zhora.eu> (raw)
In-Reply-To: <20260618144934.3249950-1-andriy.shevchenko@linux.intel.com>

Hi Andy,

On Thu, Jun 18, 2026 at 04:49:34PM +0200, Andy Shevchenko wrote:
> ON the first glance the harmless cleanup of the driver does nothing bad.
> However, as the operator precedence list states the '*' (multiplication)
> and '/' division operators have order 5 with left-to-right associativity
> the *= has order 17 and associativity right-to-left. It wouldn't not be
> a problem to replace
> 
> 	foo = foo * HZ / 1000000;
> 
> with
> 
> 	foo *= HZ / 1000000;
> 
> if HZ constant is in Hertz. The problem is that in the Linux kernel HZ is
> defined in jiffy units, which is order of magnitude smaller than a million.
> That's why operator precedence has a crucial role here. Fix the regression
> by reverting pre-optimized calculations.
> 
> Fixes: be40a3ae719f ("i2c: mpc: Use of_property_read_u32 instead of of_get_property")
> Cc: stable@vger.kernel.org
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>

merged to i2c/i2c-fixes.

Thanks,
Andi

> ---
>  drivers/i2c/busses/i2c-mpc.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/i2c/busses/i2c-mpc.c b/drivers/i2c/busses/i2c-mpc.c
> index 28c5c5c1fb7a..a21fa45bd64c 100644
> --- a/drivers/i2c/busses/i2c-mpc.c
> +++ b/drivers/i2c/busses/i2c-mpc.c
> @@ -844,7 +844,7 @@ static int fsl_i2c_probe(struct platform_device *op)
>  					      "fsl,timeout", &mpc_ops.timeout);
>  
>  	if (!result) {
> -		mpc_ops.timeout *= HZ / 1000000;
> +		mpc_ops.timeout = mpc_ops.timeout * HZ / 1000000;
>  		if (mpc_ops.timeout < 5)
>  			mpc_ops.timeout = 5;
>  	} else {
> -- 
> 2.50.1
> 

      parent reply	other threads:[~2026-06-23 15:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-18 14:49 [PATCH v1 1/1] i2c: mpc: Fix timeout calculations Andy Shevchenko
2026-06-18 21:26 ` Chris Packham
2026-06-23 15:37 ` Andi Shyti [this message]

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=ajqmNOky98RWB989@zenone.zhora.eu \
    --to=andi.shyti@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=chris.packham@alliedtelesis.co.nz \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.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