Received: by 2002:a05:6a10:6744:0:0:0:0 with SMTP id w4csp434685pxu; Fri, 23 Oct 2020 05:00:02 -0700 (PDT) X-Google-Smtp-Source: ABdhPJy2IyOtLv7JzK4jHFaNSBolEcwI7YXqBttqk9PR0GxJez/wrpTNEfabcCyt706M13YNQRfu X-Received: by 2002:a17:906:bfe2:: with SMTP id vr2mr1671268ejb.248.1603454402572; Fri, 23 Oct 2020 05:00:02 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1603454402; cv=none; d=google.com; s=arc-20160816; b=kU4tyE4LplU8ahEw+S3Ob1upPb/2WY+9mkjPkzxDzgYtq9mzfov3no26ufZR+HNISs NdVtj52EGjO++DoYZHsILrS86+Ozom9GDvisNDmHCE8PCRRIg4qQ4NNJua2SJcaKb/M4 GvPtj2x/8KHVslsozPLnTF6ZW/ecdTmIjryAcudgjeU0+tLN9YRoQK6Oxubc25c6FUkT AtVDUXSaaulsfS89Tm8ByMDdlHmx4HIMlOLVNAuPFiTfgRcL5vv300PMojt3oah3vcMV S/5oBsxYlktP1OvUQ2UK9Y5KIQd6XSk2Krb3s/PRRuw3QIjWiBDEboww20NYhxuJaDa+ UdKA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=KIC/5EdN92sJ0p7/n+Xxpx5Lw1j/gUtxTjKck0AREkI=; b=z9YpyBJ09bSjW8OP3AC3ZVwPQi36342LxGmeC5N5dRuRsYINsLeMYRu40vQ703RhUv sLQ5lsUZWaN8P0RR+GWzRdrmRUbzQ4Prq+W4PmYUFKE/cWzow+f4GDlfQId2V5CJ349H hPE/CeoryEgwcHcMRw23uiD5ekJW0P3jWDvOkY5NNSYx7D6B5YxL/PO8ApdQCFRBYpIN OffVlSXwldv20TkPIADxasdT7EVKQu8mDxCn/6s7VPyVFKj4FxuO+nQ8KcAgxP6xILiT SZkgFEHW+Y8GgnYaDpDzOzts2mpt5a8MmdPNa6Y2hJ16PGjCWb99e0wlF46GRyGV/E/9 8URA== 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 y22si602047edr.151.2020.10.23.04.59.40; Fri, 23 Oct 2020 05:00:02 -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 S2902464AbgJVSWm (ORCPT + 99 others); Thu, 22 Oct 2020 14:22:42 -0400 Received: from foss.arm.com ([217.140.110.172]:34618 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2900523AbgJVSWm (ORCPT ); Thu, 22 Oct 2020 14:22:42 -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 76477D6E; Thu, 22 Oct 2020 11:22:41 -0700 (PDT) Received: from bogus (unknown [10.57.22.167]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 5246A3F719; Thu, 22 Oct 2020 11:22:40 -0700 (PDT) Date: Thu, 22 Oct 2020 19:22:33 +0100 From: Sudeep Holla To: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, Rob Herring Cc: linux-arm-kernel@lists.infradead.org, Viresh Kumar Subject: Re: [PATCH v2 1/2] dt-bindings: arm,scmi: Do not use clocks for SCMI performance domains Message-ID: <20201022182233.hklq6j5n5kkqg4yv@bogus> References: <20201021183104.27949-1-sudeep.holla@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20201021183104.27949-1-sudeep.holla@arm.com> User-Agent: NeoMutt/20171215 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Oct 21, 2020 at 07:31:03PM +0100, Sudeep Holla wrote: > Commit dd461cd9183f ("opp: Allow dev_pm_opp_get_opp_table() to return > -EPROBE_DEFER") handles -EPROBE_DEFER for the clock/interconnects within > _allocate_opp_table() which is called from dev_pm_opp_add and it > now propagates the error back to the caller. > > SCMI performance domain re-used clock bindings to keep it simple. However > with the above mentioned change, if clock property is present in a device > node, opps can't be added until clk_get succeeds. So in order to fix the > issue, we can register dummy clocks which is completely ugly. > > Since there are no upstream users for the SCMI performance domain clock > bindings, let us introduce separate performance domain bindings for the > same. > > Signed-off-by: Sudeep Holla > --- > .../devicetree/bindings/arm/arm,scmi.txt | 19 ++++++++++++++++--- > 1 file changed, 16 insertions(+), 3 deletions(-) > > v1[1]->v2: > - Changed the generic #perf-domain-cells to more SCMI specific > property #arm,scmi-perf-domain-cells > Is more specific #arm,scmi-perf-domain-cells acceptable ? Sorry for the rush, but this fixes SCMI cpufreq which is broken after commit dd461cd9183f ("opp: Allow dev_pm_opp_get_opp_table() to return -EPROBE_DEFER") -- Regards, Sudeep