Received: by 2002:a05:7412:37c9:b0:e2:908c:2ebd with SMTP id jz9csp1403198rdb; Wed, 20 Sep 2023 08:12:27 -0700 (PDT) X-Google-Smtp-Source: AGHT+IEldtYFREY2HVSvtEt/77V88CUzQ+4clpjRKmqNukn7q7HKPFqouXzFIKhD5JFR92/Op9Lt X-Received: by 2002:a17:902:7443:b0:1c4:4462:f1bd with SMTP id e3-20020a170902744300b001c44462f1bdmr2381086plt.35.1695222746797; Wed, 20 Sep 2023 08:12:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1695222746; cv=none; d=google.com; s=arc-20160816; b=cCFf+RfEhqXKWTP2NFelJ5icdIHh6oce+iHdBxyuGcpwH5h/zCOgWH1uv3Q6HZb/ap yAlcSZXdbZICXM8+6Q8E2plRpHx4L0qYVfLugpXRe9T97XdxL3XUmYNTUndp7eNH2m1r KNYaSBiJKd4C8dE1qc3PtwOkL93IfOz92onT2XFVawnnHobP+VMDcUKfwo9uZHvW82t0 p4teTgKUNAbbV9ls7BLhkf7piX5K1KtX/gxwbJXZbuzlIB+BEjHldq2vnY/0wheqoW7b 0B/wTFLEjzEgYyGUIPmyX64t3J/01KOrWjKJoH8VBERO6Hv6xYlsqc/WpcCBzQsZfVy9 yNUA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:autocrypt :from:references:cc:to:content-language:subject:user-agent :mime-version:date:message-id; bh=8hdLURT4Fx+UunMrsxJVcIfiBdb4Tsejtw6fg644DwA=; fh=nJQBAU5/iZPN7Og1gGbI+wig8XcY4LJPI8AfKwpv5zE=; b=cU2vd3vdofsCy8b97SviIdi67cpqoeUMkac6VSdDV3tdCPadGnlaoC8so1mf/UvI+f cOlE64otDsdN+8c0EeAboWZA0gzb/lwdQgEIIbPGSDbBNyUcugfpxasBySoGOSKDQhrc LkhWXAk+jb+0Qsz5qG5HDaFyxJNKP3FBABp2dVSf47fusMPMp7VTmntcoGaC1BeaacWN u9SmU4u8Ymh2OUbMDa0OnURY52AaLvjdvnrH/r1G9AgJLfBJiJxJ0FUebCMzKNY0nDM/ j1faclGaw072Ymsp0tm8mv/eN8JoqMdkDPPCWMy/HM1lQ1oF6Bjk73F31r5nk94MfZYA EcNQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:3 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=xs4all.nl Return-Path: Received: from lipwig.vger.email (lipwig.vger.email. [2620:137:e000::3:3]) by mx.google.com with ESMTPS id jj13-20020a170903048d00b001c469b401bfsi7095956plb.93.2023.09.20.08.12.26 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 20 Sep 2023 08:12:26 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:3 as permitted sender) client-ip=2620:137:e000::3:3; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:3 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=xs4all.nl Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by lipwig.vger.email (Postfix) with ESMTP id 1D77B826A923; Wed, 20 Sep 2023 07:49:41 -0700 (PDT) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.10 at lipwig.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234636AbjITOth (ORCPT + 99 others); Wed, 20 Sep 2023 10:49:37 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47472 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234330AbjITOtf (ORCPT ); Wed, 20 Sep 2023 10:49:35 -0400 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id ECDCC9E; Wed, 20 Sep 2023 07:49:28 -0700 (PDT) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 5F7C1C433C8; Wed, 20 Sep 2023 14:49:24 +0000 (UTC) Message-ID: Date: Wed, 20 Sep 2023 16:49:22 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v12 1/7] media: v4l2: Add ignore_streaming flag Content-Language: en-US, nl To: Nicolas Dufresne , Sebastian Fricke , Mauro Carvalho Chehab , Nas Chung , Sascha Hauer , Fabio Estevam , Rob Herring , Shawn Guo , Philipp Zabel , Jackson Lee , Krzysztof Kozlowski , NXP Linux Team , Conor Dooley , Pengutronix Kernel Team Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Robert Beckett , linux-media@vger.kernel.org, linux-kernel@vger.kernel.org, kernel@collabora.com, Tomasz Figa References: <20230915-wave5_v12_on_media_master-v12-0-92fc66cd685d@collabora.com> <20230915-wave5_v12_on_media_master-v12-1-92fc66cd685d@collabora.com> <179e88f04257f21b6b723e935231de70415b3301.camel@collabora.com> From: Hans Verkuil Autocrypt: addr=hverkuil@xs4all.nl; keydata= xsFNBFQ84W0BEAC7EF1iL4s3tY8cRTVkJT/297h0Hz0ypA+ByVM4CdU9sN6ua/YoFlr9k0K4 BFUlg7JzJoUuRbKxkYb8mmqOe722j7N3HO8+ofnio5cAP5W0WwDpM0kM84BeHU0aPSTsWiGR yw55SOK2JBSq7hueotWLfJLobMWhQii0Zd83hGT9SIt9uHaHjgwmtTH7MSTIiaY6N14nw2Ud C6Uykc1va0Wqqc2ov5ihgk/2k2SKa02ookQI3e79laOrbZl5BOXNKR9LguuOZdX4XYR3Zi6/ BsJ7pVCK9xkiVf8svlEl94IHb+sa1KrlgGv3fn5xgzDw8Z222TfFceDL/2EzUyTdWc4GaPMC E/c1B4UOle6ZHg02+I8tZicjzj5+yffv1lB5A1btG+AmoZrgf0X2O1B96fqgHx8w9PIpVERN YsmkfxvhfP3MO3oHh8UY1OLKdlKamMneCLk2up1Zlli347KMjHAVjBAiy8qOguKF9k7HOjif JCLYTkggrRiEiE1xg4tblBNj8WGyKH+u/hwwwBqCd/Px2HvhAsJQ7DwuuB3vBAp845BJYUU3 06kRihFqbO0vEt4QmcQDcbWINeZ2zX5TK7QQ91ldHdqJn6MhXulPKcM8tCkdD8YNXXKyKqNl UVqXnarz8m2JCbHgjEkUlAJCNd6m3pfESLZwSWsLYL49R5yxIwARAQABzSFIYW5zIFZlcmt1 aWwgPGh2ZXJrdWlsQHhzNGFsbC5ubD7CwZUEEwECACgFAlQ84W0CGwMFCRLMAwAGCwkIBwMC BhUIAgkKCwQWAgMBAh4BAheAACEJEL0tYUhmFDtMFiEEBSzee8IVBTtonxvKvS1hSGYUO0wT 7w//frEmPBAwu3OdvAk9VDkH7X+7RcFpiuUcJxs3Xl6jpaA+SdwtZra6W1uMrs2RW8eXXiq/ 80HXJtYnal1Y8MKUBoUVhT/+5+KcMyfVQK3VFRHnNxCmC9HZV+qdyxAGwIscUd4hSlweuU6L 6tI7Dls6NzKRSTFbbGNZCRgl8OrF01TBH+CZrcFIoDgpcJA5Pw84mxo+wd2BZjPA4TNyq1od +slSRbDqFug1EqQaMVtUOdgaUgdlmjV0+GfBHoyCGedDE0knv+tRb8v5gNgv7M3hJO3Nrl+O OJVoiW0G6OWVyq92NNCKJeDy8XCB1yHCKpBd4evO2bkJNV9xcgHtLrVqozqxZAiCRKN1elWF 1fyG8KNquqItYedUr+wZZacqW+uzpVr9pZmUqpVCk9s92fzTzDZcGAxnyqkaO2QTgdhPJT2m wpG2UwIKzzi13tmwakY7OAbXm76bGWVZCO3QTHVnNV8ku9wgeMc/ZGSLUT8hMDZlwEsW7u/D qt+NlTKiOIQsSW7u7h3SFm7sMQo03X/taK9PJhS2BhhgnXg8mOa6U+yNaJy+eU0Lf5hEUiDC vDOI5x++LD3pdrJVr/6ZB0Qg3/YzZ0dk+phQ+KlP6HyeO4LG662toMbFbeLcBjcC/ceEclII 90QNEFSZKM6NVloM+NaZRYVO3ApxWkFu+1mrVTXOwU0EVDzhbQEQANzLiI6gHkIhBQKeQaYs p2SSqF9c++9LOy5x6nbQ4s0X3oTKaMGfBZuiKkkU6NnHCSa0Az5ScRWLaRGu1PzjgcVwzl5O sDawR1BtOG/XoPRNB2351PRp++W8TWo2viYYY0uJHKFHML+ku9q0P+NkdTzFGJLP+hn7x0RT DMbhKTHO3H2xJz5TXNE9zTJuIfGAz3ShDpijvzYieY330BzZYfpgvCllDVM5E4XgfF4F/N90 wWKu50fMA01ufwu+99GEwTFVG2az5T9SXd7vfSgRSkzXy7hcnxj4IhOfM6Ts85/BjMeIpeqy TDdsuetBgX9DMMWxMWl7BLeiMzMGrfkJ4tvlof0sVjurXibTibZyfyGR2ricg8iTbHyFaAzX 2uFVoZaPxrp7udDfQ96sfz0hesF9Zi8d7NnNnMYbUmUtaS083L/l2EDKvCIkhSjd48XF+aO8 VhrCfbXWpGRaLcY/gxi2TXRYG9xCa7PINgz9SyO34sL6TeFPSZn4bPQV5O1j85Dj4jBecB1k z2arzwlWWKMZUbR04HTeAuuvYvCKEMnfW3ABzdonh70QdqJbpQGfAF2p4/iCETKWuqefiOYn pR8PqoQA1DYv3t7y9DIN5Jw/8Oj5wOeEybw6vTMB0rrnx+JaXvxeHSlFzHiD6il/ChDDkJ9J /ejCHUQIl40wLSDRABEBAAHCwXwEGAECAA8FAlQ84W0CGwwFCRLMAwAAIQkQvS1hSGYUO0wW IQQFLN57whUFO2ifG8q9LWFIZhQ7TA1WD/9yxJvQrpf6LcNrr8uMlQWCg2iz2q1LGt1Itkuu KaavEF9nqHmoqhSfZeAIKAPn6xuYbGxXDrpN7dXCOH92fscLodZqZtK5FtbLvO572EPfxneY UT7JzDc/5LT9cFFugTMOhq1BG62vUm/F6V91+unyp4dRlyryAeqEuISykhvjZCVHk/woaMZv c1Dm4Uvkv0Ilelt3Pb9J7zhcx6sm5T7v16VceF96jG61bnJ2GFS+QZerZp3PY27XgtPxRxYj AmFUeF486PHx/2Yi4u1rQpIpC5inPxIgR1+ZFvQrAV36SvLFfuMhyCAxV6WBlQc85ArOiQZB Wm7L0repwr7zEJFEkdy8C81WRhMdPvHkAIh3RoY1SGcdB7rB3wCzfYkAuCBqaF7Zgfw8xkad KEiQTexRbM1sc/I8ACpla3N26SfQwrfg6V7TIoweP0RwDrcf5PVvwSWsRQp2LxFCkwnCXOra gYmkrmv0duG1FStpY+IIQn1TOkuXrciTVfZY1cZD0aVxwlxXBnUNZZNslldvXFtndxR0SFat sflovhDxKyhFwXOP0Rv8H378/+14TaykknRBIKEc0+lcr+EMOSUR5eg4aURb8Gc3Uc7fgQ6q UssTXzHPyj1hAyDpfu8DzAwlh4kKFTodxSsKAjI45SLjadSc94/5Gy8645Y1KgBzBPTH7Q== In-Reply-To: <179e88f04257f21b6b723e935231de70415b3301.camel@collabora.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-0.8 required=5.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lipwig.vger.email Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (lipwig.vger.email [0.0.0.0]); Wed, 20 Sep 2023 07:49:41 -0700 (PDT) On 20/09/2023 16:08, Nicolas Dufresne wrote: > cc Tomasz Figa > > Le mercredi 20 septembre 2023 à 14:59 +0200, Hans Verkuil a écrit : >> On 15/09/2023 23:11, Sebastian Fricke wrote: >>> Add a new flag to the `struct v4l2_m2m_dev` to toggle whether a queue >>> must be streaming in order to allow queuing jobs to the ready queue. >>> Currently, both queues (CAPTURE & OUTPUT) must be streaming in order to >>> allow adding new jobs. This behavior limits the usability of M2M for >>> some drivers, as these have to be able, to perform analysis of the >> >> able, to -> able to >> >>> sequence to ensure, that userspace prepares the CAPTURE queue correctly. >> >> ensure, that -> ensure that >> >>> >>> Signed-off-by: Sebastian Fricke >>> Signed-off-by: Nicolas Dufresne >>> --- >>> include/media/v4l2-mem2mem.h | 17 +++++++++++++++++ >>> 1 file changed, 17 insertions(+) >>> >>> diff --git a/include/media/v4l2-mem2mem.h b/include/media/v4l2-mem2mem.h >>> index d6c8eb2b5201..97a48e61e358 100644 >>> --- a/include/media/v4l2-mem2mem.h >>> +++ b/include/media/v4l2-mem2mem.h >>> @@ -57,6 +57,16 @@ struct v4l2_m2m_dev; >>> * @rdy_spinlock: spin lock to protect the struct usage >>> * @num_rdy: number of buffers ready to be processed >>> * @buffered: is the queue buffered? >>> + * @ignore_streaming: Dictates whether the queue must be streaming for a job to >>> + * be queued. >>> + * This is useful, for example, when the driver requires to >>> + * initialize the sequence with a firmware, where only a >>> + * queued OUTPUT queue buffer and STREAMON on the OUTPUT >>> + * queue is required to perform the anlysis of the bitstream >>> + * header. >>> + * This means the driver is responsible for implementing the >>> + * job_ready callback correctly to make sure that requirements >>> + * for actual decoding are met. >> >> This is a bad description and field name. > > I wonder what's your opinion about the buffered one then :-D Even worse :-) I still don't really understand what that does. Patches welcome. > >> >> Basically what this field does is that, if true, the streaming state of the >> capture queue is ignored. So just call it that: ignore_cap_streaming. >> >> And explain that, if true, job_ready() will be called even if the capture >> queue is not streaming, and that that can be used to allow hardware to >> analyze the bitstream header that arrives on the OUTPUT queue. > > Ack. > >> >> Also, doesn't this field belong to struct v4l2_m2m_ctx? It makes no sense >> for the output queue, this is really a configuration for the m2m context as >> a whole. > > Unless we come up with a completely new type of M2M that can behave like a gap > filler (like a video rate m2m), it indeed makes no sense for output. I'm just > illustrating that this is true "now" but someone can come up with valid > expectation. So I agree with you, we can move it up in the hierarchy. > > Recently over IRC and other threads, Tomasz raised a concern that CODECs where > introducing too much complexity into M2M. And I believe buffered (which is > barely documented) and this mechanism was being pointed. > > My take on that is that adding boolean configuration is what introduce > complexity, and we can fix it by doing less in the m2m. After this discussion, I > came with the idea that we should remove buffered and ignore_streaming. For > drivers that don't implement job_ready, this logic would be moved inside the > default implementation. We can then add a helper to check the common conditions. > > The alternative suggested by Tomasz, was to layer two ops. We'd have a > device_ready() ops and its default implementation would include the check we > have and would call job_ready(). Personally, I'd rather remove then add, but I > understadt the reasoning and would be fine committing to that instead. > > I'd like your feedback on this proposal. If this is something we want, I'll do > this prior to V13, otherwise we will address your comments and fix the added > mechanism. I think though that we agree that for decoders, this is nice addition > to not have to trigger work manually from vb2 ops. It comes down to a matter of taste, I guess. I personally think that using bools to tweak the behavior of a framework does not necessarily increase complexity, provided it is clearly documented what it does and why it is needed. I think an ignore_cap_streaming bool is pretty straightforward and has minimal impact in the code. As long as there are good comments. The 'buffered' flag is were this clearly failed completely, since I couldn't figure out what it is supposed to do. But that is not because it makes the code more complex, it is just because of shoddy documentation and naming. Quite often implementing tweaks like that are quite easy in a framework, since you have all the information readily available. In a driver it can quickly become messy. For codec support there are a number of issues that increase complexity: implementing support for the LAST flag and events, and supporting buffers that can be held. Especially since driver implementations tend to vary. I've been experimenting with some cleanups and changes in v4l2-mem2mem.c (https://git.linuxtv.org/hverkuil/media_tree.git/log/?h=enc-dec-cmd), mainly surrounding the handling of the LAST flag. Note: this is failing the compliance tests, I haven't had the time to pursue this further. I'm not sure whether the best approach is to move things out of the m2m framework, or move things into the m2m framework, or add a more codec-specific layer on top of the m2m framework, or a combination of all of these. It is something that needs experimentation, just see what works. But for this specific flag: I think it is fine to put that in the m2m framework, just document and name it well. Regards, Hans > > regards, > Nicolas > >> >>> * >>> * Queue for buffers ready to be processed as soon as this >>> * instance receives access to the device. >>> @@ -69,6 +79,7 @@ struct v4l2_m2m_queue_ctx { >>> spinlock_t rdy_spinlock; >>> u8 num_rdy; >>> bool buffered; >>> + bool ignore_streaming; >>> }; >>> >>> /** >>> @@ -564,6 +575,12 @@ static inline void v4l2_m2m_set_dst_buffered(struct v4l2_m2m_ctx *m2m_ctx, >>> m2m_ctx->cap_q_ctx.buffered = buffered; >>> } >>> >>> +static inline void v4l2_m2m_set_dst_ignore_streaming(struct v4l2_m2m_ctx *m2m_ctx, >>> + bool ignore_streaming) >>> +{ >>> + m2m_ctx->cap_q_ctx.ignore_streaming = ignore_streaming; >>> +} >>> + >> >> I think this is overkill, esp. when the field is moved to m2m_ctx. Just clearly >> document that drivers can set this. >> >> Regards, >> >> Hans >> >>> /** >>> * v4l2_m2m_ctx_release() - release m2m context >>> * >>> >> >