From: Manivannan Sadhasivam <mani@kernel.org>
To: Frank Li <Frank.li@nxp.com>
Cc: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
helgaas@kernel.org, imx@lists.linux.dev, bhelgaas@google.com,
devicetree@vger.kernel.org, gustavo.pimentel@synopsys.com,
kw@linux.com, leoyang.li@nxp.com,
linux-arm-kernel@lists.infradead.org, linux-imx@nxp.com,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
lorenzo.pieralisi@arm.com, minghuan.lian@nxp.com,
mingkai.hu@nxp.com, robh+dt@kernel.org, roy.zang@nxp.com,
shawnguo@kernel.org, zhiqiang.hou@nxp.com
Subject: Re: [PATCH v3 1/2] PCI: dwc: Implement general suspend/resume functionality for L2/L3 transitions
Date: Thu, 20 Jul 2023 19:50:34 +0530 [thread overview]
Message-ID: <20230720142034.GA48270@thinkpad> (raw)
In-Reply-To: <ZLg2oObBfmhSzTFg@lizhi-Precision-Tower-5810>
On Wed, Jul 19, 2023 at 03:16:48PM -0400, Frank Li wrote:
> On Tue, Jul 18, 2023 at 03:34:00PM +0530, Manivannan Sadhasivam wrote:
> > On Mon, Jul 17, 2023 at 02:36:19PM -0400, Frank Li wrote:
> >
> > Fine then. But can we check for PM_LINKST_IN_L2 SII System Information Interface
> > (SII) instead of LTSSM state?
> >
> where define PM_LINKST_IN_L2? I just find one at
>
> drivers/pci/controller/dwc/pcie-qcom.c:#define PARF_DEBUG_CNT_PM_LINKST_IN_L2 0xc04
>
Yes, this register is not exposed by the DWC core itself but the vendors may
expose such as Qcom as you pointed out. If it is not available on all platforms,
then feel free to ignore my advice.
- Mani
> Frank
>
--
மணிவண்ணன் சதாசிவம்
next prev parent reply other threads:[~2023-07-20 14:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 16:41 [PATCH v3 1/2] PCI: dwc: Implement general suspend/resume functionality for L2/L3 transitions Frank Li
2023-04-19 16:41 ` [PATCH v3 2/2] PCI: layerscape: Add power management support for ls1028a Frank Li
2023-05-12 14:47 ` [PATCH v3 1/2] PCI: dwc: Implement general suspend/resume functionality for L2/L3 transitions Frank Li
2023-06-12 16:16 ` Frank Li
2023-07-17 14:05 ` Frank Li
2023-07-17 16:45 ` Manivannan Sadhasivam
2023-07-17 18:36 ` Frank Li
2023-07-18 10:04 ` Manivannan Sadhasivam
2023-07-19 19:16 ` Frank Li
2023-07-20 14:20 ` Manivannan Sadhasivam [this message]
2023-07-20 14:25 ` Manivannan Sadhasivam
2023-07-20 14:37 ` Frank Li
2023-07-20 16:07 ` Manivannan Sadhasivam
2023-07-20 16:20 ` Bjorn Helgaas
2023-07-20 16:27 ` Manivannan Sadhasivam
2023-07-20 18:35 ` Bjorn Helgaas
2023-07-20 16:26 ` Frank Li
2023-07-20 16:43 ` Manivannan Sadhasivam
2023-07-20 16:59 ` Frank Li
2023-07-21 2:09 ` Shawn Lin
2023-07-21 14:10 ` Frank Li
2023-07-21 16:07 ` Manivannan Sadhasivam
2023-07-21 16:21 ` Frank Li
2023-07-21 14:54 ` Manivannan Sadhasivam
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=20230720142034.GA48270@thinkpad \
--to=mani@kernel.org \
--cc=Frank.li@nxp.com \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=gustavo.pimentel@synopsys.com \
--cc=helgaas@kernel.org \
--cc=imx@lists.linux.dev \
--cc=kw@linux.com \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=manivannan.sadhasivam@linaro.org \
--cc=minghuan.lian@nxp.com \
--cc=mingkai.hu@nxp.com \
--cc=robh+dt@kernel.org \
--cc=roy.zang@nxp.com \
--cc=shawnguo@kernel.org \
--cc=zhiqiang.hou@nxp.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).