[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <166566305526.1731673.7313352763401370465.b4-ty@cerno.tech>
Date: Thu, 13 Oct 2022 14:11:01 +0200
From: Maxime Ripard <maxime@...no.tech>
To: Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Thomas Zimmermann <tzimmermann@...e.de>,
Maxime Ripard <mripard@...nel.org>,
Maxime Ripard <maxime@...no.tech>,
David Airlie <airlied@...ux.ie>,
Daniel Vetter <daniel@...ll.ch>, Emma Anholt <emma@...olt.net>
Cc: dri-devel@...ts.freedesktop.org,
Marc Kleine-Budde <mkl@...gutronix.de>,
Stefan Wahren <stefan.wahren@...e.com>,
linux-kernel@...r.kernel.org
Subject: Re: (subset) [PATCH 2/2] drm/vc4: hdmi: Check the HSM rate at runtime_resume
On Thu, 29 Sep 2022 11:21:18 +0200, Maxime Ripard wrote:
> If our HSM clock has not been properly initialized, any register access
> will silently lock up the system.
>
> Let's check that this can't happen by adding a check for the rate before
> any register access, and error out otherwise.
>
>
> [...]
Applied to drm/drm-misc (drm-misc-fixes).
Thanks!
Maxime
Powered by blists - more mailing lists