From: thypon <thypon@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: pinebookpro-kernel: overclock patch
Date: Wed, 20 Jan 2021 00:07:25 +0100 [thread overview]
Message-ID: <20210119230725.1xxik2jJeNW9UGvUyLWHKTnCFh7KBSAXKptG8ZR_W7w@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28007@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1088 bytes --]
New comment by thypon on void-packages repository
https://github.com/void-linux/void-packages/pull/28007#issuecomment-763200561
Comment:
I had a quick chat with tsys, the guy that mainlined that DTC definition and maintained the manjaro linux pinebook kernel. He told me that he was using the overclock on manjaro because he was sure the first batch was supporting higher clock. He is not sure any other batch supported that higher speed, so he mainlined a more conservative profile.
He added that it should not be possible to be sure of the correct profile if we don't ask directly to rockchip.
I'm now running the patched version since some days with heavy duty tasks + browsing, the W usage is very mild (6-8), even on battery. I don't believe it will be a dangerous mod.
While there is usually a correct profile, when the vendor step in, I don't believe my one is more or less dangerous at the moment, and, due to the fact that we run a OP1 profile until now I don't see how that will be an issue while we still use a distinct kernel for pinebook wrt generic arm64 builds.
next prev parent reply other threads:[~2021-01-19 23:07 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 11:55 [PR PATCH] " thypon
2021-01-18 11:57 ` [PR PATCH] [Updated] " thypon
2021-01-18 12:16 ` Depau
2021-01-18 12:38 ` Johnnynator
2021-01-18 13:06 ` thypon
2021-01-18 17:40 ` thypon
2021-01-18 17:41 ` thypon
2021-01-18 18:02 ` CameronNemo
2021-01-18 18:10 ` thypon
2021-01-18 18:10 ` thypon
2021-01-18 18:11 ` thypon
2021-01-18 18:12 ` thypon
2021-01-18 18:20 ` CameronNemo
2021-01-18 18:45 ` Depau
2021-01-18 19:39 ` thypon
2021-01-18 19:41 ` thypon
2021-01-18 19:44 ` thypon
2021-01-18 22:12 ` thypon
2021-01-19 23:07 ` thypon [this message]
2021-01-21 14:34 ` thypon
2021-01-21 14:35 ` thypon
2021-01-21 14:37 ` thypon
2021-01-21 14:38 ` thypon
2021-01-21 14:39 ` thypon
2021-01-21 14:39 ` thypon
2021-01-21 14:40 ` thypon
2021-01-21 14:41 ` thypon
2021-01-21 14:42 ` thypon
2021-01-21 14:46 ` thypon
2021-01-21 14:46 ` thypon
2021-01-21 14:50 ` thypon
2021-01-21 14:51 ` thypon
2021-01-21 14:52 ` thypon
2021-01-21 14:53 ` thypon
2021-01-21 14:56 ` thypon
2022-05-02 2:16 ` github-actions
2022-05-17 2:13 ` [PR PATCH] [Closed]: " github-actions
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=20210119230725.1xxik2jJeNW9UGvUyLWHKTnCFh7KBSAXKptG8ZR_W7w@z \
--to=thypon@users.noreply.github.com \
--cc=ml@inbox.vuxu.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).