This seems similar to the problem I have, also the same fails with v4l2 compliance. @ShaneCCC, do you know if we could have any other verified and working driver code which deals with yuv data as reference so that we can check if our device trees and driver code are correct?
Link to my forum post for reference in case any information there is helpful for you @nkpyq