From: Keerthy <a0393675-l0cyMroinI0@public.gmane.org>
To: Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
Cc: Keerthy <j-keerthy-l0cyMroinI0@public.gmane.org>,
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
Subject: Re: [PATCH RESEND 0/4] arm: dts: am57xx: Correct the thermal thresholds
Date: Fri, 13 May 2016 10:49:20 +0530 [thread overview]
Message-ID: <573563D8.7020503@ti.com> (raw)
In-Reply-To: <20160512203505.GV5995-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
On Friday 13 May 2016 02:05 AM, Tony Lindgren wrote:
> Hi,
>
> * Keerthy <a0393675-l0cyMroinI0@public.gmane.org> [160509 21:25]:
>> Tony,
>>
>> On Thursday 28 April 2016 03:35 PM, Keerthy wrote:
>>> 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.
>>>
>>
>> A Gentle ping on this series.
>
> I already have these in Linux next for v4.7 merge window:
>
> 5b6042237dc8 ("ARM: dts: am57xx-idk: Include Industrial grade thermal thresholds")
> 266e62f97539 ("ARM: dts: am57xx-beagle-x15: Include the commercial grade thresholds")
> cf9b7d5e9cfd ("ARM: dts: am57xx: Introduce industrial grade thermal thresholds")
> 286db0a516e0 ("ARM: dts: am57xx: Introduce commercial grade thermal thresholds")
>
> Care to check if those are OK? If fixes are needed, please post an
> incremental patch against current Linux next.
Thanks Tony. Those 4 commits are fine.
Regards,
Keerthy
>
> Regards,
>
> Tony
>
--
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
WARNING: multiple messages have this Message-ID (diff)
From: a0393675@ti.com (Keerthy)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RESEND 0/4] arm: dts: am57xx: Correct the thermal thresholds
Date: Fri, 13 May 2016 10:49:20 +0530 [thread overview]
Message-ID: <573563D8.7020503@ti.com> (raw)
In-Reply-To: <20160512203505.GV5995@atomide.com>
On Friday 13 May 2016 02:05 AM, Tony Lindgren wrote:
> Hi,
>
> * Keerthy <a0393675@ti.com> [160509 21:25]:
>> Tony,
>>
>> On Thursday 28 April 2016 03:35 PM, Keerthy wrote:
>>> 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.
>>>
>>
>> A Gentle ping on this series.
>
> I already have these in Linux next for v4.7 merge window:
>
> 5b6042237dc8 ("ARM: dts: am57xx-idk: Include Industrial grade thermal thresholds")
> 266e62f97539 ("ARM: dts: am57xx-beagle-x15: Include the commercial grade thresholds")
> cf9b7d5e9cfd ("ARM: dts: am57xx: Introduce industrial grade thermal thresholds")
> 286db0a516e0 ("ARM: dts: am57xx: Introduce commercial grade thermal thresholds")
>
> Care to check if those are OK? If fixes are needed, please post an
> incremental patch against current Linux next.
Thanks Tony. Those 4 commits are fine.
Regards,
Keerthy
>
> Regards,
>
> Tony
>
next prev parent reply other threads:[~2016-05-13 5:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 10:05 [PATCH RESEND 0/4] arm: dts: am57xx: Correct the thermal thresholds Keerthy
2016-04-28 10:05 ` Keerthy
[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 " Keerthy
2016-04-28 10:05 ` Keerthy
2016-04-28 10:05 ` [PATCH RESEND 2/4] ARM: dts: am57xx: Introduce industrial " Keerthy
2016-04-28 10:05 ` 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 ` Keerthy
2016-04-28 10:05 ` [PATCH RESEND 4/4] ARM: dts: am57xx-idk: Include Industrial grade thermal thresholds Keerthy
2016-04-28 10:05 ` Keerthy
2016-05-10 4:24 ` [PATCH RESEND 0/4] arm: dts: am57xx: Correct the " Keerthy
2016-05-10 4:24 ` Keerthy
[not found] ` <57316262.80003-l0cyMroinI0@public.gmane.org>
2016-05-12 20:35 ` Tony Lindgren
2016-05-12 20:35 ` Tony Lindgren
[not found] ` <20160512203505.GV5995-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2016-05-13 5:19 ` Keerthy [this message]
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=573563D8.7020503@ti.com \
--to=a0393675-l0cymroini0@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=j-keerthy-l0cyMroinI0@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 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.