From: claudiu beznea <claudiu.beznea@tuxon.dev>
To: Biju Das <biju.das.jz@bp.renesas.com>,
Chris Brandt <Chris.Brandt@renesas.com>,
"andi.shyti@kernel.org" <andi.shyti@kernel.org>,
"robh@kernel.org" <robh@kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"geert+renesas@glider.be" <geert+renesas@glider.be>,
"magnus.damm@gmail.com" <magnus.damm@gmail.com>,
"p.zabel@pengutronix.de" <p.zabel@pengutronix.de>,
"wsa+renesas@sang-engineering.com"
<wsa+renesas@sang-engineering.com>
Cc: "linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@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, 12 Jul 2024 10:49:07 +0300 [thread overview]
Message-ID: <b5dd19d3-9a08-4187-b976-c197a2c0d9d7@tuxon.dev> (raw)
In-Reply-To: <TY3PR01MB1134611DB941585B340D09B7186A62@TY3PR01MB11346.jpnprd01.prod.outlook.com>
On 12.07.2024 10:45, Biju Das wrote:
> Hi Claudiu,
>
>> -----Original Message-----
>> From: claudiu beznea <claudiu.beznea@tuxon.dev>
>> Sent: Friday, July 12, 2024 8:41 AM
>> Subject: Re: [PATCH v3 04/11] i2c: riic: Enable runtime PM autosuspend support
>>
>> Hi, Biju,
>>
>> On 12.07.2024 10:15, Biju Das wrote:
>>> Hi Claudiu,
>>>
>>>> -----Original Message-----
>>>> From: Claudiu <claudiu.beznea@tuxon.dev>
>>>> Sent: Thursday, July 11, 2024 12:52 PM
>>>> Subject: [PATCH v3 04/11] i2c: riic: Enable runtime PM autosuspend
>>>> support
>>>>
>>>> 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.
>>>
>>> On the other hand, you are saving power. Currently the driver is
>>> highly optimized for Power usage.
>>>
>>> Before transfer turn on the clock
>>> After transfer turn off the clock, this is the optimal power usage correspond to suspend delay.
>>>
>>> By adding suspend delay, you are consuming power corresponding to that
>>> delay.
>>
>> The default delay is zero, see the following diff in this patch:
>>
>> @@ -479,6 +481,8 @@ static int riic_i2c_probe(struct platform_device *pdev)
>>
>> i2c_parse_fw_timings(dev, &i2c_t, true);
>>
>> + pm_runtime_set_autosuspend_delay(dev, 0);
>
> I just provided justification, why you addes 0 msec here, compared to xx msec
> in the original internal version.
Isn't it in the commit description already?
"The default chosen autosuspend delay is zero to keep the
previous driver behavior."
>
> Cheers,
> Biju
next prev parent reply other threads:[~2024-07-12 7:49 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 [this message]
2024-07-12 7:53 ` Biju Das
2024-08-08 15:08 ` Wolfram Sang
2024-08-09 6:58 ` claudiu beznea
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=b5dd19d3-9a08-4187-b976-c197a2c0d9d7@tuxon.dev \
--to=claudiu.beznea@tuxon.dev \
--cc=Chris.Brandt@renesas.com \
--cc=andi.shyti@kernel.org \
--cc=biju.das.jz@bp.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
all inboxes | Powered by JetHome®