From: Lukasz Majewski <lukma@denx.de>
To: Dave Gerlach <d-gerlach@ti.com>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
Rob Herring <robh+dt@kernel.org>,
Tony Lindgren <tony@atomide.com>,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
Nishanth Menon <nm@ti.com>
Subject: Re: [PATCH v5 0/4] cpufreq: Introduce TI CPUFreq/OPP Driver
Date: Sat, 4 Feb 2017 00:23:14 +0100 [thread overview]
Message-ID: <20170204002314.7ce27aee@jawa> (raw)
In-Reply-To: <20170203172929.23940-1-d-gerlach@ti.com>
Hi Dave,
> Hi,
> This is v5 of the series to introduce the ti-cpufreq driver
> which parses SoC data and provides opp-supported-hw data to the
> OPP core in order to enable the proper OPPs for the silicon in use.
>
> History:
> v4: http://www.spinics.net/lists/linux-omap/msg134629.html
> v3: http://www.spinics.net/lists/linux-omap/msg132733.html
> v2: http://www.spinics.net/lists/linux-omap/msg131601.html
> v1: http://www.spinics.net/lists/linux-omap/msg129089.html
>
> Very minor changes from v4:
> * In patch 2 change "opp_table0" to "opp_table" in example
> * Add acks on all patches (he approved change in patch 2)
> from Viresh
>
> DT patches to enable this driver will follow after the DT binding is
> merged. Branch for testing, with updated DT nodes, pushed here [1].
>
> Regards,
> Dave
>
> [1]
> https://github.com/dgerlach/linux-pm/commits/upstream/ti-cpufreq-driver-new-v5
For the whole series:
Tested-by: Lukasz Majewski <lukma@denx.de>
(code backported to v4.9)
Test HW: AM5718 and AM5728.
>
> Dave Gerlach (4):
> PM / OPP: Expose _of_get_opp_desc_node as dev_pm_opp API
> Documentation: dt: add bindings for ti-cpufreq
> cpufreq: ti: Add cpufreq driver to determine available OPPs at
> runtime cpufreq: dt: Don't use generic platdev driver for ti-cpufreq
> platforms
>
> .../devicetree/bindings/cpufreq/ti-cpufreq.txt | 128 ++++++++++
> drivers/base/power/opp/of.c | 9 +-
> drivers/cpufreq/Kconfig.arm | 11 +
> drivers/cpufreq/Makefile | 1 +
> drivers/cpufreq/cpufreq-dt-platdev.c | 2 -
> drivers/cpufreq/ti-cpufreq.c | 272
> +++++++++++++++++++++
> include/linux/pm_opp.h | 6 + 7 files
> changed, 423 insertions(+), 6 deletions(-) create mode 100644
> Documentation/devicetree/bindings/cpufreq/ti-cpufreq.txt create mode
> 100644 drivers/cpufreq/ti-cpufreq.c
>
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
next prev parent reply other threads:[~2017-02-03 23:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 17:29 [PATCH v5 0/4] cpufreq: Introduce TI CPUFreq/OPP Driver Dave Gerlach
[not found] ` <20170203172929.23940-1-d-gerlach-l0cyMroinI0@public.gmane.org>
2017-02-03 17:29 ` [PATCH v5 1/4] PM / OPP: Expose _of_get_opp_desc_node as dev_pm_opp API Dave Gerlach
2017-02-03 17:29 ` [PATCH v5 3/4] cpufreq: ti: Add cpufreq driver to determine available OPPs at runtime Dave Gerlach
2017-02-03 17:29 ` [PATCH v5 2/4] Documentation: dt: add bindings for ti-cpufreq Dave Gerlach
2017-02-08 14:44 ` Rob Herring
2017-02-08 14:45 ` Dave Gerlach
2017-02-09 0:02 ` Rafael J. Wysocki
2017-02-09 15:36 ` Dave Gerlach
2017-02-09 15:35 ` [PATCH v6 " Dave Gerlach
2017-02-09 16:01 ` Rob Herring
2017-02-09 22:03 ` Rafael J. Wysocki
2017-02-10 3:13 ` Viresh Kumar
2017-02-10 12:28 ` Rafael J. Wysocki
[not found] ` <3046998.7dExGlRDb3-yvgW3jdyMHm1GS7QM15AGw@public.gmane.org>
2017-02-10 20:55 ` Dave Gerlach
2017-02-03 17:29 ` [PATCH v5 4/4] cpufreq: dt: Don't use generic platdev driver for ti-cpufreq platforms Dave Gerlach
2017-02-03 23:23 ` Lukasz Majewski [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-02-07 16:51 [PATCH v5 0/4] cpufreq: Introduce TI CPUFreq/OPP Driver Dave Gerlach
[not found] ` <20170207165107.29394-1-d-gerlach-l0cyMroinI0@public.gmane.org>
2017-02-07 16:52 ` Dave Gerlach
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=20170204002314.7ce27aee@jawa \
--to=lukma@denx.de \
--cc=d-gerlach@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@kernel.org \
--cc=tony@atomide.com \
--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).