Received: by 2002:a25:e74b:0:0:0:0:0 with SMTP id e72csp1562931ybh; Thu, 16 Jul 2020 16:10:24 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzwGCxN14Bl/cnyr5lx8pn+xWTh2GlNp7p9PrgHRYl5dyqDVvYWckQKd3TlGgldcyJXnHax X-Received: by 2002:a17:906:365a:: with SMTP id r26mr6102394ejb.52.1594941023881; Thu, 16 Jul 2020 16:10:23 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1594941023; cv=none; d=google.com; s=arc-20160816; b=oXBs76+E7EJw4LAdks1GCQMO/MSZcSus25a2jaYfOzMfymk8EMkStRwRA9XLc3uRsV PeOxr5J/iuspE/Mm0UVYPmimjNjyWLPLkHJ1KYuQq+TBaRiSZ92Lg4zN7bTfZ5Y508kn vP0IZ63ncoTq9Tye2jG6K9TxwFXcrd3ATFoe4FUxhyv8oefke75JQ5O2ZK508IhvGcxM /O76sy2JmGKvvf9qu9koR5K6Heyz0ZmhnYrJuqucpla+Ra9zpHcHXUlSajp1QBVYjwPx fKZe39ndf1Ryo47a5rze78XPqyJvekH5jtSje5WoMduPpwjmrL37LERMfGQz7H7dhE6M ZB+g== 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=vRmrcXdGKYCulhx5JF7bmSsDjAzR+R6023P6GBnsjfQ=; b=L3y+Mjug2WQyuM7JEaq9D79ATyMPJuu6pdHxqvkflN4nFNeA/WxqtQ121XLzY8gAjk Op5sVtrzCO50LOlCiGSZzqiHeW0tyYs2B5SYN9+TlurMjAbjUHwBJ7x+mhjDtHjJpMde kydZHRE4dNnYAzFXiGS7ydzcA0YLltRfwBKtcubSZWGOXes0YEJhAYJH+1OunnlQ6EZ+ qwTBcCV9pUX7xpvWqkDTD4sdQUL67ReGXXBovXfubt3RMhD9i0ryyFsQIJ+7uyXSki/H ZpKYYSl6DDkaTuk8XKHdviwvpWGKPvLOOucjItD+RVfWPMFR78aPNuapO7b8/CIdv+2F g9Xg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=E56txzaf; 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 g12si4253055edv.266.2020.07.16.16.09.43; Thu, 16 Jul 2020 16:10:23 -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=E56txzaf; 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 S1727903AbgGPXJD (ORCPT + 99 others); Thu, 16 Jul 2020 19:09:03 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43338 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727815AbgGPXI6 (ORCPT ); Thu, 16 Jul 2020 19:08:58 -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 5F4EAC08C5FB; Thu, 16 Jul 2020 16:01:32 -0700 (PDT) Received: by mail-lf1-x144.google.com with SMTP id b30so2602072lfj.12; Thu, 16 Jul 2020 16:01:32 -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=vRmrcXdGKYCulhx5JF7bmSsDjAzR+R6023P6GBnsjfQ=; b=E56txzafzppMuffM1Gu5Z9yBTjbmyAv5+/F6FiMiUIVnnW2zq6c88cHxzrhnkrr6ow gFVX2XlNz6/TNOI0paMw6OLATpLw48J/F2WQDK1u+lH+xK43cuSZeOiSLTc066vdBHUz OR6NLSsip/EVOU+KKyVbfJlO1ObKA/e0PFM+hDzTYp7ibJ2r+L2dxpCeXcF+Fb0oGhV0 PQGskd1r2k/w9LTpmAy7RhVwrgx7IRoosJQuDzaQWfHwj+Ggw0OxvtXC8Q6DNuBPTTWU 37z0yMiIoUrbD4OM5k9f//XXEbpc3NFfsWMaxH6ejpdxx3WSoyEX0YvoM8Pw5agBQx2B tLOQ== 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=vRmrcXdGKYCulhx5JF7bmSsDjAzR+R6023P6GBnsjfQ=; b=WTbuXDY4BY/Yf5GsU2tbCHAc2o0EzB5ohTgGHKqBKlhgaIo36Ohu2rVuoYpOclNuH1 UEewVMXll+EASduvUfCTsMjq4KH9jfAhW3epq/z7+bD5nYCWzAs5I6LMEGSX6WoTsEV1 j8E4B8KMeYBhI19tFAsxc/LO/ua7VxQyGLuX/gF3bW95w/6cVDq7F/p4ggCgX7qFv6Ro 0zkzCDUiyS4tShe68eDvtzk1gJMA9p4gdYTKLzjbOXYDqQJNMi4xBFWIdTYIUI5wvyBG +UheD2MKu2CH3mn/5qo9g27zYiT9ZKwUdhYPd3SrFDxGAor6FHR0bqUBRHVJBtNe4dWT xdFA== X-Gm-Message-State: AOAM531l+NewWf9wFg1zmseHU6KTZrdx3CKDtSEtj1NM2jGzTMAWyy71 7/7CxuI25a1tHTAJEd6jPzTgQMNr X-Received: by 2002:a05:6512:250:: with SMTP id b16mr3118639lfo.67.1594940490262; Thu, 16 Jul 2020 16:01:30 -0700 (PDT) Received: from [192.168.2.145] (ppp91-76-4-184.pppoe.mtu-net.ru. [91.76.4.184]) by smtp.googlemail.com with ESMTPSA id w4sm1315624ljw.16.2020.07.16.16.01.28 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 16 Jul 2020 16:01:29 -0700 (PDT) Subject: Re: [RFC PATCH v3 16/18] gpu: host1x: mipi: Split tegra_mipi_calibrate and tegra_mipi_wait To: Sowjanya Komatineni , thierry.reding@gmail.com, jonathanh@nvidia.com, frankc@nvidia.com, hverkuil@xs4all.nl, sakari.ailus@iki.fi, robh+dt@kernel.org, helen.koike@collabora.com Cc: sboyd@kernel.org, gregkh@linuxfoundation.org, linux-media@vger.kernel.org, devicetree@vger.kernel.org, linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org References: <1594786855-26506-1-git-send-email-skomatineni@nvidia.com> <1594786855-26506-17-git-send-email-skomatineni@nvidia.com> <20d63eca-4b2b-584e-a391-a4fb64a16b40@nvidia.com> From: Dmitry Osipenko Message-ID: Date: Fri, 17 Jul 2020 02:01:28 +0300 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: 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 17.07.2020 01:49, Sowjanya Komatineni пишет: >> What keeps MIPI clock enabled after completion of the >> tegra_mipi_calibrate() invocation? > > MIPI clock is disabled at end of tegra_mipi_calibrate and is re-enabled > during tegra_mipi_wait. > > I think I should fix this to keep the clock enabled till calibration > results are latched. > > All consumers of tegra_mipi_calibrate() will call tegra_mipi_wait(). > > So will remove clk_disable mipi clk at end of tegra_mipi_calibrate() and > clk_enable mipi_clk at beginning of tegra_mipi_wait() Isn't it possible to perform the calibration after enabling CSI and before of starting the sensor streaming?