Signal padding, there happen to be empty/blank pixels sent which make things easier for display controllers when detecting timings, historically those blank pixels were there to give time for CRT electron beams to move to where the next line or frame began.

For BOE panels at 90hz, they receive frames which happen to be 858x1320 pixels in size, with an active area of 800x1280, while SDC panels use frames which are 1128x1312 in size, also with an 800x1280 active area.

So…

for BOE: 858x1320x90 = 101930400; ie a clock of ~101.93MHz; though in reality the panel runs at 102mhz so has a refresh rate of ~90.0615Hz.

and for SDC: 1128x1312x90 = 133194240; so a clock of 133.194mhz; but they run at 133.200MHz instead which gives a refresh rate of ~90.004Hz

Reducing how large of a padding area gets sent may be possible, but without having an SDC panel deck myself I’m not able to test to which degree, if any, that would be possible.

SDC at 90Hz uses ~133MHz of bandwidth while BOE at 90Hz uses ~102MHz of bandwidth; Valve’s MIPI converter seems to begin struggling at roughly ~147-148MHz which is where those numbers come from.

I do not know if SDC can be made to use narrower timings to reduce bandwidth usage or not, and given I currently only have a BOE deck I can not currently test for that.

From everything I have heard, all LE decks have BOE panels. That being said, if you run xrandr --verbose | grep MHz from desktop mode and the first [or only] value you see is close or equal to 102.00MHz you have a BOE panel but if you see a value close or equal to 133.20MHz you have an SDC panel