When VEA requests the input buffer, the client calculate the expected buffer size by the width, height, and the pixel format. However, some drivers require the plane buffers should align a certain size of bytes, or extra padding. Thus, currently we just change the width and height as workaround, trying to fulfill the requirement.

The better solution should be: Support the padding of the buffer. When VEA require input buffers from client, it also pass the padding information. Then client generate the buffer with the expected size plus the padding size.