Received: by 2002:a05:6a10:af89:0:0:0:0 with SMTP id iu9csp3507915pxb; Mon, 24 Jan 2022 11:01:51 -0800 (PST) X-Google-Smtp-Source: ABdhPJxyslqMdO+OSTgguw7xujtv53RuAKV30ntJHCMTX9vNTmYntMMKwofNhBXl6IaVi31yQkkV X-Received: by 2002:a17:902:7fc4:b0:14a:9f3d:3358 with SMTP id t4-20020a1709027fc400b0014a9f3d3358mr15747215plb.165.1643050911546; Mon, 24 Jan 2022 11:01:51 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1643050911; cv=none; d=google.com; s=arc-20160816; b=kTi0ASk7rLEFVwa5XmucQ5FGui90BYb3HkWzPiZX5bNxusnSpnHBu+7D3gr/CSFh3Z 9uHTqCpKHITu6HcJQ9XTICeE7MGj9N/41w1l7iukHlhVCFbzrdv83iHP/Y+mY38ZwhlT fOBMq0v0ccahG0Fm9ToXbsUiVy43IqqJuuySkl9emw8GcbWmgu1E+3KuWLcyXDUagvpW PP0huUCJI52GRrZwuddSEU+YZ0SdZAegpCzYyn/L3c1P8xqfQrMPbI4e2Fo/Yq0CEd9v MkyOOtSmiDiBBeMDzkz5aOcWV3DhuUeJvW9eP8SvG12vRJ6DtXqlKXfXMJxlynG4aXvD yVwA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:references:in-reply-to:message-id:date:subject :cc:to:from; bh=/6WmkFQib0JXSXe1rx1wKPCKKUwxgg8sK/cfmxgQKB8=; b=0ZXje/08tSX8b+FdhNwC4V2lPdm09GYK+GoS0bWAk8w4pRHHHlZuTyGHcZYlmH8Mzi bFaS5Zq0NjW82k62hwd8WlQ4skfjLj7imWF4XSxxYYh0M6d7gkp4IXfFt5SW6sERnB4U zMGeG9clYZ4wKjnfAVC9nQj9ythrJS8t1cfuAgjT4gKjRb6HlWOuCTYUwNv8IiBULRr1 0ifmJGJnqkgrbVq5234d84sygc7dqqs4txsBwOFIVDppwSWbQG7rAHYiiLKIYh/8wlwO gUFBzZqQykL7AlB3GouOmb2hLWiadJKsij/6wxmEFl+uDXKdlyaXujlYz5qvALlmzokW ucIA== 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 z11si7211503plg.404.2022.01.24.11.01.38; Mon, 24 Jan 2022 11:01:51 -0800 (PST) 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 S237013AbiAXKEV (ORCPT + 99 others); Mon, 24 Jan 2022 05:04:21 -0500 Received: from foss.arm.com ([217.140.110.172]:56006 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236971AbiAXKEK (ORCPT ); Mon, 24 Jan 2022 05:04:10 -0500 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 428A0101E; Mon, 24 Jan 2022 02:04:10 -0800 (PST) Received: from e120937-lin.home (unknown [172.31.20.19]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 1D9563F73B; Mon, 24 Jan 2022 02:04:08 -0800 (PST) From: Cristian Marussi To: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Cc: sudeep.holla@arm.com, james.quinlan@broadcom.com, Jonathan.Cameron@Huawei.com, f.fainelli@gmail.com, etienne.carriere@linaro.org, vincent.guittot@linaro.org, souvik.chakravarty@arm.com, peter.hilber@opensynergy.com, igor.skalkin@opensynergy.com, cristian.marussi@arm.com, Rob Herring , devicetree@vger.kernel.org Subject: [PATCH 2/6] dt-bindings: firmware: arm,scmi: Add atomic_threshold optional property Date: Mon, 24 Jan 2022 10:03:37 +0000 Message-Id: <20220124100341.41191-3-cristian.marussi@arm.com> X-Mailer: git-send-email 2.17.1 In-Reply-To: <20220124100341.41191-1-cristian.marussi@arm.com> References: <20220124100341.41191-1-cristian.marussi@arm.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org SCMI protocols in the platform can optionally signal to the OSPM agent the expected execution latency for a specific resource/operation pair. Introduce an SCMI system wide optional property to describe a global time threshold which can be configured on a per-platform base to determine the opportunity, or not, for an SCMI command advertised to have a higher latency than the threshold, to be considered for atomic operations: high-latency SCMI synchronous commands should be preferably issued in the usual non-atomic mode. Cc: Rob Herring Cc: devicetree@vger.kernel.org Signed-off-by: Cristian Marussi --- .../devicetree/bindings/firmware/arm,scmi.yaml | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/Documentation/devicetree/bindings/firmware/arm,scmi.yaml b/Documentation/devicetree/bindings/firmware/arm,scmi.yaml index eae15df36eef..8edda54dff5b 100644 --- a/Documentation/devicetree/bindings/firmware/arm,scmi.yaml +++ b/Documentation/devicetree/bindings/firmware/arm,scmi.yaml @@ -81,6 +81,14 @@ properties: '#size-cells': const: 0 + atomic_threshold: + $ref: /schemas/types.yaml#/definitions/uint32 + description: + An optional time value, expressed in microseconds, representing the + threshold above which, on this platform, any SCMI command advertised to + have a higher execution latency, should not be used in atomic mode, even + if requested. If left unconfigured defaults to zero. + arm,smc-id: $ref: /schemas/types.yaml#/definitions/uint32 description: @@ -264,6 +272,8 @@ examples: #address-cells = <1>; #size-cells = <0>; + atomic_threshold = <10000>; + scmi_devpd: protocol@11 { reg = <0x11>; #power-domain-cells = <1>; -- 2.17.1