From: Nicolas Frattaroli <nicolas.frattaroli@collabora.com>
To: linux-rockchip@lists.infradead.org, Niklas Cassel <cassel@kernel.org>
Cc: "Shawn Lin" <shawn.lin@rock-chips.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
linux-pci@vger.kernel.org, linux-rockchip@lists.infradead.org
Subject: Re: [PATCH v2] PCI: dw-rockchip: Add system PM support
Date: Thu, 17 Apr 2025 15:24:34 +0200 [thread overview]
Message-ID: <8815983.T7Z3S40VBb@workhorse> (raw)
In-Reply-To: <Z_5aib0WGKfIANj_@ryzen>
On Tuesday, 15 April 2025 15:09:29 Central European Summer Time Niklas Cassel wrote:
> On Fri, Apr 11, 2025 at 02:14:08PM +0800, Shawn Lin wrote:
> > [...]
> > + rockchip_pcie_ltssm_enable_control_mode(rockchip, PCIE_CLIENT_RC_MODE);
>
> Here you are setting PCIE_CLIENT_RC_MODE unconditionally.
>
> I really don't think that you have tested these callbacks with EP mode.
Hi Niklas,
I may be reading too much into your tone here, but I think it'd be good if
you didn't formulate this in such a passive-aggressive accusatory way. You
can just express your concern as a question about whether this was tested
with EP mode.
After all, I'm giving you specifically the same benefit of the doubt with
RC mode that has broken BAR resource mapping on RK3588 in timing-related
ways in v6.15-rc that has already taken me about a day of unreliable
bisects to try and track down, and may in fact end up bisecting to one of
your recent commits touching that part.
>
> If we look at pcie-qcom.c and pcie-qcom-ep.c, dev_pm_ops is defined in
> pcie-qcom.c, but not in pcie-qcom-ep.c.
>
> Perhaps it is starting to be time to have two separate drivers also for
> rockchip?
>
> [...]
Regards,
Nicolas Frattaroli
next prev parent reply other threads:[~2025-04-17 13:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-11 6:14 [PATCH v2] PCI: dw-rockchip: Add system PM support Shawn Lin
2025-04-11 17:21 ` Bjorn Helgaas
2025-04-15 13:09 ` Niklas Cassel
2025-04-17 10:51 ` Niklas Cassel
2025-04-18 0:27 ` Shawn Lin
2025-04-17 13:24 ` Nicolas Frattaroli [this message]
2025-04-17 14:35 ` Niklas Cassel
2025-04-17 8:17 ` Diederik de Haas
2025-04-17 8:29 ` Shawn Lin
2025-04-17 9:36 ` Diederik de Haas
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=8815983.T7Z3S40VBb@workhorse \
--to=nicolas.frattaroli@collabora.com \
--cc=bhelgaas@google.com \
--cc=cassel@kernel.org \
--cc=kw@linux.com \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=lpieralisi@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;
as well as URLs for NNTP newsgroup(s).