From: Niklas Cassel <nks@flawful.org>
To: David Bremner <david@tethera.net>
Cc: wilfred.opensource@gmail.com, alistair@alistair23.me,
bhelgaas@google.com, cassel@kernel.org, dlemoal@kernel.org,
heiko@sntech.de, kw@linux.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
linux-rockchip@lists.infradead.org, lpieralisi@kernel.org,
mani@kernel.org, p.zabel@pengutronix.de, robh@kernel.org,
wilfred.mallawa@wdc.com, Shawn Lin <shawn.lin@rock-chips.com>
Subject: Re: [PATCH v3] PCI: dw-rockchip: Add support for slot reset on link down event
Date: Mon, 14 Jul 2025 09:08:25 +0200 [thread overview]
Message-ID: <aHSs6ZF8rQIqEOyR@flawful.org> (raw)
In-Reply-To: <87cya6wdhc.fsf@tethera.net>
Hello David,
On Fri, Jul 11, 2025 at 07:48:31PM -0300, David Bremner wrote:
>
> What is the current status of this patch (and the pre-requisites) with
> respect to mainline linux?
>
> I'm wondering if it might be relevent to the problems [1] I've been
> having with rk3588 resume, but it isn't clear to me what I need to apply
> to e.g. v6.16~rc1 to test it.
This is the prerequisite series:
https://lore.kernel.org/linux-pci/20250508-pcie-reset-slot-v4-0-7050093e2b50@linaro.org/
However, Bjorn gave some comments on it, and Manivannan has said that he
will send a new version.
That said, if you have problems with suspend/resume, perhaps you want to
try this patch instead:
https://lore.kernel.org/linux-pci/1744940759-23823-1-git-send-email-shawn.lin@rock-chips.com/
I don't know if Shawn intends to send a new version or not.
Kind regards,
Niklas
next prev parent reply other threads:[~2025-07-14 7:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-09 2:30 Wilfred Mallawa
2025-05-09 13:01 ` Niklas Cassel
2025-05-15 7:50 ` Niklas Cassel
2025-07-11 22:48 ` David Bremner
2025-07-14 7:08 ` Niklas Cassel [this message]
2025-07-16 12:55 ` David Bremner
2025-07-15 3:09 ` Wilfred Mallawa
2025-07-15 22:53 ` Wilfred Mallawa
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=aHSs6ZF8rQIqEOyR@flawful.org \
--to=nks@flawful.org \
--cc=alistair@alistair23.me \
--cc=bhelgaas@google.com \
--cc=cassel@kernel.org \
--cc=david@tethera.net \
--cc=dlemoal@kernel.org \
--cc=heiko@sntech.de \
--cc=kw@linux.com \
--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=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=shawn.lin@rock-chips.com \
--cc=wilfred.mallawa@wdc.com \
--cc=wilfred.opensource@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®