[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALt+6nqxMZjuZuOKaj8Cx4dcNZx0n-0F9aa97d-vZoMWeN=bOw@mail.gmail.com>
Date: Mon, 4 Nov 2024 14:09:46 +0200
From: Giedrius Statkevičius <giedriuswork@...il.com>
To: Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>, Maxime Ripard <mripard@...nel.org>,
Thomas Zimmermann <tzimmermann@...e.de>, David Airlie <airlied@...il.com>, Simona Vetter <simona@...ll.ch>,
Jani Nikula <jani.nikula@...ux.intel.com>, Rodrigo Vivi <rodrigo.vivi@...el.com>,
Joonas Lahtinen <joonas.lahtinen@...ux.intel.com>, Tvrtko Ursulin <tursulin@...ulin.net>
Cc: Ankit Nautiyal <ankit.k.nautiyal@...el.com>, dri-devel@...ts.freedesktop.org,
linux-kernel@...r.kernel.org, intel-gfx@...ts.freedesktop.org,
intel-xe@...ts.freedesktop.org
Subject: Re: [PATCH v2] drm/i915/lspcon: do not hardcode settle timeout
Hello,
Kind ping.
On Thu, 17 Oct 2024 at 10:57, Giedrius Statkevičius
<giedriuswork@...il.com> wrote:
>
> Avoid hardcoding the LSPCON settle timeout because it takes a longer
> time on certain chips made by certain vendors. Use the function that
> already exists to determine the timeout.
>
> Reviewed-by: Ankit Nautiyal <ankit.k.nautiyal@...el.com>
> Signed-off-by: Giedrius Statkevičius <giedriuswork@...il.com>
Powered by blists - more mailing lists