Received: by 2002:a05:6a10:9e8c:0:0:0:0 with SMTP id y12csp234983pxx; Thu, 29 Oct 2020 00:56:59 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwurhskdbrX5KpuH4WC0xQg1krZd5kncTAbdS5MfEMsWDwApICxOIQsMs3WOGtmDDxmPgvM X-Received: by 2002:aa7:cb1a:: with SMTP id s26mr2648754edt.219.1603958219422; Thu, 29 Oct 2020 00:56:59 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1603958219; cv=none; d=google.com; s=arc-20160816; b=dy5h2IKyc5clqCsS8EaQLbnS3A/qiItwyhoSPlnuKn3bE63zYJTQSrVRzkudbnuiZS La6QljfYeJb+cIg0/CTTQxosP29jxesbPEHtgHuIDj3FuNqmdZniJ8h9q/okPmhwE4AV 67JAnTIm+ZPC5Txk6dJoH/2kpwdMEFlBYxAux0sUn1peOgCBWQKxLX/mh5KJ0LVLC/hh DaYd1ZjtkfUjktiziCxziep6B08QX2F2giRNIisyj3Og4ANzdiBtuu60kFOE8rQghlZY U+7mZufICPLjfibfAUATOG/RvEtqhb6AB/hPlFsdWidWZv32VU2ClJvLboDF6F8C6Y58 /Paw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=cfgFzKKhNnMi/GMVV82Uo8k8bscPVazRnoozeWTLycw=; b=shIGg3nMRxFbp69qGcV9zYjsfKoqKW3T4AZUEF1kQczssOrBfQE8T8j7mLMvRDdkV6 j5JXpZkiK3n7Cr//yA/00kXFINU2eP8Ir0Ab7hU0KO/OFneeN8W9+A/UnyfhWszGX7I/ mAEqovNMRN4vz9yIDqkLPmgPZiJY02ld/QpSyxxis0EhbN3XFz/XAg9B0g1MGf2K7x1m qHzdvlLifF0KH2nCj7HR5APqr54UwxFaf/w0/h1MNmkhyW9PMoz8FgaqN7GHe7Gds6Fd mdQEbC+Jf45AIoqpj3aL+ZNHd+BVkmp0x5npUl2a1j4+ioGR0IXO2wKwM83flK+CxKVo UGxw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=rS+WVklm; 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=linaro.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id bx3si1307568ejb.709.2020.10.29.00.56.38; Thu, 29 Oct 2020 00:56:59 -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=@linaro.org header.s=google header.b=rS+WVklm; 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=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1733064AbgJ1XPc (ORCPT + 99 others); Wed, 28 Oct 2020 19:15:32 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34620 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731477AbgJ1XMj (ORCPT ); Wed, 28 Oct 2020 19:12:39 -0400 Received: from mail-pf1-x441.google.com (mail-pf1-x441.google.com [IPv6:2607:f8b0:4864:20::441]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id EB0ABC0613D1 for ; Wed, 28 Oct 2020 16:12:37 -0700 (PDT) Received: by mail-pf1-x441.google.com with SMTP id a200so712929pfa.10 for ; Wed, 28 Oct 2020 16:12:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=cfgFzKKhNnMi/GMVV82Uo8k8bscPVazRnoozeWTLycw=; b=rS+WVklmfAY6KhDUrbki4jt4B18LTB6p22yrLLmnk1UDDko9AbIk1TGEZWZlhqIivC zCU/ojARnMEbsZz7jLseoKhAWaCVUBiQBqiG10bmzVWXbEJeO5wddw/YKCkvJZrQ5cDL 64XYdYSl6oBTARNV2zP0QvbVXEb3SNrX5EznPJZK+sPRpxJ2iiAmR6VCPX/nVsNfr3b2 gA01p83XGuwkO/GQqc7TsoG4aedAnPeq+5XK+Mi0Aqy9CKyq7U7WchIYEap71a6n2oZ9 0KVdoQpuYBvGradBQMMXowW1jSaXt3ejdLogjwP4DwIJhD+DNJOE1N59Xkx+E1WTiINF YXZQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=cfgFzKKhNnMi/GMVV82Uo8k8bscPVazRnoozeWTLycw=; b=p0uPQJYCugD5GsWCKdwYiNR3xe2etrJ8glwIqF/9TxjeI7X5+50rgmJHRRH2jhRSGb OviEka47zLP8X+D6r6bIxAF5NpnOrP8GdvH1KiD1NAxgyozUTm+vp5Pxwu9fTA/xaD8f Z78IPn8X9F22EH9gD3FEgzjKbZ/OLbOXibjD5Ehz6FN32KF8uK+PWDPsOEDKj1b/5eqM l5XiQHtTC1SgW4QI6NMEabpogSDFGlnRulaB5RaTdPQ+WW76hEVKllpwso8AphsPIChm UBgdq70fmOEjAJ9/oPscvid//QrZdf1VG4SCiq9g0ulgo6jd9AvU/Rw1NQ9/g1cCau0x qUmQ== X-Gm-Message-State: AOAM533EfH9ThWsivHeXQ9ppXXpMcKQZE8PlpAeFFzbiHgCkSqKpmGVu kFCuDU9iyt75A11PfSPkx+Ia6rnb8Jl65w== X-Received: by 2002:a17:902:8341:b029:d4:e3fa:e464 with SMTP id z1-20020a1709028341b02900d4e3fae464mr5788637pln.66.1603858318187; Tue, 27 Oct 2020 21:11:58 -0700 (PDT) Received: from localhost ([122.181.54.133]) by smtp.gmail.com with ESMTPSA id u194sm2753541pfc.176.2020.10.27.21.11.54 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 27 Oct 2020 21:11:54 -0700 (PDT) Date: Wed, 28 Oct 2020 09:41:52 +0530 From: Viresh Kumar To: Jon Hunter Cc: "Rafael J . Wysocki" , Thierry Reding , linux-pm@vger.kernel.org, linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH V2] cpufreq: tegra186: Fix initial frequency Message-ID: <20201028041152.733tkghz4vnqz2io@vireshk-i7> References: <20200824145907.331899-1-jonathanh@nvidia.com> <20200825055003.qfsuktsv7cyouxei@vireshk-i7> <09ac354e-a55b-5300-12ae-3f24c8f8b193@nvidia.com> <20201016040700.wzfegk7hmabxgpff@vireshk-i7> <9c37db70-9406-8005-3478-dc4a5e94c566@nvidia.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20180716-391-311a52 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 26-10-20, 12:57, Jon Hunter wrote: > Thinking about this some more, what are your thoughts on making the > following change? > > Basically, if the driver sets the CPUFREQ_NEED_INITIAL_FREQ_CHECK, This flag only means that the platform would like the core to check the currently programmed frequency and get it in sync with the table. > then I wonder if we should not fail if the frequency return by > >get() is not known. When do we fail if the frequency isn't known ? That's the case where we try to set it to one from the table. But (looking at your change), ->get() can't really return 0. We depend on it to get us the exact frequency the hardware is programmed at instead of reading a cached value in the software. > >This would fix the problem I see on Tegra186 > where the initial boot frequency may not be in the frequency table. With current mainline, what's the problem you see now ? Sorry I missed track of it a bit :) -- viresh