[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aWZkgeWwjkcWXPcT@ninjato>
Date: Tue, 13 Jan 2026 16:28:01 +0100
From: Wolfram Sang <wsa+renesas@...g-engineering.com>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc: Andi Shyti <andi@...da.it>, Qianfeng Rong <rongqianfeng@...o.com>,
linux-i2c@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org,
linux-rockchip@...ts.infradead.org,
Khalil Blaiech <kblaiech@...dia.com>,
Asmaa Mnebhi <asmaa@...dia.com>, Andi Shyti <andi.shyti@...nel.org>,
Qii Wang <qii.wang@...iatek.com>,
Matthias Brugger <matthias.bgg@...il.com>,
AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>,
Linus Walleij <linusw@...nel.org>, Heiko Stuebner <heiko@...ech.de>,
Patrice Chotard <patrice.chotard@...s.st.com>,
Ard Biesheuvel <ardb@...nel.org>
Subject: Re: [PATCH v1 0/7] i2c: busses: Introduce and use HZ_PER_GHZ
On Mon, Jan 12, 2026 at 02:46:08PM +0100, Andy Shevchenko wrote:
> A few drivers for I²C host controllers use HZ_PER_GHZ in numeric form.
> This is less readable and prone to subtle mistakes. Instead, introduce
> a well defined constant and use it in the drivers. No functional change
> implied except one case where 64-bit division replaced with 32-bit one.
>
> Andy Shevchenko (7):
> units: Add HZ_PER_GHZ
> i2c: mlxbf: Use HZ_PER_GHZ constant instead of custom one
> i2c: mt65xx: Use HZ_PER_GHZ constant instead of plain number
> i2c: nomadik: Use HZ_PER_GHZ constant instead of plain number
> i2c: rk3x: Use HZ_PER_GHZ constant instead of plain number
> i2c: st: Use HZ_PER_GHZ constant instead of plain number
> i2c: synquacer: Use HZ_PER_GHZ constant instead of plain number
>
Fine with me:
Reviewed-by: Wolfram Sang <wsa+renesas@...g-engineering.com>
Powered by blists - more mailing lists