[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200324170110.GB37466@atomide.com>
Date: Tue, 24 Mar 2020 10:01:10 -0700
From: Tony Lindgren <tony@...mide.com>
To: Pavel Machek <pavel@...x.de>
Cc: kernel list <linux-kernel@...r.kernel.org>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
linux-omap@...r.kernel.org, sre@...nel.org, nekit1000@...il.com,
mpartap@....net, merlijn@...zup.org, martin_rysavy@...trum.cz,
Peter Hurley <peter@...leysoftware.com>,
linux-serial@...r.kernel.org, devicetree@...r.kernel.org,
Laurent Pinchart <laurent.pinchart@...asonboard.com>
Subject: Re: Droid 4 in -next -- still no backlight was Re: [PATCH 1/4] tty:
n_gsm: Add support for serdev drivers
* Pavel Machek <pavel@...x.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
Powered by blists - more mailing lists