If you like BoxMatrix then please contribute Supportdata, Supportdata2, Firmware and/or Hardware (get in touch).
My metamonk@yahoo.com is not reachable by me since years. Please use hippie2000@webnmail.de instead.

0
U

Property:powermanagment status (event)

From BoxMatrix


BoxMatrix >> System >> powermanagment_status (event) @ BoxMatrix   -   IRC-Chat   -   Translate: de es fr it nl pl
News Selectors Models Accessories Components Environment Config Commands System Webif Software Develop Lexicon Community Project Media

Devices Filesystems Partitions Sockets Netlink Pipes Interfaces Bridges Ports Events Sources Sinks AVMIPC Processes Watchdogs Memory Slab Vmalloc ProcFS SysFS Research

Info
  
Name-Collision - multiple objects in this wiki use the name powermanagment_status!
powermanagment_status (event) DSL power saving status
powermanagment_status (evsrc) Event-Source of avm_power.ko

AVM-Event

Goto:   Subevents  -  Dependencies   -   Model-Matrix   -   Missing Supportdata   -   SMW-Browser

Details

The powermanagment_status event informs the system about the relative power consumption of a builtin DSL modem.
This is just a simple integer value. This event is similar to the telefonprofile event, but it's only used for the power metering.

This event is sent by avm_power.ko and the only subscriber is dsl_monitor, to know what is the current state of the DSL
power management. This is necessary since the avm_power device is write only and could not be queried. dsl_monitor always
knows best whether the DSL frontend is running, and can write the respective power management profile (dsl / ata) to the
avm_power device. That is one of the reasons why dsl_monitor is also running in IP-Client mode, it's also a no-dsl monitor.

As you can see in the enum below this was initially planned to be extensible for builtin modems which are not DSL,
However, this never happened.

// From include/uapi/avm/event/gen-types.h

struct avm_event_powermanagment_status {
	enum _powermanagment_status_type substatus;
	union __powermanagment_status_union param;
};

enum _powermanagment_status_type {
	dsl_status = 0,
};

union __powermanagment_status_union {
	/*--- select by [select-variable] one of (dsl_status) ---*/
	unsigned int dsl_status;
};

Subevents

From dsl_monitor --supportdata all fw 7.29:

DSL event powermanagment status cnt 2
	subevent dsl_status cnt 2
	subevent default cnt 0

From fiber_monitor --supportdata all fw 7.29:

FIBER event powermanagment status cnt 0
	subevent dsl_status cnt 0
	subevent default cnt 0

Dependencies

Daily updated index of all dependencies of this event. Last update: GMT.
A * in the Mod column marks info from Supportdata-Probes, which will always stay incomplete.
A ** in the Mod column marks info from Supportdata2 probes, which by their nature will stay way more incomplete.
A - in the Mod column marks manual research, the Firmware then shows where the item occurs, not the Relation.

Relation Typ Object Mod Firmware Info Origin
Source evsrc powermanagment_status (evsrc) 73* 6.20 - 8.00 Event-Source of avm_power.ko AVM
Sink evsink bbpd (evsink) 2* 7.81 - 7.90 Event-Sink of bbpd AVM
Sink evsink dsl_manager (evsink) 28* 6.30 - 7.80 Event-Sink of dsl_monitor AVM
3 dependencies for this event

Model-Matrix

Daily updated index of the presence, path and size of this event for each model. Last update: GMT.
Showing all models using this event. Click any column header (click-wait-click) to sort the list by the respective data.
The (main/scrpn/boot/arm/prx/atom/rtl) label in the Model column shows which CPU is meant for Multi-Linux models.
Note that this list comes from Supportdata-Probes, which can have arbitrary settings and come from different firmware versions.
It doesn't say much if a model is not listed here. It may be a missing supportdata file or just a disabled feature.

Missing Supportdata

The data in this article is incomplete due to missing Supportdata-Probes for the models listed below.
If you own any of these models and would like to help then please get in touch.

SMW-Browser

Information is currently being retrieved from the backend.