Hi, I noticed that recent codec driver additions, such as hantro, meson/vdec, mtk, used the multi-planar API (mplane) instead of the single-planar API. Is there a preference for moving towards mplane? Also I noticed that v4l-utils has a plugin that seamlessly adapts mplane devices to work with single-planar API calls, but there isn't one the other way around. Would that be something worthwhile working on? To me it seems having one central adapter is better than having applications try to use both APIs, though some such as FFmpeg already do so. My interest in this is trying to get Chromium's v4l2 video decode accelerator to work on the Raspberry Pi 3 with their downstream kernel, which has the bcm2835-v4l2 driver. It would also benefit other platforms that have a stateful VPU, such as Amlogic (meson) or Mediatek SoCs. Chromium's code uses MPLANE exclusively, and it's geared towards ChromeOS, not standard Linux, but still it might be interesting to get it to work. There's also the v4l2 slice video decode accelerator which uses the request API which has the same issue, but lets not get ahead of ourselves. Regards ChenYu
