view src/cs/drivers/drv_app/fchg/fchg_api.h @ 624:012028896cfb

FFS dev.c, Leonardo target: Fujitsu MB84VF5F5F4J2 #if 0'ed out The FFS code we got from TI/Openmoko had a stanza for "Fujitsu MB84VF5F5F4J2 stacked device", using a fake device ID code that would need to be patched manually into cfgffs.c (suppressing and overriding autodetection) and using an FFS base address in the nCS2 bank, indicating that this FFS config was probably meant for the MCP version of Leonardo which allows for 16 MiB flash with a second bank on nCS2. We previously had this FFS config stanza conditionalized under CONFIG_TARGET_LEONARDO because the base address contained therein is invalid for other targets, but now that we actually have a Leonardo build target in FC Magnetite, I realize that the better approach is to #if 0 out this stanza altogether: it is already non-functional because it uses a fake device ID code, thus it is does not add support for more Leonardo board variants, instead it is just noise.
author Mychaela Falconia <falcon@freecalypso.org>
date Sun, 22 Dec 2019 21:24:29 +0000
parents c4077830aeeb
children
line wrap: on
line source

/*
 * This header file defines the external API of the FCHG SWE,
 * callable from other tasks such as UI or AT commands.
 */

#ifndef __FCHG_API_H
#define __FCHG_API_H

#include "rv/rv_general.h"
#include "fchg/fchg_common.h"

enum fchg_user_charge_ctrl {
	FCHG_CHARGE_STOP	= 0,
	FCHG_CHARGE_START	= 1
};

struct fchg_user_state {
	enum fchg_state	chg_state;
	UINT16		batt_mv;
	T_PWR_PERCENT	batt_percent;
};

T_RV_RET fchg_user_charge_control(enum fchg_user_charge_ctrl);
T_RV_RET fchg_get_current_state(struct fchg_user_state *);

#endif	/* include guard */