Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp628598imm; Wed, 22 Aug 2018 09:49:57 -0700 (PDT) X-Google-Smtp-Source: ANB0VdYaIpbKRC0iUboUBDPB2NvleDzTTLzcvzqPaOtn2mLN+dIA8vy3/rKozEXrsTz4Cb2Q1wlm X-Received: by 2002:a63:9809:: with SMTP id q9-v6mr6813568pgd.27.1534956597365; Wed, 22 Aug 2018 09:49:57 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1534956597; cv=none; d=google.com; s=arc-20160816; b=0d9RBRR9ff/ryP76PN4q8CHo4TJO7Ed7qVRi4gTEdf3kUFySsrZUPBwAmkXdxZAnbe Dro9uwsWv7CZ0iAGddNYSw0o/UhM9qxVkCcaiplyXzdKqgwR4ION09n3wACjs2p3ornB KAnGm79V9viLQV99kzPjW1takRLXf8vz0RXj+bssD6OUAmFcE4UWumeldWQpvNZWwTRO CJxVbQMRKRSt+mPUywsE+ftOcxcMGI9SZF9lrVkv4FkTSEx9b3vCnxIfZOj4t9NV0u4j iLoIpAAHmW8cmqnmx5w3dI/HXK9F3x5EIc9vayzHayjen5kbiplotZERzNuLr5wP2mYn fP+g== 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 :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dmarc-filter :dkim-signature:dkim-signature:arc-authentication-results; bh=o6KswbQt+aNK4g9tvLLzhIFWR91Iw4EH/Kf1SGe7MJE=; b=E8KDq9e8J0EqC6UQqKR8C4zmM4ajave3WCK11lj2MTysmqU6P6N/zrC/HilK8y7O5l 8LEuZ3L4WNA6lwYIMoEGHJLO7ey7oVusSDpdeKDZ4BtqnCn92V3Hcp0TW7SWKxsJYcal difbM7haDXAAjvnFEN6El06wZjJzhwOyv9hp5Dm99rgz0tzIT1g4/3cvJPAWI+cvN+Dh 34vXRsPwdeIBdoqBebplnfVOVds3cZK5p6L6tNTbOEKI59xMrgk3VhuDJQ2wLAgULh8z eGB4fGGiNyof5snFtS9FxmbrTz9/jGCglsgSXbc1gdqYMhlGuN4BFUiNfObkYHLsfmAz AmJg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@codeaurora.org header.s=default header.b=QjtyBSXZ; dkim=pass header.i=@codeaurora.org header.s=default header.b=OWmYLT4i; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f2-v6si2084259pgg.552.2018.08.22.09.49.41; Wed, 22 Aug 2018 09:49:57 -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=@codeaurora.org header.s=default header.b=QjtyBSXZ; dkim=pass header.i=@codeaurora.org header.s=default header.b=OWmYLT4i; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727095AbeHVUOH (ORCPT + 99 others); Wed, 22 Aug 2018 16:14:07 -0400 Received: from smtp.codeaurora.org ([198.145.29.96]:36944 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726550AbeHVUOG (ORCPT ); Wed, 22 Aug 2018 16:14:06 -0400 Received: by smtp.codeaurora.org (Postfix, from userid 1000) id 83B3E60275; Wed, 22 Aug 2018 16:48:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1534956509; bh=0bKtRcGHYMsSUoco/auyLHE/2s6UEOI4ocRsNFGloBc=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=QjtyBSXZvxdeA/NRpYR9Wcoei0DdsAUjHsMgw3YEZx0KRvn+pJRrcSPFADXsFiC8N eGrL08vAEqxuE/puZ0b87qJiNFlTJqPToBCB+owJiNywvxuZ013F3ONmlWlC+jA73V FXnr/KZFSQ2KQakf95d2hQSoK7prUI2gbDguNn34= X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on pdx-caf-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.8 required=2.0 tests=ALL_TRUSTED,BAYES_00, DKIM_SIGNED,T_DKIM_INVALID autolearn=no autolearn_force=no version=3.4.0 Received: from [10.226.60.158] (i-global254.qualcomm.com [199.106.103.254]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: rkumbako@smtp.codeaurora.org) by smtp.codeaurora.org (Postfix) with ESMTPSA id 66F3C60275; Wed, 22 Aug 2018 16:48:28 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1534956508; bh=0bKtRcGHYMsSUoco/auyLHE/2s6UEOI4ocRsNFGloBc=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=OWmYLT4isanxQGAzt8JtZF17SN6JzU6Xp1mvPqYXU4qabS+nOe2SljrImc5YexoU4 HRIosTE+7LUoGb6oePLToi+KMHRnPC02+PR5dDbzpJ61cjB3zIYmgoUhw+0XLY2TNA CAqeUR9iu0zS3A4Yp9brx2UzMtn2bL1eUXFO15Dw= DMARC-Filter: OpenDMARC Filter v1.3.2 smtp.codeaurora.org 66F3C60275 Authentication-Results: pdx-caf-mail.web.codeaurora.org; dmarc=none (p=none dis=none) header.from=codeaurora.org Authentication-Results: pdx-caf-mail.web.codeaurora.org; spf=none smtp.mailfrom=rkumbako@codeaurora.org Subject: Re: [PATCH] drivers: thermal: do not clobber cooling dev state from userspace To: Lina Iyer , Zhang Rui Cc: edubezval@gmail.com, linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org References: <20180507175505.2389-1-ilina@codeaurora.org> <1532595308.2358.45.camel@intel.com> <20180814180447.GJ5081@codeaurora.org> From: Ram Chandrasekar Message-ID: <1fa9d64d-0f52-dba2-8777-799fa9272581@codeaurora.org> Date: Wed, 22 Aug 2018 10:48:27 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: <20180814180447.GJ5081@codeaurora.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 8/14/2018 12:04 PM, Lina Iyer wrote: > Adding Ram, so he can respond. > -- Lina > > On Thu, Jul 26 2018 at 02:55 -0600, Zhang Rui wrote: >> On 一, 2018-05-07 at 11:55 -0600, Lina Iyer wrote: >>> From: Ram Chandrasekar >>> >>> Let userspace be another voter for cooling device state instead of >>> the >>> overriding authority. It is possible that the thermal governor may >>> find >>> a higher cooling state desirable than what is recommended by the >>> userspace. Separate out the current cooling device state from the >>> userspace request and aggregate the userspace request with the >>> governors' recommendation. >>> >> >> hmmm, I don't understand this. >> If the governor does not work well, we should either improve the >> governor or use userspace governor instead. >> do you have any examples that the kernel governor chooses improper >> cooling state? >> Userspace governor and kernel governor could monitor different thermal zones for different thermal conditions and mitigate the same cooling device. In this case, the cooling device state request from userspace governor shouldn’t overwrite the request from kernel governor, rather it needs to be aggregated. This change is to aggregate the cooling device state requests between the userspace and kernel governors. Thanks, Ram