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;
From:   Daniel Lezcano <daniel.lezcano@linaro.org>
Subject: [RFD] Remove the userspace governor and the cooling device set state
 sysfs entry
To:     Zhang Rui <rui.zhang@intel.com>,
        "Rafael J. Wysocki" <rjw@rjwysocki.net>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Linux PM mailing list <linux-pm@vger.kernel.org>
Message-ID: <d46b5007-428b-5f31-52d9-a964cc60ad92@linaro.org>
Date:   Wed, 22 Sep 2021 11:59:32 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.13.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Precedence: bulk


Hi,

the userspace governor is sending temperature when polling is active and
trip point crossed events. Nothing else.

In the other side, the cooling device have their cooling device
set_cur_state read-writable all the time.

The thermal framework is wrongly used by userspace as a power capping
framework by acting on the cooling device opaque state. This one then
competes with the in-kernel governor decision.

As the new netlink thermal notification is able to provide the same
information than the userspace governor.

I propose to remove the userspace governor and the cur_state entry in
the sysfs exported file.

The DTPM framework is the right framework to do power capping and
moreover it deals with the aggregation via the dev pm qos.

Does it make sense ?

  -- Daniel

-- 
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog