From patchwork Tue Jul 23 06:14:10 2019 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Viresh Kumar X-Patchwork-Id: 169483 Delivered-To: patch@linaro.org Received: by 2002:a92:4782:0:0:0:0:0 with SMTP id e2csp8446957ilk; Mon, 22 Jul 2019 23:14:54 -0700 (PDT) X-Google-Smtp-Source: APXvYqwybxtf9y13fH19hYCtq7PzZGlHM1En3/keE/ylJfkdwlBWshDWc4HPpIyuBxZ6H3JLn8ic X-Received: by 2002:a65:404d:: with SMTP id h13mr73440425pgp.71.1563862494832; Mon, 22 Jul 2019 23:14:54 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1563862494; cv=none; d=google.com; s=arc-20160816; b=WcqrG6kFLOaGDLoCbfr7ldvleY4XkoBDi33iae9oowO1b++yChQQHNvEKUM1T6OWju ap0sFMLkTlMtz8QlF5hw7Uc4Hqn+WKD3AkbZyaP7Fs3PpGY7Ygx38Xf4pc3sfvB7zk+7 I4ZrcxKq+iUP9of/FRiGFRSg8x7wblxLN/LW3bbemg9wzV8uTLe4OY0EeLYgmGkwUdrB BcCnp4I1EBM5JXJGhuGIkp+Vfz7M+YvyzCAOAoz4khqvLvqAzoEVdw5mJj0LIPiKz//Q np3DZQDM5a5y3CXsvpxMXBTPIjtMcb8aolHBSnXC4LXW2eAQjBUmsVF5JX1JNKMUDKHX lyWg== 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:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=pE9tUu3P/8w1bftggmV11VxGbS0rl+eqvKACn21icvM=; b=kqxZ0H/ftWoO89zoFcfRSaT9PZ0a0SSw7AZQdFgYfObO0mX25AshwHATy0j24gMVpQ 9q/sbzR9NaBSqtrAFiy5hraBZimwKgyU4BKu24+eZAYxEkQccScN1tz1OSzL29xp/WpL 4G7pCg/VtPpMrvovAz5qHIBkZIk2hEr4mwa0vFzXTWu4ZZmXSkJx8FUnJGJDAgG1ErZJ qRMRBX2g0yRnpmyiQcaSVzy4djrBEZ+ve/+Hu6efkkIi3fhhXkucfwILewIdHprmwKfx YIzLnI5g9hAU+VFKZoCjLqs0NvbPcl3d+hWkl+6xHGqKUrSs5is8yWz3RuEzs1BNyEyn Jn3w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=ukFG103P; spf=pass (google.com: best guess record for domain of linux-pm-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-pm-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. [209.132.180.67]) by mx.google.com with ESMTP id 189si12002942pgj.416.2019.07.22.23.14.54; Mon, 22 Jul 2019 23:14:54 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-pm-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=ukFG103P; spf=pass (google.com: best guess record for domain of linux-pm-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-pm-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 S2388163AbfGWGOx (ORCPT + 11 others); Tue, 23 Jul 2019 02:14:53 -0400 Received: from mail-pg1-f194.google.com ([209.85.215.194]:38354 "EHLO mail-pg1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2388176AbfGWGOx (ORCPT ); Tue, 23 Jul 2019 02:14:53 -0400 Received: by mail-pg1-f194.google.com with SMTP id f5so10041572pgu.5 for ; Mon, 22 Jul 2019 23:14:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=pE9tUu3P/8w1bftggmV11VxGbS0rl+eqvKACn21icvM=; b=ukFG103PF/bL7cLvjS/DEUm8Y+TFfzbryVSM7lnY7E2JAgqNadFQXZ+zzONmjxQRvN /UNtFxcDJE9E6GT1fFhmaNEdT0U6LY+fM7OLyuzdFbiF9pq/AOtrPPYgpCD7pQyMpqT8 RxNXI3sOAH+3hgE3B2gEyn6lDVa9opE8HSLJBn14tv10YYA8aPxKAtF8dkorCTcbJOLV JO7eYBtRjWSkQ5J09nJfN2iaEb1vbuaov0kgzMGIN6hiJzic3uaEe2jgeHQrAJIqdUZn DjqcHIFUYDCeqAjsTvjUIo5ZGlM7ySIuaLaeWa7YvtT2/mQ9Y+PamXkRp5Yyii2rH4zi ipuA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=pE9tUu3P/8w1bftggmV11VxGbS0rl+eqvKACn21icvM=; b=Ggz4vbJpAkk69HrXCNBGjkzSWveyUm3P3Hpn4zRNZS1ST8yjdo76d7T3fKDoOCnyR7 3wv0YaDruIlQ+Sf9r0apFUhoSIfyt7jtz2ILpOwnHT8qCuJ9RWNHrqQjwMJIKaCdfWDL v1U5bHgT7Fr9l+j2UEL00MMOk4ihST5UGB64k9/irvlMUztG5EQhTipOEXyZ1Z1i2ams 2xgANhwf+oR35mO7iNt3oN+RvGrRr4PqESeQH9MNcU7mr/LjfrLv2YhH5VjM1fg/IVcj UtkyTg0Ys9Z1IWatLNYLQBumiEnqj2zG1iKxJpJ9MfKGWFZ2+y99xAayY2/vyat12j8+ Mdaw== X-Gm-Message-State: APjAAAXqEqTyPXG8mSe88FRhbCjh/FwgNtDr3g/kR5YAYN0xdzZ2QjOr 9ZAtMwEDFhu7xPsUNFtvMVQBVYM0oQI= X-Received: by 2002:aa7:90d8:: with SMTP id k24mr4051781pfk.115.1563862492359; Mon, 22 Jul 2019 23:14:52 -0700 (PDT) Received: from localhost ([122.172.28.117]) by smtp.gmail.com with ESMTPSA id f3sm65402869pfg.165.2019.07.22.23.14.51 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 22 Jul 2019 23:14:51 -0700 (PDT) From: Viresh Kumar To: Rafael Wysocki , Viresh Kumar , Jonathan Corbet Cc: linux-pm@vger.kernel.org, Vincent Guittot , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH V2 10/10] Documentation: cpufreq: Update policy notifier documentation Date: Tue, 23 Jul 2019 11:44:10 +0530 Message-Id: X-Mailer: git-send-email 2.21.0.rc0.269.g1a574e7a288b In-Reply-To: References: MIME-Version: 1.0 Sender: linux-pm-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-pm@vger.kernel.org Update documentation with the recent policy notifier updates. Signed-off-by: Viresh Kumar --- Documentation/cpu-freq/core.txt | 16 ++++------------ 1 file changed, 4 insertions(+), 12 deletions(-) -- 2.21.0.rc0.269.g1a574e7a288b diff --git a/Documentation/cpu-freq/core.txt b/Documentation/cpu-freq/core.txt index 55193e680250..ed577d9c154b 100644 --- a/Documentation/cpu-freq/core.txt +++ b/Documentation/cpu-freq/core.txt @@ -57,19 +57,11 @@ transition notifiers. 2.1 CPUFreq policy notifiers ---------------------------- -These are notified when a new policy is intended to be set. Each -CPUFreq policy notifier is called twice for a policy transition: +These are notified when a new policy is created or removed. -1.) During CPUFREQ_ADJUST all CPUFreq notifiers may change the limit if - they see a need for this - may it be thermal considerations or - hardware limitations. - -2.) And during CPUFREQ_NOTIFY all notifiers are informed of the new policy - - if two hardware drivers failed to agree on a new policy before this - stage, the incompatible hardware shall be shut down, and the user - informed of this. - -The phase is specified in the second argument to the notifier. +The phase is specified in the second argument to the notifier. The phase is +CPUFREQ_CREATE_POLICY when the policy is first created and it is +CPUFREQ_REMOVE_POLICY when the policy is removed. The third argument, a void *pointer, points to a struct cpufreq_policy consisting of several values, including min, max (the lower and upper