From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=74.125.227.138 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1793093515; b=P83z9jQf8knMh0fj3eaUsVXMVi1MhwLmLLEaejOUXKPSFORL0JTttCzkHQpeykRUwOJ1 fGJ7QGC8h+IVQ6mt6k4Un3ndf9eeeM5uBdvd2TVVv14vJ15RA+tTstxk7pnvbNub9W9a8 Z+FCxBn7CI2G7N4SZCaouNK6vOLH6vQs8eJOuYHLptRJsEZLuBgG8gJnWLazi/lVbp7si 5jGzXQgS7fsCKq51i87F4edCTkrL0dhvI30elhYeuxxYLjW8Mmpu6YGEViSSompeRwonB sIy85gkxfBNa3wl9Jz7JuWbCXOChTj35gXlYejSWhroWczIDAc284iUlVn89EOJd//Q== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1793093515; h=DMARC-Filter:Received:DKIM-Signature:X-Google-DKIM-Signature: X-Forwarded-Encrypted:X-Gm-Message-State:X-Gm-Gg:X-Received:Received: Message-ID:Date:MIME-Version:User-Agent:Subject:To:Cc:References:From: In-Reply-To:Content-Type:Content-Transfer-Encoding; bh=0lp8ix384KyuQihbhJDejl7Hsm+NKly5D1mQFcd+Ymw=; b=ypCYgrbAeNwhAbOYdvkQor4Ah3I7TaF7mtIJY7uesGrHucCeOCbDtY4WJ8IEiz8KpkZI F8p39iaeLQx4MtcmxI8uehrA0LQ0TmLJcDIZU2x2LjD2KXavIKP9WercMiYDzjBXQRuLI AdekiEp3viVLf20fWdRpC7u7lVWlKEjTqfukTiJQl2b+H3nu5DrR5x5Zdfq7lvA05IcV2 BWgXGs8RWlB2/mIxMq/calaQsXWZ4+bpjC6yEoJ1o2lex1kkP4ZqfmM95BG4uTj5JD/xv rMTYOLwjmHNUkhC8Fl43AWftmt5x9Fsn7HT5COme4+lUqdcOrjKoIclObzQfJ3clO+w== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass header.from=gmail.com; spf=pass smtp.mailfrom=gmail.com; dkim=pass header.d=gmail.com header.i=@gmail.com header.a=rsa-sha256 header.s=20251104 header.b=sq2fTXIs; arc=none smtp.remote-ip=74.125.227.138 Received: from mail-pj2-f10.google.com (mail-pj2-f10.google.com [74.125.227.138]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 6B7CE606A31D for ; Tue, 27 Oct 2026 09:31:54 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.2 smtp.subspace.kernel.org 6B7CE606A31D Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=gmail.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key, unprotected) header.d=gmail.com header.i=@gmail.com header.a=rsa-sha256 header.s=20251104 header.b=sq2fTXIs Received: by mail-pj2-f10.google.com with SMTP id d9443c01a7336-2df921c1d0eso16555905ad.1 for ; Tue, 27 Oct 2026 02:31:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1793093514; x=1793698314; darn=vger.kernel.org; h=content-transfer-encoding:content-type:in-reply-to:from:references :cc:to:subject:user-agent:mime-version:date:message-id:from:to:cc :subject:date:message-id:reply-to:content-type; bh=0lp8ix384KyuQihbhJDejl7Hsm+NKly5D1mQFcd+Ymw=; b=sq2fTXIsEYbEUtg0IqcDKMHteJoXYOAwMDyVqzIZfLLacj5r2gHuBfSfVl8SDyy//I Tgb1smw70VKqwN+dX7VApNE2E06pGewPMGMOz5yPZqhk+5pB4o3STGObkK3bQaHabu4Z vKfn2epktM8g9ZRjHpbg0zdov6W+IhCKQEfddtM5iOoYqxKzxwH5UJvsqwWkmbhJRPt6 ig1SSiA1WHltZOvqZVm+1xYWO4y0e7xlazNAlOi8z8KfyeVRmCE5lAJS81DSqE3PxT3W lZn0JcA5XH6KEsoIoxJHZ9nq3LaW8OztyM6SvlC5W86KkD92x1DZXIuLwBrr9JtjwLoO MZYQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20260707; t=1793093514; x=1793698314; h=content-transfer-encoding:content-type:in-reply-to:from: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 :content-type; bh=0lp8ix384KyuQihbhJDejl7Hsm+NKly5D1mQFcd+Ymw=; b=Jc2CPY/dIjr7Mn2T+leKG6XuhSCnNzgc4/oks7DyWWzpxFOUciWD1Ch30rozYBkIsN nxwtazIDcdKW+Pp3VoQ+JvuGpep4XthLCDJf/9b6SdpW2KViIHuJ2fHn/zfZQkhBR4w0 t45cVJuVqhuPJaj9G2DsW3dZryXp4ZaVmqsTYA3FsFh3/nlI1L51p+KyqSI/n8227k20 20gNMPUYreu6hc87ltQRlB2Gu5smmtOOHZAMwECr0C0T9Dacx6EgObQgIOQl8hiwUidh R8zFv0VYLOQqxbKLiKIrDKVKmq7MGHqWNISVspx9XCgr8+Vr1e0l07vMRwES/er2VUbt z3Rg== X-Forwarded-Encrypted: i=1; AKwUvBzOXcuffDzSIbN+FLSrah9rWtrC4y9GG+t7WcKOdDS2TyaZmKkWz6EC+L8L/WDMkbKxgkp57rONI1wzfZ4=@vger.kernel.org X-Gm-Message-State: AFq9FYKoc/SUimGeh6QHdPkRQbTnmBXykiaUfkngrFYPAGNzSdeX9KzJ wnGCjeRDWYbJS2FUVz0YNRJFQe7Bga5NenqoCcR3fFLViHp91MkQ85sx X-Gm-Gg: AYBFou2NNy815dZwAwEXDg7C0zKwJrQx1r0/Whm3YLcXOqJIqeCoIB14tJ388ZGR7HE L4drD2k9a2GoOb4+QKumX0rt+QKeHVHNxNu6vGxndocg8Odd681rXYKncY9uWgw3M4FVwFEiNPD 5WyrQimXLMY2ZnC/wsRJJ7EosWGpM5r5JkUhnP6f1nUCW352qtYHUqWLK7XFdmDS/VDNFECH2Hi IuWA59nrC21DNEQgKjKxMHeyT5QLa/9rfIlisOYdPsV+6PCr8zU1NuI1H13pmUQg1fETbCOfqn0 8wdbuO34UI3K4asloOwS3k7eeZ3AGScFrpbW+Nl3wQcs3780eLlXdT8WfYIDRS2TjoTWR6HnpwP hU8TfEEnO4+Rr5wqiSJYzL09p7MuWC+ZxIsDYQbQSIx/2Es16rV6W4tk/jDVPR9e8zZSIp5kp2z 2X6/BPz1o087OkoJBRJr7dhJecDHyncpd55uqSg9zOYeEByKQMVw0XWvscMrNU59umWIS0qso1y nUkLHVHzvvaHmjdIETiUdBzkDkk0mWsIvgYvtONehV8itmBU4tnfePHsvYHFDWMsBV6lQYwx9fx X-Received: by 2002:a17:903:3c6c:b0:2e9:7719:4104 with SMTP id d9443c01a7336-2ea9c03f2ffmr86182255ad.8.1793093513672; Tue, 27 Oct 2026 02:31:53 -0700 (PDT) Received: from [0.0.0.0] ([129.126.71.118]) by smtp.gmail.com with ESMTPSA id d9443c01a7336-2eae6c9757bsm6281855ad.58.2026.10.27.02.31.46 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 27 Oct 2026 02:31:52 -0700 (PDT) Message-ID: Date: Tue, 27 Oct 2026 17:31:44 +0800 X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH 4/4] cpufreq: add an Amlogic speed-bin driver To: Jerome Brunet , Viresh Kumar , christian.koever-draxl@student.uibk.ac.at Cc: neil.armstrong@linaro.org, sboyd@kernel.org, bmasney+clk@redhat.com, khilman@baylibre.com, martin.blumenstingl@googlemail.com, rafael@kernel.org, robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org, linux-kernel@vger.kernel.org, linux-amlogic@lists.infradead.org, linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org, devicetree@vger.kernel.org, =?UTF-8?Q?Christian_Stefan_K=C3=B6v=C3=A9r-Draxl?= References: <20261025192219.209137-1-christian.koever-draxl@student.uibk.ac.at> <20261025192219.209137-5-christian.koever-draxl@student.uibk.ac.at> <1jbj8gkff1.fsf@starbuckisacylon.baylibre.com> From: Chuan Liu In-Reply-To: <1jbj8gkff1.fsf@starbuckisacylon.baylibre.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Hi Jerome, On 10/26/2026 4:57 PM, Jerome Brunet wrote: > On lun. 26 oct. 2026 at 11:00, Viresh Kumar wrote: > >> On 25-10-26, 20:22, christian.koever-draxl@student.uibk.ac.at wrote: >>> From: Christian Stefan Kövér-Draxl >>> >>> Every S4 speed bin runs the same CPU frequencies but needs its own >>> voltage curve, and the bin can only be read through the secure monitor. >>> >>> Read the bin from the firmware, select the matching >>> "opp-microvolt-speed" property for all CPUs, then register >>> cpufreq-dt. Bins outside the known range fall back to bin 0, which >>> has the highest voltages. Like sun50i-cpufreq-nvmem, the driver binds >>> on the SoC compatible and needs no node of its own, and S4 is added to >>> the cpufreq-dt-platdev blocklist so cpufreq-dt is only created after >>> the bin has been applied. >>> >>> Signed-off-by: Christian Stefan Kövér-Draxl >>> --- >>> MAINTAINERS | 1 + >>> drivers/cpufreq/Kconfig.arm | 14 ++ >>> drivers/cpufreq/Makefile | 1 + >>> drivers/cpufreq/amlogic-cpufreq.c | 184 +++++++++++++++++++++++++++ >>> drivers/cpufreq/cpufreq-dt-platdev.c | 2 + >>> 5 files changed, 202 insertions(+) >>> create mode 100644 drivers/cpufreq/amlogic-cpufreq.c >> >> Is it safe to apply just this one ? I can take this via the PM tree then. > > I would advise to wait a little for Amlogic to chime in.> > Patch 2 is something I already rejected back when S4 support was > initially introduced. I suppose AI just unearthed it and did not bother > to mention it. > > Amlogic was supposed to migrate to SCMI at that point, and possibly > handle CPU frequency scaling through the secure fw entirely. Yes, starting from the C3 clock upstream submission, we replaced the SMCs implementation of the secure-clock with SCMI. For the latest released Amlogic SoCs (S7 and later), secure-clock is implemented uniformly through SCMI. > > They did on later SoCs, I don't know where their FW stands on the S4. Most S4 customers receive a secure firmware (bl31.bin) that sets secure-clock via SMCs (because the S4 SDK had already been released by the time we added SCMI support). We have also provided an SCMI-capable bl31.bin to some customers. > >> >> -- >> viresh > -- Best regards, Chuan