The counterpart of sfp_fdt(4). Firmware describes the cage the same way a
device tree does -- a node with compatible "sff,sfp", carried in _DSD under
_HID "PRP0001" -- but places it where ACPI places an i2c device: in the scope
of the bus its EEPROM answers on, with an I2cSerialBus resource giving the
base page's 7-bit address, 0x50.
So where the FDT front-end has to follow an "i2c-bus" phandle to find its
bus, this one simply has it as a parent, and it can own the bus request
itself rather than borrowing another device on the bus. read_eeprom is then
the same single call as on the FDT side.
Everything above this -- the SFF interface, and a NIC driver's SIOCGI2C
handler -- is shared with the FDT path and learns nothing about which of the
two described the transceiver.
Depends on D60066