From mboxrd@z Thu Jan  1 00:00:00 1970
From: xiechao_mail@163.com (Chao Xie)
Date: Wed, 10 Sep 2014 09:30:47 +0800 (CST)
Subject: [PATCH 02/12] clk: mmp: add spin lock for clk-frac
In-Reply-To: <20140903180424.11368.36053@quantum>
References: <1409027904-21859-1-git-send-email-chao.xie@marvell.com>
 <1409027904-21859-3-git-send-email-chao.xie@marvell.com>
 <20140903180424.11368.36053@quantum>
Message-ID: <39edaf46.1299c.1485d2f33e4.Coremail.xiechao_mail@163.com>
To: linux-arm-kernel@lists.infradead.org
List-Id: linux-arm-kernel.lists.infradead.org


At 2014-09-04 02:04:24, "Mike Turquette" <mturquette@linaro.org> wrote:
>Quoting Chao Xie (2014-08-25 21:38:14)
>> From: Chao Xie <chao.xie@marvell.com>
>> 
>> The register used by clk-frac may be shared with
>> other clocks.
>> So it needs to use spin lock to protect the register
>> access.
>> 
>> Signed-off-by: Chao Xie <chao.xie@marvell.com>
>
>This patch will break against the latest clk-next due to api changes.
>You can see more here[0] and use this script to update your code if you
>like[1].
>
>Basically the calls to clk_set_rate need to be changed to
>clk_provider_set_rate.

>
I see the patch set [0] is V10 now, and it is not merged to clk-next yet.
So should i wait for the patch set to be merged, then send out the updated patches?

>[0] http://lkml.kernel.org/r/<1409758148-20104-1-git-send-email-tomeu.vizoso@collabora.com>
>[1] http://cgit.collabora.com/git/user/tomeu/linux.git/commit/?h=clk-refactoring-9&id=ea48c0d655346cce26329523cf24574f9ea8feee
>
>Regards,
>Mike