From: Marek Vasut <marek.vasut@gmail.com>
To: "Pali Rohár" <pali@kernel.org>
Cc: linux-pci@vger.kernel.org, "Arnd Bergmann" <arnd@arndb.de>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
"Wolfram Sang" <wsa@the-dreams.de>,
"Yoshihiro Shimoda" <yoshihiro.shimoda.uh@renesas.com>,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v3 2/2] PCI: rcar: Return all Fs from read which triggered an exception
Date: Fri, 18 Feb 2022 02:53:39 +0100 [thread overview]
Message-ID: <4901fe69-5bf2-0083-d890-bfaee467f57d@gmail.com> (raw)
In-Reply-To: <20220217130405.xq73bqshvldy2vn2@pali>
On 2/17/22 14:04, Pali Rohár wrote:
[...]
>>>>> Flipping either bit makes no difference, suspend/resume behaves the same and
>>>>> the link always recovers.
>>>>
>>>> Ok, perfect! And what happens without suspend/resume (just in normal
>>>> conditions)? E.g. during active usage of some PCIe card (wifi, sata, etc..).
>>>
>>> PING? Also what lspci see for the root port and card itself during hot reset?
>>
>> If I recall, lspci showed the root port and card.
>
> This is suspicious. Card should not respond to config read requests when
> is in hot reset state. Could you send output of lspci -vvxx of the root
> port and also card during this test? Maybe it is possible that root port
> has broken BRIDGE_CONTROL register and did not put card into Hot Reset
> state?
Yes, I could set the hardware up again and run more tests, it will take
some time, but I can still do that.
But before I spend any more time running tests for you here, I have to
admit, it seems to me running all those tests is completely off-topic in
context of these two bugfixes here.
So maybe it would make sense to stop the discussion here and move it to
separate thread ?
I have to admit, I also don't quite understand what it is that you're
trying to find out with all those tests.
next prev parent reply other threads:[~2022-02-18 1:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-22 22:15 [PATCH v3 1/2] PCI: rcar: Finish transition to L1 state in rcar_pcie_config_access() marek.vasut
2022-01-22 22:15 ` [PATCH v3 2/2] PCI: rcar: Return all Fs from read which triggered an exception marek.vasut
2022-01-23 14:12 ` Arnd Bergmann
2022-01-23 16:02 ` Marek Vasut
2022-01-23 15:31 ` Pali Rohár
2022-01-23 16:31 ` Marek Vasut
2022-01-23 16:49 ` Pali Rohár
2022-01-24 5:46 ` Marek Vasut
2022-01-24 9:37 ` Pali Rohár
2022-01-29 4:39 ` Marek Vasut
2022-01-31 12:53 ` Pali Rohár
2022-02-17 11:29 ` Pali Rohár
2022-02-17 12:59 ` Marek Vasut
2022-02-17 13:04 ` Pali Rohár
2022-02-18 1:53 ` Marek Vasut [this message]
2022-02-18 16:17 ` Pali Rohár
2022-01-23 15:39 ` Bjorn Helgaas
2022-01-28 2:47 ` kernel test robot
2022-02-16 11:50 ` Pali Rohár
2022-02-17 3:24 ` Marek Vasut
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=4901fe69-5bf2-0083-d890-bfaee467f57d@gmail.com \
--to=marek.vasut@gmail.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=lorenzo.pieralisi@arm.com \
--cc=pali@kernel.org \
--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).