Add pci-aspm-custom property to signalise about the effects

NVMeFix/NVMeFix.cpp

@@ -202,7 +202,9 @@ void NVMeFixPlugin::forceEnableASPM(IOService *device) {
 
 	auto linkControl = pci->configRead16(space, offset);
 	pci->configWrite16(space, offset, (linkControl & ~ASPM_Mask) | ASPM_L1EntryEnabled);
-	DBGLOG(Log::Plugin, "ASPM transition on %s from %X to %X", safeString(device->getName()), linkControl, pci->configRead16(space, offset));
+	auto newLinkControl = pci->configRead16(space, offset);
+	DBGLOG(Log::Plugin, "ASPM transition on %s from %X to %X", safeString(device->getName()), linkControl, newLinkControl);
+	pci->setProperty("pci-aspm-custom", newLinkControl, 32);
 }
 
 void NVMeFixPlugin::handleController(ControllerEntry& entry) {

README.md

@@ -37,6 +37,7 @@ Configuration
 
 `-nvmefaspm` forces ASPM L1 on all the devices. This argument is recommended exclusively for testing purposes,
 as for daily usage one could inject `pci-aspm-default` device property with `<02 00 00 00>` value into the SSD devices and bridge devices they are connected to onboard.
+Updated values will be visible as `pci-aspm-custom` in the affected devices.
 
 Some SSDs misbehave when APST is on. NVMeFix attempts to detect broken motherboard and SSD
 combinations and work around them. Motherboard is detected via IORegistry keys injected by Clover,