[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <154706036649.15366.4782578068557224270@swboyd.mtv.corp.google.com>
Date: Wed, 09 Jan 2019 10:59:26 -0800
From: Stephen Boyd <sboyd@...nel.org>
To: Jeffrey Hugo <jhugo@...eaurora.org>, mturquette@...libre.com
Cc: bjorn.andersson@...aro.org, andy.gross@...aro.org,
david.brown@...aro.org, linux-arm-msm@...r.kernel.org,
linux-clk@...r.kernel.org, linux-kernel@...r.kernel.org,
kishon@...com, robh+dt@...nel.org, mark.rutland@....com,
devicetree@...r.kernel.org, gregkh@...uxfoundation.org,
balbi@...nel.org, linux-usb@...r.kernel.org,
Jeffrey Hugo <jhugo@...eaurora.org>
Subject: Re: [PATCH v1 2/6] clk: qcom: Skip halt checks on gcc_usb3_phy_pipe_clk for 8998
Quoting Jeffrey Hugo (2019-01-04 08:50:15)
> The gcc_usb3_phy_pipe_clk is generated by the phy, but is also used by
> the phy during init. The clock needs to be enabled during the init
> sequence, but may not be fully active until after the init sequence is
> complete. This causes a catch-22 if the clock status is checked during
> enable. As a result, skip the checks to avoid the troubling situation.
>
> Signed-off-by: Jeffrey Hugo <jhugo@...eaurora.org>
> ---
Applied to clk-next
Powered by blists - more mailing lists