[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <152113766641.111154.15925874974920514772@swboyd.mtv.corp.google.com>
Date: Thu, 15 Mar 2018 11:14:26 -0700
From: Stephen Boyd <sboyd@...nel.org>
To: Eddie James <eajames@...ux.vnet.ibm.com>,
linux-kernel@...r.kernel.org
Cc: linux-clk@...r.kernel.org, joel@....id.au, mturquette@...libre.com,
eajames@...ux.vnet.ibm.com, mine260309@...il.com,
ryan_chen@...eedtech.com
Subject: Re: [PATCH v2 1/2] clk: aspeed: Fix is_enabled for certain clocks
Quoting Eddie James (2018-03-08 12:57:19)
> Some of the Aspeed clocks are disabled by setting the relevant bit in
> the "clock stop control" register to one, while others are disabled by
> setting their bit to zero. The driver already uses a flag per gate to
> identify this behavior, but doesn't apply it in the clock is_enabled
> function.
>
> Use the existing gate flag to correctly return whether or not a clock
> is enabled in the aspeed_clk_is_enabled function.
>
> Signed-off-by: Eddie James <eajames@...ux.vnet.ibm.com>
> ---
Applied to clk-fixes
Powered by blists - more mailing lists