Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp3893668imm; Mon, 20 Aug 2018 06:33:15 -0700 (PDT) X-Google-Smtp-Source: AA+uWPyyZn99PGPkA/i0olZVrycIaXFm0NCpNBX+pjSlgR1Mm45dKPiLxLoSeDph/3gY9RXWxhM0 X-Received: by 2002:a62:990f:: with SMTP id d15-v6mr48171924pfe.162.1534771995417; Mon, 20 Aug 2018 06:33:15 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1534771995; cv=none; d=google.com; s=arc-20160816; b=e6aq3c1p6BtsWfjs5DmrpxZ6omDlhwYsA82XPLzvl9Sy34E2njoNt0SFLuVRaHeJwD 9gh4laCPuXPk1+jprBP2U2S3OYz6SBwbGiuphGQzbBTbTHx6aFfpqv+c4iIb6FZRb49q rsEX6DRvZ6xOBK4SbdD5RQE8mH7ECritpH7aVNVWxI+aOvCsJy1e/lBtC4CxNHzHtVGC 8M690fQCKJugHS1a4zRpenz9r+3rbWU2NOCCwzyahCnxOBnAVqsl1Az7OCspNR9ac8/C d+QG3SDexvqsJ1fmgiiSMUdXo73CRCPFYmTxuuU2RGmVTAMjxo4URozH0YOhWeFSDGxz 3nDg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:date:cc:to:from:subject:message-id :arc-authentication-results; bh=0wov8bdstL2hBKe++WAjdook4v8eTpVr1Fc+s+phYoI=; b=iqACk1Mdn6QuxGouPgVhJYuJ/uzNfl4tI8z6KJs6plm6kNzvlycdBT2dKwx3UatfBT aiLfRe55OY+783kHEOV5xtgbIQMCi4E/fRsXsU36LoEZiWM6GE5eZD9f65snNRhiFXCQ DR8KDfPHBMK3+9ehKzJUrYC/BrkgPnEj0Gg5oUN+/wa8iXuYSKLZANWQhwyvRq3WnNWS TL6gjlUp+EbMqW5lvay/xMEinfoP4lxcluenSswhR73nV9n7SMm3OUefQ+meSsh/HRfB CjLw6z2nlTsw4/k8jQq0I4SkWDlgVUdFfi5qzafmUtclPMN5+ORZ+8DAiQBrfib+U7jC H5Nw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m10-v6si9677860pfe.133.2018.08.20.06.32.59; Mon, 20 Aug 2018 06:33:15 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727135AbeHTQTp (ORCPT + 99 others); Mon, 20 Aug 2018 12:19:45 -0400 Received: from metis.ext.pengutronix.de ([85.220.165.71]:52293 "EHLO metis.ext.pengutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726709AbeHTQTo (ORCPT ); Mon, 20 Aug 2018 12:19:44 -0400 Received: from lupine.hi.pengutronix.de ([2001:67c:670:100:3ad5:47ff:feaf:1a17] helo=lupine) by metis.ext.pengutronix.de with esmtp (Exim 4.89) (envelope-from ) id 1frjqq-0002ZK-GA; Mon, 20 Aug 2018 15:04:08 +0200 Message-ID: <1534770242.5445.13.camel@pengutronix.de> Subject: Re: [PATCH 1/2] media: docs-rst: Document memory-to-memory video decoder interface From: Philipp Zabel To: Tomasz Figa , linux-media@vger.kernel.org Cc: linux-kernel@vger.kernel.org, Stanimir Varbanov , Mauro Carvalho Chehab , Hans Verkuil , Pawel Osciak , Alexandre Courbot , kamil@wypas.org, a.hajda@samsung.com, Kyungmin Park , jtp.park@samsung.com, Tiffany Lin =?UTF-8?Q?=28=E6=9E=97=E6=85=A7=E7=8F=8A=29?= , Andrew-CT Chen =?UTF-8?Q?=28=E9=99=B3=E6=99=BA=E8=BF=AA=29?= , todor.tomov@linaro.org, nicolas@ndufresne.ca, Paul Kocialkowski , Laurent Pinchart , Dave Stevenson , ezequiel@collabora.com Date: Mon, 20 Aug 2018 15:04:02 +0200 In-Reply-To: <20180724140621.59624-2-tfiga@chromium.org> References: <20180724140621.59624-1-tfiga@chromium.org> <20180724140621.59624-2-tfiga@chromium.org> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.22.6-1+deb9u1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 2001:67c:670:100:3ad5:47ff:feaf:1a17 X-SA-Exim-Mail-From: p.zabel@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false X-PTX-Original-Recipient: linux-kernel@vger.kernel.org Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 2018-07-24 at 23:06 +0900, Tomasz Figa wrote: [...] > +Seek > +==== > + > +Seek is controlled by the ``OUTPUT`` queue, as it is the source of > +bitstream data. ``CAPTURE`` queue remains unchanged/unaffected. > + > +1. Stop the ``OUTPUT`` queue to begin the seek sequence via > + :c:func:`VIDIOC_STREAMOFF`. > + > + * **Required fields:** > + > + ``type`` > + a ``V4L2_BUF_TYPE_*`` enum appropriate for ``OUTPUT`` > + > + * The driver must drop all the pending ``OUTPUT`` buffers and they are > + treated as returned to the client (following standard semantics). > + > +2. Restart the ``OUTPUT`` queue via :c:func:`VIDIOC_STREAMON` > + > + * **Required fields:** > + > + ``type`` > + a ``V4L2_BUF_TYPE_*`` enum appropriate for ``OUTPUT`` > + > + * The driver must be put in a state after seek and be ready to > + accept new source bitstream buffers. > + > +3. Start queuing buffers to ``OUTPUT`` queue containing stream data after > + the seek until a suitable resume point is found. > + > + .. note:: > + > + There is no requirement to begin queuing stream starting exactly from > + a resume point (e.g. SPS or a keyframe). The driver must handle any > + data queued and must keep processing the queued buffers until it > + finds a suitable resume point. While looking for a resume point, the I think the definition of a resume point is too vague in this place. Can the driver decide whether or not a keyframe without SPS is a suitable resume point? Or do drivers have to parse and store SPS/PPS if the hardware does not support resuming from a keyframe without sending SPS/PPS again? regards Philipp