From: Subbaraman Narayanamurthy <quic_subbaram@quicinc.com>
To: Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>,
"Rob Herring" <robh+dt@kernel.org>
Cc: <linux-arm-msm@vger.kernel.org>, <linux-gpio@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
"Subbaraman Narayanamurthy" <quic_subbaram@quicinc.com>
Subject: [PATCH 1/2] dt-bindings: pinctrl: qcom-pmic-gpio: Add output-{enable,disable} properties
Date: Mon, 13 Sep 2021 19:57:25 -0700 [thread overview]
Message-ID: <1631588246-4811-2-git-send-email-quic_subbaram@quicinc.com> (raw)
In-Reply-To: <1631588246-4811-1-git-send-email-quic_subbaram@quicinc.com>
Add support for the pinconf DT property output-enable, output-disable
so that output can be enabled/disabled.
Signed-off-by: Subbaraman Narayanamurthy <quic_subbaram@quicinc.com>
---
Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml b/Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml
index 9bd01db..fa7c319 100644
--- a/Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml
+++ b/Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml
@@ -170,6 +170,8 @@ $defs:
input-enable: true
output-high: true
output-low: true
+ output-enable: true
+ output-disable: true
power-source: true
qcom,drive-strength:
--
2.7.4
next prev parent reply other threads:[~2021-09-14 2:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-14 2:57 [PATCH 0/2] pinctrl: qcom: spmi-gpio: Add support to enable/disable output Subbaraman Narayanamurthy
2021-09-14 2:57 ` Subbaraman Narayanamurthy [this message]
2021-09-21 20:23 ` [PATCH 1/2] dt-bindings: pinctrl: qcom-pmic-gpio: Add output-{enable,disable} properties Rob Herring
2021-09-23 21:34 ` Linus Walleij
2021-09-14 2:57 ` [PATCH 2/2] pinctrl: qcom: spmi-gpio: add support to enable/disable output Subbaraman Narayanamurthy
2021-09-21 21:53 ` Bjorn Andersson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1631588246-4811-2-git-send-email-quic_subbaram@quicinc.com \
--to=quic_subbaram@quicinc.com \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).