Received: by 2002:a25:1985:0:0:0:0:0 with SMTP id 127csp2002307ybz; Thu, 30 Apr 2020 09:09:06 -0700 (PDT) X-Google-Smtp-Source: APiQypK/U30R3jwN8T36fi4JkyZVqosAPSiyO/Efs2ROwmjbpca/JnX8nYDDXbzi3qmP7NreJLzn X-Received: by 2002:a17:906:3198:: with SMTP id 24mr3163965ejy.39.1588262946117; Thu, 30 Apr 2020 09:09:06 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1588262946; cv=none; d=google.com; s=arc-20160816; b=yUI/1tH7gASG4ZdEkekcQxPbuyr5d0uXv9IImb62bUUP1VRljEL214IQl3y0GuwJHi 83qf+UL2zRi/XhYJStQH9x8GfCiTvsCnlxiMfyhEk+Q4GcBCLQQagi+RkhcR1CmixLK3 OQe8XbB8FAd1fdTpY0vnEgB47LAQnZeUSH8OOq5yDOBSp/C5hlSxj1plAjIYJ3RWFcMe cBT0fryKfhwXrDdF50ZUS90ROhX0v0KDLUD/a5lvY8mz0fKono+1jN0/JLHaxSoNZhIX PmZlni/SRxud41NX/8AsOPNVRqVVMUyUYd5RAjg5D4NS7p0L8v9c6lj6Hn861YzzT+Z6 hOww== 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=eWajUdI0iXeAXeqVD5ZpEmRaSpEhM1U8KfCosqzO194=; b=C6LR1gLspy6V9q//7y1atG2XSrMPx5SnYk9YXMw+PdatK2JHoIb+fJynOZP4CxAaSe 8bofjmZ37c56xr2SbwoKg2j3Vb273LTcWO9u8kIrTVv7aGESM0EhvcZQl2erdfwzT/Bt GNTWLxwkXTDGJgrCyPascA+fA7HuObdWJrsWK3GkBqCEZ9XNeVzIrxuqzkQvV8ykGVsg FRiNYSKBHDlLZixEMRy3W/FE6iDZIyPnLbLWfBFxd60x+UMxwSprkk4WIdo5NvJmRtRE rXJJqJoLHfmsBOjMolet9TO+O9dx1CEsS2GvXnhEYr2xtXgCDJyaK8osJD0yUyvcVPIo f6Ng== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@nvidia.com header.s=n1 header.b=kP9ln9IF; 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=NONE dis=NONE) header.from=nvidia.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id x25si13743ejs.434.2020.04.30.09.08.41; Thu, 30 Apr 2020 09:09:06 -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=@nvidia.com header.s=n1 header.b=kP9ln9IF; 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=NONE dis=NONE) header.from=nvidia.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728316AbgD3QGK (ORCPT + 99 others); Thu, 30 Apr 2020 12:06:10 -0400 Received: from hqnvemgate25.nvidia.com ([216.228.121.64]:10786 "EHLO hqnvemgate25.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727813AbgD3QGJ (ORCPT ); Thu, 30 Apr 2020 12:06:09 -0400 Received: from hqpgpgate101.nvidia.com (Not Verified[216.228.121.13]) by hqnvemgate25.nvidia.com (using TLS: TLSv1.2, DES-CBC3-SHA) id ; Thu, 30 Apr 2020 09:05:00 -0700 Received: from hqmail.nvidia.com ([172.20.161.6]) by hqpgpgate101.nvidia.com (PGP Universal service); Thu, 30 Apr 2020 09:06:07 -0700 X-PGP-Universal: processed; by hqpgpgate101.nvidia.com on Thu, 30 Apr 2020 09:06:07 -0700 Received: from DRHQMAIL107.nvidia.com (10.27.9.16) by HQMAIL105.nvidia.com (172.20.187.12) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 30 Apr 2020 16:06:07 +0000 Received: from [10.2.165.152] (10.124.1.5) by DRHQMAIL107.nvidia.com (10.27.9.16) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 30 Apr 2020 16:06:06 +0000 Subject: Re: [RFC PATCH v11 6/9] media: tegra: Add Tegra210 Video input driver To: Dmitry Osipenko , , , , , , CC: , , , , , References: <1588197606-32124-1-git-send-email-skomatineni@nvidia.com> <1588197606-32124-7-git-send-email-skomatineni@nvidia.com> <4da289e6-036f-853b-beb4-379d6462adb0@gmail.com> From: Sowjanya Komatineni Message-ID: Date: Thu, 30 Apr 2020 09:04:40 -0700 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: X-Originating-IP: [10.124.1.5] X-ClientProxiedBy: HQMAIL105.nvidia.com (172.20.187.12) 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=1588262700; bh=eWajUdI0iXeAXeqVD5ZpEmRaSpEhM1U8KfCosqzO194=; 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=kP9ln9IFyG1CyD2zYD6UBRJU+3nqtrfnnZ+cS/JlbzMx3B5faTPLBdCdqyTod9yo1 Z0Z2LBvNwQOpWFZIlo0fsv987r878bT2zeUtFfUToRuBf1Lh/HgCJgU7bLrKBMWn3Q 7EPPKclFWEMjk0R/r47l9T1m3+0SRS07OY7Pci/cE1nIgNUWDe6tk+Kayl8v2RJ0Rk 3nt0YCCT4XfBt1BFf++ZQhEXx6KRIn9v+noVua6ZqWw5Skg8oeWfj68av04Fza1i/d F7E8EIRMAtO/MowkXFoanRyv6lWSbQx/oMz+9gxgwUq+u9RKO8pXG3cOzg4ztuNvIk 5iYSGa7WbeIhA== Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 4/30/20 7:13 AM, Dmitry Osipenko wrote: > 30.04.2020 17:02, Dmitry Osipenko =D0=BF=D0=B8=D1=88=D0=B5=D1=82: >> 30.04.2020 16:56, Dmitry Osipenko =D0=BF=D0=B8=D1=88=D0=B5=D1=82: >>> 30.04.2020 01:00, Sowjanya Komatineni =D0=BF=D0=B8=D1=88=D0=B5=D1=82: >>>> +static int chan_capture_kthread_finish(void *data) >>>> +{ >>>> + struct tegra_vi_channel *chan =3D data; >>>> + struct tegra_channel_buffer *buf; >>>> + >>>> + set_freezable(); >>>> + >>>> + while (1) { >>>> + try_to_freeze(); >>> I guess it won't be great to freeze in the middle of a capture process,= so: >>> if (list_empty(&chan->done)) >>> try_to_freeze(); >> And here should be some locking protection in order not race with the >> chan_capture_kthread_start because kthread_finish could freeze before >> kthread_start. > Or maybe both start / finish threads should simply be allowed to freeze > only when both capture and done lists are empty. > > if (list_empty(&chan->capture) && > list_empty(&chan->done)) > try_to_freeze(); good to freeze when not in middle of the frame capture but why should we=20 not allow freeze in between captures? Other drivers do allow freeze in between frame captures. I guess we can freeze before dequeue for capture and in finish thread we=20 can freeze after capture done. This also don't need to check for=20 list_empty with freeze to allow between frame captures.