Received: by 2002:a25:1985:0:0:0:0:0 with SMTP id 127csp848439ybz; Wed, 15 Apr 2020 20:41:13 -0700 (PDT) X-Google-Smtp-Source: APiQypKuC+BIEDEapty44lBggDZhzHF1ctxEok65URlM6LxArydQDjaM7djHTl20zbU5CkfB05Ar X-Received: by 2002:aa7:cf16:: with SMTP id a22mr17192080edy.77.1587008472989; Wed, 15 Apr 2020 20:41:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1587008472; cv=none; d=google.com; s=arc-20160816; b=DuGz14j5Fyo3mRDmps3LdoiOFECeeiAM/bg4TtrMLniPcmPb1xbbh9HdTzDtft4QMN 3p6nI63I532zYxmO544cbv8K4danUKNVkWAsfViPDT/3UzzoavBAHBtAFFx5SkKMgBRd UFNX5l918ZHL+gnNuyzEZ3c+wUafjSTMXaLeNL/6VfsflqxmoDdgsGQ2+jFoNH/WSO8t CYGcux94ijzCH9MYzBAf+SESb61MKUti36ld1AoC0YTlF8cy6rcy7DNshmaMVcVldTQj FMX47LfUVWuiG6OrYNjOrNOYiAhmeoQldowH+jjd2MYF4k4T0OMbupgMrjXtvfUdql6P kozA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=LcBjNCK+rf+2YEVvZPZcsG/AeuTYN98gz3c92chJ7YI=; b=wUl6nTb2ZDu7TdXKHOOrs4Lu+2NulIzaTRLW0G5iUQRXt91hrK878rQrmRZh05O51D IOecAMAQX4lDTxksMcDO2PIgkvkZXKRqcgjVOZNm3Vg/Up1gsyovuGZw839Sy4mI1UK4 g4aSb6t6tzWZ2Tpl2SDIPWLqlvIp7PPJ/amfim1GqKpee2NIfP4vRTE/bIl9q3dkw+Z0 zQ4sROR8SuDV+rK4jOp+wnFKMj8j6AoVbvF/ZfWih3WO/1k+T0yJpyL/O085mlurdnDu 7yHB116wNevZDyEJxrM30wHxdzF7+vqpCKsyFOV7Vlspox30ilBVHbs9QgEobepqKZ7+ +tVA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=N62pR58M; 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 p17si6870991ejd.260.2020.04.15.20.40.49; Wed, 15 Apr 2020 20:41:12 -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=N62pR58M; 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 S2391225AbgDPDhX (ORCPT + 99 others); Wed, 15 Apr 2020 23:37:23 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48298 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1729245AbgDPDhT (ORCPT ); Wed, 15 Apr 2020 23:37:19 -0400 Received: from mail-pj1-x1044.google.com (mail-pj1-x1044.google.com [IPv6:2607:f8b0:4864:20::1044]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 174E2C061A0C for ; Wed, 15 Apr 2020 20:37:19 -0700 (PDT) Received: by mail-pj1-x1044.google.com with SMTP id a32so763389pje.5 for ; Wed, 15 Apr 2020 20:37:19 -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=LcBjNCK+rf+2YEVvZPZcsG/AeuTYN98gz3c92chJ7YI=; b=N62pR58MzOQlhuf1VXzQKfNlkAe28ps2Bt8L5EhPFsX8/ErCuUSI5IhuhLZ9lPMZmd 4fv7zApE3he/1DhHZan7KuMcZEMWwp+IYjVqAyT3oeHcIKD+PcmeejcO/8sKarT86ert QVi6jh6siT+NHR8Jl67jjHMlF8qduOugqkYjke78fFCESRf64rRWcC/EpNPn4lABmjiZ I8uMM3aDZK+rsVSzFl+vX0OPtCPq34gp37JaiW/fs+cxMxplqBiELQX6A0xmEi59cq2I tlTKyVcR5aGR1O8fMAoQvlaF9ogOD8KHOruF2CG8CAaGbXxdCDiTn4cl4SHg8QUJytwv TKeA== 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=LcBjNCK+rf+2YEVvZPZcsG/AeuTYN98gz3c92chJ7YI=; b=MYIHjFKs62ptbPnC4/W2OjjNwiPoFQw2X5LfTsk9V6tHc1+DADRbpnQFOo2fdKexl/ sEp3LBOWhhiXZ+UaW0pTx3xAnTqJRTX+eHbGyl3bvkSMsGfwKIHFR3sibdWuSdBE0aCp lozDJ4ufMD+FTRfc4vHLlp7a6f8pDfdETCooX2MNk8zKlECwmpek2eNmpUCNfcKMoGNn X2+Wvg8pebLuwEU8y9HJXZGOq77DEX0lk70tBwio7sFzd7ZLCbEqbF1LMRfWJxttBAFc VkjWb+g0nT1zSHh3Z/pRu7QfG9zPTmyxz6gHFZbZ7XH58ds11qyA50qprBgSD9OHoXPc 2ggg== X-Gm-Message-State: AGi0PublQQiFd5BZt3RyoCoyaL2SaKw+FpBd10pC7EMp8spsEa1cjv7Z ThwpFx+uN+m/I5RD8m7Ww08A1A== X-Received: by 2002:a17:902:8497:: with SMTP id c23mr8207091plo.335.1587008238452; Wed, 15 Apr 2020 20:37:18 -0700 (PDT) Received: from localhost ([122.171.118.46]) by smtp.gmail.com with ESMTPSA id u8sm14019683pgl.19.2020.04.15.20.37.17 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 15 Apr 2020 20:37:17 -0700 (PDT) Date: Thu, 16 Apr 2020 09:07:15 +0530 From: Viresh Kumar To: Sumit Gupta Cc: rjw@rjwysocki.net, catalin.marinas@arm.com, will@kernel.org, thierry.reding@gmail.com, jonathanh@nvidia.com, talho@nvidia.com, linux-pm@vger.kernel.org, linux-tegra@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, bbasu@nvidia.com, mperttunen@nvidia.com Subject: Re: [TEGRA194_CPUFREQ Patch 2/3] cpufreq: Add Tegra194 cpufreq driver Message-ID: <20200416033715.hscztwkxie2o5i3r@vireshk-i7> References: <20200406025549.qfwzlk3745y3r274@vireshk-i7> <3ab4136c-8cca-c2f9-d286-b82dac23e720@nvidia.com> <20200408055301.jhvu5bc2luu3b5qr@vireshk-i7> <08307e54-0e14-14a3-7d6a-d59e1e04a683@nvidia.com> <20200409074415.twpzu2n4frqlde7b@vireshk-i7> <00390070-38a1-19aa-ca59-42c4658bee7e@nvidia.com> <20200413062141.a6hmwipexhv3sctq@vireshk-i7> <64b609f1-efb1-425f-a91a-27a492bd3ec4@nvidia.com> <20200414054504.e3qn2cnxqur4sclw@vireshk-i7> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20180716-391-311a52 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 15-04-20, 16:55, Sumit Gupta wrote: > > > On 14/04/20 11:15 AM, Viresh Kumar wrote: > > External email: Use caution opening links or attachments > > > > > > On 13-04-20, 17:50, Sumit Gupta wrote: > > > This was done considering long delay value as explained previously. > > > Do you think that smp_call_function_single() would be better than work queue > > > here? > > > > Don't work with assumptions, you should test both and see which one > > works better. Workqueue should never be faster than > > smp_call_function_single() with my understanding. > Checked the time taken and its almost same in both cases. > Earlier we used smp_call_function_single(), but delay time period was small > in that SOC. In T194, the time period was more. So, this is an optimization > done because using work queue has advantage as interrupts will not be > disabled for that period. Hmm, okay, keep the workqueue and mention the required details in a comment for everyone to understand why the implementation is done that way. -- viresh