[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <152641691632.237094.11483387696003404182@swboyd.mtv.corp.google.com>
Date: Tue, 15 May 2018 13:41:56 -0700
From: Stephen Boyd <sboyd@...nel.org>
To: Chanwoo Choi <cw00.choi@...sung.com>,
David Airlie <airlied@...ux.ie>,
Enric Balletbo i Serra <enric.balletbo@...labora.com>,
Heiko Stuebner <heiko@...ech.de>,
Kyungmin Park <kyungmin.park@...sung.com>,
Michael Turquette <mturquette@...libre.com>,
MyungJoo Ham <myungjoo.ham@...sung.com>,
Rob Herring <robh+dt@...nel.org>,
Sandy Huang <hjc@...k-chips.com>,
Will Deacon <will.deacon@....com>
Cc: linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org,
Derek Basehore <dbasehore@...omium.org>,
linux-clk@...r.kernel.org, linux-rockchip@...ts.infradead.org,
dri-devel@...ts.freedesktop.org, Lin Huang <hl@...k-chips.com>,
kernel@...labora.com, Sean Paul <seanpaul@...omium.org>,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [RFC PATCH 07/10] clk: rockchip: set clk-ddr to GET_RATE_NOCACHE.
Quoting Enric Balletbo i Serra (2018-05-14 14:16:07)
> From: Derek Basehore <dbasehore@...omium.org>
>
> This adds the flag to the clk-ddr in rockchip to not use the cached
> rate for get_rate. This is to handle timeout error conditions in SMC
> for the set rate function.
We need some more information here. Why does timeout error condition in
set_rate() matter for get_rate()?
Powered by blists - more mailing lists