Display on Nokia N950 was Re: Serial cable N9

Display on Nokia N950 was Re: Serial cable N9

[Pavel Machek]

[-- Attachment #1: Type: text/plain, Size: 1076 bytes --]

Hi!

> > For the record, display does not work for me in 4.14 on either n9 or
> > n950. I did not investigate that, yet.
> 
> On v4.13 framebuffer console works OK (I haven't tested anything more in
> fact), but somewhere between v4.13 and v4.14-rc1 there is a commit that
> breaks things - my best guess at this time after a partial git bisect is
> that 906dde0f355bd97c080c215811ae7db1137c4af8 is the one to look at.

Confirmed. Reverting the merge (as far as it can be reverted) gets me
booting N950 with working display. (With 906dde applied, backlight
goes turns on, so it looks like display driver is initialized, but
then machine is killed, probably by watchdog).

AFAICT N950 display never worked on mainline; I'm using Sebastian's
patches to get it to work.

Linux n900 4.14.0-rc7-28884-gdf7c8f0-dirty #283 Wed Nov 1 22:31:35 CET
2017 armv7l GNU/Linux

Filip did all the work here, thanks!
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

Re: Display on Nokia N950 was Re: Serial cable N9

[Pavel Machek]

[-- Attachment #1: Type: text/plain, Size: 2196 bytes --]

Hi!

> > > For the record, display does not work for me in 4.14 on either n9 or
> > > n950. I did not investigate that, yet.
> > 
> > On v4.13 framebuffer console works OK (I haven't tested anything more in
> > fact), but somewhere between v4.13 and v4.14-rc1 there is a commit that
> > breaks things - my best guess at this time after a partial git bisect is
> > that 906dde0f355bd97c080c215811ae7db1137c4af8 is the one to look at.
> 
> Confirmed. Reverting the merge (as far as it can be reverted) gets me
> booting N950 with working display. (With 906dde applied, backlight
> goes turns on, so it looks like display driver is initialized, but
> then machine is killed, probably by watchdog).
> 
> AFAICT N950 display never worked on mainline; I'm using Sebastian's
> patches to get it to work.
> 
> Linux n900 4.14.0-rc7-28884-gdf7c8f0-dirty #283 Wed Nov 1 22:31:35 CET
> 2017 armv7l GNU/Linux
> 
> Filip did all the work here, thanks!

Reverting just fc5cc9678e130196012c17b37e555d53d3d3476b fixes the
display for me, too.

commit fc5cc9678e130196012c17b37e555d53d3d3476b
Author: Tomi Valkeinen <tomi.valkeinen@ti.com>
Date:   Wed Aug 23 12:19:02 2017 +0300

    drm/omap: work-around for omap3 display enable

    Seems that on omap3 enabling a crtc without any planes causes a
    sync
        lost flood. This only happens on the first enable, and after
    that it
        works. This looks like an HW issue and it's unclear why this
    is
        happening or how to fix it.

    This started happening after
    897145d0c7010b4e07fa9bc674b1dfb9a2c6fff9
        ("drm/omapdrm: Move commit_modeset_enables() before
    commit_planes()")
        which, as a work-around, changed omapdrm first to do the
    modeset enable,
        and plane set only after that. This WA should be fine on all
    DSS
        versions, but apparently OMAP3 DSS is an exception.

    This patch reverts that work-around for OMAP3 DSS.

    Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
    
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]