From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx0a-0031df01.pphosted.com (mx0a-0031df01.pphosted.com [205.220.168.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 0B69B3EF0DD for ; Wed, 21 Jan 2026 11:36:49 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=205.220.168.131 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768995411; cv=none; b=AKPdNvmTFaAtheHe3z1o8uGSw4pjrtCwTkG23PpdNsm2jakzJcIwqdqoa0wf7CMBrUOU7uZBMN6Lv7823WOWVMLZyswLI8FSYwRe+QCXQn4Qt4DIs+NDw2xhAd4W8fJr6ub66EH4glKq+nll0aH1OEscABb/LS46xNU1mXyij1s= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768995411; c=relaxed/simple; bh=TIo4eUNRcJupaJfar/Wjui1/HZPb+RRv0rkhGEuk/Hw=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=r//219jddbNDXnoieSFs9aIE5yeUHt3ozd1f0PRW2oImVqXhbXYJY184xixl+iOd0EZZs2xkC4OXO7blu1/c5TwMpNeRZfydvjWocj3LmsM87zwOitJq4BU4aThJGSGZxVrcCe/pZ6v2gULIipYlpKg+uYewEjxm5ZdqBzfUgfo= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=oss.qualcomm.com; spf=pass smtp.mailfrom=oss.qualcomm.com; dkim=pass (2048-bit key) header.d=qualcomm.com header.i=@qualcomm.com header.b=f7hgsYTG; dkim=pass (2048-bit key) header.d=oss.qualcomm.com header.i=@oss.qualcomm.com header.b=YvU9ttnZ; arc=none smtp.client-ip=205.220.168.131 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=oss.qualcomm.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=oss.qualcomm.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=qualcomm.com header.i=@qualcomm.com header.b="f7hgsYTG"; dkim=pass (2048-bit key) header.d=oss.qualcomm.com header.i=@oss.qualcomm.com header.b="YvU9ttnZ" Received: from pps.filterd (m0279864.ppops.net [127.0.0.1]) by mx0a-0031df01.pphosted.com (8.18.1.11/8.18.1.11) with ESMTP id 60L9euIi3991338 for ; Wed, 21 Jan 2026 11:36:49 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=qualcomm.com; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to; s=qcppdkim1; bh= +y5lKOS0WAt9c5KAoZ6HSMamjpbsexOX6flmBCX/kYU=; b=f7hgsYTGmQIm1iAn MN0Dv1796Hv9U6iNhw7K5w1KtzL/y0S/+g+65kDwxSNTJKlRIWwYw4sDG/Y91Osw klbdDm8WEfURpVpQ6u827pM+chI1Xao+x11BHQWaHGEzAFpIXcXdrV+IuTpgrFR+ LMzc0gLA6TJQnaS87voayUug7gpBVdkVo0UMqtdhYSp66bKZ+K+Krk4bbTXBQJkk 9hx5lFyBw0QoGRcPVF3lm73IJQ+8H1e3n2JEQqh2g5xSxzL58HwZjtr5OCXS1p5w w1rPvIYeZz6vsLxk6aNAXC9+f28xaqYvOwfOf0oX3gvUH99yjbCwxUnYCbdfAjA5 VjAstA== Received: from mail-qk1-f197.google.com (mail-qk1-f197.google.com [209.85.222.197]) by mx0a-0031df01.pphosted.com (PPS) with ESMTPS id 4btpm42161-1 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NOT) for ; Wed, 21 Jan 2026 11:36:49 +0000 (GMT) Received: by mail-qk1-f197.google.com with SMTP id af79cd13be357-8c52d47dfceso122115985a.3 for ; Wed, 21 Jan 2026 03:36:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oss.qualcomm.com; s=google; t=1768995408; x=1769600208; darn=vger.kernel.org; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=+y5lKOS0WAt9c5KAoZ6HSMamjpbsexOX6flmBCX/kYU=; b=YvU9ttnZ5IQDcSra7ysG6Co+va7aOogFmtknFEu9c2mgUJQH/ENM8Vv/W9Tvgs+aJ9 BkGrafit5M5ByRwKXMKhrIeLmKCIir+AhKXlB+50QPA+O3hzbw0rfN/2qBqtKu6EXLAw +2I1SgbLpyFn85UVdFUdREWuJ6drkS+hk93+p2PkjqymfsEzhJ9ucMy8OE+9SqXgK7VG XyGs0Hfhoe3dHdXTTGwjUxuH7DMRUQGdJhQm0R4RKCe1IeWA5284J4GOZMgtHwMOKpUu A9TC9RZgITlcy98egx4KLuk21An4N7uJBpAMFymdanOXOgwqZe32mHrcsoi8FMFuMgxN a/Rw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1768995408; x=1769600208; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :x-gm-gg:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=+y5lKOS0WAt9c5KAoZ6HSMamjpbsexOX6flmBCX/kYU=; b=ETDu/sKpZggLqSamKDBP+WENnINlu6H8O3D4e06SzcvdiJiglnRXSnkqeOweZAZAH5 pN81ylyo9lbPWi22+88TconpeGiBqBTGQrfILdYzu1xaY3hBB1oWD2/iJxDQXdcBrvKF NnxXYtmcDoB+cym0Smzz8gSvckycMi7YqtNEBo0OUhur1DMxQcemnMFaE1nA8l0+wgnt c23xI5Jp4d1T05pp4hvv4Zi+iQNqOF5oCYj7aoQOjdB9GwH/AjlsqfUnHmjjC3jk1GxV +WOy3kFwD4jBpo0deMBDL8NpZkjQZOkfd0jmPqzNFg4yF6Tvx+tcOlTnv4EizjrovVex lHLQ== X-Forwarded-Encrypted: i=1; AJvYcCXRdUsxuIAotq4xrUby1URHvaimEBwqLUMsBaCDs/OhSdMUh92Gz3isPct9T/Tvodc3tm/LfqkTk/b0Zt0=@vger.kernel.org X-Gm-Message-State: AOJu0Yzup4UNRLuGR0WVESl8Q3sXrMX0GnxfZY7/v7mBiHSW2tzcLmTx WCb+j5WmVNNY31kCt+Bub6qfb9j5jdhEIBoNOoXeh4E2WHk630FHjnhipmmnnng5Px/JaXYJt8d gsyIWaq0Ooajx4TBDqCl9qiDnspFO6YQFEWVKBowL+RIQuDGIZELqmjj6/IZ+U+vhaK8= X-Gm-Gg: AZuq6aKOirhc8Zx4cyOnLq3E7MjgIyV8f1LviVW599RQZEi5EiEhQwVe3h+7Fx9smZZ bV/QErLvHV0lf8UDkwlZYYjAwjslCehHjWYQJztdMn8knzMbFAnzXK0IXTIf7wkuKAkV++EZmQm j40+K7KXbx101o7h+8WQSk9FahAkcUQ/tQy5IcPLM66Jpy2e8jgLRxmsR+O2JlMZktXmEKoO4C9 5CnpNJwqFglcPW95WT6yKwPhjv5TMPuas9lB8/1BfGeRp6mJHsbcjPn6X+Wn84pUEmZNwOnI4l7 84Y4smZKkENgmmki7lmybjK/zClPVKDAG1nAAxFtrMKVksqoIYo8HIS+cRKrtJwGwD/GUWPsPv3 1h5m/imUcZJFq5Wm1BjqhaWlSNZ2j2uO98WAk9Jw4vA8KcTd3xsdVpKHxia2xQsVHKaM= X-Received: by 2002:a05:620a:4085:b0:8b2:5af3:7fce with SMTP id af79cd13be357-8c6a678d49cmr1805365285a.7.1768995408136; Wed, 21 Jan 2026 03:36:48 -0800 (PST) X-Received: by 2002:a05:620a:4085:b0:8b2:5af3:7fce with SMTP id af79cd13be357-8c6a678d49cmr1805363785a.7.1768995407662; Wed, 21 Jan 2026 03:36:47 -0800 (PST) Received: from [192.168.119.254] (078088045245.garwolin.vectranet.pl. [78.88.45.245]) by smtp.gmail.com with ESMTPSA id 4fb4d7f45d1cf-65452bce4f7sm15135672a12.6.2026.01.21.03.36.45 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 21 Jan 2026 03:36:47 -0800 (PST) Message-ID: <417f77ba-a0b0-4ba5-824d-8814b776c557@oss.qualcomm.com> Date: Wed, 21 Jan 2026 12:36:44 +0100 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH 2/2] arm64: dts: qcom: SM8750: Enable CPUFreq support To: Akhil P Oommen , Jagadeesh Kona Cc: Ajit Pandey , Imran Shaik , Taniya Das , linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, Sibi Sankar , Jassi Brar , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Bjorn Andersson , Konrad Dybcio References: <20251211-sm8750-cpufreq-v1-0-394609e8d624@oss.qualcomm.com> <20251211-sm8750-cpufreq-v1-2-394609e8d624@oss.qualcomm.com> <908b64f1-f6ac-4c5e-9c72-1174cba62017@oss.qualcomm.com> <99796cc0-f29b-40d0-b8bb-ebcbcc950b23@oss.qualcomm.com> <996f47de-5900-4a3a-9372-e5ea3ae31c8b@oss.qualcomm.com> Content-Language: en-US From: Konrad Dybcio In-Reply-To: <996f47de-5900-4a3a-9372-e5ea3ae31c8b@oss.qualcomm.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Authority-Analysis: v=2.4 cv=Jv38bc4C c=1 sm=1 tr=0 ts=6970ba51 cx=c_pps a=50t2pK5VMbmlHzFWWp8p/g==:117 a=FpWmc02/iXfjRdCD7H54yg==:17 a=IkcTkHD0fZMA:10 a=vUbySO9Y5rIA:10 a=s4-Qcg_JpJYA:10 a=VkNPw1HP01LnGYTKEx00:22 a=EUspDBNiAAAA:8 a=OKg4dU89TObxr1bLEbQA:9 a=QEXdDO2ut3YA:10 a=IoWCM6iH3mJn3m4BftBB:22 X-Proofpoint-GUID: 4d1XkVCznE05w9MLvh_Z_0UfVDADwbtU X-Proofpoint-Spam-Details-Enc: AW1haW4tMjYwMTIxMDA5NyBTYWx0ZWRfXztwdKJLnLLcn txQsZ98wNpFbt0E62xxaZuA1Z9hF2QTtHmJrIETa3+feXlLpkyQAGvHclVoCrzr1QrKE0ShdDJq PXjU36g9Tl8HUtf4UaT4qXxSaSYDattK9+p/y+QhncUWX++TXz9C1kJy3uSb1ePInoZdg9qhPSJ QCLrYl4xPTwyfRgEGzee5sI/Qy8quJjJIj+Qz7OKXcp7VC426RcUYN7YKrrQF6oDX1zy3G0xB3I PtBQtHd3ZJ1I2liuD8cIhn9rPk8cpOen892O8fyKIWW6l2KXnnXqGYen0VCf/30K55BnJHUThN7 XvFIR/iV62YkxwXYGPf28NhyqAWxIQBoS2g172LDoJDDOrtNmgbZ5/iMuMoj5VRvbhmCcJpJFKM FG/RznxtRUfKJjiZQVOM8KtL56al97+0LtDOy8Pyd4qWJ2/ic1gO63kfUS7RgSIcEHcD8zC2Ema 5yo4xnbNz0RsyNjfvXA== X-Proofpoint-ORIG-GUID: 4d1XkVCznE05w9MLvh_Z_0UfVDADwbtU X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.293,Aquarius:18.0.1121,Hydra:6.1.20,FMLib:17.12.100.49 definitions=2026-01-21_01,2026-01-20_01,2025-10-01_01 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 impostorscore=0 bulkscore=0 clxscore=1015 spamscore=0 lowpriorityscore=0 suspectscore=0 malwarescore=0 adultscore=0 priorityscore=1501 phishscore=0 classifier=typeunknown authscore=0 authtc= authcc= route=outbound adjust=0 reason=mlx scancount=1 engine=8.22.0-2601150000 definitions=main-2601210097 On 1/20/26 9:54 PM, Akhil P Oommen wrote: > On 1/20/2026 8:13 PM, Konrad Dybcio wrote: >> On 1/20/26 12:25 PM, Akhil P Oommen wrote: >>> On 1/20/2026 3:44 PM, Konrad Dybcio wrote: >>>> On 1/19/26 8:00 PM, Akhil P Oommen wrote: >>>>> On 12/11/2025 12:32 AM, Jagadeesh Kona wrote: >>>>>> Add the cpucp mailbox, sram and SCMI nodes required to enable >>>>>> the CPUFreq support using the SCMI perf protocol on SM8750 SoCs. >>>>>> >>>>>> Signed-off-by: Jagadeesh Kona >>>>> >>>>> Just curious, does this patch enable thermal mitigation for CPU clusters >>>>> too? >>>> >>>> If nothing changed, we have lets-not-explode type mitigations via LMH, >>>> but lets-not-burn-the-user would require a skin temp sensor to be >>>> wired up, which then could be used to enable some cooling action >>> >>> In some chipsets, I have noticed that the gpu cooling device throttles >>> GPU to the lowest OPP even with not-so-heavy GPU workloads, making it >>> unusable-ly slow. My hypothesis was that it was due to unmitigated CPU >>> temperature tripping up GPU Tsens. >>> >>> So, I am wondering if there are any additional CPU cooling related >>> changes required to get a reasonable overall performance under thermal >>> constraints. >> >> Yes, something like the aforementioned skin-temp sensor at least.. > > I suppose this sensor is off-chip and slow to react. Yes, this would be placed somewhere on the chassis of the device to reflect the actual temperature that the user could experience (since there are regulations about maximum values of that) >> Today Linux will not throttle the CPUs at all (they're not even declared >> as cooling devices) and we sorta agreed that in general it's a good thing >> (tm), because otherwise we'd be coding in a cooling profile into the SoC >> DTSI without taking into account the cooling capabilities of a given end >> device (i.e. in an extreme case, a PC with SM8650 with a cooler that's >> 3kg of aluminium vs a Steam Frame headset where the SoC is centimeters >> away from your face) >> >> Currently, we have cooling policies for devices with fans and the only >> other action is based on a skin temperature sensor (sc8280xp + x13s). >> Everything else is left up to the LMH defaults. AFAIK work is ongoing to >> create a more informed solution, that would have to (quite obviously) >> live in userland. > > I can understand that the skin-temp based mitigation is influenced by > various design decision outside of the SoC die. But I think there should > an on-chip sensor based mitigation which is fast and usually for a short > duration which helps to avoid extreme temperature or violating the > maximum operating point of the chipset. I guess it should depend only on > the SoC characteristics as it is a last resort. It may be implemented in > SW (like cooling device for Adreno GPU) or in HW. Probably the LMH > hardware you mentioned offers this functionality for CPU clusters. I > have no clue. :( Yes, the CPUs are covered. > I am hoping that if this on-chip mitigation is enabled and wired up > correctly for CPU clusters (probably DDR too), it would reduce the > unnecessary thermal trips on GPU Tsens and help to reach a performance > equilibrium which is reasonably good. Today, the OS is unaware that it can throttle anything else than the GPU, so in its view that's the reasonable step to take. Further, any device it knows how to throttle, it'll do so in a very jittery fashion where it crosses the threshold, gets slowed down, cools a bit, gets unthrottled, heats back up, rinse and repeat (because the cooling solution of almost any form-factor is not capable of sustaining a 100%usage workload for long) Konrad