[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <175834607850.4354.8043302414076275007@lazor>
Date: Fri, 19 Sep 2025 22:27:58 -0700
From: Stephen Boyd <sboyd@...nel.org>
To: Alexander Stein <alexander.stein@...tq-group.com>, Michael Turquette <mturquette@...libre.com>, Tero Kristo <kristo@...nel.org>
Cc: Matthias Schiffer <matthias.schiffer@...group.com>, linux-omap@...r.kernel.org, linux-clk@...r.kernel.org, linux-kernel@...r.kernel.org, Alexander Stein <alexander.stein@...tq-group.com>
Subject: Re: [PATCH 1/1] clk: ti: am33xx: keep WKUP_DEBUGSS_CLKCTRL enabled
Quoting Alexander Stein (2025-08-25 07:08:11)
> From: Matthias Schiffer <matthias.schiffer@...group.com>
>
> As described in AM335x Errata Advisory 1.0.42, WKUP_DEBUGSS_CLKCTRL
> can't be disabled - the clock module will just be stuck in transitioning
> state forever, resulting in the following warning message after the wait
> loop times out:
>
> l3-aon-clkctrl:0000:0: failed to disable
>
> Just add the clock to enable_init_clks, so no attempt is made to disable
> it.
>
> Signed-off-by: Matthias Schiffer <matthias.schiffer@...group.com>
> Signed-off-by: Alexander Stein <alexander.stein@...tq-group.com>
> ---
Applied to clk-next
Powered by blists - more mailing lists