Hi Tiffany, On Tue, Jun 23, 2020 at 10:29 AM Tiffany Lin <tiffany.lin@xxxxxxxxxxxx> wrote: > > On Mon, 2020-06-22 at 21:44 +0900, Alexandre Courbot wrote: > > On Fri, Jun 19, 2020 at 4:26 PM Tiffany Lin <tiffany.lin@xxxxxxxxxxxx> wrote: > > > > > > On Wed, 2020-05-20 at 17:27 +0900, Alexandre Courbot wrote: > > > > Different chips have different supported bitrate ranges. Move the list > > > > of supported formats to the platform data, and split the output and > > > > capture formats into two lists to make it easier to find the default > > > > format for each queue. > > > > > > > > > > Does this patch pass v4l2 compliance test? > > > > This should not change the behavior towards userspace at all (it's > > just moving data around and making it more flexible), so the test > > results should not be affected either. > > > I remember that passing compliance tests is required for upstream. > The tests try to make sure that all V4L2 driver implement interfaces in > the same way. > So user space applications could find/enumerate HW capability. I have confirmed that this CL does not introduce any regression with v4l2-compliance.
