From: Thierry Reding <thierry.reding@gmail.com>
To: Anthony Eden <aeden@csail.mit.edu>
Cc: Jon Hunter <jonathanh@nvidia.com>,
linux-tegra@vger.kernel.org, arm@kernel.org,
Olof Johansson <olof@lixom.net>,
Mikko Perttunen <mperttunen@nvidia.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL 5/5] arm64: tegra: Device tree changes for v4.19-rc1
Date: Thu, 9 Aug 2018 12:21:04 +0200 [thread overview]
Message-ID: <20180809102104.GB21639@ulmo> (raw)
In-Reply-To: <CAHMsQjU=nmpTnPK6Ryhui67YVANHExd=yRB4hp+upd7O-Tjn+Q@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 928 bytes --]
On Fri, Aug 03, 2018 at 07:26:04AM -0400, Anthony Eden wrote:
> Mesa support aside- if I start a computationally intensive job on the
> Jetson TX2 like building the Linux kernel on all cores, it will lock
> up. My only work around has been to disable the Denver CPU's. I don't
> think the tegra186 has upstream support to control the fan on the
> Jetson TX2, could this be a thermal problem?
Yes, I suppose this could be a thermal problem. Or it could be something
else entirely. We do support CPU frequency scaling on Tegra X2, so what
you could do is keep the Denver CPUs enabled, but set the powersave CPU
frequency governor. That way it should use all the CPUs but at a lower
clock rate, which should also be able to avoid any thermal issues. This
could help determine whether or not the problem is thermal or something
else.
Also adding Mikko on Cc who wrote the Tegra186 driver, maybe he's aware
of any issues.
Thierry
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2018-08-09 10:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-12 15:41 NVIDIA Tegra changes for v4.19-rc1 Thierry Reding
2018-07-12 15:41 ` [GIT PULL 1/5] dt-bindings: tegra: Changes " Thierry Reding
2018-07-14 21:20 ` Olof Johansson
2018-07-12 15:41 ` [GIT PULL 2/5] memory: " Thierry Reding
2018-07-14 21:40 ` Olof Johansson
2018-07-12 15:41 ` [GIT PULL 3/5] firmware: " Thierry Reding
2018-07-14 21:45 ` Olof Johansson
2018-07-12 15:41 ` [GIT PULL 4/5] ARM: tegra: Device tree changes " Thierry Reding
2018-07-14 21:21 ` Olof Johansson
2018-07-12 15:41 ` [GIT PULL 5/5] arm64: " Thierry Reding
2018-07-14 21:22 ` Olof Johansson
2018-08-03 10:43 ` Thierry Reding
2018-08-03 11:26 ` Anthony Eden
2018-08-09 10:21 ` Thierry Reding [this message]
2018-08-09 10:34 ` Mikko Perttunen
2018-08-09 14:07 ` Thierry Reding
2018-11-03 20:08 ` Anthony Eden
2018-07-12 16:01 ` NVIDIA Tegra " Olof Johansson
2018-07-13 14:09 ` Jon Hunter
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=20180809102104.GB21639@ulmo \
--to=thierry.reding@gmail.com \
--cc=aeden@csail.mit.edu \
--cc=arm@kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mperttunen@nvidia.com \
--cc=olof@lixom.net \
/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).