[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160130003404.GI12841@codeaurora.org>
Date: Fri, 29 Jan 2016 16:34:04 -0800
From: Stephen Boyd <sboyd@...eaurora.org>
To: Andi Shyti <andi.shyti@...sung.com>
Cc: linux-samsung-soc@...r.kernel.org,
Sangbeom Kim <sbkim73@...sung.com>,
Krzysztof Kozlowski <k.kozlowski@...sung.com>,
Michael Turquette <mturquette@...libre.com>,
linux-kernel@...r.kernel.org, linux-clk@...r.kernel.org,
Andi Shyti <andi@...zian.org>,
Yadwinder Singh Brar <yadi.brar01@...il.com>,
Jaehoon Chung <jh80.chung@...sung.com>
Subject: Re: [PATCH v3 2/4] clk: s2mps11: allocate only one structure for
clock init
On 01/20, Andi Shyti wrote:
> The driver allocates three structures, s2mpsxx_clk_init, for
> three different clock types (s2mps11, s2mps13 and s2mps14). They
> are quite similar but they differ only by the name. Only one of
> these structures is used, while the others lie unused in the
> memory.
>
> The clock's name, though, is not such a meaningful information
> and by assigning the same name to the initial data we can avoid
> over allocation. The common name chosen will be s2mps11,
> coherently with the device driver name, instead of the clock
> device.
>
> Therefore, remove the structures associated to s2mps13 and
> s2mps14 and use only the one referred to s2mps11 for all kind of
> clocks.
>
> Signed-off-by: Andi Shyti <andi.shyti@...sung.com>
> Suggested-by: Krzysztof Kozlowski <k.kozlowski@...sung.com>
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
Powered by blists - more mailing lists