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 Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 1D432EB64DC for ; Fri, 21 Jul 2023 11:56:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=KJ6Ii+OLzLkX/dqoaspNbRUrXwB3AEprgX9uzBz/QuA=; b=caFk9KvjMJ03TG RnqsKgK3vPfhEfVV+2HOHAmt2uOmCpM3D+/j2csw8SgIq+JuquSG409n1DAzAIZ0v2zV8obnPNuso TSraJZ/dJcbiPjFmTjyp35UNkDBivntVdj02Hh2hv9+O+XB/0yyJaODkeqzq3SOkZ7DSZ/AhQwFmM gxRkVwMQXdVuE6qGTtmzzuiGKIRkR7dJYWDSguDRo6dv88s3WDVD4aAoo6KqtRrYx7C0w/HV4Lwe4 37gXlKZAM4LOSXXvFuknBQkmnE0s2YJWkwGaySEj25uzNkyx3NqDMdn0ZAsxRGFN/iOw3lEFrtpBh MTObPnxmMrd/+fnRlNVw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1qMok3-00DyzK-2K; Fri, 21 Jul 2023 11:56:15 +0000 Received: from foss.arm.com ([217.140.110.172]) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1qMok0-00DyyH-0N for linux-arm-kernel@lists.infradead.org; Fri, 21 Jul 2023 11:56:13 +0000 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 9E0132F4; Fri, 21 Jul 2023 04:56:49 -0700 (PDT) Received: from bogus (unknown [10.57.96.100]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id D467C3F6C4; Fri, 21 Jul 2023 04:56:02 -0700 (PDT) Date: Fri, 21 Jul 2023 12:55:35 +0100 From: Sudeep Holla To: Ulf Hansson Cc: Cristian Marussi , Viresh Kumar , Nishanth Menon , Stephen Boyd , Nikunj Kela , Sudeep Holla , Prasad Sodagudi , Alexandre Torgue , linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Rob Herring , Krzysztof Kozlowski , Conor Dooley , devicetree@vger.kernel.org Subject: Re: [PATCH v2 08/11] dt-bindings: firmware: arm,scmi: Extend bindings for protocol@13 Message-ID: <20230721115535.mx46dg56pxjnzbuv@bogus> References: <20230713141738.23970-1-ulf.hansson@linaro.org> <20230713141738.23970-9-ulf.hansson@linaro.org> <20230719151716.qhobfnclrjf4yqkg@bogus> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20230721_045612_223536_32C04385 X-CRM114-Status: GOOD ( 22.87 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Fri, Jul 21, 2023 at 01:42:43PM +0200, Ulf Hansson wrote: > On Wed, 19 Jul 2023 at 17:17, Sudeep Holla wrote: > > > > On Thu, Jul 13, 2023 at 04:17:35PM +0200, Ulf Hansson wrote: > > > The protocol@13 node is describing the performance scaling option for the > > > ARM SCMI interface, as a clock provider. This is unnecessary limiting, as > > > performance scaling is in many cases not limited to switching a clock's > > > frequency. > > > > > > Therefore, let's extend the binding so the interface can be modelled as a > > > generic performance domaintoo. The common way to describe this, is to use > > > the "power-domain" DT bindings, so let's use that. > > > > > > > One thing I forgot to ask earlier is how we can manage different domain IDs > > for perf and power domains which is the case with current SCMI platforms as > > the spec never mandated or can ever mandate the perf and power domains IDs > > to match. They need not be same anyways. > > Based upon what you describe above, I have modelled the perf-domain > and the power-domain as two separate power-domain providers. > > A consumer device being hooked up to both domains, would specify the > domain IDs in the second power-domain-cell, along the lines of the > below. Then we would use power-domain-names to specify what each > power-domain represents. > > power-domains = <&scmi_pd 2>, <&scmi_dvfs 4>; > power-domain-names = "power", "perf"; > > I hope this makes it clearer!? Yes it make is clear definitely, but it does change the definition of the generic binding of the "power-domains" property now. I am interesting in the feedback from the binding maintainers with respect to that. Or is it already present ? IIUC, the ones supported already are generally both power and performance providers. May be it doesn't matter much, just wanted to explicit ask and confirm those details. -- Regards, Sudeep _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel