From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-8.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI, SIGNED_OFF_BY,SPF_PASS,URIBL_BLOCKED,USER_AGENT_NEOMUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id C46F5C64EB8 for ; Mon, 8 Oct 2018 05:55:54 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 88FC92085B for ; Mon, 8 Oct 2018 05:55:54 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=linaro.org header.i=@linaro.org header.b="OYS0fNut" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 88FC92085B Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=linaro.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726810AbeJHNFw (ORCPT ); Mon, 8 Oct 2018 09:05:52 -0400 Received: from mail-pf1-f196.google.com ([209.85.210.196]:42603 "EHLO mail-pf1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725842AbeJHNFv (ORCPT ); Mon, 8 Oct 2018 09:05:51 -0400 Received: by mail-pf1-f196.google.com with SMTP id f26-v6so7673185pfn.9 for ; Sun, 07 Oct 2018 22:55:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=LEMX1QnhAyJfdRytKSanJMQZrZMtpjTS9QTX9rqO890=; b=OYS0fNutBpUmn/PIpLJi1Fryv7jr6MiBTshUZwTZUeA6DOpiRZXoDJEihqPeQ+JVNn Y5rJV8O5ZrsxeWoDbM8tj4uPDxiRF2MRbZp2buZxZH2a8oHR6DhSoG8ssXK9snj8lkLV MG3e+scMoDSnYql+RKH2XFg0fIfVhHgbhcTeE= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=LEMX1QnhAyJfdRytKSanJMQZrZMtpjTS9QTX9rqO890=; b=U4doEHw+O7yWJnLNFe7mtDlF/XIOquvi0ZRsiEitxGwGVEjZWbAFCh+/Z7dsZ1YqiM 977IG5Jldm300sMQAwG7WO2qyA2w2Njm1NKNGDZZf32TJ4u8R8uKiydbIje2aSfYg95V Eyt6k3Not5O2l7WGJaS2QjjYc2PAINjPrffSeuNtCMon/ayQQkEYkPY6vTgRbtJxDJYY 8D9RoDgPH8uB3riSAQGfKhayBRV951fVwlYMh3Nw4f6irCaeKSk5NQRZUxseNB8EDWwx uiipr44rFuNDBdpkkf2zeHwmyY6m6yutjsqfeEuckpxy+Kjn8JglPcjEFBiFAcFUEJTA SWDA== X-Gm-Message-State: ABuFfojCyKP7LD7oSf32gE8dLfex/TJXTJc4oGD4F4YiTBwYzVFBzmb/ ai/6B+DmJZitU/qtROct1K/2vQ== X-Google-Smtp-Source: ACcGV63t/Qw9OsialSba0UQIpLz9uTZHv3Jxm6nMtjVMBXYGLV+uai/vajRW8UbFfiPCHFze1MK3hw== X-Received: by 2002:a62:90db:: with SMTP id q88-v6mr23364972pfk.98.1538978151298; Sun, 07 Oct 2018 22:55:51 -0700 (PDT) Received: from localhost ([122.172.112.137]) by smtp.gmail.com with ESMTPSA id k77-v6sm34659834pfg.1.2018.10.07.22.55.50 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 07 Oct 2018 22:55:50 -0700 (PDT) Date: Mon, 8 Oct 2018 11:25:47 +0530 From: Viresh Kumar To: Dmitry Torokhov Cc: "Rafael J. Wysocki" , Heiko Stuebner , Derek Basehore , Guenter Roeck , linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2] cpufreq: dt-platdev: allow RK3399 to have separate tunables per cluster Message-ID: <20181008055547.umpyi4zcmcmjlxn2@vireshk-i7> References: <20181005190058.GA234868@dtor-ws> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20181005190058.GA234868@dtor-ws> User-Agent: NeoMutt/20180323-120-3dd1ac Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 05-10-18, 12:00, Dmitry Torokhov wrote: > RK3899 has one cluster with 4 small cores, and another one with 2 big > cores, with cores in different clusters having different OPPs and thus > needing separate set of tunables. Let's enable this via > "have_governor_per_policy" platform data. > > Signed-off-by: Dmitry Torokhov > --- > > v2 changes: commit message updated. > > Not tested, but we had a patch unconditionally enabling > CPUFREQ_HAVE_GOVERNOR_PER_POLICY flag in tree we used to ship devices > based on RK3399 platform. > > drivers/cpufreq/cpufreq-dt-platdev.c | 5 ++++- > 1 file changed, 4 insertions(+), 1 deletion(-) > > diff --git a/drivers/cpufreq/cpufreq-dt-platdev.c b/drivers/cpufreq/cpufreq-dt-platdev.c > index fe14c57de6ca..040ec0f711f9 100644 > --- a/drivers/cpufreq/cpufreq-dt-platdev.c > +++ b/drivers/cpufreq/cpufreq-dt-platdev.c > @@ -78,7 +78,10 @@ static const struct of_device_id whitelist[] __initconst = { > { .compatible = "rockchip,rk3328", }, > { .compatible = "rockchip,rk3366", }, > { .compatible = "rockchip,rk3368", }, > - { .compatible = "rockchip,rk3399", }, > + { .compatible = "rockchip,rk3399", > + .data = &(struct cpufreq_dt_platform_data) > + { .have_governor_per_policy = true, }, > + }, > > { .compatible = "st-ericsson,u8500", }, > { .compatible = "st-ericsson,u8540", }, Acked-by: Viresh Kumar -- viresh