* [GIT PULL] cpufreq/arm changes for 5.3
@ 2019-06-26 7:16 Viresh Kumar
2019-06-27 21:34 ` Rafael J. Wysocki
0 siblings, 1 reply; 2+ messages in thread
From: Viresh Kumar @ 2019-06-26 7:16 UTC (permalink / raw)
To: Rafael J. Wysocki; +Cc: Linux PM
Hi Rafael,
This pull request contains:
- Minor fixes for brcmstb driver (Florian).
- New imx-cpufreq driver, its bindings and code around it (Leonard).
- New Raspberry Pi driver (Nicolas).
- Minor fix for s5pv210 driver (Pawel).
- Minor cleanup for armada driver (YueHaibing).
--
viresh
-------------------------8<-------------------------
The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9:
Linux 5.2-rc1 (2019-05-19 15:47:09 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/vireshk/pm.git cpufreq/arm/linux-next
for you to fetch changes up to f9020441dbc39133591ff72b420f21f51896afc5:
cpufreq: s5pv210: Don't flood kernel log after cpufreq change (2019-06-24 10:27:02 +0530)
----------------------------------------------------------------
Florian Fainelli (2):
cpufreq: brcmstb-avs-cpufreq: Fix initial command check
cpufreq: brcmstb-avs-cpufreq: Fix types for voltage/frequency
Leonard Crestez (5):
cpufreq: Add imx-cpufreq-dt driver
dt-bindings: imx-cpufreq-dt: Document opp-supported-hw usage
cpufreq: imx-cpufreq-dt: Fix no OPPs available on unfused parts
cpufreq: imx-cpufreq-dt: Remove global platform match list
cpufreq: Switch imx7d to imx-cpufreq-dt for speed grading
Nicolas Saenz Julienne (1):
cpufreq: add driver for Raspberry Pi
Paweł Chmiel (1):
cpufreq: s5pv210: Don't flood kernel log after cpufreq change
YueHaibing (1):
cpufreq: armada-37xx: Remove set but not used variable 'freq'
.../devicetree/bindings/cpufreq/imx-cpufreq-dt.txt | 37 +++++++++
drivers/cpufreq/Kconfig.arm | 17 ++++
drivers/cpufreq/Makefile | 2 +
drivers/cpufreq/armada-37xx-cpufreq.c | 4 +-
drivers/cpufreq/brcmstb-avs-cpufreq.c | 12 +--
drivers/cpufreq/cpufreq-dt-platdev.c | 5 +-
drivers/cpufreq/imx-cpufreq-dt.c | 97 ++++++++++++++++++++++
drivers/cpufreq/raspberrypi-cpufreq.c | 97 ++++++++++++++++++++++
drivers/cpufreq/s5pv210-cpufreq.c | 2 +-
drivers/soc/imx/soc-imx8.c | 3 +
10 files changed, 265 insertions(+), 11 deletions(-)
create mode 100644 Documentation/devicetree/bindings/cpufreq/imx-cpufreq-dt.txt
create mode 100644 drivers/cpufreq/imx-cpufreq-dt.c
create mode 100644 drivers/cpufreq/raspberrypi-cpufreq.c
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [GIT PULL] cpufreq/arm changes for 5.3
2019-06-26 7:16 [GIT PULL] cpufreq/arm changes for 5.3 Viresh Kumar
@ 2019-06-27 21:34 ` Rafael J. Wysocki
0 siblings, 0 replies; 2+ messages in thread
From: Rafael J. Wysocki @ 2019-06-27 21:34 UTC (permalink / raw)
To: Viresh Kumar; +Cc: Rafael J. Wysocki, Linux PM
On Wed, Jun 26, 2019 at 9:16 AM Viresh Kumar <viresh.kumar@linaro.org> wrote:
>
> Hi Rafael,
>
> This pull request contains:
>
> - Minor fixes for brcmstb driver (Florian).
> - New imx-cpufreq driver, its bindings and code around it (Leonard).
> - New Raspberry Pi driver (Nicolas).
> - Minor fix for s5pv210 driver (Pawel).
> - Minor cleanup for armada driver (YueHaibing).
>
> --
> viresh
>
> -------------------------8<-------------------------
> The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9:
>
> Linux 5.2-rc1 (2019-05-19 15:47:09 -0700)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/vireshk/pm.git cpufreq/arm/linux-next
>
> for you to fetch changes up to f9020441dbc39133591ff72b420f21f51896afc5:
>
> cpufreq: s5pv210: Don't flood kernel log after cpufreq change (2019-06-24 10:27:02 +0530)
>
Pulled, thanks!
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2019-06-27 21:34 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-06-26 7:16 [GIT PULL] cpufreq/arm changes for 5.3 Viresh Kumar
2019-06-27 21:34 ` Rafael J. Wysocki
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).