Received: by 2002:a25:683:0:0:0:0:0 with SMTP id 125csp3314557ybg; Sat, 6 Jun 2020 18:11:59 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxk1C0pbFv1qdRNroNYMjqaTtSVHYf84eia8t8YC+V+xS4hi21Oisw8TeflemfmUnnAR9a2 X-Received: by 2002:a17:906:70e:: with SMTP id y14mr14659401ejb.221.1591492319474; Sat, 06 Jun 2020 18:11:59 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1591492319; cv=none; d=google.com; s=arc-20160816; b=k9tlGFLfS4mPQXVbPcka7L42Oy5l9NF1mCqF886hKEwNcs2prOjcj9A8Q5a1UUXkaZ Slw+WIYJB9T6172szk/Zv5QtOLC/44A7GJGXRh7Iojdwmk990zuGbqgkeYGJJu02QYJh IRn/1mkoSNNB0VnprBv167Jdu5Hf9fT8li4HrTVzdOc7Gs4DByg5pN0FARmFxJAbR6rO XpvM0I4m3Bm4cTPMYWGvdT2ohG2leUjnapjyzmZ5gDYwdXq+afb3/tIlSO/OEFk0NJ5P /9Y4Au5TOQvom8bl5kuzg/kMR11icBzcSmg0u+f4fJRMXRnXf7nwHGCnHEJQffoP7KCH Haiw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=p+Wudnhpmc9i/PE6/yZ6j31H0t5tsBVIc8+ZHT9F+s8=; b=fNR3gaA0pdBMctXWK0UKTgLleJS4W91ZPbD/sKHobM9Y+CXEjFHgcQq1WPyK5tw4BG /m7ujIN+JDhNRbq6b5BusbXb2WTqA4hT6/PZOR4edgfr2vAFyxk5yu1DkcP2lCcUnFb4 ZgtXDFUsXjiD2k4t0yyMZf0ePfIuHspMGtFhRCSiDXGY7G+aUqKzkPEraBe4+r1Vezpc woJCkWkNMB+RQKNgA8cjnY4gM00sKGtF0DNkh9nJ7IiwRj6I7PXmNgVLxca59p1X2ffm Is8dS+iB6HHSfy64lJI0d4j7Gb9oehkZnrF9z26T7vCe3VCJHekm/vnQpnSZr1QAgHLZ jMNg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass (test mode) header.i=@ideasonboard.com header.s=mail header.b=cr2o6TWG; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id ds15si7360499ejc.14.2020.06.06.18.11.37; Sat, 06 Jun 2020 18:11:59 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass (test mode) header.i=@ideasonboard.com header.s=mail header.b=cr2o6TWG; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728911AbgFGBHk (ORCPT + 99 others); Sat, 6 Jun 2020 21:07:40 -0400 Received: from perceval.ideasonboard.com ([213.167.242.64]:39632 "EHLO perceval.ideasonboard.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728723AbgFGBHk (ORCPT ); Sat, 6 Jun 2020 21:07:40 -0400 Received: from pendragon.ideasonboard.com (81-175-216-236.bb.dnainternet.fi [81.175.216.236]) by perceval.ideasonboard.com (Postfix) with ESMTPSA id 0A5C02C9; Sun, 7 Jun 2020 03:07:37 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ideasonboard.com; s=mail; t=1591492058; bh=Zr1iCyErWTU0WRKjkUvAEEYuxaVuxgsvQL9HIU+vA4Q=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=cr2o6TWGLCpjcr4w7QOlOnhr0lXE3tqqB5QbOqPWVY53mU9Z/w3n+YM5aQymExNtj K0TZC7nGR7FecTUM6vOkgjor5lV3AIkaEwf4qZcFjAykC+b9LQn/AbGxn9sALBO/3N uRIvWSAexk9pC4nyjBlXBhD7zbhtBJKfdho3SM3g= Date: Sun, 7 Jun 2020 04:07:19 +0300 From: Laurent Pinchart To: Dmitry Buzdyk Cc: Mauro Carvalho Chehab , linux-media@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [RFC PATCH] uvcvideo: Add mapping for HEVC payloads Message-ID: <20200607010719.GU7339@pendragon.ideasonboard.com> References: <20200529010547.GA630131@dmitry-T520> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20200529010547.GA630131@dmitry-T520> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Dmitry, Thank you for the patch. On Fri, May 29, 2020 at 11:05:47AM +1000, Dmitry Buzdyk wrote: > Add HEVC GUID and assotiate with HEVC pixel format so that frame > based format descriptors recognized by the UVC video driver. The patch itself looks OK to me, but could you share a bit more information about which device(s) implement this ? Are they UVC 1.1 devices ? Could you share their full USB descriptors (retrieved with 'lsusb -v', running as root if possible) ? Is there anything else needed to get HEVC capture working, such as extension unit controls, or is this patch enough ? What userspace software do you use to capture and decode HEVC (or capture it to disk) ? > Signed-off-by: Dmitry Buzdyk > --- > drivers/media/usb/uvc/uvc_driver.c | 5 +++++ > drivers/media/usb/uvc/uvcvideo.h | 4 ++++ > 2 files changed, 9 insertions(+) > > diff --git a/drivers/media/usb/uvc/uvc_driver.c b/drivers/media/usb/uvc/uvc_driver.c > index 431d86e1c94b..825ee3601661 100644 > --- a/drivers/media/usb/uvc/uvc_driver.c > +++ b/drivers/media/usb/uvc/uvc_driver.c > @@ -214,6 +214,11 @@ static struct uvc_format_desc uvc_fmts[] = { > .guid = UVC_GUID_FORMAT_CNF4, > .fcc = V4L2_PIX_FMT_CNF4, > }, > + { > + .name = "HEVC", > + .guid = UVC_GUID_FORMAT_HEVC, > + .fcc = V4L2_PIX_FMT_HEVC, > + }, > }; > > /* ------------------------------------------------------------------------ > diff --git a/drivers/media/usb/uvc/uvcvideo.h b/drivers/media/usb/uvc/uvcvideo.h > index 6ab972c643e3..c7f043121b41 100644 > --- a/drivers/media/usb/uvc/uvcvideo.h > +++ b/drivers/media/usb/uvc/uvcvideo.h > @@ -165,6 +165,10 @@ > {0x32, 0x00, 0x00, 0x00, 0x02, 0x00, 0x10, 0x00, \ > 0x80, 0x00, 0x00, 0xaa, 0x00, 0x38, 0x9b, 0x71} > > +#define UVC_GUID_FORMAT_HEVC \ > + { 'H', 'E', 'V', 'C', 0x00, 0x00, 0x10, 0x00, \ > + 0x80, 0x00, 0x00, 0xaa, 0x00, 0x38, 0x9b, 0x71} > + > > /* ------------------------------------------------------------------------ > * Driver specific constants. -- Regards, Laurent Pinchart