From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Krishna chaitanya chundru <quic_krichai@quicinc.com>, helgaas@kernel.org
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
Subject: Re: [PATCH v4 0/2] PCI: Restrict pci transactions after pci suspend
Date: Wed, 6 Jul 2022 18:13:43 +0300 [thread overview]
Message-ID: <ceaca6d7-958d-ade6-9ee5-5e70bc57bbd7@linaro.org> (raw)
In-Reply-To: <1657118425-10304-1-git-send-email-quic_krichai@quicinc.com>
On 06/07/2022 17:40, 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).
>
> 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.
Please do not send new versions as replies to previous ones. This breaks
threading for the reviewers.
> Krishna chaitanya chundru (2):
> PCI: qcom: Add system PM support
> PCI: qcom: Restrict pci transactions after pci suspend
>
> drivers/pci/controller/dwc/pcie-designware-host.c | 14 ++-
> drivers/pci/controller/dwc/pcie-qcom.c | 121 +++++++++++++++++++++-
> 2 files changed, 131 insertions(+), 4 deletions(-)
--
With best wishes
Dmitry
prev parent reply other threads:[~2022-07-06 15:13 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 7:28 [PATCH v1 0/2] PCI: Restrict pci transactions after pci suspend Krishna chaitanya chundru
2022-06-24 7:28 ` [PATCH v1 1/2] PCI: qcom: Add system PM support Krishna chaitanya chundru
2022-06-24 18:31 ` Matthias Kaehlcke
2022-06-24 7:28 ` [PATCH v1 2/2] PCI: qcom: Restrict pci transactions after pci suspend Krishna chaitanya chundru
2022-06-29 9:33 ` [PATCH v2 0/2] PCI: " Krishna chaitanya chundru
2022-06-29 9:33 ` [PATCH v2 1/2] PCI: qcom: Add system PM support Krishna chaitanya chundru
2022-06-29 19:33 ` Matthias Kaehlcke
2022-06-30 4:34 ` Manivannan Sadhasivam
2022-06-30 9:59 ` Krishna Chaitanya Chundru
2022-07-04 4:44 ` Manivannan Sadhasivam
2022-07-04 4:48 ` Manivannan Sadhasivam
2022-06-29 9:33 ` [PATCH v2 2/2] PCI: qcom: Restrict pci transactions after pci suspend Krishna chaitanya chundru
2022-07-04 4:54 ` Manivannan Sadhasivam
2022-07-01 14:13 ` [PATCH v3 0/2] PCI: " Krishna chaitanya chundru
2022-07-01 14:13 ` [PATCH v3 1/2] PCI: qcom: Add system PM support Krishna chaitanya chundru
2022-07-01 14:13 ` [PATCH v3 2/2] PCI: qcom: Restrict pci transactions after pci suspend Krishna chaitanya chundru
2022-07-06 14:40 ` [PATCH v4 0/2] PCI: " Krishna chaitanya chundru
2022-07-06 14:40 ` [PATCH v4 1/2] PCI: qcom: Add system PM support Krishna chaitanya chundru
2022-07-11 21:53 ` Matthias Kaehlcke
2022-07-14 10:41 ` Krishna Chaitanya Chundru
2022-07-15 13:43 ` Johan Hovold
2022-07-06 14:40 ` [PATCH v4 2/2] PCI: qcom: Restrict pci transactions after pci suspend Krishna chaitanya chundru
2022-07-12 0:34 ` Matthias Kaehlcke
2022-07-15 13:51 ` Johan Hovold
2022-07-06 15:13 ` Dmitry Baryshkov [this message]
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=ceaca6d7-958d-ade6-9ee5-5e70bc57bbd7@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=helgaas@kernel.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;
as well as URLs for NNTP newsgroup(s).