-
Marco Filho authored
This commit was done with an inescrupulous "git add ." after several radical modifications. Anyway, the API was radically modified and basically the old way the code worked does not make any sense anymore. The desired architecture is the following: the API is going to be used as a class component. Each parameter will be created according to the desired number of enabled hybrids. Each parameter should use one simple API function. No information about the VMM or hybrids itself is stored in the VMMTbl class unless extremely needed. This commit leaves a few old parameters that should be removed in the future such as ADC_VALUE_VMM1, READ_ADC_VMMS, etc. This is only to serve as a reminder to add those later.
Marco Filho authoredThis commit was done with an inescrupulous "git add ." after several radical modifications. Anyway, the API was radically modified and basically the old way the code worked does not make any sense anymore. The desired architecture is the following: the API is going to be used as a class component. Each parameter will be created according to the desired number of enabled hybrids. Each parameter should use one simple API function. No information about the VMM or hybrids itself is stored in the VMMTbl class unless extremely needed. This commit leaves a few old parameters that should be removed in the future such as ADC_VALUE_VMM1, READ_ADC_VMMS, etc. This is only to serve as a reminder to add those later.
Code owners
Assign users and groups as approvers for specific file changes. Learn more.