From: Pavel Machek <pavel@nabladev.com>
To: tommaso.merciai.xr@bp.renesas.com
Cc: cip-dev@lists.cip-project.org,
Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@toshiba.co.jp>,
Pavel Machek <pavel@nabladev.com>,
Biju Das <biju.das.jz@bp.renesas.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
tomm.merciai@gmail.com
Subject: Re: [cip-dev] [PATCH 5.10.y-cip] i2c: riic: Move suspend handling to NOIRQ phase
Date: Mon, 16 Feb 2026 12:55:30 +0100 [thread overview]
Message-ID: <aZMFskqvbJa24JYR@duo.ucw.cz> (raw)
In-Reply-To: <20260210102637.484003-1-tommaso.merciai.xr@bp.renesas.com>
[-- Attachment #1: Type: text/plain, Size: 1024 bytes --]
Hi!
> Wake up the controller in the suspend() callback while runtime PM is
> still enabled. The I2C controller will remain available until the
> suspend_noirq() callback (pm_runtime_force_suspend()) is called. During
> resume, the I2C controller can be restored by the resume_noirq() callback
> (pm_runtime_force_resume()). Finally, the resume() callback re-enables
> autosuspend. As a result, the I2C controller can remain available until
> the system enters suspend_noirq() and from resume_noirq().
> +++ b/drivers/i2c/busses/i2c-riic.c
> @@ -606,6 +634,10 @@ static int riic_i2c_resume(struct device *dev)
> if (ret)
> return ret;
>
> + ret = pm_runtime_force_resume(dev);
> + if (ret)
> + return ret;
> +
> ret = riic_init_hw(riic);
> if (ret) {
> /*
Similar to the next error return, this likely should do
"reset_control_assert(riic->rstc);" before returning. I guess fixed
patch would be best here.
Thanks and best regards,
Pavel
--
In cooperation with Nabla.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2026-02-16 11:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 10:26 [PATCH 5.10.y-cip] i2c: riic: Move suspend handling to NOIRQ phase Tommaso Merciai
2026-02-16 11:55 ` Pavel Machek [this message]
2026-02-16 11:57 ` [cip-dev] " Pavel Machek
2026-02-18 5:07 ` nobuhiro.iwamatsu.x90
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=aZMFskqvbJa24JYR@duo.ucw.cz \
--to=pavel@nabladev.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=cip-dev@lists.cip-project.org \
--cc=nobuhiro1.iwamatsu@toshiba.co.jp \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=tomm.merciai@gmail.com \
--cc=tommaso.merciai.xr@bp.renesas.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