From: Christian Hewitt <christianshewitt@gmail.com>
To: Jerome Brunet <jbrunet@baylibre.com>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
joy.cho@hardkernel.com, narmstrong@baylibre.com,
khilman@baylibre.com, linux-kernel@vger.kernel.org,
Tim Lewis <elatllat@gmail.com>,
robh+dt@kernel.org, tobetter@gmail.com,
linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4] arm64: dts: meson: S922X: extend cpu opp-points
Date: Mon, 27 Apr 2020 13:19:09 +0400 [thread overview]
Message-ID: <2A9D3FBA-917A-42C7-9757-4316D6B3D284@gmail.com> (raw)
In-Reply-To: <1ja72x2t7w.fsf@starbuckisacylon.baylibre.com>
> On 27 Apr 2020, at 1:06 pm, Jerome Brunet <jbrunet@baylibre.com> wrote:
>
> On Sun 26 Apr 2020 at 18:21, Tim Lewis <elatllat@gmail.com> wrote:
>
>> Add extra cpu pop points to allow mild overclock on S922X. The opp
>> points are found in Hardkernel N2 sources [1] and testing shows no
>> obvious issues on other S922X devices. Thermal throttling should
>> keep things in-check if needed.
>
> The Odroid-N2 has a massive heatsink mounted.
> Do we have any idea if this applies (is safe) on any other S922x
> device ?
I’ve tested it on several S922X box devices that I have, and also the
original S922X version of the VIM3 - all have similar sized passive
heatsinks about 20% the size of the N2 one. No obvious issues with
Kodi software decoding to increase CPU usage. NB: The original patch
submission was N2 specific and then reworked to apply to all S922X
devices at Neil’s suggestion (after my TB and earlier comments).
CH.
[snip]
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2020-04-27 9:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-26 16:21 Tim Lewis
2020-04-27 9:06 ` Jerome Brunet
2020-04-27 9:19 ` Christian Hewitt [this message]
2020-04-29 18:54 ` Kevin Hilman
2020-04-29 19:41 ` patchwork-bot+linux-amlogic
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=2A9D3FBA-917A-42C7-9757-4316D6B3D284@gmail.com \
--to=christianshewitt@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=elatllat@gmail.com \
--cc=jbrunet@baylibre.com \
--cc=joy.cho@hardkernel.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=narmstrong@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=tobetter@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 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®