linux-i3c.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: adrianhoyin.ng@altera.com, dinguyen@kernel.org, Frank.Li@nxp.com,
	linux-i3c@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] i3c: dw: add option to disable runtime PM for DesignWare I3C controller
Date: Thu, 16 Oct 2025 09:37:53 +0200	[thread overview]
Message-ID: <aPCg0bFm4-DnmhAp@shikoro> (raw)
In-Reply-To: <20251016071051c3f647ce@mail.local>


> > Add a new Kconfig option, DW_I3C_DISABLE_RUNTIME_PM, that allows
> > disabling all runtime power management (PM) operations for the
> > Synopsys DesignWare I3C controller. When this option is selected,
> > the driver skips all runtime PM calls such as pm_runtime_enable(),
> > pm_runtime_get(), and pm_runtime_put(), keeping the controller
> > permanently active.
> 
> While the quirk may make sense, it definitively can't be activated by a
> Kconfig option. This should rather be tied to a new compatible string or
> a property.

I wondered why this is a quirk, at all, and not default behaviour. Is it
because it works with some RPM implementations and not with others,
depending on the platform?

But even if that is the case, it might be worth to opt-in for power
management instead of opting-out for buggy behaviour. Because I would
not assume that IBI have been thoroughly tested when a new platform
using this driver gets upstream. So, the buggy behaviour may only be
recognized later. Or?


-- 
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c

  reply	other threads:[~2025-10-16  7:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-16  2:03 [RFC PATCH] i3c: dw: add option to disable runtime PM for DesignWare I3C controller adrianhoyin.ng
2025-10-16  7:10 ` Alexandre Belloni
2025-10-16  7:37   ` Wolfram Sang [this message]
2025-10-30 17:09     ` Alexandre Belloni

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=aPCg0bFm4-DnmhAp@shikoro \
    --to=wsa+renesas@sang-engineering.com \
    --cc=Frank.Li@nxp.com \
    --cc=adrianhoyin.ng@altera.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=dinguyen@kernel.org \
    --cc=linux-i3c@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    /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).