Received: by 2002:a05:6a10:f3d0:0:0:0:0 with SMTP id a16csp4233459pxv; Tue, 29 Jun 2021 02:05:43 -0700 (PDT) X-Google-Smtp-Source: ABdhPJw7PVokJVcPbQxDHr/4kWwxMGQwSPkyRBheXgo3ovfJEOMaxb1bry/sW1kWmRnnhpfFyP3Q X-Received: by 2002:a17:907:2bfa:: with SMTP id gv58mr29228566ejc.529.1624957542992; Tue, 29 Jun 2021 02:05:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1624957542; cv=none; d=google.com; s=arc-20160816; b=BK8xmjT9bBOQxnSRhFSXsE/ZpLO08O4im2GjydbQbQCydoYJ4zhvcRa0BIPhqdWAEL gJYbxuRest9MbX4F5TRverZzu1wVa33+40jb/wnW0uh0wlheHYMjBIseurUBpFnmbH7Q C6eQ+pmFjwoTL8enUgMhz0hYwYLja6WGsJFLtOOOEyqKTr2R6tIZDJYexqBUVeBSKPJG nha5pSTovk1HsU+eHfYrDCWYzNV6dwzXJGh7U9uxmlqcw4V+zgyl5LBUgfDJUsixeb1E 1N2t5r7ON2hWLHl29fzsIyrsmFLcNg9fkOBwbiphLz22pqKRpGq9nHl27di4rFhUODYu TSMA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=oUiNjWKe5I14HBFZF/SLGhRzrqll93wjz2ahG4nX5gU=; b=rUHMtX1fR350pOaOZLheONoMClg9PGZJNMNXahw4eI1QdMMqaGGQghlZzd+Qxn8oGD /b8CXmr3GxwX1GWfq5ZcF4nH+1GIwWxIA/fkK3edQNHH8kpIRBosZI0X4AF5FyznA5j2 uhFqSYx2cJvkYWRE5eLsenUVe6dynVZhEEdBcoR6JYFH7bJ1D0neGZINthd0v1JM892U Cf9cDcXncp5BRdAdh1mH4VzJ4V3vpOkfEv6xAhMueUSD5qALw5Cu0xbnVWu7r4S2JoBe n+EjGgyS+i5MWCmlY3GlrU8sZve4lSnKSf2nukXx0coXhgkqcXi4GpyFUa0hNPn+nekO uNvQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id q19si17011115edv.125.2021.06.29.02.05.19; Tue, 29 Jun 2021 02:05:42 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232636AbhF2JFx (ORCPT + 99 others); Tue, 29 Jun 2021 05:05:53 -0400 Received: from foss.arm.com ([217.140.110.172]:46676 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232518AbhF2JFw (ORCPT ); Tue, 29 Jun 2021 05:05:52 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 7B5ECD6E; Tue, 29 Jun 2021 02:03:25 -0700 (PDT) Received: from bogus (unknown [10.57.78.75]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 5932F3F694; Tue, 29 Jun 2021 02:03:23 -0700 (PDT) Date: Tue, 29 Jun 2021 10:02:38 +0100 From: Sudeep Holla To: Viresh Kumar Cc: Hector Yuan , linux-mediatek@lists.infradead.org, linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org, "Rafael J. Wysocki" , Sudeep Holla , Matthias Brugger , Rob Herring , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, wsd_upstream@mediatek.com Subject: Re: [PATCH v12 1/2] cpufreq: mediatek-hw: Add support for CPUFREQ HW Message-ID: <20210629090238.n23zcttkiqvzpbb5@bogus> References: <1622307153-3639-1-git-send-email-hector.yuan@mediatek.com> <1622307153-3639-2-git-send-email-hector.yuan@mediatek.com> <20210614104058.jdwb7godqzhf7rgd@vireshk-i7> <1624781848.1958.16.camel@mtkswgap22> <20210628072641.amqk5d3svwolvhic@vireshk-i7> <20210628090956.uwkrozdqvawsm3xp@bogus> <20210629024719.nmcygaigtx5wn7g5@vireshk-i7> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210629024719.nmcygaigtx5wn7g5@vireshk-i7> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jun 29, 2021 at 08:17:19AM +0530, Viresh Kumar wrote: > On 28-06-21, 10:09, Sudeep Holla wrote: > > Probably in driver/cpufreq or some related headers if it needs to access > > related_cpus and is more cpufreq related in that way ? > > It just needs to set a mask, so doesn't really depend on cpufreq. I > was wondering if drivers/opp/of.c may be used for this, and I am not > sure. > Sounds good to me. -- Regards, Sudeep