From: Caesar Wang <caesar.upstream@gmail.com>
To: Eduardo Valentin <edubezval@gmail.com>, Heiko Stuebner <heiko@sntech.de>
Cc: Caesar Wang <wxt@rock-chips.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
dianders@chromium.org, devicetree@vger.kernel.org,
linux-pm@vger.kernel.org, Kumar Gala <galak@codeaurora.org>,
linux-kernel@vger.kernel.org,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
linux-rockchip@lists.infradead.org,
Rob Herring <robh+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org,
Pawel Moll <pawel.moll@arm.com>, Zhang Rui <rui.zhang@intel.com>,
Mark Rutland <mark.rutland@arm.com>,
Russell King <linux@arm.linux.org.uk>
Subject: Re: [PATCH 0/4] Add the OTP gpio pinctrl to fix the TSHUT issue
Date: Tue, 20 Oct 2015 17:15:11 +0800 [thread overview]
Message-ID: <5626061F.6010402@gmail.com> (raw)
In-Reply-To: <1445332264-6054-1-git-send-email-wxt@rock-chips.com>
The subject is deleted by my finger.
在 2015年10月20日 17:11, Caesar Wang 写道:
> We need the OTP pin is gpio state before resetting the TSADC controller,
> since the tshut polarity will generate a high signal.
>
> Says:
> The TSHUT temperature is setting more than 80 degree, the default
> tshut polarity is HIGH.
>
> If T > 80C, the OTP output the High Signal.
> If T < 80C, the OTP output the Low Signal.
>
> On the moment, the TSADC controller is reset, the tshut polarity will be
> Low in a short period of time.
>
> So:
> If T < 80C, the OTP output the High Signal.
> If T > 80C, the OTP output the Low Signal.
>
> In some cases, the OTP pin is connected to the PMIC, maybe the PMIC can
> accept the reset response time to avoid this issue.
>
> In other words, the system will be always reboot if we make the OTP pin
> is connected the others IC to control the power.
>
> Tested on box board.
>
>
>
> Caesar Wang (4):
> dt-bindings: Sync the dts to this document
> thermal: rockchip: ensure the otp state before resetting the
> controller
> thermal: rockchip: change the TSHUT default state
> ARM: dts: rockchip: Add the OTP gpio pinctrl
>
> .../bindings/thermal/rockchip-thermal.txt | 5 ++--
> arch/arm/boot/dts/rk3288.dtsi | 9 ++++--
> drivers/thermal/rockchip_thermal.c | 34 +++++++++++++++++++++-
> 3 files changed, 43 insertions(+), 5 deletions(-)
>
--
Thanks,
Caesar
prev parent reply other threads:[~2015-10-20 9:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 9:11 [PATCH 0/4] Caesar Wang
2015-10-20 9:11 ` [PATCH 1/4] dt-bindings: Sync the dts to this document Caesar Wang
[not found] ` <1445332264-6054-1-git-send-email-wxt-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2015-10-20 9:11 ` [PATCH 4/4] ARM: dts: rockchip: Add the OTP gpio pinctrl Caesar Wang
2015-10-20 9:15 ` Caesar Wang [this message]
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=5626061F.6010402@gmail.com \
--to=caesar.upstream@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=dmitry.torokhov@gmail.com \
--cc=edubezval@gmail.com \
--cc=galak@codeaurora.org \
--cc=heiko@sntech.de \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=rui.zhang@intel.com \
--cc=wxt@rock-chips.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).