From: claudiu beznea <claudiu.beznea@tuxon.dev>
To: Andi Shyti <andi.shyti@kernel.org>
Cc: chris.brandt@renesas.com, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, geert+renesas@glider.be,
magnus.damm@gmail.com, 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,
Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
Subject: Re: [PATCH v4 05/11] i2c: riic: Add suspend/resume support
Date: Tue, 20 Aug 2024 10:25:01 +0300 [thread overview]
Message-ID: <c9a466cc-97b5-465e-8420-ce69f307b362@tuxon.dev> (raw)
In-Reply-To: <ajj4fwoob5wq5guktq2b54h55fn5qlcakiybq6pk3xagiops7d@abpwevzemidy>
Hi, Andi,
On 19.08.2024 22:37, Andi Shyti wrote:
> Hi Claudiu,
>
> On Mon, Aug 19, 2024 at 01:23:42PM GMT, Claudiu wrote:
>> From: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
>>
>> Add suspend/resume support for the RIIC driver. This is necessary for the
>> Renesas RZ/G3S SoC which support suspend to deep sleep state where power
>> to most of the SoC components is turned off. As a result the I2C controller
>> needs to be reconfigured after suspend/resume. For this, the reset line
>> was stored in the driver private data structure as well as i2c timings.
>> The reset line and I2C timings are necessary to re-initialize the
>> controller after resume.
>>
>> Signed-off-by: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
>
> This patch doesn't have tags, so I'll add mine :-)
>
> Reviewed-by: Andi Shyti <andi.shyti@kernel.org>
>
> Just one thing, though...
>
> ...
>
>> +static int riic_i2c_resume(struct device *dev)
>> +{
>> + struct riic_dev *riic = dev_get_drvdata(dev);
>> + int ret;
>> +
>> + ret = reset_control_deassert(riic->rstc);
>> + if (ret)
>> + return ret;
>> +
>> + ret = riic_init_hw(riic);
>> + if (ret) {
>> + reset_control_assert(riic->rstc);
>> + return ret;
>
> Can I add a comment here saying:
>
> /*
> * Since the driver remains loaded after resume,
> * we want the reset line to be asserted.
> */
Sure, thank you!
> reset_control_assert(riic->rstc);
>
> Unless I missed the point :-)
>
> Thanks,
> Andi
next prev parent reply other threads:[~2024-08-20 7:25 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-19 10:23 [PATCH v4 00/11] i2c: riic: Add support for Renesas RZ/G3S Claudiu
2024-08-19 10:23 ` [PATCH v4 01/11] i2c: riic: Use temporary variable for struct device Claudiu
2024-08-19 10:23 ` [PATCH v4 02/11] i2c: riic: Call pm_runtime_get_sync() when need to access registers Claudiu
2024-08-19 10:23 ` [PATCH v4 03/11] i2c: riic: Use pm_runtime_resume_and_get() Claudiu
2024-08-19 10:23 ` [PATCH v4 04/11] i2c: riic: Enable runtime PM autosuspend support Claudiu
2024-08-19 10:23 ` [PATCH v4 05/11] i2c: riic: Add suspend/resume support Claudiu
2024-08-19 19:37 ` Andi Shyti
2024-08-20 7:25 ` claudiu beznea [this message]
2024-08-19 10:23 ` [PATCH v4 06/11] i2c: riic: Define individual arrays to describe the register offsets Claudiu
2024-08-19 20:20 ` Andi Shyti
2024-08-19 10:23 ` [PATCH v4 07/11] dt-bindings: i2c: renesas,riic: Document the R9A08G045 support Claudiu
2024-08-19 11:05 ` Krzysztof Kozlowski
2024-08-19 11:10 ` claudiu beznea
2024-08-19 11:22 ` Krzysztof Kozlowski
2024-08-19 16:39 ` Conor Dooley
2024-08-19 20:01 ` Andi Shyti
2024-08-20 7:45 ` claudiu beznea
2024-08-20 16:44 ` Conor Dooley
2024-08-19 10:23 ` [PATCH v4 08/11] i2c: riic: Add support for fast mode plus Claudiu
2024-08-19 20:12 ` Andi Shyti
2024-08-20 7:32 ` claudiu beznea
2024-08-19 10:23 ` [PATCH v4 09/11] arm64: dts: renesas: r9a08g045: Add I2C nodes Claudiu
2024-08-19 10:23 ` [PATCH v4 10/11] arm64: dts: renesas: rzg3s-smarc: Enable i2c0 node Claudiu
2024-08-19 10:23 ` [PATCH v4 11/11] arm64: dts: renesas: rzg3s-smarc-som: Enable i2c1 node Claudiu
2024-08-19 20:23 ` [PATCH v4 00/11] i2c: riic: Add support for Renesas RZ/G3S Andi Shyti
2024-08-20 10:16 ` claudiu beznea
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=c9a466cc-97b5-465e-8420-ce69f307b362@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).