linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Paweł Chmiel" <pawel.mikolaj.chmiel@gmail.com>
To: kgene@kernel.org
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
	linux-samsung-soc@vger.kernel.org, linux-pm@vger.kernel.org,
	viresh.kumar@linaro.org, rjw@rjwysocki.net,
	linux@armlinux.org.uk, krzk@kernel.org,
	linux-kernel@vger.kernel.org, robh+dt@kernel.org,
	linux-arm-kernel@lists.infradead.org,
	"Paweł Chmiel" <pawel.mikolaj.chmiel@gmail.com>
Subject: [PATCH v2 0/4] ARM: dts: s5pv210: Enable cpufreq support
Date: Thu, 10 Jan 2019 21:52:11 +0100	[thread overview]
Message-ID: <20190110205215.22030-1-pawel.mikolaj.chmiel@gmail.com> (raw)

This patchset enables cpufreq support using s5pv210-cpufreq driver.

First patch adds missing dmc nodes, which are required by driver.

Second patch is cosmetic, it stops driver from flooding kernel log with
 messages, after every change of freq.

Third patch adds defer probe support for regulators, needed by driver.
It was observed, that those regulators can be no yet initialized, when
 driver is probed, so we should wait till we can get them.

Last patch enables required kernel config options.

Changes from v1:
  - Added Acked-by to one of patches
  - Fix compilation error after changes in driver
  - Reorganize code (so it's smaller), inside patch which logs information
    about defered probe of regulators

Paweł Chmiel (4):
  ARM: dts: s5pv210: Add dmc nodes
  cpufreq: s5pv210: Don't flood kernel log after cpufreq change
  cpufreq: s5pv210: Defer probe if getting regulators fail
  ARM: defconfig: s5pv210: Add cpufreq support

 arch/arm/boot/dts/s5pv210.dtsi     | 12 +++++++++++
 arch/arm/configs/s5pv210_defconfig |  6 ++++++
 drivers/cpufreq/s5pv210-cpufreq.c  | 34 ++++++++++++++++++------------
 3 files changed, 38 insertions(+), 14 deletions(-)

-- 
2.17.1


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2019-01-10 20:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-10 20:52 Paweł Chmiel [this message]
2019-01-10 20:52 ` [PATCH v2 1/4] ARM: dts: s5pv210: Add dmc nodes Paweł Chmiel
2019-01-11  8:32   ` Krzysztof Kozlowski
2019-01-11  9:41     ` Viresh Kumar
2019-01-11  9:47       ` Krzysztof Kozlowski
2019-01-10 20:52 ` [PATCH v2 2/4] cpufreq: s5pv210: Don't flood kernel log after cpufreq change Paweł Chmiel
2019-01-10 20:52 ` [PATCH v2 3/4] cpufreq: s5pv210: Defer probe if getting regulators fail Paweł Chmiel
2019-01-11  9:46   ` Krzysztof Kozlowski
2019-01-11  9:53     ` Paweł Chmiel
2019-01-10 20:52 ` [PATCH v2 4/4] ARM: defconfig: s5pv210: Add cpufreq support Paweł Chmiel
2019-01-13  9:34   ` Krzysztof Kozlowski

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=20190110205215.22030-1-pawel.mikolaj.chmiel@gmail.com \
    --to=pawel.mikolaj.chmiel@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kgene@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=rjw@rjwysocki.net \
    --cc=robh+dt@kernel.org \
    --cc=viresh.kumar@linaro.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).