> -----Original Message----- > From: Nicolas Dufresne [mailto:nicolas@xxxxxxxxxxxx] > Sent: Saturday, January 22, 2022 6:25 AM > To: Ming Qian <ming.qian@xxxxxxx>; mchehab@xxxxxxxxxx; > shawnguo@xxxxxxxxxx; robh+dt@xxxxxxxxxx; s.hauer@xxxxxxxxxxxxxx > Cc: hverkuil-cisco@xxxxxxxxx; kernel@xxxxxxxxxxxxxx; festevam@xxxxxxxxx; > dl-linux-imx <linux-imx@xxxxxxx>; linux-media@xxxxxxxxxxxxxxx; > linux-kernel@xxxxxxxxxxxxxxx; devicetree@xxxxxxxxxxxxxxx; > linux-arm-kernel@xxxxxxxxxxxxxxxxxxx > Subject: Re: [EXT] Re: [PATCH v8 04/15] media:Add v4l2 event codec_error and > skip > > Caution: EXT Email > > Le jeudi 13 janvier 2022 à 07:18 +0000, Ming Qian a écrit : > > Hi Nicolas, > > > > I have question about skip event or similar concepts. > > If the client control the input frame count, and it won't queue any more > frames unless some frame is decoded. > > But after seek, There is no requirement to begin queuing coded data starting > exactly from a resume point (e.g. SPS or a keyframe). Any queued OUTPUT > buffers will be processed and returned to the client until a suitable resume > point is found. While looking for a resume point, the decoder should not > produce any decoded frames into CAPTURE buffers. > > > > So client may have queued some frames but without any resume point, in > this case the decoder won't produce any decoded frames into CAPTURE buffers, > and the client won't queue frames into output buffers. This creates some kind > of deadlock. > > > > In our previous solution, we send skip event to client to tell it that some > frame is skipped instead of decoded, then the client can continue to queue > frames. > > But the skip event is flawed, so we need some solution to resolve it. > > 1. decoder can produce an empty buffer with V4L2_BUF_FLAG_SKIPPED (or > V4L2_BUF_FLAG_ERROR) as you advised, but this seems to conflict with the > above description in specification. > > 2. Define a notification mechanism to notify the client > > > > Can you give some advice? This constraint of frame depth is common on > > android > > Without going against the spec, you can as of today pop a capture buffer and > mark it done with error. As it has nothing valid in it, I would also set the > payload size to 0. > > So I'd say, for every unique input timestamp, that didn't yield a frame (skipped), > pop a capture buffer, copy the timestamp, set the payload size to 0 and set it > as done with error. > > I'm not sure though if we that we can specify this, as I'm not sure this is > possible with all the existing HW. I must admit, I don't myself had to deal with > that issue as I'm not using a dummy framework. In GStreamer, we take care of > locating the next sync point. So unless there was an error in the framework, > this case does not exist for us. > Hi Nicolas, If the decoder can detect the output buffer that may trigger a error, is it better setting error flag on the output buffer, but without producing an empty capture buffer with error flag set?, or we should return both output and capture buffer with error flag set? As I can see the following description in spec: if the decoder is able to precisely report the OUTPUT buffer that triggered the error, such buffer will be returned with the V4L2_BUF_FLAG_ERROR flag set. > > > > Ming > > > > > > > > + * - ``V4L2_EVENT_SKIP`` > > > > > > + - 8 > > > > > > + - This event is triggered when one frame is decoded, > > > > > > + but it won't > > > > > > be > > > > > outputed > > > > > > + to the display. So the application can't get this frame, > > > > > > + and the > > > > > > input > > > > > frame count > > > > > > + is dismatch with the output frame count. And this evevt > > > > > > + is telling > > > > > > the > > > > > client to > > > > > > + handle this case. > > > > > > > > > > Similar to my previous comment, this event is flawed, since > > > > > userspace cannot know were the skip is located in the queued > > > > > buffers. Currently, all decoders are mandated to support > > > > > V4L2_BUF_FLAG_TIMESTAMP_COPY. The timestamp must NOT be > > > interpreted > > > > > by the driver and must be reproduce as-is in the associated > > > > > CAPTURE buffer. It is possible to "garbage" collect skipped > > > > > frames with this method, though tedious. > > > > > > > > > > An alternative, and I think it would be much nicer then this, > > > > > would be to use the v4l2_buffer.sequence counter, and just make > > > > > it skip 1 on skips. Though, the down side is that userspace must > > > > > also know how to reorder frames (a driver job for stateless > > > > > codecs) in order to identify which frame was skipped. So this is > > > > > perhaps not that useful, other then knowing something was skipped in > the past. > > > > > > > > > > A third option would be to introduce V4L2_BUF_FLAG_SKIPPED. This > > > > > way the driver could return an empty payload (bytesused = 0) > > > > > buffer with this flag set, and the proper timestamp properly > > > > > copied. This would let the driver communicate skipped frames in > > > > > real-time. Note that this could break with existing userspace, > > > > > so it would need to be opted-in somehow (a control or some flags). > > > > > > > > Hi Nicolas, > > > > The problem we meet is that userspace doesn't care which frame > > > > is skipped, it just need to know that there are a frame is > > > > skipped, the driver should promise the input frame count is equals > > > > to the output frame > > > count. > > > > Your first method is possible in theory, but we find the > > > > timestamp may be unreliable, we meet many timestamp issues that > > > > userspace may enqueue invalid timestamp or repeated timestamp and > > > > so on, so we can't > > > accept this solution. > > > > > > The driver should not interpret the provided timestamp, so it should > > > not be able to say if the timestamp is valid or not, this is not the driver's > task. > > > > > > The driver task is to match the timestamp to the CAPTURE buffer (if > > > that buffer was produced), and reproduce it exactly. > > > > > > > I think your second option is better. And there are only 1 > > > > question, we find some application prefer to use the > > > > V4L2_EVENT_EOS to check the eos, not checking the empty buffer, if > > > > we use this method to check skipped frame, the > > > > > > Checking the empty buffer is a legacy method, only available in > > > Samsung MFC driver. The spec says that the last buffer should be > > > flagged with _LAST, and any further attempt to poll should unblock and > DQBUF return EPIPE. > > > > > > > application should check empty buffer instead of V4L2_EVENT_EOS, > > > > otherwise if the last frame is skipped, the application will miss it. > > > > Of course this is not a problem, it just increases the complexity > > > > of the userspace implementation > > > > > > The EPIPE mechanism covers this issue, which we initially had with > > > the LAST flag. > > > > > > > I don't think your third method is feasible, the reasons are as below > > > > 1. usually the empty payload means eos, and as you > > > > say, it may introduce confusion. > > > > 2. The driver may not have the opportunity to return an > > > > empty payload during decoding, in our driver, driver will pass the > > > > capture buffer to firmware, and when some frame is skipped, the > > > > firmware won't return the buffer, driver may not find an available > > > > capture buffer to return to userspace. > > > > > > > > The requirement is that userspace need to match the input frame > > > > count and output frame count. It doesn't care which frame is > > > > skipped, so the V4L2_EVENT_SKIP is the easiest way for driver and > userspace. > > > > If you think this event is really inappropriate, I prefer to > > > > adopt your second option > > > > > > Please, drop SKIP from you driver and this patchset and fix your > > > draining process handling to follow the spec. The Samsung OMX > > > component is irrelevant to mainline submission, the OMX code should > > > be updated to follow the spec. > > > > > > >
