From: Niklas Cassel <cassel@kernel.org>
To: Shawn Lin <shawn.lin@rock-chips.com>
Cc: "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 12:51:15 +0200 [thread overview]
Message-ID: <aADdI7ByEImYy3Pq@ryzen> (raw)
In-Reply-To: <Z_5aib0WGKfIANj_@ryzen>
On Tue, Apr 15, 2025 at 03:09:29PM +0200, Niklas Cassel wrote:
> On Fri, Apr 11, 2025 at 02:14:08PM +0800, Shawn Lin wrote:
(snip)
> > +
> > + 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.
>
> 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?
Hmm.. looking at pcie-tegra194.c, they do still have both RC and EP in the
same file, but they simply return -ENOTSUPP in the EP case:
https://github.com/torvalds/linux/blob/v6.15-rc2/drivers/pci/controller/dwc/pcie-tegra194.c#L2381-L2384
Perhaps you could do something similar?
Kind regards,
Niklas
WARNING: multiple messages have this Message-ID (diff)
From: Niklas Cassel <cassel@kernel.org>
To: Shawn Lin <shawn.lin@rock-chips.com>
Cc: "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 12:51:15 +0200 [thread overview]
Message-ID: <aADdI7ByEImYy3Pq@ryzen> (raw)
In-Reply-To: <Z_5aib0WGKfIANj_@ryzen>
On Tue, Apr 15, 2025 at 03:09:29PM +0200, Niklas Cassel wrote:
> On Fri, Apr 11, 2025 at 02:14:08PM +0800, Shawn Lin wrote:
(snip)
> > +
> > + 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.
>
> 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?
Hmm.. looking at pcie-tegra194.c, they do still have both RC and EP in the
same file, but they simply return -ENOTSUPP in the EP case:
https://github.com/torvalds/linux/blob/v6.15-rc2/drivers/pci/controller/dwc/pcie-tegra194.c#L2381-L2384
Perhaps you could do something similar?
Kind regards,
Niklas
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2025-04-17 10:51 UTC|newest]
Thread overview: 20+ 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 6:14 ` Shawn Lin
2025-04-11 17:21 ` Bjorn Helgaas
2025-04-11 17:21 ` Bjorn Helgaas
2025-04-15 13:09 ` Niklas Cassel
2025-04-15 13:09 ` Niklas Cassel
2025-04-17 10:51 ` Niklas Cassel [this message]
2025-04-17 10:51 ` Niklas Cassel
2025-04-18 0:27 ` Shawn Lin
2025-04-18 0:27 ` Shawn Lin
2025-04-17 13:24 ` Nicolas Frattaroli
2025-04-17 13:24 ` Nicolas Frattaroli
2025-04-17 14:35 ` Niklas Cassel
2025-04-17 14:35 ` Niklas Cassel
2025-04-17 8:17 ` Diederik de Haas
2025-04-17 8:17 ` Diederik de Haas
2025-04-17 8:29 ` Shawn Lin
2025-04-17 8:29 ` Shawn Lin
2025-04-17 9:36 ` Diederik de Haas
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=aADdI7ByEImYy3Pq@ryzen \
--to=cassel@kernel.org \
--cc=bhelgaas@google.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.