From: Pavel Machek <pavel@denx.de>
To: nobuhiro1.iwamatsu@toshiba.co.jp
Cc: JohnsonCH.Chen@moxa.com, cip-dev@lists.cip-project.org, pavel@denx.de
Subject: Re: [cip-dev] [PATCH 4.4.y-cip 0/3] Add TI CPUFreq/OPP hw-supported driver
Date: Fri, 1 May 2020 11:36:15 +0200 [thread overview]
Message-ID: <20200501093615.GC11782@amd> (raw)
In-Reply-To: <OSAPR01MB3667E8AE3A76EB13D1C03BF292AA0@OSAPR01MB3667.jpnprd01.prod.outlook.com>
[-- Attachment #1.1: Type: text/plain, Size: 684 bytes --]
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.
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 419 bytes --]
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#4613): https://lists.cip-project.org/g/cip-dev/message/4613
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]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2020-05-04 22:42 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 [this message]
2020-05-28 8:28 ` Chen-Yu Tsai
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=20200501093615.GC11782@amd \
--to=pavel@denx.de \
--cc=JohnsonCH.Chen@moxa.com \
--cc=cip-dev@lists.cip-project.org \
--cc=nobuhiro1.iwamatsu@toshiba.co.jp \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.