From: Marcin Wojtas <mw@semihalf.com>
To: Denis Odintsov <d.odintsov@traviangames.com>
Cc: Tomasz Nowicki <tn@semihalf.com>,
"will@kernel.org" <will@kernel.org>,
"robin.murphy@arm.com" <robin.murphy@arm.com>,
"joro@8bytes.org" <joro@8bytes.org>,
"gregory.clement@bootlin.com" <gregory.clement@bootlin.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"hannah@marvell.com" <hannah@marvell.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"nadavh@marvell.com" <nadavh@marvell.com>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v4 0/4] Add system mmu support for Armada-806
Date: Wed, 7 Oct 2020 15:55:09 +0200 [thread overview]
Message-ID: <CAPv3WKe6jF5bMX-f3MacaOaOTVd_1ypZopm3uOynt4KL-VNQDw@mail.gmail.com> (raw)
In-Reply-To: <517BB937-1F18-4CCF-81BF-11777BB99779@traviangames.com>
Hi Denis,
Thank you for your report.
wt., 6 paź 2020 o 17:17 Denis Odintsov <d.odintsov@traviangames.com> napisał(a):
>
> Hi,
>
> > Am 15.07.2020 um 09:06 schrieb Tomasz Nowicki <tn@semihalf.com>:
> >
> > The series is meant to support SMMU for AP806 and a workaround
> > for accessing ARM SMMU 64bit registers is the gist of it.
> >
> > For the record, AP-806 can't access SMMU registers with 64bit width.
> > This patches split the readq/writeq into two 32bit accesses instead
> > and update DT bindings.
> >
> > The series was successfully tested on a vanilla v5.8-rc3 kernel and
> > Intel e1000e PCIe NIC. The same for platform devices like SATA and USB.
> >
> > For reference, previous versions are listed below:
> > V1: https://lkml.org/lkml/2018/10/15/373
> > V2: https://lkml.org/lkml/2019/7/11/426
> > V3: https://lkml.org/lkml/2020/7/2/1114
> >
>
> 1) After enabling SMMU on Armada 8040, and ARM_SMMU_DISABLE_BYPASS_BY_DEFAUL=y by default in kernel since 954a03be033c7cef80ddc232e7cbdb17df735663,
> internal eMMC is prevented from being initialised (as there is no iommus property for ap_sdhci0)
> Disabling "Disable bypass by default" make it work, but the patch highly suggest doing it properly.
> I wasn't able to find correct path for ap_sdhci for iommus in any publicly available documentation,
> would be highly appreciated addressed properly, thank you!
According to my knowledge and the docs AP IO devices cannot be
virtualized, only ones connected via CP110/CP115. We'd need to check
what should be done in such configuration and get back to you.
>
> 2) Second issue I got (btw I have ClearFog GT 8k armada-8040 based board) is mpci ath10k card.
> It is found, it is enumerated, it is visible in lspci, but it fails to be initialised. Here is the log:
>
> [ 1.743754] armada8k-pcie f2600000.pcie: host bridge /cp0/pcie@f2600000 ranges:
> [ 1.751116] armada8k-pcie f2600000.pcie: MEM 0x00f6000000..0x00f6efffff -> 0x00f6000000
> [ 1.964690] armada8k-pcie f2600000.pcie: Link up
> [ 1.969379] armada8k-pcie f2600000.pcie: PCI host bridge to bus 0000:00
> [ 1.976026] pci_bus 0000:00: root bus resource [bus 00-ff]
> [ 1.981537] pci_bus 0000:00: root bus resource [mem 0xf6000000-0xf6efffff]
> [ 1.988462] pci 0000:00:00.0: [11ab:0110] type 01 class 0x060400
> [ 1.994504] pci 0000:00:00.0: reg 0x10: [mem 0x00000000-0x000fffff]
> [ 2.000843] pci 0000:00:00.0: supports D1 D2
> [ 2.005132] pci 0000:00:00.0: PME# supported from D0 D1 D3hot
> [ 2.011853] pci 0000:01:00.0: [168c:003c] type 00 class 0x028000
> [ 2.018001] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x001fffff 64bit]
> [ 2.025002] pci 0000:01:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref]
> [ 2.032111] pci 0000:01:00.0: supports D1 D2
> [ 2.049409] pci 0000:00:00.0: BAR 14: assigned [mem 0xf6000000-0xf61fffff]
> [ 2.056322] pci 0000:00:00.0: BAR 0: assigned [mem 0xf6200000-0xf62fffff]
> [ 2.063142] pci 0000:00:00.0: BAR 15: assigned [mem 0xf6300000-0xf63fffff pref]
> [ 2.070484] pci 0000:01:00.0: BAR 0: assigned [mem 0xf6000000-0xf61fffff 64bit]
> [ 2.077880] pci 0000:01:00.0: BAR 6: assigned [mem 0xf6300000-0xf630ffff pref]
> [ 2.085135] pci 0000:00:00.0: PCI bridge to [bus 01-ff]
> [ 2.090384] pci 0000:00:00.0: bridge window [mem 0xf6000000-0xf61fffff]
> [ 2.097202] pci 0000:00:00.0: bridge window [mem 0xf6300000-0xf63fffff pref]
> [ 2.104539] pcieport 0000:00:00.0: Adding to iommu group 4
> [ 2.110232] pcieport 0000:00:00.0: PME: Signaling with IRQ 38
> [ 2.116141] pcieport 0000:00:00.0: AER: enabled with IRQ 38
> [ 8.131135] ath10k_pci 0000:01:00.0: Adding to iommu group 4
> [ 8.131874] ath10k_pci 0000:01:00.0: enabling device (0000 -> 0002)
> [ 8.132203] ath10k_pci 0000:01:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
>
> up to that point the log is the same as without SMMU enabled, except "Adding to iommu group N" lines, and IRQ being 37
>
> [ 8.221328] ath10k_pci 0000:01:00.0: failed to poke copy engine: -16
> [ 8.313362] ath10k_pci 0000:01:00.0: failed to poke copy engine: -16
> [ 8.409373] ath10k_pci 0000:01:00.0: failed to poke copy engine: -16
> [ 8.553433] ath10k_pci 0000:01:00.0: failed to poke copy engine: -16
> [ 8.641370] ath10k_pci 0000:01:00.0: failed to poke copy engine: -16
> [ 8.737979] ath10k_pci 0000:01:00.0: failed to poke copy engine: -16
> [ 8.807356] ath10k_pci 0000:01:00.0: Failed to get pcie state addr: -16
> [ 8.814032] ath10k_pci 0000:01:00.0: failed to setup init config: -16
> [ 8.820605] ath10k_pci 0000:01:00.0: could not power on hif bus (-16)
> [ 8.827111] ath10k_pci 0000:01:00.0: could not probe fw (-16)
>
> Thank you!
The PCIE was validated when booting from edk2 + using pci-host-generic
driver and standard intel NIC. Not sure if it makes any difference vs
the Designware driver ("marvell,armada8k-pcie"), but we need to
double-check that.
Best regards,
Marcin
>
> > v3 -> v4
> > - call cfg_probe() impl hook a bit earlier which simplifies errata handling
> > - use hi_lo_readq_relaxed() and hi_lo_writeq_relaxed() for register accessors
> > - keep SMMU status disabled by default and enable where possible (DTS changes)
> > - commit logs improvements and other minor fixes
> >
> > Hanna Hawa (1):
> > iommu/arm-smmu: Workaround for Marvell Armada-AP806 SoC erratum
> > #582743
> >
> > Marcin Wojtas (1):
> > arm64: dts: marvell: add SMMU support
> >
> > Tomasz Nowicki (2):
> > iommu/arm-smmu: Call configuration impl hook before consuming features
> > dt-bindings: arm-smmu: add compatible string for Marvell Armada-AP806
> > SMMU-500
> >
> > Documentation/arm64/silicon-errata.rst | 3 ++
> > .../devicetree/bindings/iommu/arm,smmu.yaml | 4 ++
> > arch/arm64/boot/dts/marvell/armada-7040.dtsi | 28 ++++++++++++
> > arch/arm64/boot/dts/marvell/armada-8040.dtsi | 40 +++++++++++++++++
> > arch/arm64/boot/dts/marvell/armada-ap80x.dtsi | 18 ++++++++
> > drivers/iommu/arm-smmu-impl.c | 45 +++++++++++++++++++
> > drivers/iommu/arm-smmu.c | 11 +++--
> > 7 files changed, 145 insertions(+), 4 deletions(-)
> >
> > --
> > 2.17.1
> >
> > _______________________________________________
> > iommu mailing list
> > iommu@lists.linux-foundation.org
> > https://lists.linuxfoundation.org/mailman/listinfo/iommu
> >
>
next prev parent reply other threads:[~2020-10-07 13:55 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 7:06 [PATCH v4 0/4] Add system mmu support for Armada-806 Tomasz Nowicki
2020-07-15 7:06 ` [PATCH v4 1/4] iommu/arm-smmu: Call configuration impl hook before consuming features Tomasz Nowicki
2020-07-15 10:20 ` Robin Murphy
2020-07-15 7:06 ` [PATCH v4 2/4] iommu/arm-smmu: Workaround for Marvell Armada-AP806 SoC erratum #582743 Tomasz Nowicki
2020-07-15 10:32 ` Robin Murphy
2020-07-16 7:24 ` Tomasz Nowicki
2020-07-15 7:06 ` [PATCH v4 3/4] dt-bindings: arm-smmu: add compatible string for Marvell Armada-AP806 SMMU-500 Tomasz Nowicki
2020-07-15 10:36 ` Robin Murphy
2020-07-16 7:27 ` Tomasz Nowicki
2020-07-15 7:06 ` [PATCH v4 4/4] arm64: dts: marvell: add SMMU support Tomasz Nowicki
2020-07-18 21:08 ` Gregory CLEMENT
2020-07-16 12:00 ` [PATCH v4 0/4] Add system mmu support for Armada-806 Will Deacon
2020-07-16 12:02 ` Will Deacon
2020-07-16 12:49 ` Marcin Wojtas
2020-07-18 21:07 ` Gregory CLEMENT
2020-10-06 15:16 ` Denis Odintsov
2020-10-07 13:55 ` Marcin Wojtas [this message]
2020-10-13 13:08 ` Robin Murphy
2020-10-19 11:49 ` Denis Odintsov
2020-10-23 12:19 ` Tomasz Nowicki
2020-10-23 12:33 ` Robin Murphy
2020-10-23 13:05 ` Tomasz Nowicki
2020-10-23 13:26 ` Denis Odintsov
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=CAPv3WKe6jF5bMX-f3MacaOaOTVd_1ypZopm3uOynt4KL-VNQDw@mail.gmail.com \
--to=mw@semihalf.com \
--cc=catalin.marinas@arm.com \
--cc=d.odintsov@traviangames.com \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=hannah@marvell.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nadavh@marvell.com \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.com \
--cc=tn@semihalf.com \
--cc=will@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).