Hi,
On 16-12-2019 15:14, Ville Syrjälä wrote:
On Mon, Dec 16, 2019 at 02:51:54PM +0100, Hans de Goede wrote:
Hi,
Thank you for the reviews.
On 16-12-2019 14:45, Ville Syrjälä wrote:
On Sun, Dec 15, 2019 at 05:38:08PM +0100, Hans de Goede wrote:
When the LCD has not been turned on by the
On Mon, Dec 16, 2019 at 02:51:54PM +0100, Hans de Goede wrote:
> Hi,
>
> Thank you for the reviews.
>
> On 16-12-2019 14:45, Ville Syrjälä wrote:
> > On Sun, Dec 15, 2019 at 05:38:08PM +0100, Hans de Goede wrote:
> >> When the LCD has not been turned on by the firmware/GOP, because e.g. the
> >>
Hi,
Thank you for the reviews.
On 16-12-2019 14:45, Ville Syrjälä wrote:
On Sun, Dec 15, 2019 at 05:38:08PM +0100, Hans de Goede wrote:
When the LCD has not been turned on by the firmware/GOP, because e.g. the
device was booted with an external monitor connected over HDMI, we should
not turn
On Sun, Dec 15, 2019 at 05:38:08PM +0100, Hans de Goede wrote:
> When the LCD has not been turned on by the firmware/GOP, because e.g. the
> device was booted with an external monitor connected over HDMI, we should
> not turn on the panel-enable GPIO when we request it.
>
> Turning on the
On Sun, Dec 15, 2019 at 5:38 PM Hans de Goede wrote:
> When the LCD has not been turned on by the firmware/GOP, because e.g. the
> device was booted with an external monitor connected over HDMI, we should
> not turn on the panel-enable GPIO when we request it.
>
> Turning on the panel-enable
When the LCD has not been turned on by the firmware/GOP, because e.g. the
device was booted with an external monitor connected over HDMI, we should
not turn on the panel-enable GPIO when we request it.
Turning on the panel-enable GPIO when we request it, means we turn it on
too early in the
