Lines Matching +full:- +full:in +full:- +full:supply

2 Linux power supply class
7 Power supply class used to represent battery, UPS, AC or DC power supply
8 properties to user-space.
11 every power supply out there. Attributes are available via sysfs and uevent
16 power supply, specific monitoring hardware may not be able to provide them
19 Power supply class is extensible, and allows to define drivers own attributes.
21 if it will be found that some attribute is applicable to many power supply
26 AC/USB power supply online status. (Note that specific details of the
34 Power supply class has predefined set of attributes, this eliminates code
35 duplication across drivers. Power supply class insist on reusing its
39 kind of power supply, and can process/present them to a user in consistent
43 See drivers/power/supply/ds2760_battery.c for the example how to declare
51   All voltages, currents, charges, energies, time and temperatures in µV,
53   stated. It's driver's job to convert its raw values to units in which
60 +--------------------------------------------------------------------------+
61 |               **Charge/Energy/Capacity - how to not confuse**            |
62 +--------------------------------------------------------------------------+
66 | - `CHARGE_*`                                                             |
67 |	attributes represents capacity in µAh only.                        |
68 | - `ENERGY_*`                                                             |
69 |	attributes represents capacity in µWh only.                        |
70 | - `CAPACITY`                                                             |
71 |	attribute represents capacity in *percents*, from 0 to 100.        |
72 +--------------------------------------------------------------------------+
85   `BATTERY_STATUS_*` values, as defined in battery.h.
94   indicates the power supply (battery or charger) connected
99   POWER_SUPPLY_HEALTH_*, defined in battery.h.
105   design values for maximal and minimal power supply voltages.
116   given power supply.
140   the current charge counter (in µAh).  This could easily
142   relative, time-based measurements.
158   maximum charge current supported by the power supply object.
163   maximum charge voltage supported by the power supply object.
184   capacity in percents.
186   minimum capacity alert value in percents.
188   maximum capacity alert value in percents.
193   temperature of the power supply.
217 Battery <-> external power supply interaction
223 For that case, power supply class implements notification mechanism for
226 External power supply (AC) lists supplicants (batteries) names in
228 issued by external power supply will notify supplicants via
235 characteristics from a devicetree battery node, defined in
236 Documentation/devicetree/bindings/power/supply/battery.yaml. This is
237 implemented in drivers/power/supply/bq27xxx_battery.c.
239 Properties in struct power_supply_battery_info and their counterparts in the
240 battery node have names corresponding to elements in enum power_supply_property,
256    Good candidates to add in future: model/part#, cycle_time, manufacturer,
264    Most likely, no. Such attribute can be placed in the driver itself, if
265    it is useful. Of course, if the attribute in question applicable to
273    in percents, but provides charge_{now,full,empty}. Should I calculate
282    should be factored out, and in fact, apm_power, the driver to serve
283    legacy APM API on top of power supply class, uses a simple heuristic of
285    voltage and so on. But full-fledged battery model is likely not subject