From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx2.zhaoxin.com (mx2.zhaoxin.com [61.152.208.219]) (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 9B21338A28E for ; Thu, 22 Jan 2026 02:18:30 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=61.152.208.219 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1769048313; cv=none; b=GK6u1tHcwI+IC2M3SL6bMzFaHdMd/37H49SVnfd35ZbKVD3lW18w5hTu0de5FJ4+w8bQd0rtJmev2KyJxMvqfOk7M2pO23DJXLVukWYbbYgKF4n4SxjqUKuEyHSmqj0Z7xvgoG9qDIagmuK6sqxFINTptETDJU9EJWLaC27pUPo= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1769048313; c=relaxed/simple; bh=mc8oAqdPKTrLSgBk9ssD4ehgVOIYktLIFwYhAv2PF6g=; h=Message-ID:Date:MIME-Version:From:Subject:To:CC:References: In-Reply-To:Content-Type; b=T7V3PRbRHV7lg7T/dHmSdlVR2YjhmfKfI0ZkwxuzNxuuFJYWHj7R/SDtK+Vc/vhhSBJNW6FpoaBlj4Uq1XJV3bNsAafBjmuCqf90Fc4LIaSaAdirDb9uehV0/laUMBmZxFOs1AheD85ooLuIAo7QifcazhKzoHc/rvqjVeWUceU= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=zhaoxin.com; spf=pass smtp.mailfrom=zhaoxin.com; arc=none smtp.client-ip=61.152.208.219 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=zhaoxin.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=zhaoxin.com X-ASG-Debug-ID: 1769048306-1eb14e7c0425a80001-xx1T2L Received: from ZXBJMBX03.zhaoxin.com (ZXBJMBX03.zhaoxin.com [10.29.252.7]) by mx2.zhaoxin.com with ESMTP id BsFZw2z7U3h3jF4U (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 22 Jan 2026 10:18:26 +0800 (CST) X-Barracuda-Envelope-From: TonyWWang-oc@zhaoxin.com X-Barracuda-RBL-Trusted-Forwarder: 10.29.252.7 Received: from ZXSHMBX1.zhaoxin.com (10.28.252.163) by ZXBJMBX03.zhaoxin.com (10.29.252.7) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.59; Thu, 22 Jan 2026 10:18:25 +0800 Received: from ZXSHMBX1.zhaoxin.com ([fe80::936:f2f9:9efa:3c85]) by ZXSHMBX1.zhaoxin.com ([fe80::936:f2f9:9efa:3c85%7]) with mapi id 15.01.2507.059; Thu, 22 Jan 2026 10:18:25 +0800 X-Barracuda-RBL-Trusted-Forwarder: 10.29.252.7 Received: from [10.32.64.8] (10.32.64.8) by ZXBJMBX03.zhaoxin.com (10.29.252.7) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.59; Thu, 22 Jan 2026 10:13:28 +0800 Message-ID: Date: Thu, 22 Jan 2026 10:13:29 +0800 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird From: Tony W Wang-oc Subject: Re: [PATCH] cpufreq: Add CPU frequency policy change notification support To: Viresh Kumar X-ASG-Orig-Subj: Re: [PATCH] cpufreq: Add CPU frequency policy change notification support CC: , , , , , , References: <20260120092445.5711-1-TonyWWang-oc@zhaoxin.com> <345044bb-15e8-48d3-bc03-d5f327aeb3ae@zhaoxin.com> Content-Language: en-US In-Reply-To: Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit X-ClientProxiedBy: zxbjmbx1.zhaoxin.com (10.29.252.163) To ZXBJMBX03.zhaoxin.com (10.29.252.7) X-Moderation-Data: 1/22/2026 10:18:18 AM X-Barracuda-Connect: ZXBJMBX03.zhaoxin.com[10.29.252.7] X-Barracuda-Start-Time: 1769048306 X-Barracuda-Encrypted: ECDHE-RSA-AES128-GCM-SHA256 X-Barracuda-URL: https://10.28.252.36:4443/cgi-mod/mark.cgi X-Virus-Scanned: by bsmtpd at zhaoxin.com X-Barracuda-Scan-Msg-Size: 1166 X-Barracuda-BRTS-Status: 1 X-Barracuda-Bayes: INNOCENT GLOBAL 0.0000 1.0000 -2.0210 X-Barracuda-Spam-Score: -2.02 X-Barracuda-Spam-Status: No, SCORE=-2.02 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=9.0 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.153386 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- On 2026/1/21 18:02, Viresh Kumar wrote: > > > On 21-01-26, 16:37, Tony W Wang-oc wrote: >> The expectation is to register a notifier of type CPUFREQ_POLICY_NOTIFIER >> via cpufreq_register_notifier in one of our drivers. The notifier callback >> will configure Zhaoxin registers to different values based on the different >> cpufreq governors when the event is CPUFREQ_GOVERNOR_CHANGE, thereby >> allowing the Zhaoxin hardware to adopt different power management >> strategies. > > Firstly, for this change to be acceptable, we would need your upstream > platform specific changes as well. > > And then I am still not sure if this it the right way to solve this > problem. > The driver for Zhaoxin using this patch still needs further verification on actual platforms; it cannot yet be submitted to the mainline. However, we have already verified that this patch itself has no issues with Zhaoxin's driver. From the perspective of this patch itself, we think it provides the capability to perceive changes in cpufreq policy for all modules concerned, and it can serve not just this Zhaoxin driver. Sincerely TonyWWang-oc