Received: by 2002:ac0:a594:0:0:0:0:0 with SMTP id m20-v6csp1546258imm; Fri, 11 May 2018 18:49:36 -0700 (PDT) X-Google-Smtp-Source: AB8JxZo04pnKtwJJl0ZHPohh/uNAagOZtmHNfN6VrGIKWr1CxhDLmiNduDp3eK7gCEjvqX3kQ69U X-Received: by 2002:a62:b03:: with SMTP id t3-v6mr1202568pfi.32.1526089776530; Fri, 11 May 2018 18:49:36 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1526089776; cv=none; d=google.com; s=arc-20160816; b=GXT+Um03oDxWyrdoRyhhHWduoxvh0r9zgn7eZSW61nLPG1WAkZ3/faluf8X5QHtJbv +pahClhYB504WA8saXYkNnYktvbRc8TrZ9+8ArVbKGSIqRay1anFcvlEPd7rLJ1Eoham q9xjYf2u8CFphjd2AO26Bs35NLE0Y0kQTIxUfEmbqJZ6B1un/0sh5dFuUGdemxsOc525 NVOUFCm1CwfZo0HhIlW5oil2HdQguLCufoIfUzZNwIigZQJGpWN91865oHZIa3JGDfVP APbqy+Q7oQjG9VC0w8O2C+m1BwfBSv+LBH3ImIKSuyFPypFmYF/ILyXafZh5Hp80qJub YUVA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:references:in-reply-to:references :in-reply-to:message-id:date:subject:cc:to:from:dmarc-filter :dkim-signature:dkim-signature:arc-authentication-results; bh=JF39jKPibK/L6MHfHa8H+5DgmDDOIlHhL2VNyYugjyU=; b=ufYaTCDj+ImFQYd7HkK2CPX0Y1rRuOQvoxio9Ok5lM8GX1r4DoSACsLpcoI+CDeOEk 5ynKMZm/PF20lRClSlI3JnRpGYjlRJnt6Mjwu3vfy13NHkKjagrbjKk2kB91ETwDPB9L 2buZzkwbesu+LvcTn20zJWjuBTHNq4y1AAfCGPz2YCsvd9yVfWR+3Sk6nfR2WOpjk2pi GBtbEcAu7h0w3Husiib+aw2F9ROmbo5d07Velfg2Q+KRej/wUUrPZbOvl6VaRqWhB9/e ujEQtJ1Wo3HgMhQT2VcAfo7Vy1MYSvrzPCTAPx2HKo7J3BDV3/V/CDSSQk9XGbGmRUsL iUPw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@codeaurora.org header.s=default header.b=Zp90H+rW; dkim=pass header.i=@codeaurora.org header.s=default header.b=F4ond5FH; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id c20-v6si4369205pls.557.2018.05.11.18.49.21; Fri, 11 May 2018 18:49:36 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@codeaurora.org header.s=default header.b=Zp90H+rW; dkim=pass header.i=@codeaurora.org header.s=default header.b=F4ond5FH; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751816AbeELBr0 (ORCPT + 99 others); Fri, 11 May 2018 21:47:26 -0400 Received: from smtp.codeaurora.org ([198.145.29.96]:47218 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750805AbeELBq4 (ORCPT ); Fri, 11 May 2018 21:46:56 -0400 Received: by smtp.codeaurora.org (Postfix, from userid 1000) id 2444C60881; Sat, 12 May 2018 01:46:56 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1526089616; bh=wjPrxjYsNqXr6bJu9mcdhRVftqSaud6DPDGCJ8kU0HI=; h=From:To:Cc:Subject:Date:In-Reply-To:References:In-Reply-To: References:From; b=Zp90H+rWeR633joeal+DXxmShQoxWDmeatHpXySNdEQTrW2Pj9Jcnq7nmzeOhl6OR F3bdcC8ks5VfsYJjI1lwB8CxFIYvc2nw8oBK+2c6Ou4mdQhw25oymRfvAzjiVOSWoO +MIhk7wOipL3vBt3v+f18s6suwAVnx/rpZ/SRKBk= X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on pdx-caf-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.8 required=2.0 tests=ALL_TRUSTED,BAYES_00, DKIM_SIGNED,T_DKIM_INVALID autolearn=no autolearn_force=no version=3.4.0 Received: from codeaurora.org (i-global254.qualcomm.com [199.106.103.254]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: collinsd@smtp.codeaurora.org) by smtp.codeaurora.org (Postfix) with ESMTPSA id C8AF5601EA; Sat, 12 May 2018 01:46:54 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1526089615; bh=wjPrxjYsNqXr6bJu9mcdhRVftqSaud6DPDGCJ8kU0HI=; h=From:To:Cc:Subject:Date:In-Reply-To:References:In-Reply-To: References:From; b=F4ond5FHoaphEXZRgG90iZFrkB0ZqxFpHOg8UvDmmTPFCTH16mbo0kOThXTdvyagf 8u/mQ5181/XrNxyJ2PGHVTRhLk9h11uI81SZMbr/Jsmocn/jEmFxpmNjdQkATaTDqZ PaSPhA9dV24WWMJ26MqxXWmXGjN9suiqXiQpO9T0= DMARC-Filter: OpenDMARC Filter v1.3.2 smtp.codeaurora.org C8AF5601EA Authentication-Results: pdx-caf-mail.web.codeaurora.org; dmarc=none (p=none dis=none) header.from=codeaurora.org Authentication-Results: pdx-caf-mail.web.codeaurora.org; spf=none smtp.mailfrom=collinsd@codeaurora.org From: David Collins To: broonie@kernel.org, lgirdwood@gmail.com, robh+dt@kernel.org, mark.rutland@arm.com Cc: David Collins , linux-arm-msm@vger.kernel.org, linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, rnayak@codeaurora.org, sboyd@kernel.org, dianders@chromium.org Subject: [PATCH 1/2] regulator: of: add property for allowed modes specification Date: Fri, 11 May 2018 18:46:46 -0700 Message-Id: X-Mailer: git-send-email 1.9.1 In-Reply-To: References: In-Reply-To: References: Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Add a common device tree property for regulator nodes to support the specification of allowed operating modes. Signed-off-by: David Collins --- Documentation/devicetree/bindings/regulator/regulator.txt | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/Documentation/devicetree/bindings/regulator/regulator.txt b/Documentation/devicetree/bindings/regulator/regulator.txt index 2babe15b..c627aa0 100644 --- a/Documentation/devicetree/bindings/regulator/regulator.txt +++ b/Documentation/devicetree/bindings/regulator/regulator.txt @@ -59,6 +59,11 @@ Optional properties: - regulator-initial-mode: initial operating mode. The set of possible operating modes depends on the capabilities of every hardware so each device binding documentation explains which values the regulator supports. +- regulator-allowed-modes: list of operating modes that software is allowed to + configure for the regulator at run-time. Elements may be specified in any + order. The set of possible operating modes depends on the capabilities of + every hardware so each device binding document explains which values the + regulator supports. - regulator-system-load: Load in uA present on regulator that is not captured by any consumer request. - regulator-pull-down: Enable pull down resistor when the regulator is disabled. -- The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project