All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Cc: Willy Wolff <willy.mh.wolff@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Russell King <linux@armlinux.org.uk>,
	Kukjin Kim <kgene@kernel.org>,
	linux-samsung-soc@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ARM: dts: exynos: fix incomplete Odroid-XU3/4 thermal-zones definition
Date: Fri, 8 Sep 2017 18:40:15 +0200	[thread overview]
Message-ID: <20170908164015.rayfh2kluy45ktfi@kozik-lap> (raw)
In-Reply-To: <1848394.K3C0KxojUN@amdc3058>

On Thu, Sep 07, 2017 at 06:10:00PM +0200, Bartlomiej Zolnierkiewicz wrote:
> From: Willy Wolff <willy.mh.wolff@gmail.com>
> 
> Odroid XU3/4 boards have thermal sensors per 4 pairs of A7+A15
> cores but currently there is only one thermal-zone (including
> cooling maps) defined (for the first pair of cores - the first
> core of the A7 cluster and the first core of A15 cluster) so
> i.e. if the task is running on any of A15 cores but the first
> one, such core can reach high temperature without any proper
> cooling action.
> 
> Fix it by adding missing thermal-zones definitions.
> 
> Also while at it fix the number of steps in cpufreq cooling for
> cpu4 (11 steps for A15 corresponds to 700MHz, for 600MHz 12 steps
> should be used).
> 
> Signed-off-by: Willy Wolff <willy.mh.wolff@gmail.com>
> Cc: Rob Herring <robh+dt@kernel.org>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Cc: Russell King <linux@armlinux.org.uk>
> Cc: Kukjin Kim <kgene@kernel.org>
> [b.zolnierkie: rewrote patch subject & description + minor fixups]
> Signed-off-by: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>

Thanks for taking care of this. I'll take it after merge window.

Best regards,
Krzysztof

WARNING: multiple messages have this Message-ID (diff)
From: krzk@kernel.org (Krzysztof Kozlowski)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: dts: exynos: fix incomplete Odroid-XU3/4 thermal-zones definition
Date: Fri, 8 Sep 2017 18:40:15 +0200	[thread overview]
Message-ID: <20170908164015.rayfh2kluy45ktfi@kozik-lap> (raw)
In-Reply-To: <1848394.K3C0KxojUN@amdc3058>

On Thu, Sep 07, 2017 at 06:10:00PM +0200, Bartlomiej Zolnierkiewicz wrote:
> From: Willy Wolff <willy.mh.wolff@gmail.com>
> 
> Odroid XU3/4 boards have thermal sensors per 4 pairs of A7+A15
> cores but currently there is only one thermal-zone (including
> cooling maps) defined (for the first pair of cores - the first
> core of the A7 cluster and the first core of A15 cluster) so
> i.e. if the task is running on any of A15 cores but the first
> one, such core can reach high temperature without any proper
> cooling action.
> 
> Fix it by adding missing thermal-zones definitions.
> 
> Also while at it fix the number of steps in cpufreq cooling for
> cpu4 (11 steps for A15 corresponds to 700MHz, for 600MHz 12 steps
> should be used).
> 
> Signed-off-by: Willy Wolff <willy.mh.wolff@gmail.com>
> Cc: Rob Herring <robh+dt@kernel.org>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Cc: Russell King <linux@armlinux.org.uk>
> Cc: Kukjin Kim <kgene@kernel.org>
> [b.zolnierkie: rewrote patch subject & description + minor fixups]
> Signed-off-by: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>

Thanks for taking care of this. I'll take it after merge window.

Best regards,
Krzysztof

  reply	other threads:[~2017-09-08 16:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20170907161007epcas1p316fba6e329eaabedde8a98628ebb9751@epcas1p3.samsung.com>
2017-09-07 16:10 ` [PATCH v2] ARM: dts: exynos: fix incomplete Odroid-XU3/4 thermal-zones definition Bartlomiej Zolnierkiewicz
2017-09-07 16:10   ` Bartlomiej Zolnierkiewicz
2017-09-08 16:40   ` Krzysztof Kozlowski [this message]
2017-09-08 16:40     ` Krzysztof Kozlowski
2017-09-17  7:34     ` Krzysztof Kozlowski
2017-09-17  7:34       ` Krzysztof Kozlowski

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=20170908164015.rayfh2kluy45ktfi@kozik-lap \
    --to=krzk@kernel.org \
    --cc=b.zolnierkie@samsung.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kgene@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=willy.mh.wolff@gmail.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 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.