Home
last modified time | relevance | path

Searched refs:battery (Results 1 – 25 of 224) sorted by relevance

123456789

/external/chromium-trace/catapult/devil/devil/android/
Dbattery_utils_test.py86 self.battery = battery_utils.BatteryUtils(
109 self.battery._cache['profile'] = self._NEXUS_5
114 (self.call.battery.GetCharging(), False),
115 (self.call.battery.GetCharging(), True)):
116 self.battery._HardwareSetCharging(True)
119 self.battery._cache['profile'] = self._NEXUS_5
124 (self.call.battery.GetCharging(), True)):
125 self.battery._HardwareSetCharging(True)
129 self.battery._cache['profile'] = self._NEXUS_5
134 (self.call.battery.GetCharging(), True),
[all …]
/external/cros/system_api/dbus/power_manager/
Dpower_supply_properties.proto14 // enough rate that the battery is discharging rather than charging; see
32 // The battery is full or close to full.
35 // The battery is being charged but is not yet full.
38 // The battery is discharging. Note that an external power source may be
40 // instantaneous power consumption. This state is also used if the battery
42 // state, which may indicate a battery defect.
45 // The system doesn't have a battery.
134 // Current state of the battery.
137 // Estimated battery charge as a percent of its total capacity, in the
138 // range [0.0, 100.0]. Unset if a battery isn't present.
[all …]
/external/autotest/client/site_tests/suite_HWQual/
Dcontrol.battery_charge_time13 This test measures the battery charging time and enforces constraints. Before
14 running this test, the battery charge should be less than 5% and the device
15 should be plugged into AC. Also, the battery capacity at test time must be
16 at least 80% of design capacity (battery wear can be 20% at most). Over the
17 course of 3 hours, the battery charge should increase by at least 94% of the
18 maximum battery charge.
25 # battery must be at least 80% of design capacity
DREADME.txt15 - AC: alternating current, implies device is not powered by battery.
178 - Run the DUT on battery. Probe the battery driver:
191 - Run the DUT on battery. Plug a power draw USB dongle in each USB
202 - Run the DUT on battery. Run the power settings test:
207 - Make sure the remaining battery charge is less than 5%. Note that the test
208 will check and fail quickly if the initial battery charge is more than 5%.
209 Run the DUT on AC. Run the battery charge test:
214 - Make sure that the battery is fully charged. Note that the test will not
215 check if the battery is fully charged before running. Run the DUT on
216 battery. Run the battery load test by first following the manual
/external/autotest/client/cros/power/
Dpower_test.py58 if not self.status.battery:
104 if self.status.battery:
105 self._start_energy = self.status.battery.energy
142 if self.status.battery:
143 keyvals['ah_charge_full'] = self.status.battery.charge_full
145 self.status.battery.charge_full_design
146 keyvals['ah_charge_now'] = self.status.battery.charge_now
147 keyvals['a_current_now'] = self.status.battery.current_now
148 keyvals['wh_energy'] = self.status.battery.energy
149 energy_used = self._start_energy - self.status.battery.energy
[all …]
/external/perfetto/docs/data-sources/
Dbattery-counters.md13 measure the charge flowing in and out of the battery. This allows Perfetto to
14 observe the total and instantaneous charge drained from the battery by the
20 ![](/docs/images/battery-counters.png "Schematic diagram of battery counters")
24 * The remaining battery capacity in %.
25 * The remaining battery charge in microampere-hours (µAh).
40 the battery. If the device is plugged to a USB cable, you will likely observe
42 the fact that charge is flowing in the battery (i.e. charging it) rather
56 …pmi-0/spmi0-02/800f000.qcom,spmi:qcom,pmi8998@2:qcom,qpnp-smb2/power_supply/battery/input_suspend`.
63 ![](/docs/images/battery-counters-ui.png)
114 Unlike the battery counters, they are not affected by the charging/discharging
[all …]
/external/chromium-trace/catapult/devil/devil/android/tools/
Ddevice_monitor_test.py58 self.battery = mock.Mock()
59 self.battery.GetBatteryInfo = mock.MagicMock(
90 get_battery.return_value = self.battery
99 get_battery.return_value = self.battery
116 get_battery.return_value = self.battery
132 get_battery.return_value = self.battery
146 get_battery.return_value = self.battery
163 get_battery.return_value = self.battery
Ddevice_status.py42 battery = battery_utils.BatteryUtils(device)
43 battery_info = battery.GetBatteryInfo(timeout=5)
48 battery = battery_utils.BatteryUtils(device)
49 if not battery.GetCharging():
50 battery.SetCharging(True)
/external/u-boot/arch/arm/dts/
Dcros-ec-sbs.dtsi3 * Smart battery dts fragment for devices that use cros-ec-sbs
9 battery: sbs-battery@b { label
10 compatible = "sbs,sbs-battery";
/external/u-boot/drivers/power/battery/
Dbat_trats.c14 static struct battery battery_trats;
19 struct battery *battery = p_bat->bat; in power_battery_charge() local
27 battery->state_of_chrg < 100; k++) { in power_battery_charge()
34 debug(" %d [V]", battery->voltage_uV); in power_battery_charge()
/external/u-boot/doc/
DREADME.power-framework38 The problem emerges when we have a device (battery) which conceptually shall be
40 to start charging the battery, use PMIC to reduce board's overall power
42 energy on the battery from FG.
55 e.g. ./drivers/power/battery/trats/bat_trats.c
64 Everything is a power device described by struct pmic. Even battery is
81 1. When hierarchy is not needed (no complex battery charge):
90 2. Complex battery charging.
92 To charge a battery, information from several "abstract" power devices is
95 -- *fg_battery_check - check if battery is not above its limits
97 battery state(voltage and current capacity)
[all …]
/external/perfetto/protos/perfetto/trace/power/
Dbattery_counters.proto24 // Remaining battery capacity percentage of total capacity
27 // Instantaneous battery current in microamperes(µA).
28 // Positive values indicate net current entering the battery from a charge
29 // source, negative values indicate net current discharging from the battery.
32 // Instantaneous battery current in microamperes(µA).
/external/autotest/client/site_tests/power_Standby/
Dpower_Standby.py61 charge_start = power_stats.battery.charge_now
62 voltage_start = power_stats.battery.voltage_now
79 charge_before = power_stats.battery.charge_now
100 charge_used = charge_before - power_stats.battery.charge_now
117 charge_end = power_stats.battery.charge_now
126 voltage_end = power_stats.battery.voltage_now
127 standby_hours = power_stats.battery.charge_full_design / \
/external/autotest/client/site_tests/power_BatteryCharge/
Dpower_BatteryCharge.py54 self.charge_full_design = self.status.battery.charge_full_design
55 self.charge_full = self.status.battery.charge_full
64 self.initial_charge = self.status.battery.charge_now
101 new_charge = self.status.battery.charge_now
108 if self.status.battery.status == 'Full':
119 keyvals['ah_final_charge'] = self.status.battery.charge_now
/external/autotest/client/site_tests/power_LoadTest/
DREADME.md6 Modern mobile computers are sold with an advertised battery life, ranging from a
8 many users report that their actual battery life doesn’t match up with the
9 advertised numbers. For Chrome OS devices, we wanted to try and report battery
12 resultant battery life. This test is as an [open source][1] Chrome extension
15 The `power_LoadTest` runs as a series of one hour long iterations until battery
27 * Screen: Set to platform default brightness on battery or 40% if default can
43 * Device only powered by battery (no AC power).
45 iterations until battery passes low threshold (typically set at 3%). Initial
46 & remaining battery charge is recorded.
78 [chroot][6]. (Make sure you have battery fully charged with AC power source and
[all …]
Dpower_LoadTest.py122 if not self._power_status.battery:
129 if not self._power_status.battery:
247 if self._power_status.battery:
248 self._ah_charge_start = self._power_status.battery.charge_now
249 self._wh_energy_start = self._power_status.battery.energy
270 if self._power_status.battery:
464 if self._power_status.battery:
465 keyvals['a_current_now'] = self._power_status.battery.current_now
467 self._power_status.battery.charge_full
469 self._power_status.battery.charge_full_design
[all …]
/external/autotest/client/site_tests/power_Draw/
Dpower_Draw.py30 start_energy = status.battery.energy
40 end_energy = status.battery.energy
46 keyvals['wh_energy_full'] = status.battery.energy_full
51 keyvals['w_end_energy_rate'] = status.battery.energy_rate
/external/autotest/client/site_tests/power_BatteryDrain/
Dcontrol7 PURPOSE = "Drain the battery quickly, as a utility for other tests."
9 DUT must not be on AC power, and battery must drop to or below the
18 This test drains the battery quickly, as a utility for other tests. It requires
20 server test. You can specify a battery threshold to drain to, and a timeout in
/external/autotest/client/site_tests/hardware_MultiReaderPowerConsumption/
Dhardware_MultiReaderPowerConsumption.py116 max_charge = self.status.battery.charge_full_design
117 initial_charge = self.status.battery.charge_now
123 charge_A = self.status.battery.charge_now
133 charge_B = self.status.battery.charge_now
143 charge_C = self.status.battery.charge_now
/external/autotest/server/site_tests/sequences/
Dcontrol.power_daily12 DEPENDENCIES = "power:battery, rpm"
30 # Charge the battery to at least 50% in preparation for the consumption
31 # test. Charging the battery from empty to full can take up to 4 hours.
44 # Charge the battery to at least 99% in preparation for the load
45 # test. Charging the battery from empty to full can take up to 4 hours.
/external/autotest/server/site_tests/firmware_ECBattery/
Dcontrol9 PURPOSE = "Servo based EC battery status report test"
10 CRITERIA = "This test will fail if EC battery status report misbehalved."
20 This test check battery status read from EC console and kernel sysfs match.
/external/autotest/client/profilers/powertop/src/
DREADME1 What's eating the battery life of my laptop? Why isn't it many more
9 idle for long periods, which translates into a longer battery life for
21 components are the biggest offenders in slurping up your battery time.
28 battery life of typical laptops was increased by one hour or more!
32 maximum battery life out of your (hopefully Intel based) laptops. Try
/external/u-boot/drivers/rtc/
DKconfig48 has a selectable I2C-bus or SPI-bus, a backup battery switch-over circuit, a
63 calendar with automatic leap year correction, 2-byte battery backed SRAM,
75 battery-backed SRAM.
78 battery-baced SRAM section.
125 and now available from NXP. It includes a battery-backed real-time
127 battery-backed RAM. The driver supports access to the clock and RAM.
/external/cpuinfo/test/dmesg/
Dgalaxy-j1-2016.log303 <4>[ 0.449432] [0: swapper/0: 1] [c0] sec_chg_dt_init: battery detect gpio 313
328 <6>[ 0.487548] [0: swapper/0: 1] [c0] sm5701_get_float_voltage: battery cv voltage 0x1e
333 <6>[ 0.497619] [0: kworker/0:0: 4] [c0] sm5701_get_float_voltage: battery cv voltage 0x1e
337 <3>[ 0.497985] [3: kworker/3:0: 25] [c3] SM5701_isr_work: Fail to get psy (battery)
338 <3>[ 0.497985] [3: kworker/3:0: 25] [c3] SM5701_isr_work: Fail to get psy (battery)
346 <3>[ 0.504638] [3: kworker/3:0: 25] [c3] SM5701_isr_work: Fail to set psy (battery)
365 <6>[ 0.511077] [3: kworker/3:0: 25] [c3] SM5701_isr_work: battery status : 1
1238 <3>[ 1.986358] [2: kworker/2:1: 92] [c2] sec_charger_cb: fail to get battery psy
1301 <6>[ 1.992797] [3: swapper/0: 1] [c3] sec-battery sec-battery.4: sec_bat_set_property: …
1302 <6>[ 1.992828] [3: swapper/0: 1] [c3] sec-battery sec-battery.4: sec_battery_probe: SEC…
[all …]
/external/autotest/client/site_tests/power_ProbeDriver/
Dpower_ProbeDriver.py56 if not status.battery:
59 if not status.battery.present:

123456789