Received: by 2002:a25:1985:0:0:0:0:0 with SMTP id 127csp1370153ybz; Sat, 25 Apr 2020 17:38:21 -0700 (PDT) X-Google-Smtp-Source: APiQypK2GWzw3Ql2oofAw2cfze4K8thSGbIOxNvpW5R/f4ou2lGbzrs3BH39lwbPlsCC1aRn9zjj X-Received: by 2002:a05:6402:1768:: with SMTP id da8mr13630588edb.216.1587861500782; Sat, 25 Apr 2020 17:38:20 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1587861500; cv=none; d=google.com; s=arc-20160816; b=fn7MOPFJ/Yezf5Jocvvv/n64JP03czf5ya5pmabNZghC9DWyxvJlxFJk+oikwr6JEK i/FDJLmIdCshw6WmVdcLmD7rz90PFzcnsVAEnXNCL/FQeKL3MSsxvDRa0lDbfgnb67ww zeJbp3w/VOXdo/8wNshqcZrIwgm7lpssNpou4j3gvq61NOmzaDEuvFQEsMDCYjVDQRuC H3XfLGo92hPd9LROPwA9g1n4Yaxhqeo7GPT6uWY2Hknx2R7LLzKfnPR4ZKisg6WdVW5F PBz42BFBJpZVLqeknRjU+Sq4TEptLZkovyMU3+kbs8Rw53rnTUNBNBPCRwqB4pnrHFqL 0cPg== 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:dkim-signature; bh=A7N+uweKX+04I/97tdi//DPnyW5rsGkuCQW0SIFkJgQ=; b=zOwZnujgiDzI881Y806yHRRXnNjoVGiLQZsd/FSGkIGnh9AjTX3MAxTAo9akItS+Oq yvt5SLDy3Rj9/y269L3W78KgUNaocpYBQsPg9TJODzoeiSBrsTpUxK8OMp5D1HInU6nw S+q8Wm9UoEYBNuFwFoNbD3n1DNtUOKQY2345AMqUYyuCL8yr4uU4XysVposYa3hgrkYZ W+JiDWk0mJoYI1cyFO3EV/EhYcDA2Vq/I4ueTlhmHGizYwhUdJDYjX5eTxaWySZadjBY uO+iEwCVYqlT4JQSHcPaUSVEaqypG7Ur62ziQ+4P6Uj6WspC3RI/XXPEPf0dHiOznUi1 KSgQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=Amd0JZPo; 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; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id e3si5508001edj.169.2020.04.25.17.37.56; Sat, 25 Apr 2020 17:38:20 -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 header.i=@gmail.com header.s=20161025 header.b=Amd0JZPo; 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; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726119AbgDZAgi (ORCPT + 99 others); Sat, 25 Apr 2020 20:36:38 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49710 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1725962AbgDZAgh (ORCPT ); Sat, 25 Apr 2020 20:36:37 -0400 Received: from mail-lf1-x144.google.com (mail-lf1-x144.google.com [IPv6:2a00:1450:4864:20::144]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 433E6C061A0C; Sat, 25 Apr 2020 17:36:37 -0700 (PDT) Received: by mail-lf1-x144.google.com with SMTP id k28so10830234lfe.10; Sat, 25 Apr 2020 17:36:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=A7N+uweKX+04I/97tdi//DPnyW5rsGkuCQW0SIFkJgQ=; b=Amd0JZPoDxFrF2SJwAILtl+b+NedLVOtr+wSvM/cmbyyfQAi9ZQZGivo0R1AOTm6DL L6pimm7/mJDbzTW1aaVJp+javcpn0q3jSAFBQG39IjdRbxL3yHHm3sF721jN6mjRr3Fr QnjuOYR9tyVBQqO/J9uEA2zMAxxcgHH8HSxt86ie3e4dpypw4WzJRqekqHKN92pHT0/o bzqiOU1eWfyHVRHylfPdNeG8m1ELSH4jMayig7xyUx83YlhoVRBAKhuI+NRGuCt6ROVC MaNdiywggCXOEjlNtkRvEfz4B1aOtLfBxQzbb0EY9Vn7IbJ8x0SMvavbjMo8LxYkXrsz dmAA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=A7N+uweKX+04I/97tdi//DPnyW5rsGkuCQW0SIFkJgQ=; b=rOeEWAHd68TPBovguc/sD/2e9gO5EIMnb2sZQBIcSJGTF0iAKNctiM24uICZsFa0/T 456BNOp3dca4haGA95H+iSrSxVmyKskWS0bM3YmS3W9ZSIa30cCo408AgU1NJFCcrnsH /tFHb4NgAV4oonUl8D5M4xz153RFAmZiHvMMdn0rGXDHPQVFsUs1yF3JhFLJHsJBqRXC 614dJR7rz/FIUj2gyq1hZLrj89w5vpEb94RqN5s633Ih7G0CjPJzNwuevC6eKpk5yjo+ 2FaHY3CieeNk2JDHO1S8j1bBt3cY0RMOtk8LP8egw4kSxhatiK+ZN7HxkDWAc3nBBxVo nsAA== X-Gm-Message-State: AGi0Pua2ZvdT2uKtdBw4JUrbS9Knke2XxwOQ1ZnKddwpZTbhXirwXfQD wIyFL+7knKNYS42KWFCycQoLsg5D X-Received: by 2002:ac2:5192:: with SMTP id u18mr10869262lfi.114.1587861395483; Sat, 25 Apr 2020 17:36:35 -0700 (PDT) Received: from [192.168.2.145] (ppp91-78-208-152.pppoe.mtu-net.ru. [91.78.208.152]) by smtp.googlemail.com with ESMTPSA id x80sm7997729lff.23.2020.04.25.17.36.33 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 25 Apr 2020 17:36:34 -0700 (PDT) Subject: Re: [RFC PATCH v10 6/9] media: tegra: Add Tegra210 Video input driver To: Hans Verkuil , Sowjanya Komatineni , thierry.reding@gmail.com, jonathanh@nvidia.com, frankc@nvidia.com, sakari.ailus@iki.fi, helen.koike@collabora.com Cc: sboyd@kernel.org, linux-media@vger.kernel.org, devicetree@vger.kernel.org, linux-clk@vger.kernel.org, linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org References: <1587700513-28449-1-git-send-email-skomatineni@nvidia.com> <1587700513-28449-7-git-send-email-skomatineni@nvidia.com> <6ca93ff9-ca59-544f-767c-4355d01a5c20@gmail.com> <62546d1f-eca5-06be-2bc2-e45ccd53830a@xs4all.nl> From: Dmitry Osipenko Message-ID: <50fd1016-ca8b-ec5d-e5a8-f257138b152e@gmail.com> Date: Sun, 26 Apr 2020 03:36:33 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: <62546d1f-eca5-06be-2bc2-e45ccd53830a@xs4all.nl> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 25.04.2020 12:36, Hans Verkuil пишет: ... >> The media/tegra/ sounds a bit too generic, the media/tegra-vi/ path >> should better reflect the driver, IMO. >> >> It also should be better to name the compiled kernel module as tegra-vi, >> IMO. >> > > The driver name and the directory should be in sync, so either tegra-video > or tegra-vi for both. I have no preference myself, as long as they are the > same. > > This can be done as a follow-up patch. Given that this driver isn't going to be reused by older pre-Tegra210 SoCs, perhaps it will also be worthwhile to name it as tegra210-vi or tegra210-video.