From: sbabic@denx.de
To: Tim Harvey <tharvey@gateworks.com>,u-boot@lists.denx.de
Subject: [PATCH 5/5] board: gateworks: venice: remove forced enable of GSC thermal protection
Date: Sat, 10 Jul 2021 21:34:34 +0200 (CEST) [thread overview]
Message-ID: <20210710193434.6932F832D4@phobos.denx.de> (raw)
In-Reply-To: <20210701000742.6522-5-tharvey@gateworks.com>
> The Gateworks System Controller thermal protection feature will disable
> the board primary power supply if the on-board temperature sensor
> reaches 86C. In many cases this could occur before the temperature
> critical components such as CPU, DRAM, eMMC, and power supplies have
> reached their max temperature.
> Remove the forced re-enable of thermal protection so that users can
> knowingly disable it.
> Signed-off-by: Tim Harvey <tharvey@gateworks.com>
Applied to u-boot-imx, master, thanks !
Best regards,
Stefano Babic
--
=====================================================================
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic@denx.de
=====================================================================
next prev parent reply other threads:[~2021-07-10 19:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-01 0:07 [PATCH 1/5] board: gateworks: venice: gsc: fix typo Tim Harvey
2021-07-01 0:07 ` [PATCH 2/5] board: gateworks: venice: gsc: fix voltage offset Tim Harvey
2021-07-10 19:35 ` sbabic
2021-07-01 0:07 ` [PATCH 3/5] board: gateworks: venice: display DTB used Tim Harvey
2021-07-10 19:36 ` sbabic
2021-07-01 0:07 ` [PATCH 4/5] board: gateworks: venice: add ftd_file env vars on boot Tim Harvey
2021-07-10 19:37 ` sbabic
2021-07-01 0:07 ` [PATCH 5/5] board: gateworks: venice: remove forced enable of GSC thermal protection Tim Harvey
2021-07-10 19:34 ` sbabic [this message]
2021-07-10 19:37 ` [PATCH 1/5] board: gateworks: venice: gsc: fix typo sbabic
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=20210710193434.6932F832D4@phobos.denx.de \
--to=sbabic@denx.de \
--cc=tharvey@gateworks.com \
--cc=u-boot@lists.denx.de \
/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