`plymouth.use-simpledrm` should be automatically applied where possible
As it stands today plymouth often starts really late in the boot process because it waits until amdgpu or i915 get loaded. Distros like Fedora and Ubuntu ship simpledrm and that's not viewed as a candidate for plymouth.
I understand that plymouth.use-simpledrm
can be used to workaround this, but simpledrm has some limitations in the information it can get (like rotation data).
I was wondering if some heuristics could be considered to opt plymouth into simpledrm in cases it's going to be known to work well. For example we could look and see if any sensor data is available showing rotation at the time of bootup. If no sensors offer rotation, it's very unlikely the display could be rotated.
What other limitations are there? Could some other heuristics be used? For example if no EDID was specified on the kernel command line and it's eDP we should be running at preferred resolution of the eDP very likely.