<rawoul>
I don't think it's actually correct, since the frame size can vary between 4 and 6
<rawoul>
although you have to be careful not to allocate a static buffer with HDMI_INFOFRAME_SIZE(VENDOR), which might be too small. The STI driver defines HDMI_INFOFRAME_MAX_SIZE 6 for this case
pespin has joined #linux-msm
pespin has quit [Remote host closed the connection]
pespin has joined #linux-msm
<lumag>
rawoul, and also the actual handling and packing of the vendor infoframe
<lumag>
rawoul, I think the define should be removed completely, as not to be misleading. Or renamed to _MIN_SIZE
svarbanov has quit [Remote host closed the connection]
svarbanov has joined #linux-msm
<lumag>
rawoul, just to clarify: I'd like to ensure that we pass proper infoframes, AVI, audio, VS, SPD, etc, It looks like this becomes more important over the time, as monitors start to require them.
<rawoul>
I agree. I remember now why I have this patch in my branch, I had also added vendor infoframe somewhere else and was hit by the exact problem I described: https://pastebin.com/UbVM6hiL
<lumag>
yeah. that's one of the reasons why I wrote that we should remove that define
<lumag>
And another problem with that define is that the HF-VSIF, vendor frame from HDMI 2.0, can take up to 32 +3 bytes