From: Bjorn Helgaas <helgaas@kernel.org>
To: Krishna chaitanya chundru <quic_krichai@quicinc.com>
Cc: linux-pci@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, mka@chromium.org,
quic_vbadigan@quicinc.com, quic_hemantk@quicinc.com,
quic_nitegupt@quicinc.com, quic_skananth@quicinc.com,
quic_ramkri@quicinc.com, manivannan.sadhasivam@linaro.org,
swboyd@chromium.org, dmitry.baryshkov@linaro.org
Subject: Re: [PATCH v5 0/3] PCI: Restrict pci transactions after pci suspend
Date: Wed, 24 Aug 2022 15:29:49 -0500 [thread overview]
Message-ID: <20220824202949.GA2805069@bhelgaas> (raw)
In-Reply-To: <1659526134-22978-1-git-send-email-quic_krichai@quicinc.com>
On Wed, Aug 03, 2022 at 04:58:51PM +0530, Krishna chaitanya chundru wrote:
> If the endpoint device state is D0 and irq's are not freed, then
> kernel try to mask interrupts in system suspend path by writing in to
> the vector table (for MSIX interrupts) and config space (for MSI's).
If clocks are being turned off while the PCI core is still accessing
the device, I think that means qcom suspend is not implemented
correctly.
> These transactions are initiated in the pm suspend after pcie clocks got
> disabled as part of platform driver pm suspend call. Due to it, these
> transactions are resulting in un-clocked access and eventually to crashes.
>
> So added a logic in qcom driver to restrict these unclocked access.
> And updated the logic to check the link state before masking
> or unmasking the interrupts.
>
> And some devices are taking time to settle the link in L1ss, so added a
> retry logic in the suspend ops.
>
> Krishna chaitanya chundru (3):
> PCI: qcom: Add system PM support
> PCI: qcom: Restrict pci transactions after pci suspend
> PCI: qcom: Add retry logic for link to be stable in L1ss
>
> drivers/pci/controller/dwc/pcie-designware-host.c | 14 ++-
> drivers/pci/controller/dwc/pcie-qcom.c | 117 +++++++++++++++++++++-
> 2 files changed, 127 insertions(+), 4 deletions(-)
>
> --
> 2.7.4
>
next prev parent reply other threads:[~2022-08-24 20:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 11:28 [PATCH v5 0/3] PCI: Restrict pci transactions after pci suspend Krishna chaitanya chundru
2022-08-03 11:28 ` [PATCH v5 1/3] PCI: qcom: Add system PM support Krishna chaitanya chundru
2022-08-10 21:50 ` Rob Herring
2022-08-24 3:28 ` Krishna Chaitanya Chundru
2022-08-24 4:11 ` Krishna Chaitanya Chundru
2022-08-03 11:28 ` [PATCH v5 2/3] PCI: qcom: Restrict pci transactions after pci suspend Krishna chaitanya chundru
2022-08-04 10:24 ` kernel test robot
2022-08-08 19:12 ` Stephen Boyd
2022-08-24 3:37 ` Krishna Chaitanya Chundru
2022-08-24 17:20 ` Stephen Boyd
2022-08-25 13:52 ` Krishna Chaitanya Chundru
2022-08-26 20:23 ` Stephen Boyd
2022-08-27 17:26 ` Manivannan Sadhasivam
2022-08-29 17:31 ` Krishna Chaitanya Chundru
2022-08-30 11:55 ` Manivannan Sadhasivam
2022-09-05 7:21 ` Sai Prakash Ranjan
2022-08-03 11:28 ` [PATCH v5 3/3] PCI: qcom: Add retry logic for link to be stable in L1ss Krishna chaitanya chundru
2022-08-04 10:24 ` kernel test robot
2022-08-04 21:33 ` Matthias Kaehlcke
2022-08-24 3:41 ` Krishna Chaitanya Chundru
2022-09-09 8:49 ` Krishna Chaitanya Chundru
2022-08-05 3:14 ` kernel test robot
2022-08-24 20:29 ` Bjorn Helgaas [this message]
2022-08-25 13:14 ` [PATCH v5 0/3] PCI: Restrict pci transactions after pci suspend Krishna Chaitanya Chundru
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=20220824202949.GA2805069@bhelgaas \
--to=helgaas@kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=mka@chromium.org \
--cc=quic_hemantk@quicinc.com \
--cc=quic_krichai@quicinc.com \
--cc=quic_nitegupt@quicinc.com \
--cc=quic_ramkri@quicinc.com \
--cc=quic_skananth@quicinc.com \
--cc=quic_vbadigan@quicinc.com \
--cc=swboyd@chromium.org \
/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