Indeed, and it continues to be a problem on 4.16. I'm guessing something about moving from drm_kms_firmware.edid_firmware to drm.edid_firmware broke this. Maybe this should be reported upstream?