Droid 4 in -next -- still no backlight was Re: [PATCH 1/4] tty: n_gsm: Add support for serdev drivers

Droid 4 in -next -- still no backlight was Re: [PATCH 1/4] tty: n_gsm: Add support for serdev drivers

[Pavel Machek]

[-- Attachment #1.1: Type: text/plain, Size: 1043 bytes --]

Hi!

> We can make use of serdev drivers to do simple device drivers for
> TS 27.010 chanels, and we can handle vendor specific protocols on top
> of TS 27.010 with serdev drivers.

I took all three series (

[PATCHv3 0/3] Lost key-up interrupt handling for omap4-keypa
[PATCH 1/3] Input: atmel_mxt_ts - use runtime PM instead of
[PATCHv5 0/4] n_gsm serdev support and protocol driver for d

) and applied them on top of next-20200320.

Good news is that result boots. (So I did partial testing of the patches).

Bad news is that I still don't have working backlight. I do have LED
and there's backlight device connected to the LED, so I can't control
the LED directly, but the screen is black (and I don't see boot
messages either).

Before I start debugging, does screen work for you in -next, or do you
have some fixes I could try?

Thanks and best regards,
									Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

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

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

Re: Droid 4 in -next -- still no backlight was Re: [PATCH 1/4] tty: n_gsm: Add support for serdev drivers

[Tony Lindgren]

* Pavel Machek <pavel@denx.de> [200322 22:43]:
> Hi!
> 
> > We can make use of serdev drivers to do simple device drivers for
> > TS 27.010 chanels, and we can handle vendor specific protocols on top
> > of TS 27.010 with serdev drivers.
> 
> I took all three series (
> 
> [PATCHv3 0/3] Lost key-up interrupt handling for omap4-keypa
> [PATCH 1/3] Input: atmel_mxt_ts - use runtime PM instead of
> [PATCHv5 0/4] n_gsm serdev support and protocol driver for d
> 
> ) and applied them on top of next-20200320.
> 
> Good news is that result boots. (So I did partial testing of the patches).
> 
> Bad news is that I still don't have working backlight. I do have LED
> and there's backlight device connected to the LED, so I can't control
> the LED directly, but the screen is black (and I don't see boot
> messages either).
> 
> Before I start debugging, does screen work for you in -next, or do you
> have some fixes I could try?

Yes the backlight works for me now just fine with current v5.6-rc.

But yeah, looks like LCD is again broken in current Linux next,
maybe Laurent and Sebastian have some clues?

Regards,

Tony

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

Re: Droid 4 in -next -- still no backlight was Re: [PATCH 1/4] tty: n_gsm: Add support for serdev drivers

[Tony Lindgren]

* Tony Lindgren <tony@atomide.com> [200324 17:02]:
> * Pavel Machek <pavel@denx.de> [200322 22:43]:
> > Before I start debugging, does screen work for you in -next, or do you
> > have some fixes I could try?
> 
> Yes the backlight works for me now just fine with current v5.6-rc.
> 
> But yeah, looks like LCD is again broken in current Linux next,
> maybe Laurent and Sebastian have some clues?

Oh it's just that now display-connector needs to be loaded instead
of the old omap specific hdmi connector :)

See commit e7e67d9a2f1d ("drm/omap: Switch the HDMI and VENC outputs
to drm_bridge") and check that you have the .config options enabled
in that patch also in your custom .config.

Regards,

Tony

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel