From: Stefan Roese <sr@denx.de>
To: linux-mips@vger.kernel.org
Cc: Paul Burton <paul.burton@mips.com>,
Harvey Hunt <harveyhuntnexus@gmail.com>,
John Crispin <john@phrozen.org>
Subject: [PATCH 1/3 v3] MIPS: ralink: mt7628a.dtsi: Add I2C controller DT node
Date: Fri, 9 Aug 2019 14:19:16 +0200 [thread overview]
Message-ID: <20190809121918.25047-1-sr@denx.de> (raw)
This patch adds the I2C controller description to the MT7628A dtsi file.
Signed-off-by: Stefan Roese <sr@denx.de>
Cc: Paul Burton <paul.burton@mips.com>
Cc: Harvey Hunt <harveyhuntnexus@gmail.com>
Cc: John Crispin <john@phrozen.org>
---
v3:
- No change (I2C controller driver is now available in mainline)
v2:
- Use Harvey's new email address (not at imgtec)
- Use correct linux-mips list address
arch/mips/boot/dts/ralink/mt7628a.dtsi | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/arch/mips/boot/dts/ralink/mt7628a.dtsi b/arch/mips/boot/dts/ralink/mt7628a.dtsi
index 61f8621e88b3..742bcc1dc2e0 100644
--- a/arch/mips/boot/dts/ralink/mt7628a.dtsi
+++ b/arch/mips/boot/dts/ralink/mt7628a.dtsi
@@ -199,6 +199,22 @@
status = "disabled";
};
+ i2c: i2c@900 {
+ compatible = "mediatek,mt7621-i2c";
+ reg = <0x900 0x100>;
+
+ pinctrl-names = "default";
+ pinctrl-0 = <&pinmux_i2c_i2c>;
+
+ resets = <&resetc 16>;
+ reset-names = "i2c";
+
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ status = "disabled";
+ };
+
uart0: uartlite@c00 {
compatible = "ns16550a";
reg = <0xc00 0x100>;
--
2.22.0
next reply other threads:[~2019-08-09 12:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-09 12:19 Stefan Roese [this message]
2019-08-09 12:19 ` [PATCH 2/3 v3] dt-bindings: mips: Add gardena vendor prefix and board description Stefan Roese
2019-08-09 17:07 ` Rob Herring
2019-08-09 12:19 ` [PATCH 3/3 v3] MIPS: ralink: Add GARDENA smart Gateway MT7688 board Stefan Roese
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=20190809121918.25047-1-sr@denx.de \
--to=sr@denx.de \
--cc=harveyhuntnexus@gmail.com \
--cc=john@phrozen.org \
--cc=linux-mips@vger.kernel.org \
--cc=paul.burton@mips.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).