From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751965AbcF0MwD (ORCPT ); Mon, 27 Jun 2016 08:52:03 -0400 Received: from zencphosting06.zen.co.uk ([82.71.204.9]:38051 "EHLO zencphosting06.zen.co.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751634AbcF0MwA (ORCPT ); Mon, 27 Jun 2016 08:52:00 -0400 Subject: Re: [PATCH v5 0/9] Output raw touch data via V4L2 To: Hans Verkuil References: <1466633313-15339-1-git-send-email-nick.dyer@itdev.co.uk> <30c68dab-b970-03d5-797b-3376d9d0dc10@xs4all.nl> <8be600b6-a424-ddda-8672-1aed4e925fe8@itdev.co.uk> <693d1756-dab4-b05c-0607-f391f63f1d62@xs4all.nl> Cc: Dmitry Torokhov , linux-input@vger.kernel.org, linux-kernel@vger.kernel.org, linux-media@vger.kernel.org, Benjamin Tissoires , Benson Leung , Alan Bowens , Javier Martinez Canillas , Chris Healy , Henrik Rydberg , Andrew Duggan , James Chen , Dudley Du , Andrew de los Reyes , sheckylin@chromium.org, Peter Hutterer , Florian Echtler , mchehab@osg.samsung.com From: Nick Dyer Message-ID: <39b18d15-848b-bf28-4ff2-a5216846fb6b@itdev.co.uk> Date: Mon, 27 Jun 2016 13:51:54 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: <693d1756-dab4-b05c-0607-f391f63f1d62@xs4all.nl> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-OutGoing-Spam-Status: No, score=-1.4 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - zencphosting06.zen.co.uk X-AntiAbuse: Original Domain - vger.kernel.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - itdev.co.uk X-Get-Message-Sender-Via: zencphosting06.zen.co.uk: authenticated_id: nick.dyer@itdev.co.uk X-Authenticated-Sender: zencphosting06.zen.co.uk: nick.dyer@itdev.co.uk Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 27/06/2016 13:22, Hans Verkuil wrote: > On 06/27/2016 01:57 PM, Nick Dyer wrote: > 2) Alternatively, if we want to keep using BUF_TYPE_VIDEO_CAPTURE, then: > > - we keep V4L2_CAP_TOUCH which is combined with CAP_VIDEO_CAPTURE (and perhaps > VIDEO_OUTPUT in the future). The CAP_TOUCH just says that this is a touch > device, not a video device, but otherwise it acts the same. > > I'd go with 2, since I see no reason to add a new BUF_TYPE for this. > It acts exactly like video after all, with only a few restrictions (i.e. no > colorspace info or interlaced). And adding a new BUF_TYPE will likely break > the existing sur40 app. OK, I will rework with this approach.