All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Gerlach <d-gerlach@ti.com>
To: Tony Lindgren <tony@atomide.com>, Rob Herring <robh+dt@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
	devicetree@vger.kernel.org, linux-pm@vger.kernel.org,
	Viresh Kumar <viresh.kumar@linaro.org>,
	Mark Rutland <mark.rutland@arm.com>, Nishanth Menon <nm@ti.com>
Subject: Re: [PATCH v2 0/3] ARM: dts: Add operating-points-v2 tables for TI platforms
Date: Wed, 14 Sep 2016 11:45:14 -0500	[thread overview]
Message-ID: <57D97E9A.90400@ti.com> (raw)
In-Reply-To: <20160913220244.txdiak6ikujvwzjk@atomide.com>

Hi Tony,
On 09/13/2016 05:02 PM, Tony Lindgren wrote:
> Hi,
>
> * Dave Gerlach <d-gerlach@ti.com> [160831 19:49]:
>> Hi,
>> This is v2 of the series to add operating-points-v2 tables for am335x,
>> am437x, dra7, and am57x platforms, but really just updates the already
>> merged v1 found here [1].
>>
>> It seems v1 was merged without the binding being finalized so this series
>> just updates the nodes that are already present in order to work with the
>> new bindings coming in v2 of the ti-cpufreq driver series which will follow
>> shortly.
>
> Assuming this will have to wait based on what you mentioned about
> am335x cpufreq regression. I guess you'll instead send few patches
> to revert?
>

Correct, these should not be merged, I will be sending a fixup series 
until this series is ready.

I needed to resend the ti-cpufreq driver at [2] to get a response about 
the dt binding and other updates Viresh asked for and sent this to 
update the merged nodes so they would work with the driver. But the 
driver has not been merged yet, so in order to re-enable the previously 
existing cpufreq support on those platforms I must revert three patches 
from v1 [1] of this series that got merged, which I will send.

I also found that 7694ca6e1d6f ("cpufreq: omap: Use generic platdev 
driver") which went in v4.6-rc1 had already broken the existing cpufreq 
support on am335x and dra7xx, so it's been missing for some time. I can 
send a patch fixing that as well but I will need to remove it once the 
ti-cpufreq driver in [2] below gets merged as that driver must create 
the cpufreq-dt platform device instead of cpufreq-dt-platdev. So I will 
send a series that can fix cpufreq until ti-cpufreq is ready which will 
give us better support for more OPPs on am335x, am437x (which has no 
implementation today), and dra7xx.

Regards,
Dave

[1] 
http://lists.infradead.org/pipermail/linux-arm-kernel/2016-May/430205.html
[2] http://www.spinics.net/lists/devicetree/msg141152.html

> Regards,
>
> Tony
>
>> [1] http://lists.infradead.org/pipermail/linux-arm-kernel/2016-May/430205.html
>>
>> Dave Gerlach (3):
>>    ARM: dts: am33xx: Change operating-points-v2 table to am3352 version
>>    ARM: dts: am4372: Change operating-points-v2 table to am4372 version
>>    ARM: dts: dra7: Change operating-points-v2 table to dra7 version
>>
>>   arch/arm/boot/dts/am33xx.dtsi | 2 +-
>>   arch/arm/boot/dts/am4372.dtsi | 2 +-
>>   arch/arm/boot/dts/dra7.dtsi   | 2 +-
>>   3 files changed, 3 insertions(+), 3 deletions(-)
>>
>> --
>> 2.9.0
>>


WARNING: multiple messages have this Message-ID (diff)
From: d-gerlach@ti.com (Dave Gerlach)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/3] ARM: dts: Add operating-points-v2 tables for TI platforms
Date: Wed, 14 Sep 2016 11:45:14 -0500	[thread overview]
Message-ID: <57D97E9A.90400@ti.com> (raw)
In-Reply-To: <20160913220244.txdiak6ikujvwzjk@atomide.com>

