devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: claudiu beznea <claudiu.beznea@tuxon.dev>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
	chris.brandt@renesas.com, andi.shyti@kernel.org, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org, geert+renesas@glider.be,
	magnus.damm@gmail.com, p.zabel@pengutronix.de,
	linux-renesas-soc@vger.kernel.org, linux-i2c@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
Subject: Re: [PATCH v3 04/11] i2c: riic: Enable runtime PM autosuspend support
Date: Fri, 9 Aug 2024 09:58:43 +0300	[thread overview]
Message-ID: <58117740-1414-49fa-b58c-db228079f406@tuxon.dev> (raw)
In-Reply-To: <ZrTfc5imZgvduGc8@shikoro>

Hi, Wolfram,

On 08.08.2024 18:08, Wolfram Sang wrote:
> On Thu, Jul 11, 2024 at 02:52:00PM +0300, Claudiu wrote:
>> From: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
>>
>> Enable runtime PM autosuspend support for the RIIC driver. With this, in
>> case there are consecutive xfer requests the device wouldn't be runtime
>> enabled/disabled after each consecutive xfer but after the
>> the delay configured by user. With this, we can avoid touching hardware
>> registers involved in runtime PM suspend/resume saving in this way some
>> cycles. The default chosen autosuspend delay is zero to keep the
>> previous driver behavior.
>>
>> Signed-off-by: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
> 
> Basically, OK with me. I'd just like a comment here like:
> 
> /* Default 0 to save power. Can be overridden via sysfs for lower latency */

Ok, I'll update it in the next version.

Thank you,
Claudiu Beznea

>> +	pm_runtime_set_autosuspend_delay(dev, 0);
>> +	pm_runtime_use_autosuspend(dev);
> 
> Other than that:
> 
> Reviewed-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> 

  reply	other threads:[~2024-08-09  6:58 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-11 11:51 [PATCH v3 00/11] i2c: riic: Add support for Renesas RZ/G3S Claudiu
2024-07-11 11:51 ` [PATCH v3 01/11] i2c: riic: Use temporary variable for struct device Claudiu
2024-08-08 14:59   ` Wolfram Sang
2024-07-11 11:51 ` [PATCH v3 02/11] i2c: riic: Call pm_runtime_get_sync() when need to access registers Claudiu
2024-08-08 15:00   ` Wolfram Sang
2024-07-11 11:51 ` [PATCH v3 03/11] i2c: riic: Use pm_runtime_resume_and_get() Claudiu
2024-08-08 15:03   ` Wolfram Sang
2024-07-11 11:52 ` [PATCH v3 04/11] i2c: riic: Enable runtime PM autosuspend support Claudiu
2024-07-12  7:15   ` Biju Das
2024-07-12  7:40     ` claudiu beznea
2024-07-12  7:45       ` Biju Das
2024-07-12  7:49         ` claudiu beznea
2024-07-12  7:53           ` Biju Das
2024-08-08 15:08   ` Wolfram Sang
2024-08-09  6:58     ` claudiu beznea [this message]
2024-07-11 11:52 ` [PATCH v3 05/11] i2c: riic: Add suspend/resume support Claudiu
2024-08-08 15:15   ` Wolfram Sang
2024-08-09  7:08     ` claudiu beznea
2024-08-09 13:35       ` Wolfram Sang
2024-07-11 11:52 ` [PATCH v3 06/11] i2c: riic: Define individual arrays to describe the register offsets Claudiu
2024-08-08 15:20   ` Wolfram Sang
2024-07-11 11:52 ` [PATCH v3 07/11] dt-bindings: i2c: renesas,riic: Document the R9A08G045 support Claudiu
2024-08-08 15:21   ` Wolfram Sang
2024-08-09  7:20     ` claudiu beznea
2024-08-09 13:39       ` Wolfram Sang
2024-07-11 11:52 ` [PATCH v3 08/11] i2c: riic: Add support for fast mode plus Claudiu
2024-08-08 15:25   ` Wolfram Sang
2024-08-09  7:24     ` claudiu beznea
2024-07-11 11:52 ` [PATCH v3 09/11] arm64: dts: renesas: r9a08g045: Add I2C nodes Claudiu
2024-07-11 11:52 ` [PATCH v3 10/11] arm64: dts: renesas: rzg3s-smarc: Enable i2c0 node Claudiu
2024-07-11 11:52 ` [PATCH v3 11/11] arm64: dts: renesas: rzg3s-smarc-som: Enable i2c1 node Claudiu
2024-08-08  8:38 ` [PATCH v3 00/11] i2c: riic: Add support for Renesas RZ/G3S Wolfram Sang

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=58117740-1414-49fa-b58c-db228079f406@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+renesas@glider.be \
    --cc=krzk+dt@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=p.zabel@pengutronix.de \
    --cc=robh@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).