linux-kernel - [PATCH 0/5] i2c: clock calculation cleanups for Renesas devices

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20230906200024.5305-1-wsa+renesas@sang-engineering.com>
Date:   Wed,  6 Sep 2023 22:00:18 +0200
From:   Wolfram Sang <wsa+renesas@...g-engineering.com>
To:     linux-renesas-soc@...r.kernel.org
Cc:     Wolfram Sang <wsa+renesas@...g-engineering.com>,
        linux-i2c@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [PATCH 0/5] i2c: clock calculation cleanups for Renesas devices

While implementing FastMode+ support for the R-Car IP core, I noticed
potential for other cleanups. It turned out that it makes sense to apply
them first, so here is the series. Tested on a Renesas Falcon board with
an R-Car V3U. The calculated values are identical for 100 and 400kHz.
The RIIC patch is build tested only.

Looking forward to comments!


Wolfram Sang (5):
  i2c: rcar: avoid non-standard use of goto
  i2c: rcar: properly format a debug output
  i2c: rcar: calculate divider instead of brute-forcing it
  i2c: rcar: remove open coded DIV_ROUND_CLOSEST
  i2c: riic: avoid potential division by zero

 drivers/i2c/busses/i2c-rcar.c | 41 +++++++++++++++--------------------
 drivers/i2c/busses/i2c-riic.c |  2 +-
 2 files changed, 19 insertions(+), 24 deletions(-)

-- 
2.35.1