From patchwork Tue Mar 22 00:47:19 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: David Collins X-Patchwork-Id: 12787991 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 1706EC433F5 for ; Tue, 22 Mar 2022 00:49:25 +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:MIME-Version:References:In-Reply-To: Message-ID:Date:Subject:CC:To:From:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=ms41nPIuaVWwGWEd6qg+N4n+omSL6awcpUaIuUO4L1c=; b=qCPznC6EicaxSO +GdnwWS8PVC5ROfjzgNl8QOR/chKS/kTtOvqBZO9GS91lWswPPFfOK38zNBniPSX33v1HAK9xh2vx A1RVUvi4JGgLcR7rt4vycwg6/8YZpHj25QzzYHT2aRUnf4D/4HPt+jzQVgWMNlK/wR5qxQtzS7c2P 2kOgUlCLvyGiorKURqBrvRDlLZVnR9U8SkM/pJyJ1GW1P1IRaGPiAj82ISEknc/ajvtF+y4lWPs9H CFC9wVJa8VzBSfRroF2qp7+K7vfS2QbHsD3TfLFmRGAzODO1wvrsIS6NcE8vkYcoPqbrzoVS6hPJx AImYOsnezClnb9RPj82g==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1nWSgz-009YAX-0v; Tue, 22 Mar 2022 00:48:09 +0000 Received: from alexa-out-sd-01.qualcomm.com ([199.106.114.38]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1nWSgm-009Y5c-8F for linux-arm-kernel@lists.infradead.org; Tue, 22 Mar 2022 00:47:59 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quicinc.com; i=@quicinc.com; q=dns/txt; s=qcdkim; t=1647910076; x=1679446076; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version; bh=ubdrenh8RZbdb9SUuFRL3yPGdNKdx7dpJeScfreUfxs=; b=ozbZL03mpLpG3wRyLNK+Mhq7Nli1k1b8AiGWslzkznetRDRzE4CAVyhp UU+b4i+dzxQPOzis7qnNXuL+6KJIt+fD1foEABkgF+b5aRbFeGAqKHNB/ dlhs2wxqGnTsVNx59XDjgMLGek6iaL15dsvJyvCxL4+svdMKilQnEpmLs U=; Received: from unknown (HELO ironmsg05-sd.qualcomm.com) ([10.53.140.145]) by alexa-out-sd-01.qualcomm.com with ESMTP; 21 Mar 2022 17:47:48 -0700 X-QCInternal: smtphost Received: from nasanex01b.na.qualcomm.com ([10.46.141.250]) by ironmsg05-sd.qualcomm.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 21 Mar 2022 17:47:48 -0700 Received: from collinsd-linux.qualcomm.com (10.80.80.8) by nasanex01b.na.qualcomm.com (10.46.141.250) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.986.22; Mon, 21 Mar 2022 17:47:47 -0700 From: David Collins To: Rob Herring , Sudeep Holla , CC: David Collins , Mark Brown , Liam Girdwood , Cristian Marussi , , , , "Subbaraman Narayanamurthy" Subject: [PATCH v2 1/2] dt-bindings: firmware: arm, scmi: define support for name based regulators Date: Mon, 21 Mar 2022 17:47:19 -0700 Message-ID: <4c94b4351b8d38167e972df46fbc507f9499513a.1647909090.git.quic_collinsd@quicinc.com> X-Mailer: git-send-email 2.17.1 In-Reply-To: References: MIME-Version: 1.0 X-Originating-IP: [10.80.80.8] X-ClientProxiedBy: nasanex01a.na.qualcomm.com (10.52.223.231) To nasanex01b.na.qualcomm.com (10.46.141.250) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220321_174756_360107_C5F61D50 X-CRM114-Status: GOOD ( 12.13 ) 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: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org Allow SCMI regulator subnodes to be specified either by ID using the "reg" property or by name using the "arm,scmi-domain-name" property. Name based SCMI regulator specification helps ensure that an SCMI agent doesn't need to be aware of the numbering scheme used for Voltage Domains by the SCMI platform. It also ensures that the correct Voltage Domain is selected for a given physical regulator. This cannot be guaranteed with numeric Voltage Domain IDs alone. Signed-off-by: David Collins --- .../devicetree/bindings/firmware/arm,scmi.yaml | 15 ++++++++++++--- 1 file changed, 12 insertions(+), 3 deletions(-) diff --git a/Documentation/devicetree/bindings/firmware/arm,scmi.yaml b/Documentation/devicetree/bindings/firmware/arm,scmi.yaml index 5c4c6782e052..08cb5de967ac 100644 --- a/Documentation/devicetree/bindings/firmware/arm,scmi.yaml +++ b/Documentation/devicetree/bindings/firmware/arm,scmi.yaml @@ -155,7 +155,7 @@ properties: The list of all regulators provided by this SCMI controller. patternProperties: - '^regulators@[0-9a-f]+$': + '^regulator.+$': type: object $ref: "../regulator/regulator.yaml#" @@ -164,8 +164,17 @@ properties: maxItems: 1 description: Identifier for the voltage regulator. - required: - - reg + arm,scmi-domain-name: + description: + A string matching the name of the SCMI voltage domain for this + regulator. + $ref: "/schemas/types.yaml#/definitions/string" + + anyOf: + - required: + - reg + - required: + - arm,scmi-domain-name additionalProperties: false