From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.0 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS, URIBL_BLOCKED,USER_AGENT_NEOMUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id B9F5FC10F13 for ; Thu, 11 Apr 2019 15:57:59 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 883532184E for ; Thu, 11 Apr 2019 15:57:59 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="plmncsjo" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 883532184E Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=bootlin.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender:Content-Type:Cc: List-Subscribe:List-Help:List-Post:List-Archive:List-Unsubscribe:List-Id: In-Reply-To:MIME-Version:References:Message-ID:Subject:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=VkU0NoJT1uc0n4yZBSI4bhQ0jiTIlUgh47yohbk3xJA=; b=plmncsjos5iE/hfjjl2R+YQo9 +AUZq58MDSZSROU0uKanISn0YIQPAhVxAHrfWtQHkVVW7dQsaOrvo6PdOGdZiucPlvuceCFseYKj5 WBykS7f41l+HENn1Y/bycamwiPsc9DrQHlslKCi8rrOChapoDiN5naWk0HCuNQH14bM47D2oIzlKX pAKRNQz0og4sOoC/sGf5BobF/RjGGUTxYNI7Hu0x+Q8RB1gAAI9EZACt8cg1K0jVZiGZ8VTu0Pe9R D12SedpDKi+zaKNRSGPyndIk8k2g7+SRRcBqNvHFHb1U0/i9bzROgUoGmIyKt0vu5I5OHAcWiDnTh KJykkornw==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.90_1 #2 (Red Hat Linux)) id 1hEc5O-00015p-9b; Thu, 11 Apr 2019 15:57:58 +0000 Received: from relay7-d.mail.gandi.net ([217.70.183.200]) by bombadil.infradead.org with esmtps (Exim 4.90_1 #2 (Red Hat Linux)) id 1hEc5L-00015N-60 for linux-arm-kernel@lists.infradead.org; Thu, 11 Apr 2019 15:57:57 +0000 X-Originating-IP: 90.88.18.121 Received: from localhost (aaubervilliers-681-1-63-121.w90-88.abo.wanadoo.fr [90.88.18.121]) (Authenticated sender: maxime.ripard@bootlin.com) by relay7-d.mail.gandi.net (Postfix) with ESMTPSA id 0A81E20012; Thu, 11 Apr 2019 15:57:49 +0000 (UTC) Date: Thu, 11 Apr 2019 17:57:49 +0200 From: Maxime Ripard To: Nicolas Dufresne Subject: Re: [PATCH RESEND v7 1/2] media: uapi: Add H264 low-level decoder API compound controls. Message-ID: <20190411155749.crdpidehjxa6edya@flea> References: <7cd913545cfc80fa9999839c62c4bf7b354a7904.1554380738.git-series.maxime.ripard@bootlin.com> <20190405151552.biesirbs35uivk7d@flea> <05078223a4098c96f6260f77e9ef2a01b966daa6.camel@collabora.com> MIME-Version: 1.0 In-Reply-To: <05078223a4098c96f6260f77e9ef2a01b966daa6.camel@collabora.com> User-Agent: NeoMutt/20180716 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20190411_085755_526838_D8A3C435 X-CRM114-Status: GOOD ( 27.45 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: "list@263.net:IOMMU DRIVERS , Joerg Roedel , " , Thomas Petazzoni , Alexandre Courbot , Jonas Karlman , Jens Kuske , linux-sunxi , Linux Kernel Mailing List , Jernej Skrabec , Tomasz Figa , Paul Kocialkowski , Chen-Yu Tsai , Hans Verkuil , Laurent Pinchart , Sakari Ailus , Guenter Roeck , Ezequiel Garcia , Pawel Osciak , Linux Media Mailing List Content-Type: multipart/mixed; boundary="===============5440393919484409468==" Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org --===============5440393919484409468== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="gy5eppcjekdsrhyc" Content-Disposition: inline --gy5eppcjekdsrhyc Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, On Fri, Apr 05, 2019 at 12:27:48PM -0400, Nicolas Dufresne wrote: > Le vendredi 05 avril 2019 =E0 17:15 +0200, Maxime Ripard a =E9crit : > > Hi Nicolas, > > > > On Thu, Apr 04, 2019 at 11:41:13AM -0400, Nicolas Dufresne wrote: > > > > > > + * - __u16 > > > > > > + - ``pic_width_in_mbs_minus1`` > > > > > > + - > > > > > > + * - __u16 > > > > > > + - ``pic_height_in_map_units_minus1`` > > > > > > + - > > > > > > > > > > We recently had some reflection with Alex that this is redundant = with > > > > > the width and height in the OUTPUT format. It may also apply to s= ome > > > > > other fields in these structs. I feel like they should be removed= and > > > > > passed via corresponding generic V4L2 properties - format, select= ion, > > > > > etc. > > > > > > > > > > The same problem is also present in the MPEG2 controls. In fact, = there > > > > > was a patch already which used some fields from the controls to > > > > > calculate the destination buffer strides, rather than bytesperlin= e in > > > > > the format. > > > > > > > > > > Since we're in staging, it could be done with a follow-up patch, = though. > > > > > > > > Just my two cents. I played with some codecs a while back. IIRC some > > > > specify a "codec" size in addition to the actual picture size, like > > > > when the encoder does padding to fit the requirements of the codec > > > > (spec). Is this needed anywhere? > > > > > > With state-less encoders, the headers, which contains the crop > > > information is created by userspace and for state less decoder, the > > > headers that contains this information is parsed by userspace. So I > > > believe that in theory, the accelerator does not strictly need to be > > > aware of the cropped dimensions. > > > > > > Another thing, is that there is not guarantied matches between e.g. > > > depth of the chrome/luma and the final image buffers. Some hardware m= ay > > > have bandwidth limitation or internal converter and could possibly > > > decode 10bit data into 8bit buffers. > > > > > > A third reason why I would not try and encode this header information > > > is that there can be multiple PPS/SPS at the same time, and I think > > > it's confusing if the relevant information to differentiate them is > > > removed. > > > > Sorry if that sounds a bit dumb, but it's not really clear to me if > > you're arguing for the removal of the data as Tomasz suggests, or if > > you want to keep them. > > > > The first paragrah seems to advocate for the former, but the two > > others for the latter. > > I think the data should stay. As I said, there can be multiple SPS/PPS, > while there is only one format. That being said, how does SPS/PPS > activation works ? How do you tell the driver about all the SPS/PPS and > which one is being activated ? The current way of dealing with this is that the _SLICE_PARAMS control actually takes an array of SPS's. And same thing for PPS. There's no difference between activated and deactivated ones though. What is the use case for this? Thanks! Maxime -- Maxime Ripard, Bootlin Embedded Linux and Kernel engineering https://bootlin.com --gy5eppcjekdsrhyc Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEABYIAB0WIQRcEzekXsqa64kGDp7j7w1vZxhRxQUCXK9j/QAKCRDj7w1vZxhR xaYGAQCsc7VzPLi6Wez6KKZYGFulznMkEwVKTW7odXkXkgtCIwEAmJwWZjLVEXE4 EQyZH/dg/cuLi5H6A+QpU9SjLypRswE= =TYHB -----END PGP SIGNATURE----- --gy5eppcjekdsrhyc-- --===============5440393919484409468== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel --===============5440393919484409468==--