linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: amit.daniel@samsung.com (Amit Daniel Kachhap)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V5 0/4] cpufreq: exynos5440: support for cpufreq driver
Date: Thu, 28 Mar 2013 13:35:18 +0530	[thread overview]
Message-ID: <1364457923-8499-1-git-send-email-amit.daniel@samsung.com> (raw)

Submitting the V5 version of exynos5440 cpufreq driver. This patchset addresses
all the coding and design concerns raised especially by Viresh.

Changes in V5:
* Removed the unnecessary DT look up entry from mach-exynos5-dt.c.
* Fixed all coding and comments issue raised by Viresh.

Changes in V4:
* Added dev_err logs instead of pr_err.
* Used the devm_ioremap_resource API.
* Implemented several coding guidelines and minor error comments from Sylwester,
  Russell and Viresh.

Changes in V3:
* Converted the driver to probe based as suggested by Viresh. This is also
  beneficial for multiplatform kernel.
* Other coding guidelines related changes.
* Moved the DT node outside cpu0 node as the driver is now a platform
  driver.

Changes in V2:
* Added OPP library support to parse DT parameters.
* Removed a hack to handle interrupts in bootup.
* Implemented other review comments from Viresh and Inder.

All these patches are dependent on Thomas Abraham common clock patches.
(http://www.mail-archive.com/linux-samsung-soc at vger.kernel.org/msg15860.html)
This whole patch series is based on 3.9-rc4.

Amit Daniel Kachhap (4):
  cpufreq: exynos: Add cpufreq driver for exynos5440
  cpufreq: exynos: Remove error return even if no soc is found
  arm: exynos: Enable OPP library support for exynos5440
  arm: dts: Add cpufreq controller node for Exynos5440 SoC

 .../bindings/cpufreq/cpufreq-exynos5440.txt        |   28 ++
 arch/arm/boot/dts/exynos5440.dtsi                  |   12 +
 arch/arm/mach-exynos/Kconfig                       |    2 +
 drivers/cpufreq/Kconfig.arm                        |    9 +
 drivers/cpufreq/Makefile                           |    1 +
 drivers/cpufreq/exynos-cpufreq.c                   |    2 +-
 drivers/cpufreq/exynos5440-cpufreq.c               |  474 ++++++++++++++++++++
 7 files changed, 527 insertions(+), 1 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/cpufreq/cpufreq-exynos5440.txt
 create mode 100644 drivers/cpufreq/exynos5440-cpufreq.c

             reply	other threads:[~2013-03-28  8:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-28  8:05 Amit Daniel Kachhap [this message]
2013-03-28  8:05 ` [PATCH V5 1/4] cpufreq: exynos: Add cpufreq driver for exynos5440 Amit Daniel Kachhap
2013-03-28  8:53   ` Viresh Kumar
2013-03-28 12:42   ` Viresh Kumar
2013-04-08  8:25     ` amit daniel kachhap
2013-03-28  8:05 ` [PATCH V5 2/4] cpufreq: exynos: Remove error return even if no soc is found Amit Daniel Kachhap
2013-03-28  8:05 ` [PATCH V5 3/4] arm: exynos: Enable OPP library support for exynos5440 Amit Daniel Kachhap
2013-03-28  8:05 ` [PATCH V5 4/4] arm: dts: Add cpufreq controller node for Exynos5440 SoC Amit Daniel Kachhap
2013-03-28  8:33 ` [PATCH V5 0/4] cpufreq: exynos5440: support for cpufreq driver Viresh Kumar
2013-04-05 12:38 ` Rafael J. Wysocki
2013-04-08  8:36   ` amit daniel kachhap
2013-04-08 12:02     ` Kukjin Kim
2013-04-08 19:49       ` Rafael J. Wysocki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1364457923-8499-1-git-send-email-amit.daniel@samsung.com \
    --to=amit.daniel@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).