[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150501011043.GF32407@codeaurora.org>
Date: Thu, 30 Apr 2015 18:10:43 -0700
From: Stephen Boyd <sboyd@...eaurora.org>
To: Dong Aisheng <aisheng.dong@...escale.com>
Cc: linux-clk@...r.kernel.org, linux-kernel@...r.kernel.org,
mturquette@...aro.org, shawn.guo@...aro.org, b29396@...escale.com,
linux-arm-kernel@...ts.infradead.org,
Ranjani.Vaidyanathan@...escale.com, b20596@...escale.com,
r64343@...escale.com, b20788@...escale.com
Subject: Re: [PATCH RFC v1 5/5] clk: introduce clk_core_enable_lock and
clk_core_disable_lock functions
On 04/15, Dong Aisheng wrote:
> This can be usefully when clock core wants to enable/disable clocks.
> Then we don't have to convert the struct clk_core to struct clk to call
> clk_enable/clk_disable which is a bit un-align with exist using.
>
> Cc: Mike Turquette <mturquette@...aro.org>
> Cc: Stephen Boyd <sboyd@...eaurora.org>
> Signed-off-by: Dong Aisheng <aisheng.dong@...escale.com>
> ---
Yeah let's add this patch either before patch 4 or squash it into
patch 4. Also, avoid adding more function prototypes please.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists