From: Sebastian Reichel <sre@debian.org>
To: Sebastian Reichel <sre@debian.org>,
Tony Lindgren <tony@atomide.com>,
Anton Vorontsov <anton@enomsg.org>
Cc: "David Woodhouse" <dwmw2@infradead.org>,
"Grant Likely" <grant.likely@linaro.org>,
"Rob Herring" <rob.herring@calxeda.com>,
"Pawel Moll" <pawel.moll@arm.com>,
"Mark Rutland" <mark.rutland@arm.com>,
"Stephen Warren" <swarren@wwwdotorg.org>,
"Ian Campbell" <ijc+devicetree@hellion.org.uk>,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, "Pali Rohár" <pali.rohar@gmail.com>
Subject: [PATCH 2/2] dt: binding documentation for isp1704 charger
Date: Thu, 14 Nov 2013 12:38:54 +0000 [thread overview]
Message-ID: <1384432734-1490-2-git-send-email-sre@debian.org> (raw)
In-Reply-To: <1384432734-1490-1-git-send-email-sre@debian.org>
Add devicetree binding documentation for isp1704-charger.
Signed-off-by: Sebastian Reichel <sre@debian.org>
---
Documentation/devicetree/bindings/power/isp1704.txt | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
create mode 100644 Documentation/devicetree/bindings/power/isp1704.txt
diff --git a/Documentation/devicetree/bindings/power/isp1704.txt b/Documentation/devicetree/bindings/power/isp1704.txt
new file mode 100644
index 0000000..bbeec11
--- /dev/null
+++ b/Documentation/devicetree/bindings/power/isp1704.txt
@@ -0,0 +1,17 @@
+Binding for NXP ISP1704 USB Charger Detection
+
+Required properties:
+- compatible: Should contain one of the following:
+ * "nxp,isp1704"
+- nxp,enable-gpio: Should contain a phandle to the
+ GPIO pin connected to the chip's enable pin.
+- usb-phy: Should contain a phandle to the USB PHY
+ the ISP1704 is connected to.
+
+Example:
+
+isp1704 {
+ compatible = "nxp,isp1704";
+ nxp,enable-gpio = <&gpio3 3 GPIO_ACTIVE_LOW>;
+ usb-phy = <&usb2_phy>;
+};
--
1.8.4.2
next prev parent reply other threads:[~2013-11-14 12:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-14 12:38 [PATCH 1/2] isp1704_charger: Add DT support Sebastian Reichel
2013-11-14 12:38 ` Sebastian Reichel [this message]
2013-11-15 11:26 ` [PATCH 2/2] dt: binding documentation for isp1704 charger Mark Rutland
[not found] ` <1384432734-1490-1-git-send-email-sre-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
2013-11-14 17:52 ` [PATCH 1/2] isp1704_charger: Add DT support Tony Lindgren
2013-12-01 1:00 ` [PATCHv2 0/2] DT support for isp1704-charger Sebastian Reichel
2013-12-01 1:00 ` [PATCHv2 1/2] isp1704_charger: Add DT support Sebastian Reichel
2013-12-01 1:00 ` [PATCHv2 2/2] dt: binding documentation for isp1704 charger Sebastian Reichel
2013-12-24 2:35 ` [PATCHv2 0/2] DT support for isp1704-charger Anton Vorontsov
2013-11-14 18:05 ` [PATCH 1/2] isp1704_charger: Add DT support Pali Rohár
2013-11-14 22:34 ` Sebastian Reichel
2013-11-15 6:45 ` Pali Rohár
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=1384432734-1490-2-git-send-email-sre@debian.org \
--to=sre@debian.org \
--cc=anton@enomsg.org \
--cc=devicetree@vger.kernel.org \
--cc=dwmw2@infradead.org \
--cc=grant.likely@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pali.rohar@gmail.com \
--cc=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--cc=swarren@wwwdotorg.org \
--cc=tony@atomide.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).