view src/cs/riviera/rvm/rvm_ext_priorities.h @ 261:841a848ba762

SPI SWE: clear any pending boot-time interrupts in spi_init() Charger plug/unplug hw logic in the Iota ABB has no built-in debouncing, thus electrical contact bounce on the charging power connection interface produces a lot of charger plug/unplug interrupts. When we boot in charging mode (charging power present at boot time and is presumably the cause of Switch-ON), some bounce may occur between the initial Iota Switch-ON action and Calypso firmware booting. By clearing any accumulated ITSTATREG interrupts on boot, we prevent these pre-boot interrupts from generating charger plug/unplug events to FCHG, which would upset smooth from-boot charging.
author Mychaela Falconia <falcon@freecalypso.org>
date Fri, 14 May 2021 02:49:05 +0000
parents 0faa72eaedcb
children 2d7d95e7f9c2
line wrap: on
line source

/*******************************************************************************
 *                                                                             *
 *  Name        rvm_ext_priorities.h                                           *
 *                                                                             *
 *  Function    this file priorities defintitions for basic SWEs	       *
 *		It includes a file                                             *
 *                                                                             *
 *  Version	0.1							       *
 *								               *
 *  Date       	Modification					               *
 *  ------------------------------------			               *
 *  10/11/2000	Create						               *
 *								               *
 *  Author	Cristian Livadiotti (c-livadiotti@ti.com)	               *
 *								               *
 * (C) Copyright 2000 by Texas Instruments Incorporated, All Rights Reserved   *
 *                                                                             *
 * --------------------------------------------------------------------------- *
 *                                                                             *
 *   History:                                                                  *
 *                                                                             *
 *   10/18/2001 - Updated for R2D by Christophe Favergeon                      *
 *                                                                             *
 ******************************************************************************/

#ifndef __RVM_EXT_PRIORITIES_H_
#define __RVM_EXT_PRIORITIES_H_

/* PRIORITIES SETTING:                        */
/* All user priority should be set under 250: */
/* Higher values are reserved                 */

/*
** External Priority definitions
** Note that RVM_EXPL_TASK_PRIORITY is used for testing purpose (refer to RTEST).
** Hence, users have to make sure that such a priority is lower than the software
** entity under test, not to starve the system.
*/
#define		RVM_EXPL_TASK_PRIORITY	(242)

#define		RVM_RGUI_TASK_PRIORITY	(240)
#define		RVM_R2D_TASK_PRIORITY	(239)

#define		RVM_DEV1_TASK_PRIORITY	(245)
#define		RVM_DEV2_TASK_PRIORITY	(245)
#define		RVM_DEV3_TASK_PRIORITY	(245)

#define		RVM_UVM_TASK_PRIORITY	(245)

#define		RVM_BTU_TASK_PRIORITY	(248) /* was 240 */
#define		RVM_BTUI_TASK_PRIORITY	(240)
#define		RVM_BTA_TASK_PRIORITY	(248) /* rl: was 200 */
#define		RVM_BTH_TASK_PRIORITY	(200)

#define		RVM_FCBM_TASK_PRIORITY	(238)

#endif /* __RVM_EXT_PRIORITIES_H_ */