Implement get_state for each device module

[flavius-t]

Each device module requires a get_state() -> dict method which will query the current state of the device by performing register reads, and return the state as a dictionary.

Current device modules:

• LED
• TC
• DAC
• ADC

[sjpark608]

this is link to the datasheet
basics of i2c
python-periphery docs

[sjpark608]

@flavius-t
Things to be represented in the get_state() functions in each module
DAC: {channel : {code, voltage}}
ADC:{ADC1: {conv_mode, input, datarate, filter}}, it looks like ADC module already have get_state(), is this correct?
LED:{LEDx : {state}}, seems like LED module also already has get_state()
TC: {?}

[flavius-t]

Things to be represented in the get_state() functions in each module
DAC: {channel : {code, voltage}}
ADC:{ADC1: {conv_mode, input, datarate, filter}}, it looks like ADC module already have get_state(), is this correct?
LED:{LEDx : {state}}, seems like LED module also already has get_state()
TC: {?}

@sjpark608

The states/format we plan to track for each module are in:
https://github.com/osensa/edgepi-device-manager/issues/2
https://github.com/osensa/edgepi-device-manager/issues/3
https://github.com/osensa/edgepi-device-manager/issues/4
https://github.com/osensa/edgepi-device-manager/issues/5

ADC:{ADC1: {conv_mode, input, datarate, filter}}, it looks like ADC module already have get_state(), is this correct?
LED:{LEDx : {state}}, seems like LED module also already has get_state()

The get_state and ADCState in edgepi_adc were added before we began the device shadow issue, they were meant for internal use inside the EdgePiADC class. So we still need to add the actual get_state to EdgePiADC but I think we could make use of this internal get_state to make the implementation easier (we should rename the internal get_state probably).

The LED get_state is intended for the device shadow though.