armio.c: make GPIOs 8 & 13 outputs driving 1 on all "classic" targets Calypso GPIOs 8 & 13 are pinmuxed with MCUEN1 & MCUEN2, respectively, and on powerup these pins are MCUEN, i.e., outputs driving 1. TI's code for C-Sample and earlier turns them into GPIOs configured as outputs also driving 1 - so far, so good - but TI's code for BOARD 41 (which covers D-Sample, Leonardo and all real world Calypso devices derived from the latter) switches them from MCUEN to GPIOs, but then leaves them as inputs. Given that the hardware powerup state of these two pins is outputs driving 1, every Calypso board design MUST be compatible with such driving; typically these GPIO signals will be either unused and unconnected or connected as outputs driving some peripheral. Turning these pins into GPIO inputs will result in floating inputs on every reasonably-wired board, thus I am convinced that this configuration is nothing but a bug on the part of whoever wrote this code at TI. This floating input bug had already been fixed earlier for GTA modem and FCDEV3B targets; the present change makes the fix unconditional for all "classic" targets. The newly affected targets are D-Sample, Leonardo, Tango and GTM900.

/*
 * In this header file we are going to define the messages
 * that can be sent to the FCHG task.
 */

#ifndef __FCHG_MESSAGES_H
#define __FCHG_MESSAGES_H

#include "rv/rv_general.h"

// Request mail
struct pwr_req_s {
     T_RV_HDR header;
};

// Indication mail with ADC measurements
struct pwr_adc_ind_s {
     T_RV_HDR header;
     unsigned short data[9+1]; // ADC measurements + status of VRPCSTS register
};

// Message IDs for all PWR module messages
enum pwr_msg_id {
	/* message types new to FCHG */
	USER_START_CHARGE_REQ	= 1,
	USER_STOP_CHARGE_REQ,
	/* messages sent to us by SPI task, same as TI's LCC */
	PWR_CHARGER_PLUGGED_IND  = 40,
	PWR_CHARGER_UNPLUGGED_IND,
	PWR_ADC_IND = 90
};

#endif