Milk-V Jupiter

[geerlingguy]

Basic information

• Board URL (official): https://milkv.io/jupiter
• Board purchased from: (Provided by Milk-V)
• Board purchase date: July 17, 2024
• Board specs (as tested): M1 @ 1.8GHz, 16GB RAM
• Board price (as tested): $115 (pre-order pricing)

Linux/system information

# output of `screenfetch`
root@milkv-jupiter:~# screenfetch
                          ./+o+-       root@milkv-jupiter
                  yyyyy- -yyyyyy+      OS: Ubuntu 23.10 mantic
               ://+//////-yyyyyyo      Kernel: riscv64 Linux 6.1.15
           .++ .:/++++++/-.+sss/`      Uptime: 11m
         .:++o:  /++++++++/:--:/-      Packages: 1667
        o:+o+:++.`..```.-/oo+++++/     Shell: bash 5.2.15
       .:+o:+o/.          `+sssoo+/    Disk: 4.1G / 6.1G (71%)
  .++/+:+oo+o:`             /sssooo.   CPU: Spacemit X60 @ 8x 1.8GHz
 /+++//+:`oo+o               /::--:.   GPU: 
 \+/+o+++`o++o               ++////.   RAM: 847MiB / 15771MiB
  .++.o+++oo+:`             /dddhhh.  
       .+.o+oo:.          `oddhhhh+   
        \+.++o+o``-````.:ohdhhhhh+    
         `:o+++ `ohhhhhhhhyo++os:     
           .o:`.syhhhhhhh/.oo++o`     
               /osyyyyyyo++ooo+++/    
                   ````` +oo+++o\:    
                          `oo++.  

# output of `uname -a`
Linux milkv-jupiter 6.1.15 #1.0.8 SMP PREEMPT Tue Jul 16 07:18:48 UTC 2024 riscv64 riscv64 riscv64 GNU/Linux

Benchmark results

CPU

• Geekbench 6: (78 single / 356 multi - https://browser.geekbench.com/v6/cpu/6979805)
• 5.656 Gflops at 0.53 Gflops/W (geerlingguy/top500-benchmark HPL result)

Power

• Idle power draw (at wall): 3.5 W
• Maximum simulated power draw (stress-ng --matrix 0): 8 W
• During Geekbench multicore benchmark: 10 W
• During top500 HPL benchmark: 10.6 W

(Note: Tests were performed using a 12V 8A power adapter. When I switched to a 27W Aergon PWR GaN adapter, idle draw was measured at 10W, and stress-ng --matrix 0 at 10W)

Disk

MakerDisk A1 128GB microSD

Benchmark	Result
iozone 4K random read	11.28 MB/s
iozone 4K random write	3.75 MB/s
iozone 1M random read	74.95 MB/s
iozone 1M random write	49.97 MB/s
iozone 1M sequential read	75.47 MB/s
iozone 1M sequential write	50.40 MB/s

Kioxia XG8 2TB NVMe SSD

Benchmark	Result
iozone 4K random read	43.42 MB/s
iozone 4K random write	80.55 MB/s
iozone 1M random read	314.43 MB/s
iozone 1M random write	345.83 MB/s
iozone 1M sequential read	315.34 MB/s
iozone 1M sequential write	346.40 MB/s

32GB SanDisk eMMC Module V1.2

Benchmark	Result
iozone 4K random read	18.72 MB/s
iozone 4K random write	29.24 MB/s
iozone 1M random read	194.06 MB/s
iozone 1M random write	195.67 MB/s
iozone 1M sequential read	208.09 MB/s
iozone 1M sequential write	193.82 MB/s

wget https://raw.githubusercontent.com/geerlingguy/pi-cluster/master/benchmarks/disk-benchmark.sh
chmod +x disk-benchmark.sh
sudo MOUNT_PATH=/ TEST_SIZE=1g ./disk-benchmark.sh

Run benchmark on any attached storage device (e.g. eMMC, microSD, NVMe, SATA) and add results under an additional heading.

Also consider running PiBenchmarks.com script.

Network

iperf3 results:

Built-in 1 Gbps LAN

• iperf3 -c $SERVER_IP: 939 Mbps
• iperf3 -c $SERVER_IP --reverse: 885 Mbps
• iperf3 -c $SERVER_IP --bidir: 942 Mbps up, 136 Mbps down

Built-in WiFi 6

So far, I have been unable to bring up this interface. See WiFi not working under Ubuntu or Bianbu.

• iperf3 -c $SERVER_IP: 362 Mbps
• iperf3 -c $SERVER_IP --reverse: 313 Mbps
• iperf3 -c $SERVER_IP --bidir: 228 Mbps up, 140 Mbps down

GPU

glmark2-es2-wayland results:

=======================================================
    glmark2 2023.01
=======================================================
    OpenGL Information
    GL_VENDOR:      Imagination Technologies
    GL_RENDERER:    PowerVR B-Series BXE-2-32
    GL_VERSION:     OpenGL ES 3.2 build 23.2@6460340
    Surface Config: buf=32 r=8 g=8 b=8 a=8 depth=24 stencil=8 samples=0
    Surface Size:   800x600 windowed
=======================================================
[build] use-vbo=false: FPS: 300 FrameTime: 3.338 ms
[build] use-vbo=true: FPS: 682 FrameTime: 1.468 ms
[texture] texture-filter=nearest: FPS: 629 FrameTime: 1.591 ms
[texture] texture-filter=linear: FPS: 680 FrameTime: 1.471 ms
[texture] texture-filter=mipmap: FPS: 617 FrameTime: 1.621 ms
[shading] shading=gouraud: FPS: 555 FrameTime: 1.805 ms
[shading] shading=blinn-phong-inf: FPS: 562 FrameTime: 1.782 ms
[shading] shading=phong: FPS: 477 FrameTime: 2.099 ms
[shading] shading=cel: FPS: 461 FrameTime: 2.172 ms
[bump] bump-render=high-poly: FPS: 315 FrameTime: 3.176 ms
[bump] bump-render=normals: FPS: 710 FrameTime: 1.410 ms
[bump] bump-render=height: FPS: 733 FrameTime: 1.365 ms
[effect2d] kernel=0,1,0;1,-4,1;0,1,0;: FPS: 382 FrameTime: 2.623 ms
[effect2d] kernel=1,1,1,1,1;1,1,1,1,1;1,1,1,1,1;: FPS: 137 FrameTime: 7.309 ms
[pulsar] light=false:quads=5:texture=false: FPS: 754 FrameTime: 1.328 ms
[desktop] blur-radius=5:effect=blur:passes=1:separable=true:windows=4: FPS: 144 FrameTime: 6.977 ms
[desktop] effect=shadow:windows=4: FPS: 412 FrameTime: 2.433 ms
[buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 151 FrameTime: 6.631 ms
[buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=subdata: FPS: 154 FrameTime: 6.513 ms
[buffer] columns=200:interleave=true:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 204 FrameTime: 4.912 ms
[ideas] speed=duration: FPS: 308 FrameTime: 3.251 ms
[jellyfish] <default>: FPS: 270 FrameTime: 3.713 ms
[terrain] <default>: FPS: 20 FrameTime: 52.388 ms
[shadow] <default>: FPS: 335 FrameTime: 2.989 ms
[refract] <default>: FPS: 41 FrameTime: 24.497 ms
[conditionals] fragment-steps=0:vertex-steps=0: FPS: 789 FrameTime: 1.268 ms
[conditionals] fragment-steps=5:vertex-steps=0: FPS: 536 FrameTime: 1.869 ms
[conditionals] fragment-steps=0:vertex-steps=5: FPS: 745 FrameTime: 1.343 ms
[function] fragment-complexity=low:fragment-steps=5: FPS: 704 FrameTime: 1.422 ms
[function] fragment-complexity=medium:fragment-steps=5: FPS: 393 FrameTime: 2.550 ms
[loop] fragment-loop=false:fragment-steps=5:vertex-steps=5: FPS: 691 FrameTime: 1.448 ms
[loop] fragment-steps=5:fragment-uniform=false:vertex-steps=5: FPS: 665 FrameTime: 1.506 ms
[loop] fragment-steps=5:fragment-uniform=true:vertex-steps=5: FPS: 643 FrameTime: 1.555 ms
=======================================================
                                  glmark2 Score: 459 
=======================================================

Note: This benchmark requires an active display on the device. Not all devices may be able to run glmark2-es2, so in that case, make a note and move on!

TODO: See this issue for discussion about a full suite of standardized GPU benchmarks.

Memory

tinymembench results:

Click to expand memory benchmark result

tinymembench v0.4.10 (simple benchmark for memory throughput and latency)

==========================================================================
== Memory bandwidth tests                                               ==
==                                                                      ==
== Note 1: 1MB = 1000000 bytes                                          ==
== Note 2: Results for 'copy' tests show how many bytes can be          ==
==         copied per second (adding together read and writen           ==
==         bytes would have provided twice higher numbers)              ==
== Note 3: 2-pass copy means that we are using a small temporary buffer ==
==         to first fetch data into it, and only then write it to the   ==
==         destination (source -> L1 cache, L1 cache -> destination)    ==
== Note 4: If sample standard deviation exceeds 0.1%, it is shown in    ==
==         brackets                                                     ==
==========================================================================

 C copy backwards                                     :   3073.1 MB/s (0.6%)
 C copy backwards (32 byte blocks)                    :    662.7 MB/s
 C copy backwards (64 byte blocks)                    :   3079.1 MB/s (0.6%)
 C copy                                               :   3081.3 MB/s (0.5%)
 C copy prefetched (32 bytes step)                    :   3087.2 MB/s (0.6%)
 C copy prefetched (64 bytes step)                    :   3087.5 MB/s (0.7%)
 C 2-pass copy                                        :   2953.6 MB/s
 C 2-pass copy prefetched (32 bytes step)             :   2947.5 MB/s (0.5%)
 C 2-pass copy prefetched (64 bytes step)             :   2948.0 MB/s (0.4%)
 C fill                                               :   7570.4 MB/s (0.3%)
 C fill (shuffle within 16 byte blocks)               :   7574.7 MB/s (0.4%)
 C fill (shuffle within 32 byte blocks)               :    675.4 MB/s (0.2%)
 C fill (shuffle within 64 byte blocks)               :    675.3 MB/s (0.2%)
 ---
 standard memcpy                                      :   2886.5 MB/s (0.8%)
 standard memset                                      :   7577.1 MB/s (0.5%)

==========================================================================
== Memory latency test                                                  ==
==                                                                      ==
== Average time is measured for random memory accesses in the buffers   ==
== of different sizes. The larger is the buffer, the more significant   ==
== are relative contributions of TLB, L1/L2 cache misses and SDRAM      ==
== accesses. For extremely large buffer sizes we are expecting to see   ==
== page table walk with several requests to SDRAM for almost every      ==
== memory access (though 64MiB is not nearly large enough to experience ==
== this effect to its fullest).                                         ==
==                                                                      ==
== Note 1: All the numbers are representing extra time, which needs to  ==
==         be added to L1 cache latency. The cycle timings for L1 cache ==
==         latency can be usually found in the processor documentation. ==
== Note 2: Dual random read means that we are simultaneously performing ==
==         two independent memory accesses at a time. In the case if    ==
==         the memory subsystem can't handle multiple outstanding       ==
==         requests, dual random read has the same timings as two       ==
==         single reads performed one after another.                    ==
==========================================================================

block size : single random read / dual random read
      1024 :    0.1 ns          /     0.1 ns 
      2048 :    0.1 ns          /     0.1 ns 
      4096 :    0.1 ns          /     0.1 ns 
      8192 :    0.1 ns          /     0.1 ns 
     16384 :    0.1 ns          /     0.1 ns 
     32768 :    0.2 ns          /     0.2 ns 
     65536 :    9.3 ns          /    14.3 ns 
    131072 :   15.9 ns          /    21.2 ns 
    262144 :   19.3 ns          /    23.8 ns 
    524288 :   38.4 ns          /    52.5 ns 
   1048576 :  119.4 ns          /   175.0 ns 
   2097152 :  169.3 ns          /   221.4 ns 
   4194304 :  198.2 ns          /   241.2 ns 
   8388608 :  223.5 ns          /   268.5 ns 
  16777216 :  238.2 ns          /   288.6 ns 
  33554432 :  248.7 ns          /   306.2 ns 
  67108864 :  281.1 ns          /   361.7 ns 

sbc-bench results

Run sbc-bench and paste a link to the results here: ThomasKaiser/sbc-bench#96 / https://0x0.st/X904.bin

Phoronix Test Suite

Results from pi-general-benchmark.sh:

• pts/encode-mp3: N/A (wouldn't install)
• pts/x264 4K: N/A (wouldn't install)
• pts/x264 1080p: N/A (wouldn't install)
• pts/phpbench: 89706
• pts/build-linux-kernel (defconfig): 3345.196 sec

[geerlingguy]

After speaking with Milk-V about some of their RISC-V boards, they wanted to send over a Jupiter for me to test. I plan on running it through my usual tests, and also seeing how the board behaves as a regular ol' PC ITX board, testing front panel connectors, USB 3.0 and other IO. It also comes with a heatsink/fan (a pretty small one, mind you), and an IO shield. I haven't unboxed it fully but will hopefully do that tomorrow or Monday!

[geerlingguy]

First test round will be with https://github.com/milkv-jupiter/jupiter-ubuntu-build/releases - Ubuntu 23.10 desktop release 1.0.8. I will flash it to a microSD card first.

First challenge: I can't determine what pins to use for a front panel power button connection on the F_PANEL header, so I opened the linked issue to see if someone can help with that.

I assume the board will just power on like a typical SBC when I apply DC_IN or PD power via the Type C port (according to their documentation. I will probably power the board with 12VDC for now, but may attach an ATX power supply to test that out too. [Edit: The board doesn't power on automatically, so I will need to figure out how to press the power button on the F_PANEL header I think.]

[geerlingguy]

Apparently there's some amount of standardization in the world... got this from Milk-V:

It does seem to boot up immediately upon getting power. To hard-power-off, hold down the power button for 5 seconds (or maybe 6 or so). To boot up again, press the power button for 1-2s.

[geerlingguy]

I can boot and log in via serial console; it also has an Ethernet connection, at 1 Gbps, and I can access it via UART or SSH, but so far I don't have an HDMI output working. xrandr gives me 'Couldn't open display'. I will try another HDMI monitor and see if that works. For some reason a lot of RISC-V boards don't seem to like my HP EliteDisplay E231.

[geerlingguy]

The docs for the Jupiter describe using gparted to expand the SD partition, but I elected to use the RVSpace guide Extend Partition on SD Card or eMMC.

root@milkv-jupiter:~# resize2fs /dev/mmcblk0p6
resize2fs 1.47.0 (5-Feb-2023)
Filesystem at /dev/mmcblk0p6 is mounted on /; on-line resizing required
old_desc_blocks = 1, new_desc_blocks = 15
The filesystem on /dev/mmcblk0p6 is now 30571264 (4k) blocks long.

root@milkv-jupiter:~# df -h
Filesystem      Size  Used Avail Use% Mounted on
tmpfs           1.6G  6.3M  1.6G   1% /run
/dev/mmcblk0p6  115G  4.0G  106G   4% /
tmpfs           7.8G     0  7.8G   0% /dev/shm
tmpfs           5.0M   12K  5.0M   1% /run/lock
/dev/mmcblk0p5  224M   27M  180M  13% /boot
tmpfs           1.6G  112K  1.6G   1% /run/user/120
tmpfs           1.6G   64K  1.6G   1% /run/user/0

[geerlingguy]

I was originally wondering if the fan or fan connector was dead, but no—just the heatsink seems to be good enough for 99% of the time—the fan will only spin up deep into a multicore test, and briefly at that. It's noticeable but not annoying the few times it does spin up.

[geerlingguy]

I'm able to get the HDMI output to feed into OBS through my CamLink 4K, so it's probably an incompatibility with that HP monitor:

[geerlingguy]

So far I'm unable to activate Bluetooth or see any WiFi settings, and I'm wondering if that's due to the Ubuntu image not including drivers or something. Need to do a little more exploration there.

I just noticed there's a newer release of the 23.10 desktop: https://github.com/milkv-jupiter/jupiter-ubuntu-build/releases/tag/v1.0.9

(As well as Bianbu). Fedora also has a RISC-V task force building images for the Jupiter—see the downloadable images here: https://mirror.iscas.ac.cn/fedora-riscv/dl/Milk-V/Jupiter/images/latest/

[geerlingguy]

Notes on Bianbu OS minimal install:

• It truly is minimal, doesn't include utilities like nmcli, openssh-server, lsusb, or lspci (have to apt install network-manager rfkill openssh-server usbutils pciutils etc.
• The premade image on GitHub is set to Chinese locale by default, so run sudo dpkg-reconfigure locales and select your language.

As with the Ubuntu image, I'm not seeing the WiFi device, just the two Ethernet ports and a sit0 interface (something to do with IPv6 I think):

root@milkv-jupiter:~# nmcli d
DEVICE  TYPE      STATE      CONNECTION 
end0    ethernet  unmanaged  --         
end1    ethernet  unmanaged  --         
sit0    iptunnel  unmanaged  --         
lo      loopback  unmanaged  --   

Bluetooth looks to be present, at least:

root@milkv-jupiter:~# rfkill
ID TYPE      DEVICE         SOFT      HARD
 0 bluetooth spacemit-bt blocked unblocked

I opened the issue on the Milk-V community forum WiFi under Ubuntu not working.

[geerlingguy]

I'm also re-running Geekbench 6 under the Bianbu minimal install to see if there's any difference between it and the Ubuntu release.

[Edit: Heh, identical result, 78/356.]

[geerlingguy]

I've also asked on the Community forum about the SATAPWR1 and 2 headers, which look like 4-pin ATX fan connectors, but I'm scared to plug in a fan to one of them in case the pinout is incorrect :)

It would be nice to provide a couple fan headers so I can run a case fan off the ITX board, but I'm not sure if those are wired up to any PWM controls.

[geerlingguy]

Fedora 40 with Gnome runs stable, if slow. No GPU drivers present in that build, it seems—everything goes to the CPU and runs a bit slowish. YouTube can kinda play back at 240p, whereas on Bianbu and Ubuntu I can hit 720p passably.

I'm also not able to enable Bluetooth (which seems to be present) or WiFi (which is not, like on the other OSes).

[geerlingguy]

I don't seem to be getting any GPU acceleration under Ubuntu or Bianbu, at least not by default... it seems like they should both be able to render a lot better using the built-in GPU (see Banana Pi BPI-F3 here).

[geerlingguy]

Kioxia XG8 over PCIe:

0001:01:00.0 Non-Volatile memory controller: KIOXIA Corporation NVMe SSD Controller XG8 (rev 01) (prog-if 02 [NVM Express])
	Subsystem: KIOXIA Corporation Device 0001
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 56
	Region 0: Memory at 90200000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: [80] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [90] MSI: Enable- Count=1/32 Maskable+ 64bit+
		Address: 0000000000000000  Data: 0000
		Masking: 00000000  Pending: 00000000
	Capabilities: [b0] MSI-X: Enable+ Count=65 Masked-
		Vector table: BAR=0 offset=00002000
		PBA: BAR=0 offset=00003000
	Capabilities: [c0] Express (v2) Endpoint, MSI 00
		DevCap:	MaxPayload 256 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited
			ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset+ SlotPowerLimit 0W
		DevCtl:	CorrErr+ NonFatalErr+ FatalErr+ UnsupReq+
			RlxdOrd- ExtTag+ PhantFunc- AuxPwr- NoSnoop- FLReset-
			MaxPayload 128 bytes, MaxReadReq 512 bytes
		DevSta:	CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend-
		LnkCap:	Port #0, Speed 16GT/s, Width x4, ASPM L1, Exit Latency L1 <32us
			ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp+
		LnkCtl:	ASPM Disabled; RCB 64 bytes, Disabled- CommClk+
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 5GT/s (downgraded), Width x1 (downgraded)
			TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
		DevCap2: Completion Timeout: Range ABCD, TimeoutDis+ NROPrPrP- LTR+
			 10BitTagComp+ 10BitTagReq- OBFF Not Supported, ExtFmt+ EETLPPrefix-
			 EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
			 FRS- TPHComp- ExtTPHComp-
			 AtomicOpsCap: 32bit- 64bit- 128bitCAS-
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR+ 10BitTagReq- OBFF Disabled,
			 AtomicOpsCtl: ReqEn-
		LnkCap2: Supported Link Speeds: 2.5-16GT/s, Crosslink- Retimer+ 2Retimers+ DRS-
		LnkCtl2: Target Link Speed: 16GT/s, EnterCompliance- SpeedDis-
			 Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
			 Compliance Preset/De-emphasis: -6dB de-emphasis, 0dB preshoot
		LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete- EqualizationPhase1-
			 EqualizationPhase2- EqualizationPhase3- LinkEqualizationRequest-
			 Retimer- 2Retimers- CrosslinkRes: unsupported
	Capabilities: [100 v2] Advanced Error Reporting
		UESta:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UEMsk:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UESvrt:	DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
		CESta:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr-
		CEMsk:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
		AERCap:	First Error Pointer: 00, ECRCGenCap+ ECRCGenEn- ECRCChkCap+ ECRCChkEn-
			MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
		HeaderLog: 00000000 00000000 00000000 00000000
	Capabilities: [150 v1] Virtual Channel
		Caps:	LPEVC=0 RefClk=100ns PATEntryBits=1
		Arb:	Fixed- WRR32- WRR64- WRR128-
		Ctrl:	ArbSelect=Fixed
		Status:	InProgress-
		VC0:	Caps:	PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
			Arb:	Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
			Ctrl:	Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
			Status:	NegoPending- InProgress-
	Capabilities: [260 v1] Latency Tolerance Reporting
		Max snoop latency: 0ns
		Max no snoop latency: 0ns
	Capabilities: [300 v1] Secondary PCI Express
		LnkCtl3: LnkEquIntrruptEn- PerformEqu-
		LaneErrStat: 0
	Capabilities: [360 v1] Data Link Feature <?>
	Capabilities: [380 v1] Physical Layer 16.0 GT/s <?>
	Capabilities: [400 v1] L1 PM Substates
		L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1- L1_PM_Substates+
			  PortCommonModeRestoreTime=60us PortTPowerOnTime=150us
		L1SubCtl1: PCI-PM_L1.2- PCI-PM_L1.1- ASPM_L1.2- ASPM_L1.1-
			   T_CommonMode=0us LTR1.2_Threshold=0ns
		L1SubCtl2: T_PwrOn=10us
	Capabilities: [470 v1] Lane Margining at the Receiver <?>
	Kernel driver in use: nvme