linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nagarjuna Kristam <nkristam@nvidia.com>
To: <vkoul@kernel.org>, <kishon@ti.com>
Cc: <thierry.reding@gmail.com>, <devicetree@vger.kernel.org>,
	<linux-tegra@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	"Nagarjuna Kristam" <nkristam@nvidia.com>
Subject: [PATCH V5 1/7] dt-bindings: phy: tegra-xusb: Add charger-detect property
Date: Mon, 20 Jul 2020 15:25:42 +0530	[thread overview]
Message-ID: <1595238948-20531-2-git-send-email-nkristam@nvidia.com> (raw)
In-Reply-To: <1595238948-20531-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>
Acked-by: Rob Herring <robh@kernel.org>
Acked-by: Thierry Reding <treding@nvidia.com>
---
V4-V5:
 - No changes
---
V3:
 - Added Acked-by updates to commit message.
---
V2:
 - Added Acked-by updates to commit message.
---
 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


  reply	other threads:[~2020-07-20  9:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-20  9:55 [PATCH V5 0/7] Tegra XUSB charger detect support Nagarjuna Kristam
2020-07-20  9:55 ` Nagarjuna Kristam [this message]
2020-07-20  9:55 ` [PATCH V5 2/7] phy: tegra: xusb: Add support for UTMI pad power control Nagarjuna Kristam
2020-07-20  9:55 ` [PATCH V5 3/7] phy: tegra: xusb: Add USB2 pad power control support for Tegra210 Nagarjuna Kristam
2020-08-23 14:03   ` Vinod Koul
2020-07-20  9:55 ` [PATCH V5 4/7] phy: tegra: xusb: Add soc ops API to enable UTMI PAD protection Nagarjuna Kristam
2020-08-31  7:35   ` Vinod Koul
2020-07-20  9:55 ` [PATCH V5 5/7] phy: tegra: xusb: Add support for charger detect Nagarjuna Kristam
2020-08-31  8:50   ` Vinod Koul
2020-07-20  9:55 ` [PATCH V5 6/7] phy: tegra: xusb: Enable charger detect for Tegra186 Nagarjuna Kristam
2020-07-20  9:55 ` [PATCH V5 7/7] phy: tegra: xusb: Enable charger detect for Tegra210 Nagarjuna Kristam

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=1595238948-20531-2-git-send-email-nkristam@nvidia.com \
    --to=nkristam@nvidia.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kishon@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=thierry.reding@gmail.com \
    --cc=vkoul@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).