From: Matthias Brugger <matthias.bgg@gmail.com>
To: robh+dt@kernel.org, mark.rutland@arm.com
Cc: wsa@the-dreams.de, tglx@linutronix.de, jason@lakedaemon.net,
marc.zyngier@arm.com, linux-i2c@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
Matthias Brugger <matthias.bgg@gmail.com>
Subject: [PATCH 3/4] dt-bindigns: i2c-mtk: Delete bindings
Date: Mon, 22 May 2017 11:40:20 +0200 [thread overview]
Message-ID: <20170522094021.7837-3-matthias.bgg@gmail.com> (raw)
In-Reply-To: <20170522094021.7837-1-matthias.bgg@gmail.com>
The bindings file list bindings for mt1827 and mt8135 but
these bindings are not supported by the driver. Remove the bindings.
Also do some minor style changes to the compatible documentation
Signed-off-by: Matthias Brugger <matthias.bgg@gmail.com>
---
Documentation/devicetree/bindings/i2c/i2c-mtk.txt | 8 +++-----
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/Documentation/devicetree/bindings/i2c/i2c-mtk.txt b/Documentation/devicetree/bindings/i2c/i2c-mtk.txt
index 0ce6fa3242f0..060a9ec98215 100644
--- a/Documentation/devicetree/bindings/i2c/i2c-mtk.txt
+++ b/Documentation/devicetree/bindings/i2c/i2c-mtk.txt
@@ -4,11 +4,9 @@ The Mediatek's I2C controller is used to interface with I2C devices.
Required properties:
- compatible: value should be either of the following.
- (a) "mediatek,mt6577-i2c", for i2c compatible with mt6577 i2c.
- (b) "mediatek,mt6589-i2c", for i2c compatible with mt6589 i2c.
- (c) "mediatek,mt8127-i2c", for i2c compatible with mt8127 i2c.
- (d) "mediatek,mt8135-i2c", for i2c compatible with mt8135 i2c.
- (e) "mediatek,mt8173-i2c", for i2c compatible with mt8173 i2c.
+ "mediatek,mt6577-i2c": for i2c compatible with mt6577.
+ "mediatek,mt6589-i2c": for i2c compatible with mt6589.
+ "mediatek,mt8173-i2c": for i2c compatible with mt8173.
- reg: physical base address of the controller and dma base, length of memory
mapped region.
- interrupts: interrupt number to the cpu.
--
2.12.0
next prev parent reply other threads:[~2017-05-22 9:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-22 9:40 [PATCH 1/4] dt-bindings: mtk-sysirq: Correct bindings for supported SoCs Matthias Brugger
2017-05-22 9:40 ` [PATCH 2/4] dt-bindings: i2c-mt6577: Rename file to reflect bindings Matthias Brugger
[not found] ` <20170522094021.7837-2-matthias.bgg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-06-07 16:15 ` Wolfram Sang
2017-05-22 9:40 ` Matthias Brugger [this message]
2017-06-07 16:15 ` [PATCH 3/4] dt-bindigns: i2c-mtk: Delete bindings Wolfram Sang
2017-05-22 9:40 ` [PATCH 4/4] dt-bindings: i2c-mtk: Add mt7623 binding Matthias Brugger
2017-06-07 16:15 ` Wolfram Sang
[not found] ` <20170522094021.7837-1-matthias.bgg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-05-30 23:13 ` [PATCH 1/4] dt-bindings: mtk-sysirq: Correct bindings for supported SoCs Rob Herring
2017-05-31 12:05 ` Matthias Brugger
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=20170522094021.7837-3-matthias.bgg@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
--cc=wsa@the-dreams.de \
/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).