[PATCH v4 RESEND 0/7] clk: bcm281xx: updates

[Alex Elder]

This series includes updates for the bcm281xx clock code.  It is
dependent on the following patch, which has been taken into the
clk-fixes tree:
    clk: bcm281xx: don't use unnamed structs or unions
    https://lkml.org/lkml/2014/4/7/322

There are three groups of patches:
    - Some straightforward code cleanups
    - Changing CCU and clock definitions so they're almost
      completely initialized statically (i.e., not at run-time)
    - Add two small features

Initially this series included support for "prerequisite clocks"
but that has been removed so it can be discussed independently.

The patches in this series--based on the current linus/master branch
plus the patch mentioned above--are available here:
    http://git.linaro.org/landing-teams/working/broadcom/kernel.git
    Branch review/bcm-clk-next-v4

    					-Alex

History:
  - v4: Rebased on current linus/master and reworked to account
  	for the no-longer-unnamed union and struct members.
  - v3: Dropped prerequisite clock support so resolving how
	best to handle that can be resolved separately.  As
	a result, bus clock support is no longer included.
  - v2: Removed one unrelated patch from the series.

Alex Elder (7):
  clk: bcm281xx: warn if ccu_wait_bit() fails
  clk: bcm281xx: use init_data.name for clock name
  clk: bcm281xx: change some symbol names
  clk: bcm281xx: initialize CCU structures statically
  clk: bcm281xx: define CCU clock data statically
  clk: bcm281xx: add clock policy support
  clk: bcm281xx: add clock hysteresis support

 drivers/clk/bcm/clk-bcm281xx.c   | 243 +++++++++++++++++----------------------
 drivers/clk/bcm/clk-kona-setup.c | 229 ++++++++++++++++++++++++++----------
 drivers/clk/bcm/clk-kona.c       | 212 ++++++++++++++++++++++++++++++++--
 drivers/clk/bcm/clk-kona.h       | 160 +++++++++++++++++++++-----
 4 files changed, 611 insertions(+), 233 deletions(-)

-- 
1.9.1

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/