Niklas, all, > Yes, this is a bug in the rcar-vin driver which is addressed in the Gen3 > patches. However I'm not sure those patches will make it to v4.10, not > much review from the V4L2 side yet (Geert and Sergei have had a few > comments so there will at lest be one more iteration). > > If this is a big blocker I can try and break out the fix from the Gen3 > patch series, but I fear even that series would be quiet large since a > rework on the whole logic is needed to fix this (maybe a workaround can > be figure out to fix this until Gen3 patches are accepted). Let me know > what you think. Thanks for your investigation and heads up! I think we should do the following: * upstream the patches with no issues for v4.10 (Simon started this already) * rebase the demux branch on top of the one you mentioned with the vin fixes and retest * if all works in renesas-drivers, then just wait until vin patches are upstream and then we upstream the hdmi-demux-patches And orthogonal to that: * keep discussing what to do with DFVS (postponed to next week for me because of other duties) Sounds good? Wolfram
Attachment:
signature.asc
Description: PGP signature
