From: liviu.dudau@arm.com (Liviu Dudau)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2 v4] drm/pl111: Support the Versatile Express
Date: Tue, 1 May 2018 09:41:39 +0100 [thread overview]
Message-ID: <20180501084139.GC1027@e110455-lin.cambridge.arm.com> (raw)
In-Reply-To: <14c7fb88-120c-5aa6-e1f3-a26650e857c3@arm.com>
On Mon, Apr 30, 2018 at 03:55:41PM +0100, Robin Murphy wrote:
> On 27/04/18 19:51, Linus Walleij wrote:
> > On Fri, Apr 27, 2018 at 5:02 PM, Robin Murphy <robin.murphy@arm.com> wrote:
> >
> > > I dug a little bit and it seems pl111_modeset_init() is deferring because it
> > > can't find endpoint 0. And given that that's apparently pointing at some
> > > non-existent panel rather than the DVI encoder as I would (naively) expect,
> > > I can at least form a self-consistent explanation and give up on the grounds
> > > that I'm probably missing some important DT changes.
> >
> > Yeah it does help if I also send the required DT changes :/
> >
> > Sorry for my absentmindedness, I'll shoot it off right now so you
> > can test it.
>
> Hooray, thanks for that.
>
> For these 2 patches with a V2P-CA15_A7 tile and the DT fixed up,
>
> Tested-by: Robin Murphy <robin.murphy@arm.com>
>
> Framebuffer console and /dev/fb0 access for the motherboard CLCD works, and
> it keeps out of the way as expected with CONFIG_DRM_HDLCD=y. I can't
> convince an X session to start, but that appears more to do with sii902x
> falling apart*, which I can't be bothered to even try debugging.
>
> Robin.
>
>
> *specifically, lots of this, which I imagine is related to xorg trying to
> either read the EDID or change mode:
> ...
> [ 243.439669] i2c i2c-0: sendbytes: NAK bailout.
> [ 243.454247] i2c i2c-0: sendbytes: NAK bailout.
> [ 247.743261] i2c i2c-0: sendbytes: NAK bailout.
> [ 247.770281] sii902x 0-0039: failed to read status (-6)
> [ 247.786609] i2c i2c-0: sendbytes: NAK bailout.
> [ 248.118522] i2c i2c-0: sendbytes: NAK bailout.
> [ 248.145485] sii902x 0-0039: failed to read status (-6)
> [ 248.177800] i2c i2c-0: sendbytes: NAK bailout.
> [ 258.256500] i2c i2c-0: sendbytes: NAK bailout.
> [ 258.274763] i2c i2c-0: sendbytes: NAK bailout.
> [ 268.499637] i2c i2c-0: sendbytes: NAK bailout.
> [ 268.517899] i2c i2c-0: sendbytes: NAK bailout.
That's a long standing issue that I've never got to the bottom of. The
sii902x seems to have been wired in a curious way on the VExpress board
and it is struggling to pass-through the I2C connection to the monitor.
Best regards,
Liviu
> ...
> _______________________________________________
> dri-devel mailing list
> dri-devel at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
--
====================
| I would like to |
| fix the world, |
| but they're not |
| giving me the |
\ source code! /
---------------
?\_(?)_/?
prev parent reply other threads:[~2018-05-01 8:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-23 7:20 [PATCH 1/2 v4] drm/pl111: Support the Versatile Express Linus Walleij
[not found] ` <4255fd6b-caf7-1347-b97b-ab7b229a08ba@arm.com>
2018-04-26 7:52 ` Linus Walleij
2018-04-27 15:02 ` Robin Murphy
2018-04-27 18:51 ` Linus Walleij
2018-04-30 14:55 ` Robin Murphy
2018-05-01 8:41 ` Liviu Dudau [this message]
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=20180501084139.GC1027@e110455-lin.cambridge.arm.com \
--to=liviu.dudau@arm.com \
--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).