From: Huacai Chen <chenhuacai@kernel.org>
To: Jiaxun Yang <jiaxun.yang@flygoat.com>
Cc: linux-pci@vger.kernel.org, bhelgaas@google.com,
linux-kernel@vger.kernel.org, kw@linux.com,
lpieralisi@kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2] pci: loongson: Workaround MIPS firmware MRRS settings
Date: Sun, 6 Aug 2023 22:30:45 +0800 [thread overview]
Message-ID: <CAAhV-H7_OjTaU_wn6mUW0-JSrXS+=A2rXCiBc8cyce5ob49BLg@mail.gmail.com> (raw)
In-Reply-To: <e9c103dc-98ac-9a51-7291-f5da1467b2ff@flygoat.com>
Hi, Jiaxun,
On Sun, Aug 6, 2023 at 10:20 AM Jiaxun Yang <jiaxun.yang@flygoat.com> wrote:
>
>
>
> 在 2023/7/25 14:10, Jiaxun Yang 写道:
> > This is a partial revert of commit 8b3517f88ff2 ("PCI:
> > loongson: Prevent LS7A MRRS increases") for MIPS based Loongson.
> >
> > There are many MIPS based Loongson systems in wild that
> > shipped with firmware which does not set maximum MRRS properly.
> >
> > Limiting MRRS to 256 for all as MIPS Loongson comes with higher
> > MRRS support is considered rare.
> >
> > Cc: stable@vger.kernel.org
> > Closes: https://bugzilla.kernel.org/show_bug.cgi?id=217680
> > Fixes: 8b3517f88ff2 ("PCI: loongson: Prevent LS7A MRRS increases")
> > Signed-off-by: Jiaxun Yang <jiaxun.yang@flygoat.com>
>
> Ping?
> I expect this patch to go through PCI fixes tree.
Can we do it like this by modifying the existing loongson_mrrs_quirk()?
static void loongson_mrrs_quirk(struct pci_dev *pdev)
{
/*
* Some Loongson PCIe ports have h/w limitations of maximum read
* request size. They can't handle anything larger than this. So
* force this limit on any devices attached under these ports.
*/
struct pci_host_bridge *bridge = pci_find_host_bridge(pdev->bus);
#ifdef CONFIG_MIPS
set_pcie_ports_to_mrrs_256_to_emulate_the_firmware_behavior();
#endif
bridge->no_inc_mrrs = 1;
}
>
> Thanks
> - Jiaxun
>
> > ---
> > v2: Rename quirk name to: loongson_old_mrrs_quirk
> > ---
> > drivers/pci/controller/pci-loongson.c | 38 +++++++++++++++++++++++++++
> > 1 file changed, 38 insertions(+)
> >
> > diff --git a/drivers/pci/controller/pci-loongson.c b/drivers/pci/controller/pci-loongson.c
> > index fe0f732f6e43..d0f68b102d10 100644
> > --- a/drivers/pci/controller/pci-loongson.c
> > +++ b/drivers/pci/controller/pci-loongson.c
> > @@ -108,6 +108,44 @@ DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_LOONGSON,
> > DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_LOONGSON,
> > DEV_LS7A_PCIE_PORT6, loongson_mrrs_quirk);
> >
> > +#ifdef CONFIG_MIPS
> > +static void loongson_old_mrrs_quirk(struct pci_dev *pdev)
> > +{
> > + struct pci_bus *bus = pdev->bus;
> > + struct pci_dev *bridge;
> > + static const struct pci_device_id bridge_devids[] = {
> > + { PCI_VDEVICE(LOONGSON, DEV_LS2K_PCIE_PORT0) },
> > + { PCI_VDEVICE(LOONGSON, DEV_LS7A_PCIE_PORT0) },
> > + { PCI_VDEVICE(LOONGSON, DEV_LS7A_PCIE_PORT1) },
> > + { PCI_VDEVICE(LOONGSON, DEV_LS7A_PCIE_PORT2) },
> > + { PCI_VDEVICE(LOONGSON, DEV_LS7A_PCIE_PORT3) },
> > + { PCI_VDEVICE(LOONGSON, DEV_LS7A_PCIE_PORT4) },
> > + { PCI_VDEVICE(LOONGSON, DEV_LS7A_PCIE_PORT5) },
> > + { PCI_VDEVICE(LOONGSON, DEV_LS7A_PCIE_PORT6) },
> > + { 0, },
> > + };
> > +
> > + /* look for the matching bridge */
> > + while (!pci_is_root_bus(bus)) {
> > + bridge = bus->self;
> > + bus = bus->parent;
> > + /*
> > + * There are still some wild MIPS Loongson firmware won't
> > + * set MRRS properly. Limiting MRRS to 256 as MIPS Loongson
> > + * comes with higher MRRS support is considered rare.
> > + */
> > + if (pci_match_id(bridge_devids, bridge)) {
> > + if (pcie_get_readrq(pdev) > 256) {
> > + pci_info(pdev, "limiting MRRS to 256\n");
> > + pcie_set_readrq(pdev, 256);
> > + }
> > + break;
> > + }
> > + }
> > +}
> > +DECLARE_PCI_FIXUP_ENABLE(PCI_ANY_ID, PCI_ANY_ID, loongson_old_mrrs_quirk);
> > +#endif
> > +
> > static void loongson_pci_pin_quirk(struct pci_dev *pdev)
> > {
> > pdev->pin = 1 + (PCI_FUNC(pdev->devfn) & 3);
>
next prev parent reply other threads:[~2023-08-06 14:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 6:10 [PATCH v2] pci: loongson: Workaround MIPS firmware MRRS settings Jiaxun Yang
2023-08-06 2:20 ` Jiaxun Yang
2023-08-06 14:30 ` Huacai Chen [this message]
2023-08-08 7:38 ` Jiaxun Yang
2023-08-29 12:26 ` Linux regression tracking (Thorsten Leemhuis)
2023-08-31 5:31 ` Jiaxun Yang
2023-08-31 6:22 ` Huacai Chen
2023-08-31 8:58 ` Jiaxun Yang
2023-08-31 9:42 ` Huacai Chen
2023-08-31 10:04 ` Jiaxun Yang
2023-09-06 16:11 ` Jiaxun Yang
2023-09-07 1:18 ` Manivannan Sadhasivam
2023-09-07 3:13 ` Jiaxun Yang
2023-09-07 5:08 ` Manivannan Sadhasivam
2023-09-20 12:33 ` Linux regression tracking (Thorsten Leemhuis)
2023-10-20 11:04 ` Thorsten Leemhuis
2023-10-22 13:36 ` Jiaxun Yang
2023-10-22 13:38 ` Jiaxun Yang
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='CAAhV-H7_OjTaU_wn6mUW0-JSrXS+=A2rXCiBc8cyce5ob49BLg@mail.gmail.com' \
--to=chenhuacai@kernel.org \
--cc=bhelgaas@google.com \
--cc=jiaxun.yang@flygoat.com \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=stable@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).