[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <3109854.2nZ1kdONIi@phil>
Date: Thu, 09 May 2019 10:46:49 +0200
From: Heiko Stuebner <heiko@...ech.de>
To: Douglas Anderson <dianders@...omium.org>
Cc: Shawn Lin <shawn.lin@...k-chips.com>, hal@...emmerich.com,
linux-rockchip@...ts.infradead.org, mka@...omium.org,
Michael Turquette <mturquette@...libre.com>,
Stephen Boyd <sboyd@...nel.org>, linux-kernel@...r.kernel.org,
linux-clk@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] clk: rockchip: Don't yell about bad mmc phases when getting
Am Freitag, 3. Mai 2019, 23:22:08 CEST schrieb Douglas Anderson:
> At boot time, my rk3288-veyron devices yell with 8 lines that look
> like this:
> [ 0.000000] rockchip_mmc_get_phase: invalid clk rate
>
> This is because the clock framework at clk_register() time tries to
> get the phase but we don't have a parent yet.
>
> While the errors appear to be harmless they are still ugly and, in
> general, we don't want yells like this in the log unless they are
> important.
>
> There's no real reason to be yelling here. We can still return
> -EINVAL to indicate that the phase makes no sense without a parent.
> If someone really tries to do tuning and the clock is reported as 0
> then we'll see the yells in rockchip_mmc_set_phase().
>
> Fixes: 4bf59902b500 ("clk: rockchip: Prevent calculating mmc phase if clock rate is zero")
> Signed-off-by: Douglas Anderson <dianders@...omium.org>
applied for 5.3
Thanks
Heiko
Powered by blists - more mailing lists