[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <152297065260.143116.4250583205921081457@swboyd.mtv.corp.google.com>
Date: Thu, 05 Apr 2018 16:24:12 -0700
From: Stephen Boyd <sboyd@...nel.org>
To: Michael Turquette <mturquette@...libre.com>,
Stephen Boyd <sboyd@...eaurora.org>,
Taniya Das <tdas@...eaurora.org>
Cc: Andy Gross <andy.gross@...aro.org>,
David Brown <david.brown@...aro.org>,
Rajendra Nayak <rnayak@...eaurora.org>,
Odelu Kukatla <okukatla@...eaurora.org>,
Amit Nischal <anischal@...eaurora.org>,
linux-arm-msm@...r.kernel.org, linux-soc@...r.kernel.org,
linux-clk@...r.kernel.org, linux-kernel@...r.kernel.org,
Taniya Das <tdas@...eaurora.org>
Subject: Re: [PATCH 2/3] clk: qcom: gdsc: Add support to poll for higher timeout value
Quoting Taniya Das (2018-04-02 03:45:44)
> From: Amit Nischal <anischal@...eaurora.org>
>
> For some gdscs, it might take longer time up to 500us for
> updating their status. So add support for the same by
> defining a new flag 'GDS_TIMEOUT' to mark such gdsc in
> order to poll their status for longer timeout value.
>
> Signed-off-by: Amit Nischal <anischal@...eaurora.org>
> Signed-off-by: Taniya Das <tdas@...eaurora.org>
> ---
Let's just increase the timeout to 500 if it's required? This is a
timeout, so we're not really expecting to hit it anyway so optimizing
the uncommon case is not useful.
Powered by blists - more mailing lists