From: Chen-Yu Tsai <wens@csie.org>
To: cip-dev@lists.cip-project.org
Cc: nobuhiro1.iwamatsu@toshiba.co.jp, JohnsonCH.Chen@moxa.com,
pavel@denx.de, wens@csie.org
Subject: Re: [cip-dev] [PATCH 4.4.y-cip 0/3] Add TI CPUFreq/OPP hw-supported driver
Date: Thu, 28 May 2020 16:28:50 +0800 [thread overview]
Message-ID: <20200528082850.GA6672@wens.csie.org> (raw)
In-Reply-To: <20200501093615.GC11782@amd>
[-- Attachment #1: Type: text/plain, Size: 1518 bytes --]
Hi,
On Fri, May 01, 2020 at 11:36:15AM +0200, Pavel Machek wrote:
> Hi!
>
> > > Tested on MOXA UC-8100A-ME that uses AM335x's SoC we have in house.
> > >
> > > Dave Gerlach (1):
> > > cpufreq: ti: Add cpufreq driver to determine available OPPs at runtime
> > >
> > > Viresh Kumar (2):
> > > PM / OPP: Add "opp-supported-hw" binding
> > > PM / OPP: Parse 'opp-supported-hw' binding
> >
> > Looks good to me.
> > If there is no opinion, I will apply this series.
>
> I have made some comments. 3/3 has double-free in error path, that one
> may be worth fixing before the merge.
I will take over backporting these patches from Johnson, and other
in MOXA's kernel tree that were included from TI's SDK.
TI's SDK actually includes many more patches related to PM/OPP and
cpufreq. Most of them are already in mainline. I plan to backport
these in several steps, split by the original submission and kernel
version.
The first part will be from kernel v4.5, which includes the series
"PM / OPP: opp-supported-hw and <prop>-name bindings" [1] and later
-rc fixes in v4.5
The second part will be from kernel v4.6, which is the series
"PM / OPP: Introduce APIs to transition OPPs" [2] and -rc fixes.
The last part will be the ti-cpufreq driver and related fixes request
by Pavel, as well as conversion of am33xx dts to opp-v2.
Regards
ChenYu
[1] https://lore.kernel.org/linux-pm/cover.1447209519.git.viresh.kumar@linaro.org/
[2] https://lore.kernel.org/linux-pm/cover.1454992186.git.viresh.kumar@linaro.org/
[-- Attachment #2: Type: text/plain, Size: 419 bytes --]
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#4652): https://lists.cip-project.org/g/cip-dev/message/4652
Mute This Topic: https://lists.cip-project.org/mt/73369238/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2020-05-28 12:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 3:33 [cip-dev] [PATCH 4.4.y-cip 0/3] Add TI CPUFreq/OPP hw-supported driver Johnson CH Chen (陳昭勳)
2020-04-30 8:58 ` Nobuhiro Iwamatsu
2020-05-01 9:36 ` Pavel Machek
2020-05-28 8:28 ` Chen-Yu Tsai [this message]
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=20200528082850.GA6672@wens.csie.org \
--to=wens@csie.org \
--cc=JohnsonCH.Chen@moxa.com \
--cc=cip-dev@lists.cip-project.org \
--cc=nobuhiro1.iwamatsu@toshiba.co.jp \
--cc=pavel@denx.de \
/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