devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Keerthy <a0393675@ti.com>
To: Tony Lindgren <tony@atomide.com>, Keerthy <j-keerthy@ti.com>
Cc: edubezval@gmail.com, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	linux-omap@vger.kernel.org, linux@arm.linux.org.uk,
	galak@codeaurora.org, ijc+devicetree@hellion.org.uk,
	mark.rutland@arm.com
Subject: Re: [PATCH 0/3] arm: dts: DRA7: Add IVA and DSPEVE thermal domain data
Date: Tue, 9 Feb 2016 09:07:27 +0530	[thread overview]
Message-ID: <56B95EF7.9080107@ti.com> (raw)
In-Reply-To: <20160208195704.GW19432@atomide.com>



On Tuesday 09 February 2016 01:27 AM, Tony Lindgren wrote:
> * Keerthy <j-keerthy@ti.com> [160208 01:19]:
>> OMAP5 has 3 thermal zones cpu, core and multimedia.
>> On the other hand DRA7 has 5 thermal zones cpu, gpu, core, dspeve
>> and iva. Currently cpu, core and multimedia are being added via dt
>> and the other 2 are getting added via kernel. Add the missing thermal
>> domains in dt so as give the correct trip numbers, type and temperatures.
>>
>> Tested on DRA7-EVM.
>
> Are these critical fixes to have for v4.5-rc cycle or can they
> wait for v4.6 merge window?

Driver configures some default thresholds that are a bit higher but 
there are some thresholds already for dspeve and iva too. So guess these 
can wait if its already too late.

Regards,
Keerthy

>
> Regards,
>
> Tony
>
>> Keerthy (3):
>>    arm: dts: DRA7: Add DSPEVE thermal data
>>    arm: dts: DRA7: Add IVA thermal data
>>    arm: dts: DRA7: Add missing IVA and DSPEVE thermal domain data
>>
>>   arch/arm/boot/dts/dra7-dspeve-thermal.dtsi | 27 +++++++++++++++++++++++++++
>>   arch/arm/boot/dts/dra7-iva-thermal.dtsi    | 27 +++++++++++++++++++++++++++
>>   arch/arm/boot/dts/dra7.dtsi                |  2 ++
>>   3 files changed, 56 insertions(+)
>>   create mode 100644 arch/arm/boot/dts/dra7-dspeve-thermal.dtsi
>>   create mode 100644 arch/arm/boot/dts/dra7-iva-thermal.dtsi
>>
>> --
>> 1.9.1
>>

  reply	other threads:[~2016-02-09  3:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-08  9:16 [PATCH 0/3] arm: dts: DRA7: Add IVA and DSPEVE thermal domain data Keerthy
2016-02-08  9:16 ` [PATCH 1/3] arm: dts: DRA7: Add DSPEVE thermal data Keerthy
2016-02-08  9:16 ` [PATCH 2/3] arm: dts: DRA7: Add IVA " Keerthy
2016-02-08  9:16 ` [PATCH 3/3] arm: dts: DRA7: Add missing IVA and DSPEVE thermal domain data Keerthy
     [not found] ` <1454922990-7501-1-git-send-email-j-keerthy-l0cyMroinI0@public.gmane.org>
2016-02-08 19:57   ` [PATCH 0/3] arm: dts: DRA7: Add " Tony Lindgren
2016-02-09  3:37     ` Keerthy [this message]
2016-02-09 15:58       ` Tony Lindgren
2016-02-09 21:53       ` Eduardo Valentin
2016-02-10  3:37         ` Keerthy
2016-02-09 21:52 ` Eduardo Valentin
     [not found]   ` <20160209215210.GB27284-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2016-02-12 22:21     ` 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=56B95EF7.9080107@ti.com \
    --to=a0393675@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=edubezval@gmail.com \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=j-keerthy@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=tony@atomide.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).