Received: by 2002:a25:6193:0:0:0:0:0 with SMTP id v141csp601ybb; Tue, 7 Apr 2020 15:23:05 -0700 (PDT) X-Google-Smtp-Source: APiQypJ7C8MbImwlHNWk/SXglQRjQu+mmmU6iZe1Ayp1tCA10g5FEe52sea1MeKGC6ByhKr6+IHl X-Received: by 2002:a4a:929b:: with SMTP id i27mr3711110ooh.95.1586298185035; Tue, 07 Apr 2020 15:23:05 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1586298185; cv=none; d=google.com; s=arc-20160816; b=W9d3z0NIZ819IhPkDDGUl+YxzC4Cb4AZy9aEoqY7Z+OE08so2gOF+g3jo4BuilU/4u kzQhu5shvymZj/evbfxSaMU7sUgwV3gy1wmS+Cb8chRCJHaN6OArduEJjKrUfMfpO3ok cDjr6f7Vg80qIsqAx7tPOebAtiTIBS//89SdBSuZN5dSAhR8ll37Hl05Hx2FzvsyxUDm gz5u3zhl5eyPYofNn0LuJ7+TNPflhjsnj2M5TeVfwus8SRTQdb1EpJ8zld771iiA+xiR sZJrgu8+9X/ttDkqhU9HRpU4PUkdzFl4uPHn0TmfokkE9ozrPfvpAr+ReoMqNXDcQSEu uq7Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:dkim-signature:content-language :content-transfer-encoding:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=affO1Yr/fVkdDgXtDFDw59Iv7waWtClGoqGLbuDmMvA=; b=EyJ/GnXA/0b2WAdhHLC+d/elcsrjnoDZ5QyzRa5mEFeJuP23Dt/XDNf4q9RsYsH7qS CJXZMzbPEDJsMgJ3pTAE+AU1aJP1Yg8NYJ/+phqUBfSdoHj7Pk5rJUoSK1EUytwUvq9E mlub2gZDkrlRi+zxe1nVIQS8vr8e04BAO0/KnD23obngVWLpggoe18S52p9roZwPfa4A xjBa9dRp42OYsg6HMaz4F0AiVzj+eq9JasMpgYO/HdQIxs/svtIfEkNyQropIszfapn0 vI3Nt+5W88YtRCpcrk1YuLM7ZVsojF9uQQAj65z/KOwRs9pU+/DjU0gmU+nJ2QT4g0Ku fMBA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@nvidia.com header.s=n1 header.b=gQN4aVBF; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=nvidia.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id i6si1676488oor.75.2020.04.07.15.22.45; Tue, 07 Apr 2020 15:23:05 -0700 (PDT) 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; dkim=pass header.i=@nvidia.com header.s=n1 header.b=gQN4aVBF; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=nvidia.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726510AbgDGWWK (ORCPT + 99 others); Tue, 7 Apr 2020 18:22:10 -0400 Received: from hqnvemgate24.nvidia.com ([216.228.121.143]:13202 "EHLO hqnvemgate24.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726438AbgDGWWJ (ORCPT ); Tue, 7 Apr 2020 18:22:09 -0400 Received: from hqpgpgate101.nvidia.com (Not Verified[216.228.121.13]) by hqnvemgate24.nvidia.com (using TLS: TLSv1.2, DES-CBC3-SHA) id ; Tue, 07 Apr 2020 15:20:25 -0700 Received: from hqmail.nvidia.com ([172.20.161.6]) by hqpgpgate101.nvidia.com (PGP Universal service); Tue, 07 Apr 2020 15:22:08 -0700 X-PGP-Universal: processed; by hqpgpgate101.nvidia.com on Tue, 07 Apr 2020 15:22:08 -0700 Received: from DRHQMAIL107.nvidia.com (10.27.9.16) by HQMAIL109.nvidia.com (172.20.187.15) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 7 Apr 2020 22:22:07 +0000 Received: from [10.2.171.175] (172.20.13.39) by DRHQMAIL107.nvidia.com (10.27.9.16) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 7 Apr 2020 22:22:06 +0000 Subject: Re: [RFC PATCH v6 6/9] media: tegra: Add Tegra210 Video input driver To: Dmitry Osipenko , , , , , , CC: , , , , , References: <1585963507-12610-1-git-send-email-skomatineni@nvidia.com> <1585963507-12610-7-git-send-email-skomatineni@nvidia.com> <200bb96e-2d07-764f-9e14-55538dc742fd@gmail.com> <23bfab09-b464-6e51-9843-06d13000e9b9@nvidia.com> <08cd31d5-e8b9-4d3a-fb0e-0e4462947d96@nvidia.com> <12a834ac-52b1-6dc0-7d3a-3e6a1fa85a2a@gmail.com> <760d071e-0cbc-b3eb-9231-fb9f9ecb44a6@nvidia.com> <9e317f65-8a02-3b15-cfec-8e0d8374130e@gmail.com> <97b35910-4c93-123a-43a0-eb14476ed0f3@nvidia.com> <84ad4e2d-6ac1-e1f4-1c55-5edaae850631@nvidia.com> <15a879b3-8fb9-6821-3cdc-104ba583ac12@gmail.com> From: Sowjanya Komatineni Message-ID: <0c425505-347f-7418-af7e-d121fe0d06dc@nvidia.com> Date: Tue, 7 Apr 2020 15:22:05 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 In-Reply-To: <15a879b3-8fb9-6821-3cdc-104ba583ac12@gmail.com> X-Originating-IP: [172.20.13.39] X-ClientProxiedBy: HQMAIL107.nvidia.com (172.20.187.13) To DRHQMAIL107.nvidia.com (10.27.9.16) Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: quoted-printable Content-Language: en-US DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nvidia.com; s=n1; t=1586298025; bh=affO1Yr/fVkdDgXtDFDw59Iv7waWtClGoqGLbuDmMvA=; h=X-PGP-Universal:Subject:To:CC:References:From:Message-ID:Date: User-Agent:MIME-Version:In-Reply-To:X-Originating-IP: X-ClientProxiedBy:Content-Type:Content-Transfer-Encoding: Content-Language; b=gQN4aVBFGHGfJTH4B+1M5e3V40VRWaNWZ/4VYh6O83zGBgCCkEPn7tt+e+40JAfW1 LyY6THdOiL1ww8uD/iOy8wzG4YyNEoYiepsyeHS3cPFJrvmG/hk0wWHEJQKrfU/xVY kKlhkNye6bffxcrrQFV3xQ/bIdjKoo5BG4CTP/CirNy9gMgdx2lpwob70+O9RBk5hF xHrfDGeBjgLLWYilKcS3QWfJ8gALhtXkFruZyu+210ZEkZAmfQZtORygckCHc6fPx9 IaCUaNMPEmyknNUyPY8tn3H/mHhuj1EgBiYlZ56GJn7NlTw5AZ8i+xuen6mBQ/1c7e EFZIAi3TcTWcw== Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 4/7/20 3:08 PM, Dmitry Osipenko wrote: > External email: Use caution opening links or attachments > > > 08.04.2020 00:08, Sowjanya Komatineni =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > ... >>>> I think you need a semaphore with resource count =3D 2. >>> we hold on to issuing capture if more than 2 buffers are queued and it >>> continues only after fifo has min 1 slot empty >> >> Just want to close on this part of feedback. Hope above explanation is >> clear regarding triggering/issuing at max 2 frame capture to VI HW and >> also regarding capture threads where they use wait_event_interruptible >> to prevent blocking waiting for buffers to be available for captures. >> >> So no changes related to this part are needed in v7. > From what I see in the code, you "hold on" by making kthread to spin in > a busy-loop while caps_inflight >=3D SYNCPT_FIFO_DEPTH. So some change > should be needed to prevent this. > > The wait_event_interruptible seems should be okay. We don't want to prevent that as we already have buffers available for=20 capture so as soon as VI HW issuing single shot is done and when min 1=20 slot is empty we should continue with issuing for another capture. As long as buffers are available, we should continue to capture and=20 should not hold