From: Nagarjuna Kristam <nkristam@nvidia.com>
To: <kishon@ti.com>, <robh+dt@kernel.org>, <thierry.reding@gmail.com>,
<jonathanh@nvidia.com>, <balbi@kernel.org>,
<gregkh@linuxfoundation.org>
Cc: <linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-tegra@vger.kernel.org>, <linux-usb@vger.kernel.org>,
<jckuo@nvidia.com>, Nagarjuna Kristam <nkristam@nvidia.com>
Subject: [PATCH V1 1/8] dt-bindings: phy: tegra-xusb: Add charger-detect property
Date: Wed, 18 Mar 2020 16:01:00 +0530 [thread overview]
Message-ID: <1584527467-8058-2-git-send-email-nkristam@nvidia.com> (raw)
In-Reply-To: <1584527467-8058-1-git-send-email-nkristam@nvidia.com>
Add nvidia,charger-detect boolean property for Tegra210 and Tegra186
platforms. This property is used to inform driver to perform charger
detection on corresponding USB 2 port.
Signed-off-by: Nagarjuna Kristam <nkristam@nvidia.com>
---
Documentation/devicetree/bindings/phy/nvidia,tegra124-xusb-padctl.txt | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/Documentation/devicetree/bindings/phy/nvidia,tegra124-xusb-padctl.txt b/Documentation/devicetree/bindings/phy/nvidia,tegra124-xusb-padctl.txt
index 38c5fa2..9b2d2dd 100644
--- a/Documentation/devicetree/bindings/phy/nvidia,tegra124-xusb-padctl.txt
+++ b/Documentation/devicetree/bindings/phy/nvidia,tegra124-xusb-padctl.txt
@@ -190,6 +190,10 @@ Required properties for OTG/Peripheral capable USB2 ports:
and peripheral roles. Connector should be added as subnode.
See usb/usb-conn-gpio.txt.
+Optional properties for OTG/Peripheral capable USB2 ports:
+- nvidia,charger-detect: A boolean property whose presence inform driver to
+ perform charger-detect activity.
+
Optional properties:
- nvidia,internal: A boolean property whose presence determines that a port
is internal. In the absence of this property the port is considered to be
--
2.7.4
next prev parent reply other threads:[~2020-03-18 10:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 10:30 [PATCH V1 0/8] Tegra XUSB charger detect support Nagarjuna Kristam
2020-03-18 10:31 ` Nagarjuna Kristam [this message]
2020-03-30 23:06 ` [PATCH V1 1/8] dt-bindings: phy: tegra-xusb: Add charger-detect property Rob Herring
2020-03-18 10:31 ` [PATCH V1 2/8] usb: gadget: tegra-xudc: Add vbus_draw support Nagarjuna Kristam
2020-03-18 10:31 ` [PATCH V1 3/8] phy: tegra: xusb: Add support for UTMI pad power control Nagarjuna Kristam
2020-03-18 10:31 ` [PATCH V1 4/8] phy: tegra: xusb: Add USB2 pad power control support for Tegra210 Nagarjuna Kristam
2020-03-18 10:31 ` [PATCH V1 5/8] phy: tegra: xusb: Add soc ops API to enable UTMI PAD protection Nagarjuna Kristam
2020-03-18 10:31 ` [PATCH V1 6/8] phy: tegra: xusb: Add support for charger detect Nagarjuna Kristam
2020-03-18 10:31 ` [PATCH V1 7/8] phy: tegra: xusb: Enable charger detect for Tegra186 Nagarjuna Kristam
2020-03-18 10:31 ` [PATCH V1 8/8] phy: tegra: xusb: Enable charger detect for Tegra210 Nagarjuna Kristam
2020-03-29 10:40 ` [PATCH V1 0/8] Tegra XUSB charger detect support Felipe Balbi
2020-03-30 8:46 ` Nagarjuna Kristam
2020-03-30 10:07 ` Felipe Balbi
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=1584527467-8058-2-git-send-email-nkristam@nvidia.com \
--to=nkristam@nvidia.com \
--cc=balbi@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jckuo@nvidia.com \
--cc=jonathanh@nvidia.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
/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).