From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Navon John Lukose <navonjohnlukose@gmail.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Lee Jones <lee@kernel.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
mfd@lists.linux.dev, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] mfd: intel-lpss: Set d3hot_delay to 0
Date: Thu, 22 Oct 2026 13:19:39 +0300 (EEST) [thread overview]
Message-ID: <42bbb588-8750-0985-4daf-57608cb09c46@linux.intel.com> (raw)
In-Reply-To: <20261022040453.45797-1-navonjohnlukose@gmail.com>
On Thu, 22 Oct 2026, Navon John Lukose wrote:
> intel-lpss-pci already clears d3cold_delay, but every runtime resume of an
> LPSS controller still sleeps the default 10 ms d3hot_delay in
> pci_power_up().
>
> The PCI spec asks for those 10 ms on D3hot->D0. Mika pointed out that the
Please include the surname too. Since you'll have the email address in
Mika's tag that's probably enough (otherwise you should include the email
as well).
> LPSS controllers are not really PCI-connected devices, so the delay is
> likely not needed. quirk_remove_d3hot_delay() drops it on several older
> Intel chipsets, Cherry Trail among them, and commit 815b4448198f ("i3c:
> mipi-i3c-hci-pci: Set d3hot_delay to 0 for Intel controllers") does the
> same for the Intel I3C controllers.
>
> Nothing misbehaves with the delay in place, so this only shortens resume.
> On Arrow Lake-H (Lenovo Yoga Pro 7 14IAH10) the touchpad's I2C controller
> autosuspends after 1 s idle, and the first report afterwards waits for the
> resume. With d3hot_delay set to 0 the i2c-hid interrupt handler for that
> report takes 1.1-1.9 ms instead of 12.6-14.4 ms, with no I2C errors. Only
> Arrow Lake-H was tested.
I don't like how this changelog is structured.
You should make it clear at the beginning that there's some delay
(introducing the problem you're trying to address early) even if
everything "works" with the delay and that the delay is due to default 10
ms D3hot->D0 wait.
And only then proceed with in depth explanation about the delay and why
it's not needed.
--
i.
> Signed-off-by: Navon John Lukose <navonjohnlukose@gmail.com>
> ---
>
> Notes:
> Changes since RFC:
> - Drop RFC and add the review discussion to the changelog (Andy).
>
> RFC: https://lore.kernel.org/r/20261016114347.23633-1-navonjohnlukose@gmail.com
>
> drivers/mfd/intel-lpss-pci.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/mfd/intel-lpss-pci.c b/drivers/mfd/intel-lpss-pci.c
> index 63a3fb58566..5672f033e5c 100644
> --- a/drivers/mfd/intel-lpss-pci.c
> +++ b/drivers/mfd/intel-lpss-pci.c
> @@ -70,6 +70,7 @@ static int intel_lpss_pci_probe(struct pci_dev *pdev,
> info->quirks = quirk_pci_info->driver_data;
>
> pdev->d3cold_delay = 0;
> + pdev->d3hot_delay = 0;
>
> /* Probably it is enough to set this for iDMA capable devices only */
> pci_set_master(pdev);
>
prev parent reply other threads:[~2026-10-22 10:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 4:04 Navon John Lukose
2026-10-22 4:57 ` Mika Westerberg
2026-10-22 10:19 ` Ilpo Järvinen [this message]
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=42bbb588-8750-0985-4daf-57608cb09c46@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mfd@lists.linux.dev \
--cc=mika.westerberg@linux.intel.com \
--cc=navonjohnlukose@gmail.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®