[0/5] i2c: clock calculation cleanups for Renesas devices

Message

Wolfram Sang Sept. 6, 2023, 8 p.m. UTC

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(-)

Comments

Wolfram Sang Sept. 19, 2023, 9:12 a.m. UTC | #1

On Wed, Sep 06, 2023 at 10:00:18PM +0200, Wolfram Sang wrote:
> 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
> 

Applied to for-next, thanks!