Re: [PATCH 0/2] edid-decode: ARVR parsers and DisplayID sanity checks

[Hans Verkuil <hverkuil+cisco@kernel.org>]

Hi Yassine,

On 23/01/2026 16:26, HAYOU YASSINE wrote:
> Hi,
> 
> This patch series includes two improvements to edid-decode:
> 
> Patch 1/2: Implements full parsing for DisplayID 2.1 AR/VR data blocks
> - Tag 0x2c (ARVR_HMD): 79-byte block with optics, lens adjustment,
>   field of view, center of projection, and streams per layer fields
> - Tag 0x2d (ARVR_Layer): 20-byte block with HMD identification,
>   layer configuration, lens distortion, and scaling support
> - Includes comprehensive sanity checks for both blocks
> 
> Patch 2/2: Adds validation checks for DisplayID data blocks
> - Tag 0x20 (Product ID): Validates payload length, week range, and model year
> - Tag 0x21 (Display Parameters v2): Validates pixel format, chromaticity
>   coordinates, luminance information, and gamma EOTF range
> - Tag 0x22 (Type VII Timing): Validates pixel clock max, image dimensions max,
>   and negative blanking periods
> - Tag 0x24 (Type IX Timing): Validates image dimensions max and refresh rate max
> - Tag 0x25 (Dynamic Video Timing Range Limits): Validates pixel clock and
>   refresh rate ranges with revision-specific limits
> 
> These patches improve edid-decode's ability to parse and validate DisplayID
> data according to the VESA DisplayID Standard Version 2.1a, helping identify
> corrupted or invalid EDID data early and providing better error reporting
> for debugging display issues.
> 
> Please review.

I've been going over these patches, and they look good to me. Nice to see
this implemented.

Do you have an EDID that has the ARVR data blocks? If you do, then that
might be a good one to add to the data directory with example EDIDs.

If possible, I'd like to check the output with such an EDID first before I commit
the first patch.

Regards,

	Hans

> 
> Thanks,
> Yassine