NvDisplay Architecture Platform Restrictions

The NvDisplay architecture on NVIDIA DriveOS™ Thor platforms is subject to the following operational constraints and usage requirements:

- Single Client Limitation: Only one NvDisplay client process can be active at any given time on DriveOS Thor platforms. Multiple concurrent NvDisplay client sessions are not supported.

- DisplayPort-to-HDMI Compatibility: Passive DisplayPort-to-HDMI (DP++) cables, dongles, or adapters are not supported on DriveOS. Only active conversion solutions are permitted for DP-to-HDMI connectivity.

- Overlay Submission Requirements: For surround-view camera use cases, the DriveOS client must aggregate all overlays (either four or two, depending on configuration) and submit them to NvDisplay simultaneously.

- Delayed Frame Detection: For use cases involving delayed-frame detection (measuring latency between frame submission and scan-out), the DriveOS client must provide a valid and permissible latency threshold value.

- Postfence Syncpoint Handling: DriveOS clients receiving a Postfence Syncpoint must not modify, duplicate, or share the Syncpoint with any other process or entity.

- Prefence Syncpoint Signaling: DriveOS clients utilizing Syncpoints for flip requests (Prefence Syncpoints) must signal these Syncpoints within the predefined time window to ensure that the corresponding flip operation is processed successfully.