Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id AF546C38142 for ; Mon, 23 Jan 2023 18:02:38 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233375AbjAWSCh (ORCPT ); Mon, 23 Jan 2023 13:02:37 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40880 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233321AbjAWSCg (ORCPT ); Mon, 23 Jan 2023 13:02:36 -0500 Received: from mail-wm1-x334.google.com (mail-wm1-x334.google.com [IPv6:2a00:1450:4864:20::334]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D4A692CFC5 for ; Mon, 23 Jan 2023 10:02:34 -0800 (PST) Received: by mail-wm1-x334.google.com with SMTP id l8so9704055wms.3 for ; Mon, 23 Jan 2023 10:02:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=yk2fX5q0jXoyVU2uukxJAFScsvm4XeRwSWczxQlKv7c=; b=qVg6gV5Bi3EkI4zHTcNGByKaQjGFOvWPkBlorpwTICHLWmVwrLQrcfzy/pakxNgb4Z t0obd8NOlg5OQGEGZeM+JLUmnxOFZZmvzHfTkuJpSMMWrGeb5DbHs0A2lbl7xXY0ojAM 9Jwdo85MZEtuQI+eN5SBsoN6aykHJ4v0sC25XWV55+4Fbzq0ijYWhzsrn4C1JKHyjQe3 b59kTAt2uuwxE6RgBuqnrjH99UJzmNuHDV/3biLsCEtClktzXNKoenweJq8vmTA2J5jx cdsT/4Cn2zZz5M9VW8ZI/OqX67Sc23sU6Hu86Ec3RzdOPCW0n0NncMu0cdgm9iB18XqN 4F9A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=yk2fX5q0jXoyVU2uukxJAFScsvm4XeRwSWczxQlKv7c=; b=aPHi//r28qiqP8aVpzVVyL92aU0rMe1CKUnNUbNP2IAJ0DIjgb0c4rNf/04w5SPSMN cgG6l9k9nJXI6eKJkW2Ld1mZpDkR4bz8l0kgIu/49ZuEEbMsBDm/f7YKwSopvOSrAFL6 mgQqjQbljVaEjspzHvC5J4hLdJ4w8ypsyVo0rMyECyANkaPf9WC+brXoVWIDOrp7XcZ7 +FeZwecodbWDJpwpwGpS5NNRHcqW64KSnckdEb6XFqJH1/aEb3hr4x+VnsD8mSO65aIy 39qe+6GtNFRpcoMXm7RGV8RA4hE8v6GKMHNDzo4OaVZvxhErnTr6mdYE0M2DhF8YO31k oMAw== X-Gm-Message-State: AFqh2krwfSrBbFwBisXm4OOI7tcaIHAjW1Yuu4H7HTA1mhPlGi0cteVk hxFjuERk+4owRWm/7ear4gOXXA== X-Google-Smtp-Source: AMrXdXvWK2tDK4Ma8vpazDen+DCctMU1tiawaFCNhCgqr3FDwfsmSpAB9iG7lkjLzjTOIU1xSNynqg== X-Received: by 2002:a05:600c:4fcb:b0:3db:1919:41b5 with SMTP id o11-20020a05600c4fcb00b003db191941b5mr19016437wmq.21.1674496953315; Mon, 23 Jan 2023 10:02:33 -0800 (PST) Received: from [192.168.10.46] (146725694.box.freepro.com. [130.180.211.218]) by smtp.googlemail.com with ESMTPSA id m18-20020a05600c4f5200b003cffd3c3d6csm12116756wmq.12.2023.01.23.10.02.32 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 23 Jan 2023 10:02:32 -0800 (PST) Message-ID: <7b263423-11f8-d3e8-d040-e045dc2fb74c@linaro.org> Date: Mon, 23 Jan 2023 19:02:31 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2 Subject: Re: [PATCH 2/3] thermal/drivers/intel: Use generic trip points for processor_thermal_device_pci Content-Language: en-US To: srinivas pandruvada , rafael@kernel.org Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org, rui.zhang@intel.com, Amit Kucheria , Sumeet Pawnikar , Shang XiaoJing References: <20230118181622.33335-1-daniel.lezcano@linaro.org> <20230118181622.33335-2-daniel.lezcano@linaro.org> From: Daniel Lezcano In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Srinivas, On 18/01/2023 20:09, srinivas pandruvada wrote: > On Wed, 2023-01-18 at 19:16 +0100, Daniel Lezcano wrote: >> The thermal framework gives the possibility to register the trip >> points with the thermal zone. When that is done, no get_trip_* ops >> are >> needed and they can be removed. >> >> Convert ops content logic into generic trip points and register them >> with the >> thermal zone. >> > In this scheme is the assumption is that trip point temperature never > changes? If firmware updated the trip temperature, what needs to be > done? I'm a bit confused about the situation where the firmware can change the trip point in the back of the OSPM. Does the firmware send a notification about the trip change? Or does it assume the OSPM will be reading the trip point while monitoring/polling the thermal zone ? Is the question for this particular driver? If the trip point is changed by the userspace (via sysfs), thermal_zone_set_trip() is used which in turn changes the thermal trip temperature directly in the generic structure and then calls the back set_trip_temp. -- Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog