On 21/09/25(Sun) 10:40, Patrick Wildt wrote:
> Hi,
> 
> I'd like to get some more testing done on the initial SMMUv3 support
> that's in the tree.  I've mostly been testing on the Rockchip RK3588
> but I think this should also affect e.g. Ampere Altra-based systems?
> 
> Please give this diff a go on newer Arm-based machines and check if a
> new smmu device pops up in dmesg, and if it does, if your I/O devices
> still perform the same (or better or worse).
> 
> On Apple devices this diff won't make a difference, on those we have
> apldart(4).
> 
> On QC machines this diff might make the driver try to attach in ACPI
> mode; and possibly panic.  Reports on booting this diff in ACPI mode
> would be highly appreciated.  In FDT mode this should not attach.
> 
> On Ampere Altra I'm expecting it to attach -- and hopefully work fine.

It attaches but doesn't work.  Diff in dmesg below.

I also had to do a cold reboot after testing a kernel with smmu to get
USB detected and working.

--- dmesg.before	Sun Sep 21 12:08:49 2025
+++ dmesg.after	Sun Sep 21 12:12:27 2025
@@ -267,6 +267,12 @@
 acpi0: tables DSDT FACP BERT DBG2 GTDT SPCR EINJ HEST SSDT TPM2 APIC PPTT SLIT SRAT PCCT IORT MCFG BDAT
 acpi0: wakeup devices
 acpiiort0 at acpi0
+smmu0 at acpiiort0 addr 0x33ffe0000000/0x20000
+smmu1 at acpiiort0 addr 0x37ffe0000000/0x20000
+smmu2 at acpiiort0 addr 0x3fffe0000000/0x20000
+smmu3 at acpiiort0 addr 0x23ffe0000000/0x20000
+smmu4 at acpiiort0 addr 0x2bffe0000000/0x20000
+smmu5 at acpiiort0 addr 0x2fffe0000000/0x20000
 acpimcfg0 at acpi0
 acpimcfg0: addr 0x33fff0000000, bus 0-255
 acpimcfg0: addr 0x37fff0000000, bus 0-255
@@ -390,33 +396,13 @@
 ppb13 at pci15 dev 7 function 0 "Ampere Altra PCIe" rev 0x04: irq 156
 pci19 at ppb13 bus 4
 nvme0 at pci19 dev 0 function 0 "Samsung SM981/PM981" rev 0x00: msix, NVMe 1.3
-nvme0: Samsung SSD 970 EVO Plus 1TB, firmware 2B2QEXM7, serial S4EWNX0W512994M
-scsibus0 at nvme0: 2 targets, initiator 0
-sd0 at scsibus0 targ 1 lun 0: <NVMe, Samsung SSD 970, 2B2Q>
-sd0: 953869MB, 512 bytes/sector, 1953525168 sectors
-uhub1 at uhub0 port 4 configuration 1 interface 0 "Microchip USB7206 Smart Hub" rev 3.20/6.25 addr 2
-uhub2 at uhub0 port 8 configuration 1 interface 0 "Microchip USB4206 Smart Hub" rev 2.10/6.25 addr 3
-bwfm0 at uhub2 port 3 configuration 1 interface 0 "Broadcom Remote Download Wireless Adapter" rev 2.00/0.01 addr 4
-uhub3 at uhub2 port 4 configuration 1 interface 0 "American Megatrends Inc. Virtual Hub" rev 2.00/1.00 addr 5
-uhidev0 at uhub3 port 3 configuration 1 interface 0 "American Megatrends Inc. Virtual Keyboard and Mouse" rev 1.10/1.00 addr 6
-uhidev0: iclass 3/1
-ukbd0 at uhidev0: 8 variable keys, 6 key codes
-wskbd0 at ukbd0 mux 1
-uhidev1 at uhub3 port 3 configuration 1 interface 1 "American Megatrends Inc. Virtual Keyboard and Mouse" rev 1.10/1.00 addr 6
-uhidev1: iclass 3/1
-ums0 at uhidev1: 3 buttons, Z dir
-wsmouse0 at ums0 mux 0
-uaudio0 at uhub2 port 5 configuration 1 interface 2 "Microchip Tech USB2 Controller Hub" rev 2.01/6.25 addr 7
-uaudio0: class v1, high-speed, sync, channels: 2 play, 2 rec, 4 ctls
-audio0 at uaudio0
-ugen0 at uhub2 port 5 configuration 1 "Microchip Tech USB2 Controller Hub" rev 2.01/6.25 addr 7
+nvme0: , firmware , serial
+scsibus0 at nvme0: 1 targets, initiator 0
+uhub0: device problem, disabling port 4
+uhub0: device problem, disabling port 8
 vscsi0 at root
 scsibus1 at vscsi0: 256 targets
 softraid0 at root
 scsibus2 at softraid0: 256 targets
-root on sd0a (9dcf66f5b05cac34.a) swap on sd0b dump on sd0b
-simplefb0 at mainbus0: 1024x768, 32bpp
-wsdisplay0 at simplefb0 mux 1
-wskbd0: connecting to wsdisplay0
-wsdisplay0: screen 0-5 added (std, vt100 emulation)
-bwfm0: address d4:7b:b0:7a:22:a0
+root device:
+