From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: marek.vasut@gmail.com, linux-pci@vger.kernel.org
Cc: "Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Arnd Bergmann" <arnd@arndb.de>,
linux-renesas-soc@vger.kernel.org,
"Krzysztof Wilczyński" <kw@linux.com>,
"Wolfram Sang" <wsa@the-dreams.de>,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
"Marek Vasut" <marek.vasut+renesas@gmail.com>,
"Yoshihiro Shimoda" <yoshihiro.shimoda.uh@renesas.com>
Subject: Re: [PATCH v5 1/2] PCI: rcar: Finish transition to L1 state in rcar_pcie_config_access()
Date: Tue, 1 Mar 2022 17:07:08 +0000 [thread overview]
Message-ID: <164615441330.28960.10937638212220997224.b4-ty@arm.com> (raw)
In-Reply-To: <20220219034604.603656-1-marek.vasut@gmail.com>
On Sat, 19 Feb 2022 04:46:03 +0100, marek.vasut@gmail.com wrote:
> From: Marek Vasut <marek.vasut+renesas@gmail.com>
>
> In case the controller is transitioning to L1 in rcar_pcie_config_access(),
> any read/write access to PCIECDR triggers asynchronous external abort. This
> is because the transition to L1 link state must be manually finished by the
> driver. The PCIe IP can transition back from L1 state to L0 on its own.
>
> [...]
Applied to pci/rcar, thanks!
[1/2] PCI: rcar: Finish transition to L1 state in rcar_pcie_config_access()
https://git.kernel.org/lpieralisi/pci/c/de6b5097f5
[2/2] PCI: rcar: Use PCI_SET_ERROR_RESPONSE after read which triggered an exception
https://git.kernel.org/lpieralisi/pci/c/9775965dba
Thanks,
Lorenzo
prev parent reply other threads:[~2022-03-01 17:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-19 3:46 [PATCH v5 1/2] PCI: rcar: Finish transition to L1 state in rcar_pcie_config_access() marek.vasut
2022-02-19 3:46 ` [PATCH v5 2/2] PCI: rcar: Use PCI_SET_ERROR_RESPONSE after read which triggered an exception marek.vasut
2022-02-23 13:20 ` Geert Uytterhoeven
2022-02-23 13:15 ` [PATCH v5 1/2] PCI: rcar: Finish transition to L1 state in rcar_pcie_config_access() Geert Uytterhoeven
2022-03-01 17:07 ` 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=164615441330.28960.10937638212220997224.b4-ty@arm.com \
--to=lorenzo.pieralisi@arm.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=geert+renesas@glider.be \
--cc=kw@linux.com \
--cc=linux-pci@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=marek.vasut+renesas@gmail.com \
--cc=marek.vasut@gmail.com \
--cc=wsa@the-dreams.de \
--cc=yoshihiro.shimoda.uh@renesas.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).