From: claudiu beznea <claudiu.beznea@tuxon.dev>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
Andi Shyti <andi.shyti@kernel.org>
Cc: chris.brandt@renesas.com, 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 04/12] i2c: riic: Use pm_runtime_resume_and_get()
Date: Mon, 8 Jul 2024 08:19:18 +0300 [thread overview]
Message-ID: <dc232ee9-b28d-486f-a878-0320be84d1b9@tuxon.dev> (raw)
In-Reply-To: <CAMuHMdV=Uhqar6k_z_wo5jzge_7oY4tBK5zNiBbpsWa39Wvabw@mail.gmail.com>
On 05.07.2024 10:19, Geert Uytterhoeven wrote:
> Hi Andi,
>
> On Fri, Jul 5, 2024 at 12:42 AM Andi Shyti <andi.shyti@kernel.org> wrote:
>>> diff --git a/drivers/i2c/busses/i2c-riic.c b/drivers/i2c/busses/i2c-riic.c
>>> index 83e4d5e14ab6..002b11b020fa 100644
>>> --- a/drivers/i2c/busses/i2c-riic.c
>>> +++ b/drivers/i2c/busses/i2c-riic.c
>>> @@ -113,6 +113,8 @@ struct riic_irq_desc {
>>> char *name;
>>> };
>>>
>>> +static const char * const riic_rpm_err_msg = "Failed to runtime resume";
>>
>> Please, don't do this. Much clearer to write the message
>> explicitly.
>
> And the compiler will merge all identical strings, emitting
> just a single string.
>
>>
>>> +
>>> static inline void riic_writeb(struct riic_dev *riic, u8 val, u8 offset)
>>> {
>>> writeb(val, riic->base + riic->info->regs[offset]);
>>> @@ -133,10 +135,14 @@ static int riic_xfer(struct i2c_adapter *adap, struct i2c_msg msgs[], int num)
>>> struct riic_dev *riic = i2c_get_adapdata(adap);
>>> struct device *dev = adap->dev.parent;
>>> unsigned long time_left;
>>> - int i;
>>> + int i, ret;
>>> u8 start_bit;
>>>
>>> - pm_runtime_get_sync(dev);
>>> + ret = pm_runtime_resume_and_get(dev);
>>
>> In principle I like the error message to be always checked and I
>
> s/message/condition/?
>
>> will always approve it. Whenever there is a return value, even
>> when we are sure it's always '0', it needs to be checked.
>>
>> I had lots of discussions in the past about this topic but I
>> haven't always found support. I'd love to have the ack from a
>> renesas maintainer here.
>
> I don't mind checking for the error here.
>
>>
>>> + if (ret) {
>>> + dev_err(dev, riic_rpm_err_msg);
>
> Do you need to print these error messages?
No. I have it here as a result of some internal reviews.
Thank you,
Claudiu Beznea
> AFAIU, this cannot happen anyway.
> Ultimately, I expect the device driver that requested the transfer to
> handle failures, and print a message when needed.
>
> Gr{oetje,eeting}s,
>
> Geert
>
next prev parent reply other threads:[~2024-07-08 5:19 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 [this message]
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
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=dc232ee9-b28d-486f-a878-0320be84d1b9@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).