From: "Guilherme G. Piccoli" <email@example.com>
Cc: firstname.lastname@example.org, email@example.com,
Subject: Re: [PATCH] arm64: dts: qcom: msm8996: Add CPU cooling suppor,t
Date: Mon, 27 Sep 2021 18:52:35 -0300 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
On 27/09/2021 18:45, Guilherme G. Piccoli wrote:
> Hi Yassine, thanks for the patch! I was doing some experiments with a
> dragonboard 820-based board, and without your patch, a CPU benchmark can
> quickly cause overheating - throttling mechanism doesn't start and we
> get a FW reset to a bad state (likely a HW protection mechanism).
> I noticed that a similar patch including cooling maps is present in
> Linaro's qcom tree , and it was submitted upstream , but there was
> a re-submission  by Konrad that was merged and dropped the thermals
> part. Based on some threads I read, it seems a FW lockup was detected
> with the complete patch?
> I'm not sure, so I'm looping Konrad / Loic / Bjorn here, to understand
> better what made this portion of the patch to be dropped.
> Anyway, I think worth to mention this in your commit message Yassine,
> including perhaps a fixes tag like:
> Fixes: 90173a954a22 ("arm64: dts: qcom: msm8996: Add CPU opps").
> Also, I'm not sure why there was no response here or why it wasn't
> merged, but if it helps, please have my:
> Tested-by: Guilherme G. Piccoli <email@example.com>
Unfortunately, (likely) due to a typo in the Subject field, this wasn't
threaded correctly. So, the original message I was responding is:
I'm sorry about the confusion with the mail thread!
prev parent reply other threads:[~2021-09-27 21:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-27 21:45 [PATCH] arm64: dts: qcom: msm8996: Add CPU cooling suppor,t Guilherme G. Piccoli
2021-09-27 21:52 ` Guilherme G. Piccoli [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).