On Thu, Apr 16, 2015 at 1:18 PM, Keerthy <j-keerthy@xxxxxx> wrote:
> DESCRIPTION
>
> Spurious Thermal Alert: Talert can happen randomly while the device remains under the temperature limit
> defined for this event to trig. This spurious event is caused by a incorrect re-synchronization between
> clock domains. The comparison between configured threshold and current temperature value can happen
> while the value is transitioning (metastable), thus causing inappropriate event generation.
> No spurious event occurs as long as the threshold value stays unchanged. Spurious event can be
> generated while a thermal alert threshold is modified in
> CONTROL_BANDGAP_THRESHOLD_MPU/GPU/CORE/DSPEVE/IVA_n.
> WORKAROUND
>
> Spurious event generation can be avoided by performing following sequence when the threshold is
> modified:
> 1. Mask the hot/cold events at the thermal IP level.
> 2. Modify Threshold.
> 3. Unmask the hot/cold events at the thermal IP level.
>
> Signed-off-by: Keerthy <j-keerthy@xxxxxx>
> ---
> .../thermal/ti-soc-thermal/dra752-thermal-data.c | 3 +-
> drivers/thermal/ti-soc-thermal/ti-bandgap.c | 41 +++++++++++++++++++++-
> drivers/thermal/ti-soc-thermal/ti-bandgap.h | 4 ++-
> 3 files changed, 45 insertions(+), 3 deletions(-)
>
> ...
> diff --git a/drivers/thermal/ti-soc-thermal/ti-bandgap.h b/drivers/thermal/ti-soc-thermal/ti-bandgap.h
> index b2da3fc..0c52f7a 100644
> --- a/drivers/thermal/ti-soc-thermal/ti-bandgap.h
> +++ b/drivers/thermal/ti-soc-thermal/ti-bandgap.h
> @@ -320,7 +320,8 @@ struct ti_temp_sensor {
> *
> * TI_BANDGAP_FEATURE_ERRATA_814 - used to workaorund when the bandgap device
> * has Errata 814
> - *
> + * TI_BANDGAP_FEATURE_ERRATA_813 - used to workaorund when the bandgap device
> + * has Errata 813
workaorund?
--
Gražvydas
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
