From: Zhou Wang <wangzhou1@hisilicon.com>
To: Zhangfei Gao <zhangfei.gao@linaro.org>,
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>
Cc: <linux-pci@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 0/3] PCI: Add a quirk to enable SVA for HiSilicon chip
Date: Mon, 28 Jun 2021 09:52:25 +0800 [thread overview]
Message-ID: <4a4b1c5c-e4a7-0cf1-623e-672973fc1f0a@hisilicon.com> (raw)
In-Reply-To: <1623209801-1709-1-git-send-email-zhangfei.gao@linaro.org>
On 2021/6/9 11:36, Zhangfei Gao wrote:
> HiSilicon KunPeng920 and KunPeng930 have devices appear as PCI but are
> actually on the AMBA bus. These fake PCI devices have PASID capability
> though not supporting TLP.
>
> Add a quirk to set pasid_no_tlp and dma-can-stall for these devices.
>
> Jean's dma-can-stall patchset has been accepted
> https://lore.kernel.org/linux-iommu/162314710744.3707892.6632600736379822229.b4-ty@kernel.org/
>
> v4:
> Applied to Linux 5.13-rc2, and build successfully with only these three patches.
>
> v3:
> https://lore.kernel.org/linux-pci/1615258837-12189-1-git-send-email-zhangfei.gao@linaro.org/
> Rebase to Linux 5.12-rc1
> Change commit msg adding:
> Property dma-can-stall depends on patchset
> https://lore.kernel.org/linux-iommu/20210302092644.2553014-1-jean-philippe@linaro.org/
>
> By the way the patchset can directly applied on 5.12-rc1 and build successfully though
> without the dependent patchset.
>
> v2:
> Add a new pci_dev bit: pasid_no_tlp, suggested by Bjorn
> "Apparently these devices have a PASID capability. I think you should
> add a new pci_dev bit that is specific to this idea of "PASID works
> without TLP prefixes" and then change pci_enable_pasid() to look at
> that bit as well as eetlp_prefix_path."
> https://lore.kernel.org/linux-pci/20210112170230.GA1838341@bjorn-Precision-5520/
>
> Zhangfei Gao (3):
> PCI: PASID can be enabled without TLP prefix
> PCI: Add a quirk to set pasid_no_tlp for HiSilicon chips
> PCI: Set dma-can-stall for HiSilicon chips
>
> drivers/pci/ats.c | 2 +-
> drivers/pci/quirks.c | 27 +++++++++++++++++++++++++++
> include/linux/pci.h | 1 +
> 3 files changed, 29 insertions(+), 1 deletion(-)
>
Hi Bjorn,
Could you take this series for coming v5.14-rc1? With this series, HiSilicon accelerators(ZIP/SEC/HPRE)
will work in mainline, as the related SMMU series had been accepted.
Best,
Zhou
prev parent reply other threads:[~2021-06-28 1:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-09 3:36 [PATCH v4 0/3] PCI: Add a quirk to enable SVA for HiSilicon chip Zhangfei Gao
2021-06-09 3:36 ` [PATCH v4 1/3] PCI: PASID can be enabled without TLP prefix Zhangfei Gao
2021-06-09 3:36 ` [PATCH v4 2/3] PCI: Add a quirk to set pasid_no_tlp for HiSilicon chips Zhangfei Gao
2021-06-09 3:36 ` [PATCH v4 3/3] PCI: Set dma-can-stall " Zhangfei Gao
2021-06-16 8:42 ` [PATCH v4 0/3] PCI: Add a quirk to enable SVA for HiSilicon chip Zhangfei Gao
2021-06-28 1:52 ` Zhou Wang [this message]
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=4a4b1c5c-e4a7-0cf1-623e-672973fc1f0a@hisilicon.com \
--to=wangzhou1@hisilicon.com \
--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=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;
as well as URLs for NNTP newsgroup(s).