If you have access and a method for saving the produced text file, then this will get all the info:What ioreg command do you use to find this? I'm thinking maybe you could run this on a display model when M5 hits the stores.
Code:
ioreg -fliw0 > ioregall.txt
This one doesn't save any properties - it just gets the list of nodes:
Code:
ioreg -iw0 > ioreg.txt
Then search for DPIn.
This M4 example has three Thunderbolt controllers (one per Thunderbolt port), each with two DisplayPort In Adapters.
Code:
| | +-o acio0@81F00000 <class IORegistryEntry:IOService:AppleARMIODevice>
| | | +-o AppleThunderboltHALType7 <class IORegistryEntry:IOService:AppleThunderboltGenericHAL:AppleThunderboltHALGenericACIO:AppleThunderboltHALType7>
| | | | +-o AppleThunderboltNHIType7 <class IORegistryEntry:IOService:IOThunderboltNHI:AppleThunderboltNHI:AppleThunderboltNHIGenericACIO:AppleThunderboltNHIType7>
| | | | +-o IOThunderboltControllerType7 <class IORegistryEntry:IOService:IOThunderboltController:IOThunderboltControllerGenericACIO:IOThunderboltControllerType7>
| | | | | +-o IOThunderboltPort@5 <class IORegistryEntry:IOService:IOThunderboltNub:IOThunderboltPort>
| | | | | | +-o AppleThunderboltDPInAdapterOS2 <class IORegistryEntry:IOService:IOThunderboltTunnelDriver:AppleThunderboltDPAdapterFamilyBase:AppleThunderboltDPInAdapterBase:AppleThunderboltDPInAdapterCM:AppleThunderboltDPInAdapterOS:AppleThunderboltDPInAdapterOS2>
| | | | | +-o IOThunderboltPort@6 <class IORegistryEntry:IOService:IOThunderboltNub:IOThunderboltPort>
| | | | | +-o AppleThunderboltDPInAdapterOS2 <class IORegistryEntry:IOService:IOThunderboltTunnelDriver:AppleThunderboltDPAdapterFamilyBase:AppleThunderboltDPInAdapterBase:AppleThunderboltDPInAdapterCM:AppleThunderboltDPInAdapterOS:AppleThunderboltDPInAdapterOS2>
| | +-o acio1@89F00000 <class IORegistryEntry:IOService:AppleARMIODevice>
-- same as above
| | +-o acio2@91F00000 <class IORegistryEntry:IOService:AppleARMIODevice>
-- same as above