Expose Interface Name As D-Bus Property?

[santoshpuranik]

Is it reasonable for mctpd to expose the MCTP interface name (Ex: mctpi2c14) as a D-Bus property (say "Name") under the interface D-Bus object, interface au.com.CodeConstruct.MCTP.Interface1 D-Bus interface?

Our use case here is that we need to write an EM configuration to setup an MCTP interface, but we have nothing to Probe on (No FRU EEPROMs/device tree "eeprom"). I was thinking we could use the MCTP interface itself to probe on, something like:

"Probe": "au.com.CodeConstruct.MCTP.Interface1({'Role': 'BusOwner'})"

And then expose the interface name directly:

    "Exposes": [
        {
            "Address": "0x1d",
            "Interface": $Name,
            "Name": "Blah",
            "Type": "MCTPDevice"
        }

[jk-ozlabs]

Don't you already know the name, as it is present in the object path?

(I'd prefer not to have to extract it from the object path, but didn't the caller know what the interface name was when it initially constructed the object path?)

If it's because the Interface1 object was returned as some sort of enumeration, that sounds like a reasonable addition. We may as well add the ifindex at the same time.