On Tue, Aug 7, 2018 at 4:20 PM Paul Kocialkowski <paul.kocialkowski@xxxxxxxxxxx> wrote: > > Hi, > > On Mon, 2018-08-06 at 23:10 +0900, Tomasz Figa wrote: > > Hi Paul, > > > > On Mon, Aug 6, 2018 at 10:50 PM Paul Kocialkowski > > <paul.kocialkowski@xxxxxxxxxxx> wrote: > > > > > > Hi Hans and thanks for the review! > > > > > > On Sat, 2018-08-04 at 14:18 +0200, Hans Verkuil wrote: > > > > Hi Paul, > > > > > > > > See below for my review comments. Mostly small fry, the main issue I found is > > > > that there is no support for VIDIOC_DECODER_CMD. That's the proper way of > > > > stopping a decoder. Don't rely on the deprecated allow_zero_bytesused field. > > > > > > Mhh, it looks like this was kept around by negligence, but we do expect > > > that streamoff stops the decoder, not a zero bytesused field. > > > > > > Is it still required to implement the V4L2_DEC_CMD_STOP > > > VIDIOC_DECODER_CMD in that case? I read in the doc that this ioctl > > > should be optional. > > > > If I understand correctly that this decoder is stateless, there should > > be no need for any special flush sequence, since a 1:1 relation > > between OUTPUT and CAPTURE buffers is expected, which means that > > userspace can just stop queuing new OUTPUT buffers and keep dequeuing > > CAPTURE buffers until it matches all OUTPUT buffers queued before. > > This is indeed a stateless decoder and I don't have any particular need > for a particular stop command indeed, since flushing remaining buffers > when stopping is already implemented at streamoff time. > Do you mean implemented in user space or the driver? Obviously the latter is against the API specification, since VIDIOC_STREAMOFF is expected to instantly stop any pending hardware operations and gracefully discard any queued buffers or processing results. > > By the way, I guess we will also need some documentation for the > > stateless codec interface. Do you or Maxime (who sent the H264 part) > > have any plans to work on it? We have some internal documents, which > > should be convertible to rst using pandoc, but we might need some help > > with updating to latest request API and further editing. Alexandre > > (moved from Cc to To) is going to be looking into this. > > As far as I'm concerned, I am interested in contributing to this > documentation although our priorities for the Allwinner VPU effort are > currently focused on H265 support. This might mean that my contributions > to this documentation will be made on a best-effort basis (as opposed to > during the workday). Either way, if someone was to come up with an > initial draft, I'd be happy to review it! I've talked with Alex and he should be able to convert our internal document and post it as the initial draft RFC. Help with review will be definitely appreciated, thanks! Note that we shouldn't repeat the same mistake as with stateful codecs and allow merging drivers without the API being specified. That led to drivers doing this their own ways and having to account for those quirks in the stateful codec API specification we're working on right now. Best regards, Tomasz -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
