From patchwork Tue Jul 16 09:54:54 2019 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Viresh Kumar X-Patchwork-Id: 169050 Delivered-To: patch@linaro.org Received: by 2002:a92:4782:0:0:0:0:0 with SMTP id e2csp619357ilk; Tue, 16 Jul 2019 02:55:32 -0700 (PDT) X-Google-Smtp-Source: APXvYqzOpjrIkvFiHNiAUGiRJ6cB7bbETcR55bh0tlmgAvNdU6ic+Q5byd1K1yYbFNwORL/hyC4x X-Received: by 2002:a17:902:b582:: with SMTP id a2mr34606160pls.128.1563270932837; Tue, 16 Jul 2019 02:55:32 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1563270932; cv=none; d=google.com; s=arc-20160816; b=cfHBgI255hoDmuQE90jcEBVM4cwWbCLceFI7ODOYEsrjpByZ6IqT3PStISl3gdjlz0 2//jZjb7/QVP74JAPwcdWc9QU/9RgQzsJLAyMuFqoiBn08IxIFKVBB1YU+J/HaAWQMbJ k/PfoojfNnQycG9Wop7imDBIS5QftUY/4r5SwccY710VPXOpAlHtbqg8cHBXW4IOhfEl /jH9V1QyYsvnDsPWMAc6Vy5blAsUXSPUtj/n4S402hsWty5+UFBVoDdqQem+8iTdvaZa E9uWZ0CkWopdw6fl8iriNVyFVtKtA1iogrYyM6hDLMFCPasBOKznk5ZQRfKnGY7SLd/5 F75g== 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=j9CPag+ihAeKmeHNKcPHDy3IUTBk0GySQWFpNM7jlh0=; b=QNdAxJ5lvJG1rZnN55H5zYyTgJ1wCoPl7sXccz4VSLYHWoAxFwMhnOLMH7Y4BeNKBP VXW4Z1XAcOsQG5ObIp8jAX7W5E6FS5u7soMaOltHCvxIDIwCnLRHoNKd6VTlxbEgYons hgK4OyzbkmjkvS+ZbrG97bUBk55Z7GJwvtP+PQFol+0IybwQ07wT6WkGuCKCzRiC6uJg RKXq5gziejuAuouwtguVuGzqYxgSJNTltwTO4gQzGc0G+0RxckIFr1q7BtPKGpW2DpOd bl2i8lJOQT+bcWQU5YyZOp278DlVAlHAjj0MbErbvg6wN3l17QgiSauXet2HCgsPFi+i cvCA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=uakV8TcQ; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 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. [209.132.180.67]) by mx.google.com with ESMTP id a24si20313130pfi.205.2019.07.16.02.55.32; Tue, 16 Jul 2019 02:55:32 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-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=uakV8TcQ; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 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 S1733311AbfGPJzb (ORCPT + 29 others); Tue, 16 Jul 2019 05:55:31 -0400 Received: from mail-pg1-f193.google.com ([209.85.215.193]:44011 "EHLO mail-pg1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1733254AbfGPJz1 (ORCPT ); Tue, 16 Jul 2019 05:55:27 -0400 Received: by mail-pg1-f193.google.com with SMTP id f25so9173069pgv.10 for ; Tue, 16 Jul 2019 02:55:27 -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=j9CPag+ihAeKmeHNKcPHDy3IUTBk0GySQWFpNM7jlh0=; b=uakV8TcQGVyYIY3mCGPNuqIsaoT779Q6itiqhB5woh+Rh4UZK047zRIWVEwZGqm/Uo R9tyHSLa4YS1kRHGj0xlEB4bsQaC6dKp7/BR7xQ9fqA3/riZMPfZnU4YUvqHvPKfuUV0 yzMy0zq1h1C1ra+z/k+whZQAJ7TmP9A70pJlzHhumNS5RQ8wousuAAKMnLmbiaPvlGT8 DC1MBvbhsZFOVnhcAAfU0Z7VCn+5kx18m7HOrXgrfUqQIEKP+w6TL498T8V0cCSI0JN4 0l8eUsimM2NqHmfrb68Lf/PYsX4n4eCZwcs6oGHdDFl3oa7zTKk+NBCKbDLWRiSeEk4v 5fuw== 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=j9CPag+ihAeKmeHNKcPHDy3IUTBk0GySQWFpNM7jlh0=; b=BKQ54Blf2Lmo2Qi2yJ9JiYoOne+dmj1Muzb3lon3UDrxNctE0g1qVc8SM/4ZXoi9Ar /TjJQ4w7BEr2pUxjSEmmW8ksqZLzB3VLz/RvbuGbLl+3n/YjawQEwgeeaddVJuYMIB2e cKyWI+DcbmvaCfP+7x5e/f1yzUh5IUdG+ifiyq7b64SSq297OObpA9+A5fkyIzyllOcp m4eAKMdvqFfdYeUfQaZOhdbsKNqculc5rIRGJ0PDL5BDZ+QdRf8hvOzfJdoVt3KLLSwY +8x6oDn8l+W/xFM0S9OI7rTsVywsL8xN6cjr6BCdIjVhSJz0a8iKF6XG07LUUIv7Fpsw UIYg== X-Gm-Message-State: APjAAAUbfNv0hLh5jCZ9eHNcYcIu7vWY8jZ38T3TjOWxPNkzev7jodV9 uNewPnLM8Wsl4oqNOensDL6zLQ== X-Received: by 2002:a65:50c8:: with SMTP id s8mr25725239pgp.339.1563270926697; Tue, 16 Jul 2019 02:55:26 -0700 (PDT) Received: from localhost ([122.172.28.117]) by smtp.gmail.com with ESMTPSA id 21sm8260153pfj.76.2019.07.16.02.55.25 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 16 Jul 2019 02:55:26 -0700 (PDT) From: Viresh Kumar To: Rafael Wysocki , Viresh Kumar Cc: linux-pm@vger.kernel.org, Vincent Guittot , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH 10/10] Documentation: cpufreq: Update policy notifier documentation Date: Tue, 16 Jul 2019 15:24:54 +0530 Message-Id: <437a6b7e7876b6edee52f7ef829ee905b14d89a5.1563270828.git.viresh.kumar@linaro.org> X-Mailer: git-send-email 2.21.0.rc0.269.g1a574e7a288b In-Reply-To: References: MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@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 073f128af5a7..af5c0d60b466 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