From: thypon <thypon@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: pinebookpro-kernel: overclock patch
Date: Mon, 18 Jan 2021 20:44:40 +0100 [thread overview]
Message-ID: <20210118194440.7gDincMQdphbSJjtCLXxlwIGetFmHvDUf5NauLR6to0@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: 1034 bytes --]
New comment by thypon on void-packages repository
https://github.com/void-linux/void-packages/pull/28007#issuecomment-762438319
Comment:
> @thypon how does it affect power consumption. I know that excessive power consumption (even with the barrel charger plugged in) has been an issue. Especially when using an SSD.
I tested with power cord on. That really depends on the usage. Do you want me to do a battery time test from 100 to 0? Or watt usage? Watt usage is below 12w for me.
The problem is I have a very power efficient nvme, because I bought the less power hungry available, but that may not apply to everybody.
The barrel charger is known to not be able to provide enough energy even with no overclock, but this is a problem due to power hungry pcie devices imho.
After applying the patch it is anyway possible to disable the 2.01ghz extra step with /sys so I don't see a huge problem, if it does not crash in most cases. Disabling it requires only an 'echo', enabling dtb or dto compilation and loading through uboot.
next prev parent reply other threads:[~2021-01-18 19:44 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 [this message]
2021-01-18 22:12 ` thypon
2021-01-19 23:07 ` thypon
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=20210118194440.7gDincMQdphbSJjtCLXxlwIGetFmHvDUf5NauLR6to0@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).