From: Jiwei <jiwei.sun.bj@qq.com>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>, Jiwei Sun <sjiwei@163.com>
Cc: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
linux-pci@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
helgaas@kernel.org, "Lukas Wunner" <lukas@wunner.de>,
ahuang12@lenovo.com, sunjw10@lenovo.com, sunjw10@outlook.com
Subject: Re: [PATCH v2 2/2] PCI: reread the Link Control 2 Register before using
Date: Mon, 20 Jan 2025 22:19:01 +0800 [thread overview]
Message-ID: <tencent_DBC0851ABE9B45D70B4BA098F876F5F10609@qq.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2501180101360.27432@angie.orcam.me.uk>
On 1/18/25 09:03, Maciej W. Rozycki wrote:
> On Fri, 17 Jan 2025, Jiwei Sun wrote:
>
>> However, within this section of code, lnkctl2 is not modified (after
>> reading from register on line 111) at all and remains 0x5. This results
>> in the condition on line 130 evaluating to 0 (false), which in turn
>> prevents the code from line 132 onward from being executed. The removing
>> 2.5GT/s downstream link speed restriction work can not be done.
>
> It seems like a regression from my original code indeed.
Sorry, I am confused by this sentence.
IIUC, there is no regression regarding the lifting 2.5GT/s restriction in
the commit a89c82249c37 ("PCI: Work around PCIe link training failures").
However, since commit de9a6c8d5dbf ("PCI/bwctrl: Add
pcie_set_target_speed() to set PCIe Link Speed"), the code to lift the
restriction is no longer executed. Therefore, commit de9a6c8d5dbf
("PCI/bwctrl: Add pcie_set_target_speed() to set PCIe Link Speed") can be
considered a regression of commit a a89c82249c37 ("PCI: Work around PCIe
link training failures").
So, this fix patch(PCI: reread the Link Control 2 Register before using)
is required, right?
Thanks,
Regards,
Jiwei
>
> Maciej
next prev parent reply other threads:[~2025-01-20 14:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-15 13:41 [PATCH v2 0/2] PCI: Fix the wrong reading of register fields Jiwei Sun
2025-01-15 13:41 ` [PATCH v2 1/2] " Jiwei Sun
2025-01-16 13:52 ` Ilpo Järvinen
2025-01-15 13:41 ` [PATCH v2 2/2] PCI: reread the Link Control 2 Register before using Jiwei Sun
2025-01-16 14:12 ` Ilpo Järvinen
2025-01-16 15:00 ` Maciej W. Rozycki
2025-01-17 13:53 ` Jiwei Sun
2025-01-18 1:03 ` Maciej W. Rozycki
2025-01-20 14:19 ` Jiwei [this message]
2025-01-20 15:05 ` Maciej W. Rozycki
2025-01-20 15:20 ` Jiwei
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=tencent_DBC0851ABE9B45D70B4BA098F876F5F10609@qq.com \
--to=jiwei.sun.bj@qq.com \
--cc=ahuang12@lenovo.com \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=macro@orcam.me.uk \
--cc=sjiwei@163.com \
--cc=sunjw10@lenovo.com \
--cc=sunjw10@outlook.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
all inboxes | Powered by JetHome®