[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <84cyj9es6g.fsf@jogness.linutronix.de>
Date: Tue, 05 Nov 2024 14:23:11 +0106
From: John Ogness <john.ogness@...utronix.de>
To: Jocelyn Falempe <jfalempe@...hat.com>, Maarten Lankhorst
<maarten.lankhorst@...ux.intel.com>, Maxime Ripard <mripard@...nel.org>,
Thomas Zimmermann <tzimmermann@...e.de>, David Airlie <airlied@...il.com>,
Daniel Vetter <daniel@...ll.ch>, Javier Martinez Canillas
<javierm@...hat.com>, "Guilherme G . Piccoli" <gpiccoli@...lia.com>,
bluescreen_avenger@...izon.net, Caleb Connolly
<caleb.connolly@...aro.org>, Petr Mladek <pmladek@...e.com>,
dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org
Cc: Jocelyn Falempe <jfalempe@...hat.com>
Subject: Re: [PATCH v6 5/6] drm/log: Implement suspend/resume
On 2024-11-05, Jocelyn Falempe <jfalempe@...hat.com> wrote:
> Normally the console is already suspended when the graphic driver
> suspend callback is called, but if the parameter no_console_suspend
> is set, it might still be active.
> So call console_stop()/console_start() in the suspend/resume
> callbacks, to make sure it won't try to write to the framebuffer
> while the graphic driver is suspended.
>
> Signed-off-by: Jocelyn Falempe <jfalempe@...hat.com>
Reviewed-by: John Ogness <john.ogness@...utronix.de>
Powered by blists - more mailing lists