All of lore.kernel.org
 help / color / mirror / Atom feed
From: Javier Martinez Canillas <javier@osg.samsung.com>
To: linux-kernel@vger.kernel.org
Cc: Aaro Koskinen <aaro.koskinen@iki.fi>,
	devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
	Tony Lindgren <tony@atomide.com>,
	Lee Jones <lee.jones@linaro.org>,
	Javier Martinez Canillas <javier@osg.samsung.com>,
	Mark Rutland <mark.rutland@arm.com>
Subject: [PATCH v4 6/8] dt-bindings: mfd: Add TI tps6105x chip bindings
Date: Tue,  4 Apr 2017 11:30:34 -0400	[thread overview]
Message-ID: <20170404153036.6651-7-javier@osg.samsung.com> (raw)
In-Reply-To: <20170404153036.6651-1-javier@osg.samsung.com>

There are Device Tree source files defining a device node for the
tps61050/61052 I2C chip but there isn't a binding document for it.

Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com>

---

Changes in v4:
- Use "dt-bindings: mfd:" prefix in subject line (Rob Herring).
- Add information about what functions the device serve (Lee Jones).

Changes in v3: None
Changes in v2: None

 Documentation/devicetree/bindings/mfd/tps6105x.txt | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/mfd/tps6105x.txt

diff --git a/Documentation/devicetree/bindings/mfd/tps6105x.txt b/Documentation/devicetree/bindings/mfd/tps6105x.txt
new file mode 100644
index 000000000000..93602c7a19c8
--- /dev/null
+++ b/Documentation/devicetree/bindings/mfd/tps6105x.txt
@@ -0,0 +1,17 @@
+* Device tree bindings for TI TPS61050/61052 Boost Converters
+
+The TP61050/TPS61052 is a high-power "white LED driver". The
+device provides LED, GPIO and regulator functionalities.
+
+Required properties:
+- compatible:		"ti,tps61050" or "ti,tps61052"
+- reg:			Specifies the I2C slave address
+
+Example:
+
+i2c0 {
+	tps61052@33 {
+		compatible = "ti,tps61052";
+		reg = <0x33>;
+	};
+};
-- 
2.9.3

  parent reply	other threads:[~2017-04-04 15:31 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-04 15:30 [PATCH v4 0/8] mfd: Add OF device table to I2C drivers that are missing it Javier Martinez Canillas
2017-04-04 15:30 ` Javier Martinez Canillas
2017-04-04 15:30 ` [PATCH v4 1/8] dt-bindings: mfd: Add retu/tahvo ASIC chips bindings Javier Martinez Canillas
2017-04-04 16:54   ` Rob Herring
2017-04-04 17:01     ` Javier Martinez Canillas
2017-04-04 17:01       ` Javier Martinez Canillas
2017-04-11 13:57   ` Lee Jones
2017-04-04 15:30 ` [PATCH v4 2/8] mfd: retu: Drop -mfd suffix from I2C device ID name Javier Martinez Canillas
2017-04-04 15:30   ` Javier Martinez Canillas
2017-04-04 15:30   ` Javier Martinez Canillas
2017-04-11 13:56   ` Lee Jones
2017-04-11 13:56     ` Lee Jones
2017-04-04 15:30 ` [PATCH v4 3/8] mfd: retu: Add OF device ID table Javier Martinez Canillas
2017-04-11 13:56   ` Lee Jones
2017-04-11 13:56     ` Lee Jones
2017-04-04 15:30 ` [PATCH v4 4/8] ARM: dts: n8x0: Add vendor prefix to retu node Javier Martinez Canillas
2017-04-04 15:30   ` Javier Martinez Canillas
2017-04-04 15:30   ` Javier Martinez Canillas
2017-04-04 15:30 ` [PATCH v4 5/8] i2c: i2c-cbus-gpio: Add vendor prefix to retu node in example Javier Martinez Canillas
2017-04-04 15:30 ` Javier Martinez Canillas [this message]
2017-04-04 15:30 ` [PATCH v4 7/8] mfd: tps6105x: Add OF device ID table Javier Martinez Canillas
2017-04-11 13:57   ` Lee Jones
2017-04-11 13:57     ` Lee Jones
2017-04-04 15:30 ` [PATCH v4 8/8] ARM: ux500: Add vendor prefix to tps61052 node Javier Martinez Canillas
2017-04-04 15:30   ` Javier Martinez Canillas
2017-04-04 15:30   ` Javier Martinez Canillas
2017-04-04 16:54 ` [PATCH v4 0/8] mfd: Add OF device table to I2C drivers that are missing it Rob Herring
2017-04-04 16:54   ` Rob Herring
2017-04-04 17:38 ` Aaro Koskinen
2017-04-04 17:38   ` Aaro Koskinen
2017-04-04 17:43 ` Tony Lindgren
2017-04-04 17:43   ` Tony Lindgren
2017-04-04 17:43   ` Tony Lindgren
2017-04-04 17:46   ` Javier Martinez Canillas
2017-04-04 17:46     ` Javier Martinez Canillas
2017-04-04 17:46     ` Javier Martinez Canillas

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=20170404153036.6651-7-javier@osg.samsung.com \
    --to=javier@osg.samsung.com \
    --cc=aaro.koskinen@iki.fi \
    --cc=devicetree@vger.kernel.org \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.