Received: by 2002:a05:6a10:22f:0:0:0:0 with SMTP id 15csp4124133pxk; Tue, 8 Sep 2020 11:17:06 -0700 (PDT) X-Google-Smtp-Source: ABdhPJysdjENTqcbOxyaovjNLxr/kiI8nSqT2FNydrVpXt6dlrj3nAVEwQb5AI+InrUocTEBfm6J X-Received: by 2002:a05:6402:1356:: with SMTP id y22mr254160edw.110.1599589026641; Tue, 08 Sep 2020 11:17:06 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1599589026; cv=none; d=google.com; s=arc-20160816; b=WVrucHMK29ZD7Rp44naduKLwmthje1VpWfwJ35TScNTUWJqsDSrNiJxqvq9OEbNVv/ +xaBMIeH0VcFzqbV6SSanr1RHHrzlhgd1darXipXgorCkNgMBltzr6EpG0h/BZAUdrj5 T2URq6eGV22hdwVuoQDkIaf1gzDBa18MgZLatdp3lLzBZJiNXD/v7GUxLrkarnzEOGZS e2//YnAi+W4Y121QPoDnnkBgnrsAuPwHVGdvr0OVdnUzzL9qSF17z9EnNd6D9fXdoW8t MwQDTblLpUL/0Y1LUrVerhM8y5qJGGmfYyLB4ysnMjOsWXXcX6/vA+qEuKFIa+xbEPXt Z9pw== 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=v0oEvFN4sVVTaf28ZaWjZlHZQyMojiy8rT7wrNRNgFo=; b=OTUGNcAZMpPzC7ldf/9moSkt3HyL4cQmO5jqN00/4/2vDaRko8xypfq5cTabT2actN A3rKzwLkGPU/3AlwRRv5kHJOCcYYvt7WEndMQhShHFldL4NS+t0w26/hzMKvvV2PjmBl 838BwQMfFs/MvFymz3uF+rrCuzEWV5j9OML5jdE5EsAlAfoxvTyL3j5VeykX4AvlWgud 2VVol5SFd4wM/SW90fsiwIizckR4ToO/kKboAL4bvJ8IoXUWuuNQ/eZneGq5d/FIZh97 zJJ67J8Jui+wbVPJyrmDBNKd0fGKerk3E1uDGBeuh4zNT3aYT8UUHAy1lmPG5FPMUtTR TjjQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@nvidia.com header.s=n1 header.b=CdS9t7nf; 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 40si12123009edr.35.2020.09.08.11.16.44; Tue, 08 Sep 2020 11:17: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=CdS9t7nf; 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 S1732235AbgIHSNd (ORCPT + 99 others); Tue, 8 Sep 2020 14:13:33 -0400 Received: from hqnvemgate25.nvidia.com ([216.228.121.64]:13431 "EHLO hqnvemgate25.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728297AbgIHSNU (ORCPT ); Tue, 8 Sep 2020 14:13:20 -0400 Received: from hqpgpgate102.nvidia.com (Not Verified[216.228.121.13]) by hqnvemgate25.nvidia.com (using TLS: TLSv1.2, DES-CBC3-SHA) id ; Tue, 08 Sep 2020 11:12:30 -0700 Received: from hqmail.nvidia.com ([172.20.161.6]) by hqpgpgate102.nvidia.com (PGP Universal service); Tue, 08 Sep 2020 11:13:20 -0700 X-PGP-Universal: processed; by hqpgpgate102.nvidia.com on Tue, 08 Sep 2020 11:13:20 -0700 Received: from [10.2.171.137] (10.124.1.5) by HQMAIL107.nvidia.com (172.20.187.13) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 8 Sep 2020 18:13:18 +0000 Subject: Re: [PATCH v5 3/3] media: i2c: imx274: Add IMX274 power on and off sequence To: Jacopo Mondi CC: , , , , , , , , , , , , References: <1599012278-10203-1-git-send-email-skomatineni@nvidia.com> <1599012278-10203-4-git-send-email-skomatineni@nvidia.com> <20200903144713.fyhmhs2bfcz5br6d@uno.localdomain> <094073f1-ef58-a2fd-bed4-7fa3b99dd120@nvidia.com> <20200904085552.5xddn2kecoktuesg@uno.localdomain> <5ebe8d22-86fb-7bf2-ab19-e729caf8d88f@nvidia.com> <20200907074854.uxq4a76k5amjfopi@uno.localdomain> From: Sowjanya Komatineni Message-ID: Date: Tue, 8 Sep 2020 11:13:17 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: <20200907074854.uxq4a76k5amjfopi@uno.localdomain> X-Originating-IP: [10.124.1.5] X-ClientProxiedBy: HQMAIL105.nvidia.com (172.20.187.12) To HQMAIL107.nvidia.com (172.20.187.13) Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nvidia.com; s=n1; t=1599588750; bh=v0oEvFN4sVVTaf28ZaWjZlHZQyMojiy8rT7wrNRNgFo=; 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=CdS9t7nffzVjIWFzTDV62nY10cM3BSKRzMIs5DxNV/h89pfFBcqGbdhiPDlgl54km WIcX67UgeYUjEpDTvjz5zum1vI5L+qByhdNwbp2tp9kvJ/ST0eq3DB2cRRDZq93Zgt LvVGcrxSTcMDk5wPMYOXDu0X2LSapZEbFixMVMZ/S4sVyhARvckVDCHBj0qfWAcWMN cNoVI65rrNTFQ0iwpCxtAdRQb8ElnPYSAiENJxdi6o1E5A6dltAPO9l7i57xBMFXis bj+1K3LPieni8cHFGzbwaci9mz3VZitTNE3CJSiMVcxNRUEwgkliXiWndL1itjFUUi v3m0LiByqiLVg== Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 9/7/20 12:48 AM, Jacopo Mondi wrote: > Hello, > > On Fri, Sep 04, 2020 at 10:04:10AM -0700, Sowjanya Komatineni wrote: >> On 9/4/20 1:55 AM, Jacopo Mondi wrote: >>>>> usleep_range() allows you to provide an interval in which your timeout >>>>> can be coalesced with others. Giving a [1usec, 2usec] range kind of >>>>> defeat the purpose. And most than everything, does sleeping for 2usec >>>>> serve any real purpose ? >>>> Following delay recommendation from DS for power on sequence. >>>> >>> 2 useconds ? Seems very short:) >>> >> As per IMX274 datasheet for power on sequence, 100ns is the min wait time >> after the last power supply of 1v8/1v2/2v8 is ON before releasing RESET >> high. > ook.. well, it's actually reasonable, it's just the time for the > regulators to ramp up, I initially thought it was the time for the > chip to exit reset. > > Let me be a bit more picky and ask if you have considered busy waiting > on such a small sleep interval by using udelay. Again, as this happens > at chip power on only, the impact on the system of mis-using > usleep_range() is negligible, but according to documentation: > > SLEEPING FOR "A FEW" USECS ( < ~10us? ): > * Use udelay > > - Why not usleep? > On slower systems, (embedded, OR perhaps a speed- > stepped PC!) the overhead of setting up the hrtimers > for usleep *may* not be worth it. Such an evaluation > will obviously depend on your specific situation, but > it is something to be aware of. > > Up to you, really! > > Thanks > j Thanks Jacopo. Will update in v6 to use udelay.