devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: claudiu beznea <claudiu.beznea@tuxon.dev>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: chris.brandt@renesas.com, andi.shyti@kernel.org, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org, magnus.damm@gmail.com,
	mturquette@baylibre.com, sboyd@kernel.org,
	p.zabel@pengutronix.de, wsa+renesas@sang-engineering.com,
	linux-renesas-soc@vger.kernel.org, linux-i2c@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-clk@vger.kernel.org,
	Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
Subject: Re: [PATCH v2 09/12] i2c: riic: Add support for fast mode plus
Date: Fri, 28 Jun 2024 13:06:35 +0300	[thread overview]
Message-ID: <89b7f219-8e22-408d-b49f-c69f59377b88@tuxon.dev> (raw)
In-Reply-To: <CAMuHMdX4hWou9OtdE8XgU7-U0ghJ6vk2kVqgT90U0ZjsxzR5DA@mail.gmail.com>



On 28.06.2024 12:22, Geert Uytterhoeven wrote:
> Hi Claudiu,
> 
> On Tue, Jun 25, 2024 at 2:14 PM Claudiu <claudiu.beznea@tuxon.dev> wrote:
>> From: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
>>
>> Fast mode plus is available on most of the IP variants that RIIC driver
>> is working with. The exception is (according to HW manuals of the SoCs
>> where this IP is available) the Renesas RZ/A1H. For this, patch
>> introduces the struct riic_of_data::fast_mode_plus.
>>
>> Fast mode plus was tested on RZ/G3S, RZ/G2{L,UL,LC}, RZ/Five by
>> instantiating the RIIC frequency to 1MHz and issuing i2c reads on the
>> fast mode plus capable devices (and the i2c clock frequency was checked on
>> RZ/G3S).
>>
>> Signed-off-by: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
> 
> Thanks for your patch!
> 
>> --- a/drivers/i2c/busses/i2c-riic.c
>> +++ b/drivers/i2c/busses/i2c-riic.c
>> @@ -407,6 +413,9 @@ static int riic_init_hw(struct riic_dev *riic)
>>         riic_writeb(riic, 0, RIIC_ICSER);
>>         riic_writeb(riic, ICMR3_ACKWP | ICMR3_RDRFS, RIIC_ICMR3);
>>
>> +       if (info->fast_mode_plus && t->bus_freq_hz == I2C_MAX_FAST_MODE_PLUS_FREQ)
>> +               riic_clear_set_bit(riic, 0, ICFER_FMPE, RIIC_ICFER);
> 
> Unless FM+ is specified, RIIC_ICFER is never written to.
> Probably the register should always be initialized, also to make sure
> the FMPE bit is cleared when it was set by the boot loader, but FM+
> is not to be used.

OK, that's a good point.

Thank you,
Claudiu Beznea

