lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Mon,  1 Sep 2014 11:47:02 -0700
From:	Mike Turquette <>
	"Rafael J. Wysocki" <>,
	Viresh Kumar <>
Cc:, Mike Turquette <>,
	Andrew Lunn <>,
	Tomeu Vizoso <>
Subject: [PATCH 0/3] arm: kirkwood: model cpu clock mux and update cpufreq driver

While reviewing Tomeu's "Per-user clock constraints" series I saw that
the Kirkwood cpufreq driver needed to use a new, public clk_is_enabled()
which I hoped not to merge [0].

This led to some investigation as to why this was needed and with
Andrew's help I came to realize that the powersave_clk on the kirkwood
platform acts more like a clock signal multiplexer than a gate. This mux
is unique to Kirkwood; none of the other mvebu platforms have it.

This series updates the kirkwood clock driver to model the powersave_clk
as a mux instead of a gate, and it updates and slightly simplifies the
cpufreq driver to use this clock as a mux.

Rafael & Viresh: I'd prefer to merge the cpufreq driver patch through
the clock tree since Tomeu's changes to the clock core depend on it.


Mike Turquette (3):
  clk: mvebu: share locks between gate clocks
  clk: mvebu: powersave clock is a multiplexer
  cpufreq: kirkwood: use the powersave multiplexer

 drivers/clk/mvebu/common.c         |   9 ++--
 drivers/clk/mvebu/common.h         |   2 +
 drivers/clk/mvebu/kirkwood.c       | 102 ++++++++++++++++++++++++++++++++++++-
 drivers/cpufreq/kirkwood-cpufreq.c |  14 ++---
 4 files changed, 113 insertions(+), 14 deletions(-)


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists