From: Keerthy <j-keerthy-l0cyMroinI0@public.gmane.org>
To: tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org
Cc: robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
mark.rutland-5wv7dgnIgG8@public.gmane.org,
linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
t-kristo-l0cyMroinI0@public.gmane.org,
j-keerthy-l0cyMroinI0@public.gmane.org
Subject: [PATCH RESEND 0/4] arm: dts: am57xx: Correct the thermal thresholds
Date: Thu, 28 Apr 2016 15:35:45 +0530 [thread overview]
Message-ID: <1461837949-11116-1-git-send-email-j-keerthy@ti.com> (raw)
Noticed that earlier post had a wrong list name hence resending the
series.
Currently all the am57xx versions are wrongly re-using the dra7 thermal
threholds. Introduing the correct thermal thresholds based on industrial
or commercial grade silicon present on the individual boards.
Tested on AM57XX-BEAGLE-X15 (Commercial) and AM572X-IDK(Industrial)
for the trip_point node sysfs temperatures.
These patches are on top of:
https://kernel.googlesource.com/pub/scm/linux/kernel/git/tmlind/linux-omap/+/omap-for-v4.7/dt
Keerthy (4):
ARM: dts: am57xx: Introduce commercial grade thermal thresholds
ARM: dts: am57xx: Introduce industrial grade thermal thresholds
ARM: dts: am57xx: Include the commercial grade thresholds
ARM: dts: am57xx-idk: Include Industrial grade thermal thresholds
arch/arm/boot/dts/am57xx-beagle-x15.dts | 1 +
arch/arm/boot/dts/am57xx-commercial-grade.dtsi | 23 +++++++++++++++++++++++
arch/arm/boot/dts/am57xx-idk-common.dtsi | 2 ++
arch/arm/boot/dts/am57xx-industrial-grade.dtsi | 23 +++++++++++++++++++++++
4 files changed, 49 insertions(+)
create mode 100644 arch/arm/boot/dts/am57xx-commercial-grade.dtsi
create mode 100644 arch/arm/boot/dts/am57xx-industrial-grade.dtsi
--
1.9.1
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2016-04-28 10:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 10:05 Keerthy [this message]
[not found] ` <1461837949-11116-1-git-send-email-j-keerthy-l0cyMroinI0@public.gmane.org>
2016-04-28 10:05 ` [PATCH RESEND 1/4] ARM: dts: am57xx: Introduce commercial grade thermal thresholds Keerthy
2016-04-28 10:05 ` [PATCH RESEND 2/4] ARM: dts: am57xx: Introduce industrial " Keerthy
2016-04-28 10:05 ` [PATCH RESEND 3/4] ARM: dts: am57xx-beagle-x15: Include the commercial grade thresholds Keerthy
2016-04-28 10:05 ` [PATCH RESEND 4/4] ARM: dts: am57xx-idk: Include Industrial grade thermal thresholds Keerthy
2016-05-10 4:24 ` [PATCH RESEND 0/4] arm: dts: am57xx: Correct the " Keerthy
[not found] ` <57316262.80003-l0cyMroinI0@public.gmane.org>
2016-05-12 20:35 ` Tony Lindgren
[not found] ` <20160512203505.GV5995-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2016-05-13 5:19 ` Keerthy
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=1461837949-11116-1-git-send-email-j-keerthy@ti.com \
--to=j-keerthy-l0cymroini0@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=t-kristo-l0cyMroinI0@public.gmane.org \
--cc=tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.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 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).