mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Igor Velkov <iav@iav.lv>
To: Enrique Hernández Bello <ehbello@gmail.com>
Cc: shawn.lin@rock-chips.com, lpieralisi@kernel.org,
	kwilczynski@kernel.org, mani@kernel.org, bhelgaas@google.com,
	robh@kernel.org, heiko@sntech.de, dlemoal@kernel.org,
	linux-pci@vger.kernel.org, linux-rockchip@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	manivannan.sadhasivam@oss.qualcomm.com, iav@iav.lv
Subject: Re: [PATCH v2] PCI: rockchip: Skip the Tpvperl wait when power is already valid
Date: Wed, 28 Oct 2026 07:10:00 +0200	[thread overview]
Message-ID: <20261028-h64-tpvperl-ab-skip@iav.lv> (raw)
In-Reply-To: <20261028005548.2399155-1-ehbello@gmail.com>

On Wed, 28 Oct 2026 00:55:48 +0000, Enrique Hernández Bello wrote:
> If your first resume then survives, the resume hunk is the problem
> and I will drop it

Since the next version keeps the full wait on resume, it no longer
changes the resume path, so I'll skip the A/B and test that version
on Helios64 instead: boots plus s2idle cycles, results in reply to it.

The probe SError is in the cover letter of my rockchip-host RFC:
https://lore.kernel.org/r/20261024-rockchip-pcie-resume-v1-0-58e54a5cf5f1@iav.lv

Igor

  reply	other threads:[~2026-10-28  5:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-11 21:15 Enrique Hernández Bello
2026-09-12  1:21 ` Shawn Lin
2026-09-12 14:14   ` Enrique Hernández Bello
2026-10-14  7:27 ` Manivannan Sadhasivam
2026-10-16  0:21   ` Igor Velkov
2026-10-28  0:55     ` Enrique Hernández Bello
2026-10-28  5:10       ` Igor Velkov [this message]
2026-10-28 17:31         ` Enrique Hernández Bello
2026-10-28  0:55   ` Enrique Hernández Bello

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=20261028-h64-tpvperl-ab-skip@iav.lv \
    --to=iav@iav.lv \
    --cc=bhelgaas@google.com \
    --cc=dlemoal@kernel.org \
    --cc=ehbello@gmail.com \
    --cc=heiko@sntech.de \
    --cc=kwilczynski@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=lpieralisi@kernel.org \
    --cc=mani@kernel.org \
    --cc=manivannan.sadhasivam@oss.qualcomm.com \
    --cc=robh@kernel.org \
    --cc=shawn.lin@rock-chips.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®