Rob Herring writes:
> The expected stride calculation is completely wrong. It should
> ultimately be multiplying cpp and width rather than dividing. The width
> also needs to be aligned to the tiling width first before converting to
> stride bytes.
>
> The whole stride check here is possibly poin
The expected stride calculation is completely wrong. It should
ultimately be multiplying cpp and width rather than dividing. The width
also needs to be aligned to the tiling width first before converting to
stride bytes.
The whole stride check here is possibly pointless. Any buffers which
were all
