Re: [PATCH v5 1/1] ltq-vdsl-app: extent dsl metrics with state_num and power_state_num

2021-04-12 Thread Andre Heider
On 13/04/2021 08:28, Florian Eckert wrote:   +/* These values are exported via ubus and backwards compability + * needs to be kept! + */ +enum { +    LSTATE_MAP_UNKNOWN = 0, +    LSTATE_MAP_EXCEPTION, +    LSTATE_MAP_IDLE, +    LSTATE_MAP_SILENT, +    LSTATE_MAP_HANDSHAKE, +    LSTATE_MAP_FULL_IN

Re: [PATCH v5 1/1] ltq-vdsl-app: extent dsl metrics with state_num and power_state_num

2021-04-12 Thread Florian Eckert
+/* These values are exported via ubus and backwards compability + * needs to be kept! + */ +enum { + LSTATE_MAP_UNKNOWN = 0, + LSTATE_MAP_EXCEPTION, + LSTATE_MAP_IDLE, + LSTATE_MAP_SILENT, + LSTATE_MAP_HANDSHAKE, + LSTATE_MAP_FULL_INIT, + LSTATE_MAP_SHO

Re: [PATCH v5 1/1] ltq-vdsl-app: extent dsl metrics with state_num and power_state_num

2021-04-12 Thread Andre Heider
On 12/04/2021 12:37, Florian Eckert wrote: With the old ubus dsl API, the numbers for the individual line_states and power_states were also returned. These were not ported to the new DSL C-API. This commit adds the missing information. For this the internal values are mapped to numbers. * addit

[PATCH v5 1/1] ltq-vdsl-app: extent dsl metrics with state_num and power_state_num

2021-04-12 Thread Florian Eckert
With the old ubus dsl API, the numbers for the individual line_states and power_states were also returned. These were not ported to the new DSL C-API. This commit adds the missing information. For this the internal values are mapped to numbers. * additional JSON output for state_num: "state_num":