[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-id: <1377020063-30213-1-git-send-email-s.nawrocki@samsung.com>
Date: Tue, 20 Aug 2013 19:34:19 +0200
From: Sylwester Nawrocki <s.nawrocki@...sung.com>
To: linux-arm-kernel@...ts.infradead.org
Cc: linux@....linux.org.uk, mturquette@...aro.org,
jiada_wang@...tor.com, robherring2@...il.com,
grant.likely@...aro.org, broonie@...nel.org, vapier@...too.org,
ralf@...ux-mips.org, kyungmin.park@...sung.com,
shawn.guo@...aro.org, sebastian.hesselbarth@...il.com,
LW@...O-electronics.de, t.figa@...sung.com, g.liakhovetski@....de,
laurent.pinchart@...asonboard.com, linux-kernel@...r.kernel.org,
uclinux-dist-devel@...ckfin.uclinux.org, linux-mips@...ux-mips.org,
linux-sh@...r.kernel.org,
Sylwester Nawrocki <s.nawrocki@...sung.com>
Subject: [PATCH v2 0/4] clk: clock deregistration support
This series combines my previous ones ([1], [2]) adding clk_unregister()
function's implementation and fixing a race condition in the device tree
related part of clk_get().
There are couple changes since the RFC v1:
- moved of_clk_{lock, unlock}, __of_clk_get_from_provider() function
declaractions to a local header,
- renamed clk_dummy_* to clk_nodrv_*.
[1] https://lkml.org/lkml/2013/8/6/306
[2] http://www.spinics.net/lists/arm-kernel/msg265989.html
Sylwester Nawrocki (4):
clk: add common __clk_get(), __clk_put() implementations
clk: implement clk_unregister
clk: Provide not locked variant of of_clk_get_from_provider()
clkdev: Fix race condition in clock lookup from device tree
arch/arm/include/asm/clkdev.h | 2 +
arch/blackfin/include/asm/clkdev.h | 2 +
arch/mips/include/asm/clkdev.h | 2 +
arch/sh/include/asm/clkdev.h | 2 +
drivers/clk/clk.c | 185 +++++++++++++++++++++++++++++++++---
drivers/clk/clk.h | 16 ++++
drivers/clk/clkdev.c | 12 ++-
include/linux/clk-private.h | 5 +
include/linux/clkdev.h | 5 +
9 files changed, 218 insertions(+), 13 deletions(-)
create mode 100644 drivers/clk/clk.h
--
1.7.9.5
--
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