From: Lorenzo Pieralisi <lpieralisi@kernel.org>
To: l.stach@pengutronix.de, bhelgaas@google.com,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Richard Zhu <hongxing.zhu@nxp.com>
Cc: linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel@pengutronix.de,
linux-imx@nxp.com
Subject: Re: [PATCH v2] PCI: imx6: Save and restore MSI control of RC in suspend and resume
Date: Mon, 19 Jun 2023 11:38:41 +0200 [thread overview]
Message-ID: <168716742193.19064.16064178044930090085.b4-ty@kernel.org> (raw)
In-Reply-To: <1670479534-22154-1-git-send-email-hongxing.zhu@nxp.com>
On Thu, 08 Dec 2022 14:05:34 +0800, Richard Zhu wrote:
> The MSI Enable bit controls delivery of MSI interrupts from components
> below the Root Port. This bit might lost during the suspend, should be
> re-stored during resume.
>
> Save the MSI control during suspend, and restore it in resume.
>
>
> [...]
Applied to controller/dwc (commit log rewritten - please check), thanks!
[1/1] PCI: imx6: Save and restore MSI control of RC in suspend and resume
https://git.kernel.org/pci/pci/c/3bbc3c72c4b8
Thanks,
Lorenzo
prev parent reply other threads:[~2023-06-19 9:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 6:05 [PATCH v2] PCI: imx6: Save and restore MSI control of RC in suspend and resume Richard Zhu
2022-12-30 15:06 ` Lorenzo Pieralisi
2023-01-09 2:08 ` Hongxing Zhu
2023-03-10 16:13 ` Lorenzo Pieralisi
2023-03-13 2:50 ` Hongxing Zhu
2023-03-13 17:49 ` Bjorn Helgaas
2023-03-14 3:24 ` Hongxing Zhu
2023-03-14 10:27 ` Lorenzo Pieralisi
2023-03-16 7:37 ` Hongxing Zhu
2023-03-16 8:10 ` Lorenzo Pieralisi
2023-03-17 7:38 ` Hongxing Zhu
2023-03-17 22:24 ` Bjorn Helgaas
2023-03-20 7:02 ` Hongxing Zhu
2023-03-24 15:59 ` Lorenzo Pieralisi
2023-03-27 0:22 ` Hongxing Zhu
2023-04-05 15:55 ` Lorenzo Pieralisi
2023-04-10 6:48 ` Hongxing Zhu
2023-06-19 9:07 ` Lorenzo Pieralisi
2023-04-11 2:36 ` Serge Semin
2023-06-19 9:38 ` Lorenzo Pieralisi [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=168716742193.19064.16064178044930090085.b4-ty@kernel.org \
--to=lpieralisi@kernel.org \
--cc=bhelgaas@google.com \
--cc=hongxing.zhu@nxp.com \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.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).