From: Nicolas Cavallari <nicolas.cavallari@green-communications.fr>
To: linux-wireless@vger.kernel.org
Cc: Ryder Lee <ryder.lee@mediatek.com>,
Lorenzo Bianconi <lorenzo.bianconi83@gmail.com>,
Felix Fietkau <nbd@nbd.name>
Subject: Issues with mt7915 thermal throttling
Date: Tue, 18 Jan 2022 10:08:15 +0100 [thread overview]
Message-ID: <d7ce90d8-552a-2cab-6310-3a84584172a1@green-communications.fr> (raw)
I noticed some strange issues with mt7915's thermal throttling,
particularly the cooling_device.
First, it seems that the thermal subsystem expect that higher
cooling_device states provide more cooling, but mt7915e apparently does
the opposite and use it as a duty cycle, where state=1 does severe
throttling/max cooling (iperf throughput basically go down to near zero)
and state=100 is full power.
Also, state=0, from the comments, apparently disable thermal management,
except that in practice, it does not change the throttle state, since
throughput stays low when switching from state=1 to state=0, and stays
high when switching from 100 to 0.
As a result, as soon as the default thermal zone runs a little hot, the
performance of mt7915e is destroyed and does not recover much when the
temperature drops down.
I can come up with a patch to fix the first issue, but not the state=0
one, and i would like some pointers/confirmation.
next reply other threads:[~2022-01-18 9:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 9:08 Nicolas Cavallari [this message]
2022-02-07 17:37 ` [PATCH RFC 1/3] mt76: mt7915e: Fix degraded performance after temporary overheat Nicolas Cavallari
2022-02-07 17:37 ` [PATCH RFC 2/3] mt76: mt7915e: Add a hwmon attribute to get the actual throttle state Nicolas Cavallari
2022-02-07 17:37 ` [PATCH RFC 3/3] mt76: mt7915e: Enable thermal management by default Nicolas Cavallari
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=d7ce90d8-552a-2cab-6310-3a84584172a1@green-communications.fr \
--to=nicolas.cavallari@green-communications.fr \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo.bianconi83@gmail.com \
--cc=nbd@nbd.name \
--cc=ryder.lee@mediatek.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;
as well as URLs for NNTP newsgroup(s).