[PATCH linux dev-4.13] clk: aspeed: Prevent reset and enable if clock is already enabled
Andrew Jeffery
andrew at aj.id.au
Wed Mar 7 10:09:33 AEDT 2018
On Wed, 7 Mar 2018, at 06:54, Eddie James wrote:
> Systems are seeing some issues where the LPC clock gets into a bad state
> when the ASPEED clock driver resets and enables the clock during
> startup. The LPC clock (according to AST2500 spec) is enabled by default,
> so resetting and re-enabling is not desired.
Well, maybe. Why do we have to avoid this sequence?
> Add a simple check before the
> enable procedure to see if the clock is already enabled.
I don't think this actually solves the problem, just papers over it. Can we solve it properly?
Andrew
More information about the openbmc
mailing list