Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965262AbcDYVsj (ORCPT ); Mon, 25 Apr 2016 17:48:39 -0400 Received: from mail-lf0-f67.google.com ([209.85.215.67]:36362 "EHLO mail-lf0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965170AbcDYVsh (ORCPT ); Mon, 25 Apr 2016 17:48:37 -0400 MIME-Version: 1.0 In-Reply-To: <20160425214533.GA29990@codeaurora.org> References: <20160422222736.GU13149@codeaurora.org> <20160425093650.GG32183@vireshk-i7> <20160425214533.GA29990@codeaurora.org> Date: Mon, 25 Apr 2016 23:48:35 +0200 X-Google-Sender-Auth: QkA-aMavzl8J6yrJUWJourFpysc Message-ID: Subject: Re: [PATCH 07/10] cpufreq: dt: Identify cpu-sharing for platforms without operating-points-v2 From: "Rafael J. Wysocki" To: Stephen Boyd Cc: Viresh Kumar , Rafael Wysocki , Lists linaro-kernel , "linux-pm@vger.kernel.org" , Nishanth Menon , Arnd Bergmann , andrew@lunn.ch, gregory.clement@free-electrons.com, Jason Cooper , sebastian.hesselbarth@gmail.com, Thomas Petazzoni , Linux Kernel Mailing List Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1007 Lines: 23 On Mon, Apr 25, 2016 at 11:45 PM, Stephen Boyd wrote: > On 04/25, Viresh Kumar wrote: >> On 22-04-16, 15:27, Stephen Boyd wrote: >> > On 04/21, Viresh Kumar wrote: >> > > @@ -167,14 +167,16 @@ static int cpufreq_init(struct cpufreq_policy *policy) >> > > /* Get OPP-sharing information from "operating-points-v2" bindings */ >> > > ret = dev_pm_opp_of_get_sharing_cpus(cpu_dev, policy->cpus); > [..] >> > > + if (dev_pm_opp_get_sharing_cpus(cpu_dev, policy->cpus)) >> > > + fallback = true; >> > >> > I'm sort of lost, we make the same call twice here. Why would the >> > return value change between the first time and the second? >> >> Two different APIs, which look similar :) >> >> The first one tries to find the sharing-cpus relation from DT, the >> other one is for v1 bindings and finds it due to platform code >> dev_pm_opp_set_sharing_cpus() call. > > Ah thanks. My eyes glossed over the "of" part. Sounds fine. So that would be an "ACK", right?