lists.openwall.net   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  linux-cve-announce  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]
Message-Id: <cover.1377093938.git.viresh.kumar@linaro.org>
Date:	Wed, 21 Aug 2013 20:12:19 +0530
From:	Viresh Kumar <viresh.kumar@...aro.org>
To:	rjw@...k.pl
Cc:	linaro-kernel@...ts.linaro.org, patches@...aro.org,
	cpufreq@...r.kernel.org, linux-pm@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	Viresh Kumar <viresh.kumar@...aro.org>
Subject: [PATCH 00/14] cpufreq: create & use cpufreq_generic_init() routine

Many CPUFreq drivers for SMP system (where all cores share same clock lines), do
similar stuff in their ->init() part.

This patch creates a generic routine in cpufreq core which can be used by these
so that we can remove some redundant code. And later part of patchset makes
other drivers use this infrastructure.

Many drivers which weren't setting policy->cpus haven't been updated as they
might have separate clocks for CPUs and setting all CPUs in policy->cpus may
corrupt them..

This is Sixth part of my cleanup work for CPUFreq, first five are (And
obviously its rebased over them):

1: cpufreq: Introduce cpufreq_table_validate_and_show()
https://lkml.org/lkml/2013/8/8/263

2: cpufreq: define generic routines for cpufreq drivers
https://lkml.org/lkml/2013/8/10/48

3. CPUFreq: Implement light weight ->target(): for 3.13
https://lkml.org/lkml/2013/8/13/349

4. CPUFreq: set policy->cur in cpufreq core instead of drivers
https://lkml.org/lkml/2013/8/14/288

5. CPUFreq: Move freq change notifications out of drivers
https://lkml.org/lkml/2013/8/15/506

All these are pushed here:
https://git.linaro.org/gitweb?p=people/vireshk/linux.git;a=shortlog;h=refs/heads/for-v3.13

Viresh Kumar (14):
  cpufreq: create cpufreq_generic_init() routine
  cpufreq: cpu0: use cpufreq_generic_init() routine
  cpufreq: dbx500: use cpufreq_generic_init() routine
  cpufreq: exynos: use cpufreq_generic_init() routine
  cpufreq: imx6q: use cpufreq_generic_init() routine
  cpufreq: kirkwood: use cpufreq_generic_init() routine
  cpufreq: maple: use cpufreq_generic_init() routine
  cpufreq: pasemi: use cpufreq_generic_init() routine
  cpufreq: pmac64: use cpufreq_generic_init() routine
  cpufreq: s3c: use cpufreq_generic_init() routine
  cpufreq: s5pv210: use cpufreq_generic_init() routine
  cpufreq: sa11x0: use cpufreq_generic_init() routine
  cpufreq: spear: use cpufreq_generic_init() routine
  cpufreq: tegra: use cpufreq_generic_init() routine

 drivers/cpufreq/cpufreq-cpu0.c       | 19 +------------------
 drivers/cpufreq/cpufreq.c            | 31 +++++++++++++++++++++++++++++++
 drivers/cpufreq/dbx500-cpufreq.c     | 21 +--------------------
 drivers/cpufreq/exynos-cpufreq.c     |  7 +------
 drivers/cpufreq/exynos5440-cpufreq.c | 14 ++------------
 drivers/cpufreq/imx6q-cpufreq.c      | 13 +------------
 drivers/cpufreq/kirkwood-cpufreq.c   |  5 +----
 drivers/cpufreq/maple-cpufreq.c      |  9 +--------
 drivers/cpufreq/pasemi-cpufreq.c     |  9 +--------
 drivers/cpufreq/pmac64-cpufreq.c     |  9 +--------
 drivers/cpufreq/s3c2416-cpufreq.c    |  6 ++----
 drivers/cpufreq/s3c24xx-cpufreq.c    | 13 +------------
 drivers/cpufreq/s3c64xx-cpufreq.c    |  5 ++---
 drivers/cpufreq/s5pv210-cpufreq.c    |  4 +---
 drivers/cpufreq/sa1100-cpufreq.c     |  6 +-----
 drivers/cpufreq/sa1110-cpufreq.c     |  6 +-----
 drivers/cpufreq/spear-cpufreq.c      | 14 ++------------
 drivers/cpufreq/tegra-cpufreq.c      | 14 +++++++++-----
 include/linux/cpufreq.h              |  3 +++
 19 files changed, 63 insertions(+), 145 deletions(-)

-- 
1.7.12.rc2.18.g61b472e

--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