Hi Javier,
On Thu, Oct 27, 2022 at 05:25:49PM +0200, Javier Martinez Canillas wrote:
> On 10/21/22 15:13, max...@cerno.tech wrote:
> > Commit ae71ab585c81 ("drm/vc4: hdmi: Enforce the minimum rate at
> > runtime_resume") reintroduced the call to clk_set_min_rate in an attempt
> > to fix the boot w
On Fri, 21 Oct 2022 15:13:39 +0200, max...@cerno.tech wrote:
> Commit ae71ab585c81 ("drm/vc4: hdmi: Enforce the minimum rate at
> runtime_resume") reintroduced the call to clk_set_min_rate in an attempt
> to fix the boot without a monitor connected on the RaspberryPi3.
>
> However, that introduced
On 10/21/22 15:13, max...@cerno.tech wrote:
> Commit ae71ab585c81 ("drm/vc4: hdmi: Enforce the minimum rate at
> runtime_resume") reintroduced the call to clk_set_min_rate in an attempt
> to fix the boot without a monitor connected on the RaspberryPi3.
>
> However, that introduced a regression bre
On Fri, Oct 21, 2022 at 2:13 PM wrote:
>
> Commit ae71ab585c81 ("drm/vc4: hdmi: Enforce the minimum rate at
> runtime_resume") reintroduced the call to clk_set_min_rate in an attempt
> to fix the boot without a monitor connected on the RaspberryPi3.
>
> However, that introduced a regression breaki
Commit ae71ab585c81 ("drm/vc4: hdmi: Enforce the minimum rate at
runtime_resume") reintroduced the call to clk_set_min_rate in an attempt
to fix the boot without a monitor connected on the RaspberryPi3.
However, that introduced a regression breaking the display output
entirely (black screen but no