Hi Tony,
On 09/13/2016 05:02 PM, Tony Lindgren wrote:
> Hi,
>
> * Dave Gerlach <d-gerlach@ti.com> [160831 19:49]:
>> Hi,
>> This is v2 of the series to add operating-points-v2 tables for am335x,
>> am437x, dra7, and am57x platforms, but really just updates the already
>> merged v1 found here [1].
>>
>> It seems v1 was merged without the binding being finalized so this series
>> just updates the nodes that are already present in order to work with the
>> new bindings coming in v2 of the ti-cpufreq driver series which will follow
>> shortly.
>
> Assuming this will have to wait based on what you mentioned about
> am335x cpufreq regression. I guess you'll instead send few patches
> to revert?
>

Correct, these should not be merged, I will be sending a fixup series 
until this series is ready.

I needed to resend the ti-cpufreq driver at [2] to get a response about 
the dt binding and other updates Viresh asked for and sent this to 
update the merged nodes so they would work with the driver. But the 
driver has not been merged yet, so in order to re-enable the previously 
existing cpufreq support on those platforms I must revert three patches 
from v1 [1] of this series that got merged, which I will send.

I also found that 7694ca6e1d6f ("cpufreq: omap: Use generic platdev 
driver") which went in v4.6-rc1 had already broken the existing cpufreq 
support on am335x and dra7xx, so it's been missing for some time. I can 
send a patch fixing that as well but I will need to remove it once the 
ti-cpufreq driver in [2] below gets merged as that driver must create 
the cpufreq-dt platform device instead of cpufreq-dt-platdev. So I will 
send a series that can fix cpufreq until ti-cpufreq is ready which will 
give us better support for more OPPs on am335x, am437x (which has no 
implementation today), and dra7xx.

Regards,
Dave

[1] 
http://lists.infradead.org/pipermail/linux-arm-kernel/2016-May/430205.html
[2] http://www.spinics.net/lists/devicetree/msg141152.html

> Regards,
>
> Tony
>
>> [1] http://lists.infradead.org/pipermail/linux-arm-kernel/2016-May/430205.html
>>
>> Dave Gerlach (3):
>>    ARM: dts: am33xx: Change operating-points-v2 table to am3352 version
>>    ARM: dts: am4372: Change operating-points-v2 table to am4372 version
>>    ARM: dts: dra7: Change operating-points-v2 table to dra7 version
>>
>>   arch/arm/boot/dts/am33xx.dtsi | 2 +-
>>   arch/arm/boot/dts/am4372.dtsi | 2 +-
>>   arch/arm/boot/dts/dra7.dtsi   | 2 +-
>>   3 files changed, 3 insertions(+), 3 deletions(-)
>>
>> --
>> 2.9.0
>>

  reply	other threads:[~2016-09-14 16:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-01  2:48 [PATCH v2 0/3] ARM: dts: Add operating-points-v2 tables for TI platforms Dave Gerlach
2016-09-01  2:48 ` Dave Gerlach
2016-09-01  2:48 ` [PATCH v2 1/3] ARM: dts: am33xx: Change operating-points-v2 table to am3352 version Dave Gerlach
2016-09-01  2:48   ` Dave Gerlach
2016-09-01  2:48 ` [PATCH v2 2/3] ARM: dts: am4372: Change operating-points-v2 table to am4372 version Dave Gerlach
2016-09-01  2:48   ` Dave Gerlach
2016-09-01  2:48 ` [PATCH v2 3/3] ARM: dts: dra7: Change operating-points-v2 table to dra7 version Dave Gerlach
2016-09-01  2:48   ` Dave Gerlach
     [not found] ` <20160901024816.32390-1-d-gerlach-l0cyMroinI0@public.gmane.org>
2016-09-13 22:02   ` [PATCH v2 0/3] ARM: dts: Add operating-points-v2 tables for TI platforms Tony Lindgren
2016-09-13 22:02     ` Tony Lindgren
2016-09-14 16:45     ` Dave Gerlach [this message]
2016-09-14 16:45       ` Dave Gerlach
2016-09-14 16:56       ` Tony Lindgren
2016-09-14 16:56         ` Tony Lindgren

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=57D97E9A.90400@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 \
    /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.