From: Bjorn Helgaas <helgaas@kernel.org>
To: Zhangfei Gao <zhangfei.gao@linaro.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Arnd Bergmann <arnd@arndb.de>,
jean-philippe <jean-philippe@linaro.org>,
kenneth-lee-2012@foxmail.com, wangzhou1@hisilicon.com,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/3] PCI: set dma-can-stall for HiSilicon chip
Date: Thu, 21 Jan 2021 10:57:06 -0600 [thread overview]
Message-ID: <20210121165706.GA2663152@bjorn-Precision-5520> (raw)
In-Reply-To: <1610960316-28935-4-git-send-email-zhangfei.gao@linaro.org>
On Mon, Jan 18, 2021 at 04:58:36PM +0800, Zhangfei Gao wrote:
> HiSilicon KunPeng920 and KunPeng930 have devices appear as PCI but are
> actually on the AMBA bus. These fake PCI devices can support SVA via
> SMMU stall feature, by setting dma-can-stall for ACPI platforms.
>
> Signed-off-by: Zhangfei Gao <zhangfei.gao@linaro.org>
> Signed-off-by: Jean-Philippe Brucker <jean-philippe@linaro.org>
> Signed-off-by: Zhou Wang <wangzhou1@hisilicon.com>
> ---
> Property dma-can-stall depends on patchset
> https://lore.kernel.org/linux-iommu/20210108145217.2254447-1-jean-philippe@linaro.org/
>
> drivers/pci/quirks.c | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c
> index 873d27f..b866cdf 100644
> --- a/drivers/pci/quirks.c
> +++ b/drivers/pci/quirks.c
> @@ -1827,10 +1827,23 @@ DECLARE_PCI_FIXUP_CLASS_FINAL(PCI_VENDOR_ID_HUAWEI, 0x1610, PCI_CLASS_BRIDGE_PCI
>
> static void quirk_huawei_pcie_sva(struct pci_dev *pdev)
> {
> + struct property_entry properties[] = {
> + PROPERTY_ENTRY_BOOL("dma-can-stall"),
> + {},
> + };
> +
> if (pdev->revision != 0x21 && pdev->revision != 0x30)
> return;
>
> pdev->pasid_no_tlp = 1;
> +
> + /*
> + * Set the dma-can-stall property on ACPI platforms. Device tree
> + * can set it directly.
> + */
> + if (!pdev->dev.of_node &&
> + device_add_properties(&pdev->dev, properties))
> + pci_warn(pdev, "could not add stall property");
What's the purpose of adding the "dma-can-stall" property? I don't
see any reference to that property in the tree or in this series. If
this is related to some other series that uses it, perhaps this part
should be moved to that series?
> }
> DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_HUAWEI, 0xa250, quirk_huawei_pcie_sva);
> DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_HUAWEI, 0xa251, quirk_huawei_pcie_sva);
> --
> 2.7.4
>
next prev parent reply other threads:[~2021-01-21 16:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 8:58 [PATCH v2 0/3] PCI: Add a quirk to enable SVA for HiSilicon chip Zhangfei Gao
2021-01-18 8:58 ` [PATCH v2 1/3] PCI: PASID can be enabled without TLP prefix Zhangfei Gao
2021-01-18 8:58 ` [PATCH v2 2/3] PCI: Add a quirk to set pasid_no_tlp for HiSilicon chip Zhangfei Gao
2021-01-18 8:58 ` [PATCH v2 3/3] PCI: set dma-can-stall " Zhangfei Gao
2021-01-21 16:57 ` Bjorn Helgaas [this message]
2021-01-21 17:50 ` Bjorn Helgaas
2021-03-07 17:54 ` Krzysztof Wilczyński
2021-03-09 3:08 ` Zhangfei Gao
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=20210121165706.GA2663152@bjorn-Precision-5520 \
--to=helgaas@kernel.org \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=jean-philippe@linaro.org \
--cc=kenneth-lee-2012@foxmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=wangzhou1@hisilicon.com \
--cc=zhangfei.gao@linaro.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