> 
> 
>> +
>>         riic_clear_set_bit(riic, ICCR1_IICRST, 0, RIIC_ICCR1);
>>
>>         pm_runtime_mark_last_busy(dev);
> 
> Gr{oetje,eeting}s,
> 
>                         Geert
> 

  reply	other threads:[~2024-06-28 10:06 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-25 12:13 [PATCH v2 00/12] i2c: riic: Add support for Renesas RZ/G3S Claudiu
2024-06-25 12:13 ` [PATCH v2 01/12] clk: renesas: r9a08g045: Add clock, reset and power domain support for I2C Claudiu
2024-06-26 12:19   ` Geert Uytterhoeven
2024-06-25 12:13 ` [PATCH v2 02/12] i2c: riic: Use temporary variable for struct device Claudiu
2024-07-04 22:30   ` Andi Shyti
2024-07-08  5:13     ` claudiu beznea
2024-06-25 12:13 ` [PATCH v2 03/12] i2c: riic: Call pm_runtime_get_sync() when need to access registers Claudiu
2024-07-04 22:32   ` Andi Shyti
2024-06-25 12:13 ` [PATCH v2 04/12] i2c: riic: Use pm_runtime_resume_and_get() Claudiu
2024-06-25 15:53   ` Biju Das
2024-06-26  6:13     ` claudiu beznea
2024-06-26  6:23       ` Biju Das
2024-06-26  6:30         ` claudiu beznea
2024-06-27 19:21           ` Andi Shyti
2024-06-26  7:10         ` Geert Uytterhoeven
2024-06-26  8:15           ` Biju Das
2024-07-04 22:42   ` Andi Shyti
2024-07-05  7:19     ` Geert Uytterhoeven
2024-07-05 12:14       ` Andi Shyti
2024-07-08  5:19       ` claudiu beznea
2024-07-08  5:36     ` Biju Das
2024-07-08  9:33       ` Biju Das
2024-06-25 12:13 ` [PATCH v2 05/12] i2c: riic: Enable runtime PM autosuspend support Claudiu
2024-06-25 12:13 ` [PATCH v2 06/12] i2c: riic: Add suspend/resume support Claudiu
2024-06-25 12:13 ` [PATCH v2 07/12] i2c: riic: Define individual arrays to describe the register offsets Claudiu
2024-06-28  5:59   ` Biju Das
2024-06-28  7:32     ` claudiu beznea
2024-06-28  7:55       ` Biju Das
2024-06-28  8:02         ` claudiu beznea
2024-06-28  8:04           ` claudiu beznea
2024-06-28  8:09           ` Biju Das
2024-06-28  8:12             ` claudiu beznea
2024-06-28  8:24               ` Biju Das
2024-06-28  8:29                 ` Biju Das
2024-06-28 10:25                 ` claudiu beznea
2024-06-28 10:49                   ` Biju Das
2024-06-28 11:24                     ` claudiu beznea
2024-06-28 11:29                       ` Biju Das
2024-06-28 15:05                         ` Biju Das
2024-06-28  9:13               ` Geert Uytterhoeven
2024-06-28 10:28                 ` claudiu beznea
2024-06-28 11:39                   ` Geert Uytterhoeven
2024-06-29 11:11                     ` claudiu beznea
2024-08-19 19:56                     ` Andi Shyti
2024-06-28  9:08             ` Geert Uytterhoeven
2024-06-28  9:13               ` Biju Das
2024-06-25 12:13 ` [PATCH v2 08/12] dt-bindings: i2c: renesas,riic: Document the R9A08G045 support Claudiu
2024-06-25 16:28   ` Conor Dooley
2024-06-25 12:13 ` [PATCH v2 09/12] i2c: riic: Add support for fast mode plus Claudiu
2024-06-28  9:22   ` Geert Uytterhoeven
2024-06-28 10:06     ` claudiu beznea [this message]
2024-07-10 14:20     ` claudiu beznea
2024-07-11  7:53       ` Geert Uytterhoeven
2024-07-11 10:55         ` claudiu beznea
2024-06-29  5:38   ` Biju Das
2024-06-29 11:13     ` claudiu beznea
2024-06-25 12:13 ` [PATCH v2 10/12] arm64: dts: renesas: r9a08g045: Add I2C nodes Claudiu
2024-06-25 12:13 ` [PATCH v2 11/12] arm64: dts: renesas: rzg3s-smarc: Enable i2c0 node Claudiu
2024-06-25 12:13 ` [PATCH v2 12/12] arm64: dts: renesas: rzg3s-smarc-som: Enable i2c1 node Claudiu

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=89b7f219-8e22-408d-b49f-c69f59377b88@tuxon.dev \
    --to=claudiu.beznea@tuxon.dev \
    --cc=andi.shyti@kernel.org \
    --cc=chris.brandt@renesas.com \
    --cc=claudiu.beznea.uj@bp.renesas.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=mturquette@baylibre.com \
    --cc=p.zabel@pengutronix.de \
    --cc=robh@kernel.org \
    --cc=sboyd@kernel.org \
    --cc=wsa+renesas@sang-engineering.com \
    /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;
as well as URLs for NNTP newsgroup(s).