From: dianders@chromium.org (Douglas Anderson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: Add ddc i2c reference to veyron
Date: Wed, 2 Sep 2015 14:25:48 -0700 [thread overview]
Message-ID: <1441229148-12095-1-git-send-email-dianders@chromium.org> (raw)
The ddc-i2c-bus property was missing from the veyron dtsi file since
downstream the ddc-i2c-bus was still being specified in rk3288.dtsi and
nobody noticed when the veyron dtsi was sent upstream. Add it.
Signed-off-by: Douglas Anderson <dianders@chromium.org>
---
Note: I noticed that this was wrong but I don't currently have
graphics up and running on upstream on veyron. Posting this anyway
since it's pretty clear that it's needed. If someone else wants to
try it out that'd be nice, otherwise I'll put it on my list to figure
out how to get myself setup for graphics upstream. ;)
arch/arm/boot/dts/rk3288-veyron.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/boot/dts/rk3288-veyron.dtsi b/arch/arm/boot/dts/rk3288-veyron.dtsi
index 2fa7a0d..275c78c 100644
--- a/arch/arm/boot/dts/rk3288-veyron.dtsi
+++ b/arch/arm/boot/dts/rk3288-veyron.dtsi
@@ -158,6 +158,7 @@
};
&hdmi {
+ ddc-i2c-bus = <&i2c5>;
status = "okay";
};
--
2.5.0.457.gab17608
next reply other threads:[~2015-09-02 21:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-02 21:25 Douglas Anderson [this message]
2015-09-03 0:13 ` [PATCH] ARM: dts: Add ddc i2c reference to veyron Rob Herring
2015-09-03 0:22 ` Doug Anderson
2015-09-03 8:22 ` Russell King - ARM Linux
2015-09-03 14:46 ` Rob Herring
2015-09-03 15:18 ` Russell King - ARM Linux
2015-09-03 15:46 ` Rob Herring
2015-09-03 16:04 ` Doug Anderson
2015-09-03 16:13 ` Lucas Stach
2015-09-03 16:28 ` Doug Anderson
2015-09-03 15:55 ` Doug Anderson
2015-09-03 21:00 ` Doug Anderson
2015-09-03 22:01 ` Heiko Stuebner
2015-09-03 22:56 ` Brian Norris
2015-09-13 12:23 ` Heiko Stübner
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=1441229148-12095-1-git-send-email-dianders@chromium.org \
--to=dianders@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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).