Received: by 2002:a6b:fb09:0:0:0:0:0 with SMTP id h9csp61871iog; Wed, 29 Jun 2022 18:08:32 -0700 (PDT) X-Google-Smtp-Source: AGRyM1tNlnru7VQmQuQsY0x29LDzoVtXxmditAVgGJzL9YIfniw8Zp07/PuEGc66maHEYPh/mz99 X-Received: by 2002:a05:6402:430a:b0:435:8ec9:31ec with SMTP id m10-20020a056402430a00b004358ec931ecmr8077158edc.248.1656551311855; Wed, 29 Jun 2022 18:08:31 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1656551311; cv=none; d=google.com; s=arc-20160816; b=V8zYROFqVy6MuJmvH80OTuFKUZZO0A4RjOGxUoihbfVEqPBQzvYXoHEWZaD5xX72cJ QDtparomexdv6iZ3tmHGXaDwavsMk9oENNV4N91rmTEUuZSTXNUx4sjit4Pmk7nwi2C5 WZd/u6YzkNhxc4ukaLlAe9iT174LTfInV6algexFC65JKKl+2JaQVAmOqNHWWtppe8ly TyanTaLu3FwQoKS5c6kEoXk4iZHlBIPGGOLiLbyzkA2ql0/FXBXyZW/eVg1sRhdJeyug Z/gDJP7ZT0G88S/G2z/7r234VwawiFoVm1EedWswZoTf9hy12SL23RCFjW5+3C/uEZhN 5aMg== 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:dkim-signature; bh=ec4XEkBPA35XnLcPG87goxGDH+EEGY22aWvX/z3PefI=; b=vtFgptHm9Av34PI3k12ea7z90TdTJmqADwhRJcnuDaVTkQdoRpd7jm/jfes0uyA7Ng WwEzuPxnGHK2rdCBDSXykxyhz6WdrwBN56BnS0Nrppt2K9u/9rzahFBfITBgSXH7i02q oFDndl6BY+TGNnRruhzTH4QzRfEH1lv2XhMGJsArPfIPI6itPOUhxPTtV7grQAfMXiyM 96PAv3JmICgIoNySIZhIuzYABKXpH7qfsHF00cgvmCJlE3OrLCHw5zSelRQovMgDjiuc 2G4LYfohfet0ZkatJT+AGPF2xEGtJC0dsfEXNJJrEV+xZOuinzIre1egFkcTfiRnItth hTnw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=NFWCuFGR; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id b6-20020a056402278600b0042e1708c0ebsi5748485ede.579.2022.06.29.18.08.03; Wed, 29 Jun 2022 18:08:31 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=NFWCuFGR; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230416AbiF3Aue (ORCPT + 99 others); Wed, 29 Jun 2022 20:50:34 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40346 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229539AbiF3Auc (ORCPT ); Wed, 29 Jun 2022 20:50:32 -0400 Received: from mail-pf1-x434.google.com (mail-pf1-x434.google.com [IPv6:2607:f8b0:4864:20::434]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 55A223FDB1 for ; Wed, 29 Jun 2022 17:50:31 -0700 (PDT) Received: by mail-pf1-x434.google.com with SMTP id t21so16642896pfq.1 for ; Wed, 29 Jun 2022 17:50:31 -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; bh=ec4XEkBPA35XnLcPG87goxGDH+EEGY22aWvX/z3PefI=; b=NFWCuFGRbcAjPzdLWOr/NQp3XWuDNO6BMyHySS+trahq6mX9UFO7j+zQOkjuhlioWl xSYxRMQtRJOqPe6f8aUpkpL4C7uRkzlXaGc1roT4R/8VsrW+toIgTh/7JqCViwZCe/Eo bM3/bnNdqFYGfV+tPNcVNd3eWRc0Rn5hwxOdK1VlUJRRIZ3O9GRQV5RBdLfmhk10TlJk 2ATBJG6SR6FP3U4213Q+Xm15I5KrUa3o0Fr+ZWYv1hYrq+etlRvLYAfJW1P6ul5x863m GIRBOHuiCVrxZTYkdgcV7H2J/2nN8WZlUCw9A7RUKMGArEVcHcudATd8abMaGeTV4LBH kHxg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=ec4XEkBPA35XnLcPG87goxGDH+EEGY22aWvX/z3PefI=; b=hkrBrhXkrIdRUCD+clETMBEF/VR7Hefx+84pgCL7S8aszb5e58b3+/z8JPXeTLuIoQ hO1Rn/kSbOdJL+5ur62xPc5aGzJ/mi2A6rRPDohyOnPo4hGZgzrToTPm7ivCbg5B2lF8 hKbJpEaZot5Yy0u3IWmldr1ErMLtlJg34JLV8ANc1ighMQoHBlvEHDmCps2doSWhTHlx 4yH9WFSFvm0Gvb0/XOYttN3FOrHhZpznS7FaQIOMgCSBsQa1c7i2sijbAKvN+HVxbUFs VNa8lUHc6HkICIkBN/3xpf5W7wekXM8liaFUcq843IATbS5GTuT+bMnhODI1be00U4YI AQsg== X-Gm-Message-State: AJIora9+NfyAmQ14UU5q8/vPnw/0xyBkjyqaYPTdp/7sF89P4Zj59F2f h8SOWTLs/4uZoCI2kPX8kMFDgQ== X-Received: by 2002:a65:6bd4:0:b0:405:2d64:532c with SMTP id e20-20020a656bd4000000b004052d64532cmr5361306pgw.179.1656550230789; Wed, 29 Jun 2022 17:50:30 -0700 (PDT) Received: from localhost ([122.172.201.58]) by smtp.gmail.com with ESMTPSA id 4-20020aa79244000000b005252a06750esm4541969pfp.182.2022.06.29.17.50.29 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 29 Jun 2022 17:50:30 -0700 (PDT) Date: Thu, 30 Jun 2022 06:20:28 +0530 From: Viresh Kumar To: Dmitry Osipenko Cc: Jon Hunter , Krzysztof Kozlowski , Viresh Kumar , Nishanth Menon , Stephen Boyd , "Rafael J. Wysocki" , linux-pm@vger.kernel.org, Vincent Guittot , linux-kernel@vger.kernel.org, "linux-tegra@vger.kernel.org" Subject: Re: [PATCH 5/8] OPP: Allow multiple clocks for a device Message-ID: <20220630005028.fddtcbkoksbygwc5@vireshk-i7> References: <8b29fa207024dc295639f9ba52c28e45782e3baa.1654849214.git.viresh.kumar@linaro.org> <55623c12-dda3-613f-5bc9-80b3b6fec5f9@nvidia.com> <20220622141511.yzg5itkdwirpavfj@vireshk-i7> <40e616eb-22f9-19c2-8d77-20cd3c7c518b@nvidia.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 29-06-22, 21:33, Dmitry Osipenko wrote: > Today I noticed that tegra30-devfreq driver now fails to probe because > dev_pm_opp_find_freq_ceil() fails with -ERANGE. This patch is guilty for > that. Could you please take a look? I remember this corner case now [1] and it was easy to miss this. So you want the OPP core to still parse the DT to read opp-hz, but don't want dev_pm_opp_set_opp() to update the clock rate for it. What was the reason for this again ? I have a couple of solutions in mind, but one may be other than second and so want to know the real issue at hand first. -- viresh [1] https://lore.kernel.org/lkml/71451eb2-46b2-1ea0-efcc-0811568159a4@gmail.com/