From: briannorris@chromium.org (Brian Norris)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: Add ddc i2c reference to veyron
Date: Thu, 3 Sep 2015 15:56:17 -0700 [thread overview]
Message-ID: <20150903225617.GA75694@google.com> (raw)
In-Reply-To: <CAD=FV=WkFPitTsagQa+94DAWujzYECVqk7fO+OUdrfFq3bWTuQ@mail.gmail.com>
On Thu, Sep 03, 2015 at 02:00:26PM -0700, Doug Anderson wrote:
> On Wed, Sep 2, 2015 at 2:25 PM, Douglas Anderson <dianders@chromium.org> wrote:
> > 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. ;)
>
> OK, I've used Heiko's "somewhat stable" branch to test this against
> something very close to mainline.
>
> Without my patch I can't read the HDMI EDID. With my patch I can. :)
Same for veyron-jaq:
Tested-by: Brian Norris <briannorris@chromium.org>
next prev parent reply other threads:[~2015-09-03 22:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-02 21:25 [PATCH] ARM: dts: Add ddc i2c reference to veyron Douglas Anderson
2015-09-03 0:13 ` 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 [this message]
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=20150903225617.GA75694@google.com \
--to=briannorris@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).