We're a bit puzzled, but we'll try to replicate this.
Somewhere above you reported it returned to LP11 state but for a very short time (perhaps too short), whereas with these settings it's not returning to LP11 state at all when perhaps it should. Which seems paradoxical: it ought to do it if time allows and not otherwise.
Unless transmitting or receiving commands, software should not be interfering with DSI after initialization; it just feeds frames into the DPI/DMA block.
We're aware of several differences with commands -- anything sent by a panel driver before DSI has been started could get dropped on the floor; and this driver doesn't [yet] honour the per-command flag to switch between LP and HS -- though I think you already checked that the start-up sequence looked correct. Does your driver send any commands after start-up?
Somewhere above you reported it returned to LP11 state but for a very short time (perhaps too short), whereas with these settings it's not returning to LP11 state at all when perhaps it should. Which seems paradoxical: it ought to do it if time allows and not otherwise.
Unless transmitting or receiving commands, software should not be interfering with DSI after initialization; it just feeds frames into the DPI/DMA block.
We're aware of several differences with commands -- anything sent by a panel driver before DSI has been started could get dropped on the floor; and this driver doesn't [yet] honour the per-command flag to switch between LP and HS -- though I think you already checked that the start-up sequence looked correct. Does your driver send any commands after start-up?
Statistics: Posted by njh — Fri Jul 26, 2024 12:04 pm