linux-kernel - [RFC v2 0/4] Add basic support for ASV

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: <1384515691-26299-1-git-send-email-sachin.kamat@linaro.org>
Date:	Fri, 15 Nov 2013 17:11:27 +0530
From:	Sachin Kamat <sachin.kamat@...aro.org>
To:	linux-pm@...r.kernel.org
Cc:	linux-samsung-soc@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org, rjw@...ysocki.net,
	kgene.kim@...sung.com, tomasz.figa@...il.com,
	yadi.brar01@...il.com, sachin.kamat@...aro.org,
	myungjoo.ham@...sung.com
Subject: [RFC v2 0/4] Add basic support for ASV

Original cover letter from Yadwinder:
This series is to add basic common infrastructure for ASV.
 Basically ASV is a technique used on samsung SoCs, which provides the
recommended supply voltage for dvfs of arm, mif etc. For a given operating
frequency, the voltage is recommended based on SoC's ASV group.
ASV group gets fussed on SoCs during process of mass production.

This series includes:
 - basic common infrastructue for ASV. It provides common APIs for user drivers
like cpufreq & devfreq and and an interface for SoC specific drivers to
register ASV members(instances)
 - a common platform driver to register ASV members for exynos SoCs
 - an example providing minimal support (only for ARM ASV) for exynos5250 chips

Its just basic skelton which I wanted to get it reviewed or discussed in
early stage, before going ahead on further development based on it.
 Presently example is based on static ASV table provided in SoC specific file,
which I expects to go into DT. But exactly how and where needs to be discussed,
may be in next revisions once we get through the basic skelton.
 Also the location of driver in kernel may also seem odd to someone and
many more things :).

Looking for your valuable reviews and suggestions.

Changes since v1:
* Rebased onto the latest linux-next
* Used devm* and *opp APIs
* Code cleanup and some fixes
* Updated kernel doc and Kconfig text

Yadwinder Singh Brar (4):
  power: asv: Add common ASV support for Samsung SoCs
  power: asv: Add a common ASV driver for Exynos SoCs.
  power: asv: Add support for Exynos5250
  ARM: SAMSUNG: Register static platform device for ASV for Exynos5

 arch/arm/mach-exynos/mach-exynos5-dt.c |    2 +
 drivers/power/Kconfig                  |    1 +
 drivers/power/Makefile                 |    1 +
 drivers/power/asv/Kconfig              |   23 +++++
 drivers/power/asv/Makefile             |    2 +
 drivers/power/asv/asv.c                |  176 ++++++++++++++++++++++++++++++++
 drivers/power/asv/exynos-asv.c         |   78 ++++++++++++++
 drivers/power/asv/exynos-asv.h         |   22 ++++
 drivers/power/asv/exynos5250-asv.c     |  139 +++++++++++++++++++++++++
 include/linux/power/asv-driver.h       |   62 +++++++++++
 include/linux/power/asv.h              |   37 +++++++
 11 files changed, 543 insertions(+)
 create mode 100644 drivers/power/asv/Kconfig
 create mode 100644 drivers/power/asv/Makefile
 create mode 100644 drivers/power/asv/asv.c
 create mode 100644 drivers/power/asv/exynos-asv.c
 create mode 100644 drivers/power/asv/exynos-asv.h
 create mode 100644 drivers/power/asv/exynos5250-asv.c
 create mode 100644 include/linux/power/asv-driver.h
 create mode 100644 include/linux/power/asv.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/