From: Keerthy <j-keerthy@ti.com>
To: <tony@atomide.com>, <edubezval@gmail.com>
Cc: <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>, Keerthy <j-keerthy@ti.com>
Subject: [PATCH 3/3] arm: dts: DRA7: Add missing IVA and DSPEVE thermal domain data
Date: Mon, 8 Feb 2016 14:46:30 +0530 [thread overview]
Message-ID: <1454922990-7501-4-git-send-email-j-keerthy@ti.com> (raw)
In-Reply-To: <1454922990-7501-1-git-send-email-j-keerthy@ti.com>
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 device tree
and the other 2 are getting added via kernel. Add the missing thermal
domains in device tree so we can create the zones with the appropriate
trip numbers, type and temperatures.
Signed-off-by: Keerthy <j-keerthy@ti.com>
---
arch/arm/boot/dts/dra7.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/boot/dts/dra7.dtsi b/arch/arm/boot/dts/dra7.dtsi
index c4d9175..9f65d0d 100644
--- a/arch/arm/boot/dts/dra7.dtsi
+++ b/arch/arm/boot/dts/dra7.dtsi
@@ -1603,6 +1603,8 @@
#include "omap4-cpu-thermal.dtsi"
#include "omap5-gpu-thermal.dtsi"
#include "omap5-core-thermal.dtsi"
+ #include "dra7-dspeve-thermal.dtsi"
+ #include "dra7-iva-thermal.dtsi"
};
};
--
1.9.1
next prev parent reply other threads:[~2016-02-08 9:18 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 " 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 ` Keerthy [this message]
2016-02-08 19:57 ` [PATCH 0/3] arm: dts: DRA7: Add IVA and DSPEVE thermal domain data Tony Lindgren
2016-02-09 3:37 ` Keerthy
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
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=1454922990-7501-4-git-send-email-j-keerthy@ti.com \
--to=j-keerthy@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=edubezval@gmail.com \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--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
all inboxes | Powered by JetHome®