Received: by 10.223.185.116 with SMTP id b49csp1709648wrg; Thu, 22 Feb 2018 01:39:44 -0800 (PST) X-Google-Smtp-Source: AH8x2245Z7+pK3WeuzTBx3+xDeXWDURCIP5HkAPKLrGFyDwLgnS9AMhcM5/yiKgvwXQipItyzu44 X-Received: by 2002:a17:902:7d83:: with SMTP id a3-v6mr6030655plm.184.1519292384430; Thu, 22 Feb 2018 01:39:44 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1519292384; cv=none; d=google.com; s=arc-20160816; b=mqznd9nJGlxDYk6ElHyQzeP9bels8XM4q6G/f709oi+XTDEkz2OK/+ERC/NYCAmW8f Avfs48DmWIRn2xwJXZdI7g4N5xU3KIbDMa5j1VCJkbQ8moV0lQtkIIfBtdagB0LN5ds7 ve0mQS0AOQZS0D4Coassa+1TCtDAabG57VETLuF4QFTnnvoYmQ5yUJV7Q9pfvKOYcSbP tkmUzYzU1qWbx2PUUzls2VRneRVDhN6V29KlXgyOWnE3qM57gXCMLULXfPG0cmkiYJlI Sf1wRQYSJo+LMnC/+l7qNyO06QHELoeyc99JY6bJvWiihOwdJfZJY+8/ndRaEcb2hSZR QPOw== 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 :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:arc-authentication-results; bh=gmQJ4Gfp0BytnYgGCLoCK24aUK3RYKA5ZBOW+SZJMn8=; b=Nl4YHZXWA+c/GQlML+RmqdgD/B46RTE8CdJmp6Sc91nn342t2nQanOy8rxsf2uG0Zb JGbfegvLszZml4kwZA8ph3JjG3eBfaLls+WGm9od44HQ3lTVRhZnNzq/ueUMZCSQvzAQ coZk27Fi88DIE3+KE5g7LdvjkgQCWc4yk1eHhhf5LStilgLqO4IyU0tV5hakl9HUMLmq /9px3jlgG1GhwnTkegrqWIVrO6+wGUes6NpNZqZ5oMD6zhD82aYMdAnBdC9Qxir9i7mp WkqfQdzjermallIk5m7jcT6RzLjzOqDx+Hn94aowgRmEYO1qWW9/fsPDkJESl16+JduL /FeA== ARC-Authentication-Results: i=1; mx.google.com; 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 x123si867960pgb.607.2018.02.22.01.39.29; Thu, 22 Feb 2018 01:39:44 -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; 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 S1753160AbeBVJi2 (ORCPT + 99 others); Thu, 22 Feb 2018 04:38:28 -0500 Received: from lb3-smtp-cloud8.xs4all.net ([194.109.24.29]:42925 "EHLO lb3-smtp-cloud8.xs4all.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752961AbeBVJi0 (ORCPT ); Thu, 22 Feb 2018 04:38:26 -0500 Received: from [IPv6:2001:420:44c1:2579:d0b3:4eff:352f:2858] ([IPv6:2001:420:44c1:2579:d0b3:4eff:352f:2858]) by smtp-cloud8.xs4all.net with ESMTPA id onKTeuSdizfiSonKXeYvuL; Thu, 22 Feb 2018 10:38:25 +0100 Subject: Re: [RFCv4 01/21] media: add request API core and UAPI To: Alexandre Courbot Cc: Mauro Carvalho Chehab , Laurent Pinchart , Pawel Osciak , Marek Szyprowski , Tomasz Figa , Sakari Ailus , Gustavo Padovan , Linux Media Mailing List , LKML References: <20180220044425.169493-1-acourbot@chromium.org> <20180220044425.169493-2-acourbot@chromium.org> <5fd863ad-a0fe-88d7-05bd-90c2b4096145@xs4all.nl> From: Hans Verkuil Message-ID: <591e7b83-9322-bf73-c762-6709c811d9de@xs4all.nl> Date: Thu, 22 Feb 2018 10:38:17 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-CMAE-Envelope: MS4wfMTa//nD4+e1/4KvVK0dXV9XnlOLtOaQGK0OM+RQBpqPdZM7C9JivYRgfjev2uA2tAfyeSS2dHWgJPjlFW0IXE3ma5P/oL3zwsg3aawy2apl/5CLGd1/ dX12y/WIj27J0p1YCYcle9TzvkPE2HyidkNPZwC0vdxihfgI7DWYCcKGRFT3ZrdTEEtCJeTfTghD2lq0H1gyl/6IP++FIkm06QCQptZIvuvPUMuXdvBDDFn0 UocVxvX6saFGUg1u/mLmeIMpT2VCdJm2k3DVFeuPSSdfqxksmXoALM1DRIOn5vE2HJHcELrDQN899hcx5sT0TVIqBLo4VTb0e/AwM2Sl44nSGm3O5jfZw/8X gXuZohfXQWU0rdvP58xFn7Id6V9FVV6uV2/pwvH/YOwZ7+69bhfq7ZCZ8inFdrx5hlJ69PFtfKTAgyeNmAFoJRAkUYZpHmLuXKQnHd5IGshQL01673KxXbIO C3PnfFwTckrgQ47Hw1A/sQxpvbWKRQe3BCsZHQSCxWibORJjgmcXnzd9cpAl2z03mIMiDbZJ0TyOLdRkUutxN7f8A/2NyjMnMojOFHqfKwuNjuzg22iFHzM/ V94= Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 02/22/18 10:30, Alexandre Courbot wrote: > On Wed, Feb 21, 2018 at 4:29 PM, Hans Verkuil wrote: >> On 02/21/2018 07:01 AM, Alexandre Courbot wrote: >>> Hi Hans, >>> >>> On Tue, Feb 20, 2018 at 7:36 PM, Hans Verkuil wrote: >>>> On 02/20/18 05:44, Alexandre Courbot wrote: >> >> >> >>>>> +#define MEDIA_REQUEST_IOC(__cmd, func) \ >>>>> + [_IOC_NR(MEDIA_REQUEST_IOC_##__cmd) - 0x80] = { \ >>>>> + .cmd = MEDIA_REQUEST_IOC_##__cmd, \ >>>>> + .fn = func, \ >>>>> + } >>>>> + >>>>> +struct media_request_ioctl_info { >>>>> + unsigned int cmd; >>>>> + long (*fn)(struct media_request *req); >>>>> +}; >>>>> + >>>>> +static const struct media_request_ioctl_info ioctl_info[] = { >>>>> + MEDIA_REQUEST_IOC(SUBMIT, media_request_ioctl_submit), >>>>> + MEDIA_REQUEST_IOC(REINIT, media_request_ioctl_reinit), >>>> >>>> There are only two ioctls, so there is really no need for the >>>> MEDIA_REQUEST_IOC define. Just keep it simple. >>> >>> The number of times it is used doesn't change the fact that it helps >>> with readability IMHO. >> >> But this macro just boils down to: >> >> static const struct media_request_ioctl_info ioctl_info[] = { >> { MEDIA_REQUEST_IOC_SUBMIT, media_request_ioctl_submit }, >> { MEDIA_REQUEST_IOC_REINIT, media_request_ioctl_reinit }, >> }; >> >> It's absolutely identical! So it seems senseless to me. > > This expands to more than that - the index needs to be offset by 0x80, > something we probably don't want to repeat every line. > >> >>> >>>> >>>>> +}; >>>>> + >>>>> +static long media_request_ioctl(struct file *filp, unsigned int cmd, >>>>> + unsigned long __arg) >>>>> +{ >>>>> + struct media_request *req = filp->private_data; >>>>> + const struct media_request_ioctl_info *info; >>>>> + >>>>> + if ((_IOC_NR(cmd) < 0x80) || >>>> >>>> Why start the ioctl number at 0x80? Why not just 0? >>>> It avoids all this hassle with the 0x80 offset. >> >> There is no clash with the MC ioctls, so I really don't believe the 0x80 >> offset is needed. > > I suppose your comment in patch 16 supersedes this one. :) Yes, it does. I realized later why this was done like this. That said, I don't like the magic value. Something like this might be cleaner: const unsigned int first_ioc_nr = _IOC_NR(MEDIA_REQUEST_IOC_SUBMIT); Then use first_ioc_nr (or nr_offset or whatever) instead of 0x80. Regards, Hans