Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp2408367imu; Thu, 24 Jan 2019 12:14:42 -0800 (PST) X-Google-Smtp-Source: ALg8bN7Ukq52IfZrUjO8am3sJ4mBGwiJ7RKdSUb9PO5Q+KQOvKWrvJ3AU1pTcyW0u+9tqqI0pict X-Received: by 2002:a63:ec13:: with SMTP id j19mr7228287pgh.6.1548360881962; Thu, 24 Jan 2019 12:14:41 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1548360881; cv=none; d=google.com; s=arc-20160816; b=xmYx/oZ+mT3C3Ey+xeR8YcyyVgu+zwSVDARIenVreJMBgLkEHYCcnag+L4gBpseYwx 8oCnAVhglrUVBIUqqiCzaAc3uN4/B2WsJw319/gwCXlAY5ePbSbaQyickrFJ0mp7cMqC ogGmxxsDfG8uktkrU8szttFrZPnZ3rEVDAACu86L+2blktdnA+V2wXKEaXUMw6XDN024 RyJnYgqPGARi7APNpCe0VMTX+TcnR6j1z8hqVHbFcSG8Pld3NqL67zMbnxH6zF6x5/bG /ZLw7Z6co+6WN/YGjg44nbGQlYIszvbzc+7Lc9GpHjSZnRbB9hl/PKlN7b5+ecKNJcKh hn8Q== 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 :user-agent:references:in-reply-to:date:cc:to:from:subject :message-id:dkim-signature; bh=/eLWF2nBpm4xYIb4J+nXrGXHgxha/99iWqDqjCF/hxo=; b=KWRXzMWX8KBI07bHr54dIKEz8o07XQEcnv9X1SILP3//1hJYl2M/AdHZZDJ1XdMdJ/ NgmdG3ltolxQaoxMskjSwM5s4+QiLWl36SGC77YIzbBbaa7MWyiv+qCzHYa9N/AxF4eS Wu+CLheZS7a3LdA87WjZQMcHLsjXf/9ZkcnibJJjbOj4pGfO9UO6Xf5VWpiQN+r0R8Dy bIQm5jrcEQdLggZnFiJD6f8MoEbo+tHBrn4v79W7nIUpBsHyT93H/xcJnP+2WQKusQy5 QGO/ZiOw/rmzlsJJHrkhroRly4ki3usRTM5h6BTQkBTMQHbiDGoEhAWEWKWZWk35pknb un2g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ndufresne-ca.20150623.gappssmtp.com header.s=20150623 header.b=P5KXRuLH; 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 t13si23419227pgm.175.2019.01.24.12.14.26; Thu, 24 Jan 2019 12:14:41 -0800 (PST) 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; dkim=pass header.i=@ndufresne-ca.20150623.gappssmtp.com header.s=20150623 header.b=P5KXRuLH; 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 S1730440AbfAXUOW (ORCPT + 99 others); Thu, 24 Jan 2019 15:14:22 -0500 Received: from mail-qt1-f194.google.com ([209.85.160.194]:41019 "EHLO mail-qt1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730195AbfAXUOV (ORCPT ); Thu, 24 Jan 2019 15:14:21 -0500 Received: by mail-qt1-f194.google.com with SMTP id l12so8199213qtf.8 for ; Thu, 24 Jan 2019 12:14:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ndufresne-ca.20150623.gappssmtp.com; s=20150623; h=message-id:subject:from:to:cc:date:in-reply-to:references :user-agent:mime-version:content-transfer-encoding; bh=/eLWF2nBpm4xYIb4J+nXrGXHgxha/99iWqDqjCF/hxo=; b=P5KXRuLHrM1JXw/KPqJrZ56CtTGz/p65b9igENNu130Zl7tjMfvMNqltUxMSlxRza0 A2gG722/oO9+UCYEzggDE7D7sMKNbuWnhag25c3hWzGWc/DpuB6GydkuIgZk/X5YfYop WNw8zqLVLOAUNBIEW/TeLEwKu5GA59cQ6M9AQDKWlT/3zobTCt6XB20VQ7uOOlFPSwbX h7WynjvTiOwquXraaQH8r6i+1tMiAAZ0WluRqvRbfANEVShwbktHlB8nIMZaFBkqtJbW uXgQEdFrpktsoZtkuKBVajv/8Xcdw2ORyNxgUsBeJbj9UzJLnGQtFJHsES7alvWXazvn 6qtQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:cc:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=/eLWF2nBpm4xYIb4J+nXrGXHgxha/99iWqDqjCF/hxo=; b=rOlC4ZVWVdSkmwxHq/VrXRj94cj3L+RWepQtcTvV0tCYE233ZZOYEr5QjTSjtT4+uW FPQtYkgzYddXHKwI8cIlkoz0EJ30idPg0pPtytUUObplrBEN1CDFm63/C7qn9qLJs3Or eDj3V+wq3aXRZ3eji1/iPsrrBkfMMJKNUq4nJE5ZAsTXz/RHVfak61UGoLnuj/+fzSXK Nshmt6L4oWbg87zaOy1SX05NMiMbALNkxH+CJGGsMqaYBVKZ7WuN2x64wG9AcV+PhxZx T6ouRs85VUBPW78aMSwSsVk8hGOvKkeDsaaxIJ8O9U01cZJu6iep0/IYpB5UMd8ESTlH N0TQ== X-Gm-Message-State: AJcUukenfXD24vXD3z5c7grh+JU4q0N1nnSTXQjDblkOdLA1q0WMONJO PdsubgxKzaAHt+mqTlFzdT/Vlw== X-Received: by 2002:aed:2f82:: with SMTP id m2mr8375505qtd.4.1548360860574; Thu, 24 Jan 2019 12:14:20 -0800 (PST) Received: from skullcanyon ([192.222.193.21]) by smtp.gmail.com with ESMTPSA id r24sm77410788qtr.2.2019.01.24.12.14.18 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 24 Jan 2019 12:14:19 -0800 (PST) Message-ID: <0452db20a894c1c4cce263b7e07ba274a58aa8fa.camel@ndufresne.ca> Subject: Re: [PATCH v2 2/2] media: docs-rst: Document memory-to-memory video encoder interface From: Nicolas Dufresne To: Hans Verkuil , Tomasz Figa Cc: Linux Media Mailing List , Linux Kernel Mailing List , Mauro Carvalho Chehab , =?UTF-8?Q?Pawe=C5=82_O=C5=9Bciak?= , Alexandre Courbot , Kamil Debski , Andrzej Hajda , Kyungmin Park , Jeongtae Park , Philipp Zabel , Tiffany Lin , Andrew-CT Chen , Stanimir Varbanov , Todor Tomov , Paul Kocialkowski , Laurent Pinchart , dave.stevenson@raspberrypi.org, Ezequiel Garcia , Maxime Jourdan Date: Thu, 24 Jan 2019 15:14:18 -0500 In-Reply-To: <75334288-69af-6680-fbe7-2dd5ef2462ea@xs4all.nl> References: <20181022144901.113852-1-tfiga@chromium.org> <20181022144901.113852-3-tfiga@chromium.org> <4cd223f0-b09c-da07-f26c-3b3f7a8868d7@xs4all.nl> <75334288-69af-6680-fbe7-2dd5ef2462ea@xs4all.nl> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.30.4 (3.30.4-1.fc29) Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Le mercredi 23 janvier 2019 à 14:04 +0100, Hans Verkuil a écrit : > > > Does this return the same set of formats as in the 'Querying Capabilities' phase? > > > > > > > It's actually an interesting question. At this point we wouldn't have > > the OUTPUT resolution set yet, so that would be the same set as in the > > initial query. If we set the resolution (with some arbitrary > > pixelformat), it may become a subset... > > But doesn't setting the capture format also set the resolution? > > To quote from the text above: > > "The encoder will derive a new ``OUTPUT`` format from the ``CAPTURE`` format > being set, including resolution, colorimetry parameters, etc." > > So you set the capture format with a resolution (you know that), then > ENUM_FMT will return the subset for that codec and resolution. > > But see also the comment at the end of this email. I'm thinking that the fact that there is no "unset" value for pixel format creates a certain ambiguity. Maybe we could create a new pixel format, and all CODEC driver could have that set by default ? Then we can just fail STREAMON if that format is set. That being said, in GStreamer, I have split each elements per CODEC, and now only enumerate the information "per-codec". That makes me think this "global" enumeration was just a miss-use of the API / me learning to use it. Not having to implement this rather complex thing in the driver would be nice. Notably, the new Amlogic driver does not have this "Querying Capabilities" phase, and with latest GStreamer works just fine. Nicolas