From: Yong Li <yong.b.li@intel.com>
To: bcousson@baylibre.com, tony@atomide.com, robh+dt@kernel.org,
pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
linux@arm.linux.org.uk, linux-omap@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: sdliyong@gmail.com
Subject: [PATCH] ARM: dts: am335x-boneblack: add i2c1 DT entry
Date: Thu, 2 Jun 2016 15:41:50 +0800 [thread overview]
Message-ID: <1464853310-8738-1-git-send-email-yong.b.li@intel.com> (raw)
From: Yong Li <sdliyong@gmail.com>
Without this patch, I2C-1 is missing on beaglebone black boards
Signed-off-by: Yong Li <sdliyong@gmail.com>
---
arch/arm/boot/dts/am335x-boneblack.dts | 15 +++++++++++++++
1 file changed, 15 insertions(+)
diff --git a/arch/arm/boot/dts/am335x-boneblack.dts b/arch/arm/boot/dts/am335x-boneblack.dts
index 55c0e95..7eee5c4 100644
--- a/arch/arm/boot/dts/am335x-boneblack.dts
+++ b/arch/arm/boot/dts/am335x-boneblack.dts
@@ -64,6 +64,13 @@
AM33XX_IOPAD(0x9b0, PIN_OUTPUT_PULLDOWN | MUX_MODE3) /* xdma_event_intr0 */
>;
};
+
+ i2c1_pins: pinmux_i2c1_pins {
+ pinctrl-single,pins = <
+ AM33XX_IOPAD(0x958, PIN_INPUT_PULLUP | MUX_MODE2) /* spi0_d1.i2c1_sda */
+ AM33XX_IOPAD(0x95c, PIN_INPUT_PULLUP | MUX_MODE2) /* spi0_cs0.i2c1_scl */
+ >;
+ };
};
&lcdc {
@@ -91,6 +98,14 @@
};
};
+&i2c1 {
+ pinctrl-names = "default";
+ pinctrl-0 = <&i2c2_pins>;
+
+ status = "okay";
+ clock-frequency = <100000>;
+};
+
&rtc {
system-power-controller;
};
--
2.7.4
next reply other threads:[~2016-06-02 7:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-02 7:41 Yong Li [this message]
[not found] ` <CAOCHtYib9YxckneM-j0Gk1YE=MnvAwAhvDjEDEuFJbH6W3EcWA@mail.gmail.com>
2016-06-02 17:39 ` [PATCH] ARM: dts: am335x-boneblack: add i2c1 DT entry Tony Lindgren
2016-06-02 17:45 ` Robert Nelson
2016-06-02 17:56 ` Tony Lindgren
2016-06-03 5:46 ` Li, Yong B
2016-06-07 6:00 ` Tony Lindgren
2016-06-07 6:14 ` Li, Yong B
2016-06-07 17:14 ` Robert Nelson
2016-06-08 7:11 ` Li, Yong B
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=1464853310-8738-1-git-send-email-yong.b.li@intel.com \
--to=yong.b.li@intel.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=sdliyong@gmail.com \
--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).