devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Gerlach <d-gerlach@ti.com>
To: Viresh Kumar <viresh.kumar@linaro.org>, Nishanth Menon <nm@ti.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
	devicetree@vger.kernel.org, linux-pm@vger.kernel.org,
	Tony Lindgren <tony@atomide.com>,
	Yegor Yefremov <yegorslists@googlemail.com>,
	Rob Herring <robh+dt@kernel.org>,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/8] ARM: dts: Add operating-points-v2 tables for TI platforms
Date: Mon, 20 Jun 2016 11:57:14 -0500	[thread overview]
Message-ID: <5768206A.5050501@ti.com> (raw)
In-Reply-To: <20160611024400.GE27439@vireshk-i7>

On 06/10/2016 09:44 PM, Viresh Kumar wrote:
> On 10-06-16, 09:50, Nishanth Menon wrote:
>> On 06/10/2016 06:04 AM, Tony Lindgren wrote:
>>> * Viresh Kumar <viresh.kumar@linaro.org> [160518 21:49]:
>>>> On 18-05-16, 18:36, Dave Gerlach wrote:
>>>>> Hi,
>>>>> This series adds operating-points-v2 tables for am335x, am437x, dra7xx,
>>>>> and am57xx based platforms along with some support patches so that we
>>>>> can enable more OPPs for the CPU on these platforms.
>>>>>
>>>>> These patches rely on the ti-cpufreq series sent here [1] and provide
>>>>> opp-supported-hw data for each OPP so that only the appropriate OPPs
>>>>> for a specific piece of silicon get enabled.
>>>>
>>>> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
>>>
>>> Applying all the dts changes into omap-for-v4.8/dt thanks.
>>>
>>> Tony
>>>
>> Viresh, are we ready with the cpufreq series?
>>
>> https://patchwork.kernel.org/patch/9122961/
>> https://patchwork.kernel.org/patch/9122921/
>>
>> Also current series: https://patchwork.kernel.org/patch/9123071/
>> Seems to have comments pending.
>>
>> Dave is on vacation for another week or so, doubt he can respond in
>> time -> Should we wait on this series till we get the cpufreq support in?
>
> Rafael handles all the merges, etc. It would be better if you can
> reply to that thread instead.
>

Sorry for the delay responding here, the only issue with this series 
would be that we haven't received an ACK on the DT binding doc from 
cpufreq series [1] from a DT maintainer, so if comments are received 
there these patches could potentially change. I had pinged but still no 
response either way.

Regards,
Dave

[1] https://patchwork.kernel.org/patch/9122921/

  reply	other threads:[~2016-06-20 16:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-18 23:36 [PATCH 0/8] ARM: dts: Add operating-points-v2 tables for TI platforms Dave Gerlach
     [not found] ` <cover.1463606963.git.d-gerlach-l0cyMroinI0@public.gmane.org>
2016-05-18 23:36   ` [PATCH 1/8] ARM: dts: am335x: Update MPU regulator range for TI boards Dave Gerlach
2016-05-18 23:36   ` [PATCH 6/8] ARM: dts: dra7: Add dt node for the syscon control module wkup Dave Gerlach
2016-05-18 23:36 ` [PATCH 2/8] ARM: dts: am33xx: Move to operating-points-v2 table and ti-cpufreq driver Dave Gerlach
2016-05-19  4:41   ` Viresh Kumar
2016-05-18 23:36 ` [PATCH 3/8] ARM: dts: am335x-boneblack: Enable 1GHz OPP for cpu Dave Gerlach
2016-05-18 23:36 ` [PATCH 4/8] ARM: dts: am4372: Add operating-points-v2 table Dave Gerlach
2016-05-18 23:36 ` [PATCH 5/8] ARM: dts: am437x-gp-evm: Hook dcdc2 as the cpu0-supply Dave Gerlach
2016-05-18 23:36 ` [PATCH 7/8] ARM: dts: dra7: Move cpus node to parent dts for dra74x and dra72x Dave Gerlach
2016-05-18 23:36 ` [PATCH 8/8] ARM: dts: dra7: Move to operating-points-v2 table Dave Gerlach
2016-05-19  4:47 ` [PATCH 0/8] ARM: dts: Add operating-points-v2 tables for TI platforms Viresh Kumar
2016-06-10 11:04   ` Tony Lindgren
2016-06-10 14:50     ` Nishanth Menon
2016-06-11  2:44       ` Viresh Kumar
2016-06-20 16:57         ` Dave Gerlach [this message]
2016-09-01  2:46           ` 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=5768206A.5050501@ti.com \
    --to=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=mark.rutland@arm.com \
    --cc=nm@ti.com \
    --cc=robh+dt@kernel.org \
    --cc=tony@atomide.com \
    --cc=viresh.kumar@linaro.org \
    --cc=yegorslists@googlemail.com \
    /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).