From: Marek Vasut <marek.vasut@gmail.com>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Bjorn Helgaas <helgaas@kernel.org>
Cc: linux-pci@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Wolfram Sang <wsa@the-dreams.de>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH] PCI: rcar: Add L1 link state fix into data abort hook
Date: Sun, 29 Nov 2020 14:02:42 +0100 [thread overview]
Message-ID: <092d664e-098d-2f51-9d47-4a60a8bd9bb6@gmail.com> (raw)
In-Reply-To: <20201119162508.GA23852@e121166-lin.cambridge.arm.com>
On 11/19/20 5:25 PM, Lorenzo Pieralisi wrote:
[...]
>>> The R-Car PCIe controller is capable of handling L0s/L1 link states.
>>> While the controller can enter and exit L0s link state, and exit L1
>>> link state, without any additional action from the driver, to enter
>>> L1 link state, the driver must complete the link state transition by
>>> issuing additional commands to the controller.
>>
>> So IIUC an R-Car Root Port can't enter L1 without help from the
>> driver? That *sounds* like a hardware defect, since ASPM is supposed
>> to be "hardware-autonomous" once configured.
>
> Sorry for the late feedback, starting to queue patches for v5.11.
Same here.
> Is this issue ASPM related (ie is it supported by the host controller) ?
>
> *Or* it is related to kernel driven device D-{1,2,3} L1 entry ?
>
> I am asking because if it is only related to D-{1,2,3} device state
> entry we could intercept the PMCSR write and move the quirk in config
> space accessors.
I don't think you can always intercept the entry into L1 state (e.g. if
userspace triggers it), but you should be able to recover from such a
state (this controller does permit you to do so), so I would say this is
a third option.
next prev parent reply other threads:[~2020-11-29 13:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-12 21:18 [PATCH] PCI: rcar: Add L1 link state fix into data abort hook marek.vasut
2020-09-13 17:22 ` Bjorn Helgaas
2020-09-14 1:36 ` Marek Vasut
2020-09-14 4:01 ` Bjorn Helgaas
2020-09-16 13:50 ` Marek Vasut
2020-11-19 16:25 ` Lorenzo Pieralisi
2020-11-29 13:02 ` Marek Vasut [this message]
2020-09-14 9:29 ` Geert Uytterhoeven
2020-09-14 10:11 ` Geert Uytterhoeven
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=092d664e-098d-2f51-9d47-4a60a8bd9bb6@gmail.com \
--to=marek.vasut@gmail.com \
--cc=bhelgaas@google.com \
--cc=geert+renesas@glider.be \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.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).