[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160323224226.GD18567@codeaurora.org>
Date: Wed, 23 Mar 2016 15:42:26 -0700
From: Stephen Boyd <sboyd@...eaurora.org>
To: Matthew McClintock <mmcclint@...eaurora.org>
Cc: andy.gross@...aro.org, linux-arm-msm@...r.kernel.org,
qca-upstream.external@....qualcomm.com,
Wim Van Sebroeck <wim@...ana.be>,
Guenter Roeck <linux@...ck-us.net>,
"open list:WATCHDOG DEVICE DRIVERS" <linux-watchdog@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 08/17] watchdog: qcom: configure BARK time in addition to
BITE time
On 03/23, Matthew McClintock wrote:
> For certain parts and some versions of TZ, TZ will reset the chip
> when a BARK is triggered even though it was not configured here. So
> by default let's configure this BARK time as well.
>
Why isn't TZ configuring the bark time to what it wants? I'm lost
why we have to do this for them.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
Powered by blists - more mailing lists