From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Khalil Blaiech <kblaiech@nvidia.com>,
Asmaa Mnebhi <asmaa@nvidia.com>,
Andi Shyti <andi.shyti@kernel.org>
Subject: [PATCH v1 2/2] i2c: mlxbf: Use HZ_PER_KHZ in the driver
Date: Mon, 12 Jan 2026 14:55:11 +0100 [thread overview]
Message-ID: <20260112135603.4150952-3-andriy.shevchenko@linux.intel.com> (raw)
In-Reply-To: <20260112135603.4150952-1-andriy.shevchenko@linux.intel.com>
Use predefined HZ_PER_MHZ constant where it is appropriate.
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
---
drivers/i2c/busses/i2c-mlxbf.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/i2c/busses/i2c-mlxbf.c b/drivers/i2c/busses/i2c-mlxbf.c
index 9f0048044112..6c1cfe9ec8ac 100644
--- a/drivers/i2c/busses/i2c-mlxbf.c
+++ b/drivers/i2c/busses/i2c-mlxbf.c
@@ -66,7 +66,7 @@
* strongly dependent on the core clock frequency of the SMBus
* Master. Default value is set to 400MHz.
*/
-#define MLXBF_I2C_TYU_PLL_OUT_FREQ (400 * 1000 * 1000)
+#define MLXBF_I2C_TYU_PLL_OUT_FREQ (400 * HZ_PER_MHZ)
/* Reference clock for Bluefield - 156 MHz. */
#define MLXBF_I2C_PLL_IN_FREQ 156250000ULL
--
2.50.1
next prev parent reply other threads:[~2026-01-12 13:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 13:55 [PATCH v1 0/2] i2c: mlxbf: A couple of cleanups Andy Shevchenko
2026-01-12 13:55 ` [PATCH v1 1/2] i2c: mlxbf: Remove unused bus speed definitions Andy Shevchenko
2026-01-12 13:55 ` Andy Shevchenko [this message]
2026-01-12 20:33 ` [PATCH v1 2/2] i2c: mlxbf: Use HZ_PER_KHZ in the driver kernel test robot
2026-01-12 20:36 ` Andy Shevchenko
2026-01-13 7:30 ` Andy Shevchenko
2026-01-13 13:48 ` Philip Li
2026-01-13 20:42 ` Andy Shevchenko
2026-01-13 23:55 ` Philip Li
2026-01-14 7:36 ` [PATCH v1 0/2] i2c: mlxbf: A couple of cleanups Andi Shyti
2026-01-14 8:24 ` Andy Shevchenko
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=20260112135603.4150952-3-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=andi.shyti@kernel.org \
--cc=asmaa@nvidia.com \
--cc=kblaiech@nvidia.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@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