From: Bjorn Helgaas <helgaas@kernel.org>
To: LeoLiu-oc <LeoLiu-oc@zhaoxin.com>
Cc: bhelgaas@google.com, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, CobeChen@zhaoxin.com,
TonyWWang@zhaoxin.com, YeeLi@zhaoxin.com, Leoliu@zhaoxin.com
Subject: Re: [PATCH] PCI: Extend PCI root port device IDs for Zhaoxin platforms
Date: Fri, 1 Dec 2023 09:53:20 -0600 [thread overview]
Message-ID: <20231201155320.GA518898@bhelgaas> (raw)
In-Reply-To: <20231201120942.680075-1-LeoLiu-oc@zhaoxin.com>
On Fri, Dec 01, 2023 at 08:09:42PM +0800, LeoLiu-oc wrote:
> From: leoliu-oc <leoliu-oc@zhaoxin.com>
>
> Add more PCI root port device IDs to the
> pci_quirk_zhaoxin_pcie_ports_acs() for some new Zhaoxin platforms.
Can you please add a note about the plan to deal with this for future
devices, e.g., something like "future Zhaoxin devices now in
development will advertise an ACS Capability as described in the
PCIe spec"?
The point of quirks is to work around hardware that is broken or
doesn't conform to the spec in some way. We have to add quirks when
broken hardware is already in the field, but we should have a plan to
fix newer devices so they don't require quirks.
> Signed-off-by: leoliu-oc <leoliu-oc@zhaoxin.com>
> ---
> drivers/pci/quirks.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c
> index ea476252280a..db74f8f07096 100644
> --- a/drivers/pci/quirks.c
> +++ b/drivers/pci/quirks.c
> @@ -4709,7 +4709,7 @@ static int pci_quirk_zhaoxin_pcie_ports_acs(struct pci_dev *dev, u16 acs_flags)
> switch (dev->device) {
> case 0x0710 ... 0x071e:
> case 0x0721:
> - case 0x0723 ... 0x0732:
> + case 0x0723 ... 0x073b:
> return pci_acs_ctrl_enabled(acs_flags,
> PCI_ACS_SV | PCI_ACS_RR | PCI_ACS_CR | PCI_ACS_UF);
> }
> --
> 2.34.1
>
next prev parent reply other threads:[~2023-12-01 15:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 12:09 [PATCH] PCI: Extend PCI root port device IDs for Zhaoxin platforms LeoLiu-oc
2023-12-01 15:53 ` Bjorn Helgaas [this message]
2023-12-11 9:11 ` LeoLiu-oc
2023-12-11 9:15 ` [PATCH v2] " LeoLiu-oc
2023-12-11 20:07 ` Bjorn Helgaas
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=20231201155320.GA518898@bhelgaas \
--to=helgaas@kernel.org \
--cc=CobeChen@zhaoxin.com \
--cc=LeoLiu-oc@zhaoxin.com \
--cc=Leoliu@zhaoxin.com \
--cc=TonyWWang@zhaoxin.com \
--cc=YeeLi@zhaoxin.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@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