Home
last modified time | relevance | path

Searched refs:hours (Results 1 – 25 of 121) sorted by relevance

12345

/linux/drivers/rtc/
H A Drtc-ds1685.c265 u8 seconds, minutes, hours, wday, mday, month, years; in ds1685_rtc_read_time() local
271 hours = rtc->read(rtc, RTC_HRS); in ds1685_rtc_read_time()
288 tm->tm_hour = ds1685_rtc_bcd2bin(rtc, hours, RTC_HRS_24_BCD_MASK, in ds1685_rtc_read_time()
312 u8 ctrlb, seconds, minutes, hours, wday, mday, month, years, century; in ds1685_rtc_set_time() local
319 hours = ds1685_rtc_bin2bcd(rtc, tm->tm_hour, RTC_HRS_24_BIN_MASK, in ds1685_rtc_set_time()
361 rtc->write(rtc, RTC_HRS, hours); in ds1685_rtc_set_time()
388 u8 seconds, minutes, hours, mday, ctrlb, ctrlc; in ds1685_rtc_read_alarm() local
395 hours = rtc->read(rtc, RTC_HRS_ALARM); in ds1685_rtc_read_alarm()
423 if (likely(hours < 0xc0)) in ds1685_rtc_read_alarm()
424 alrm->time.tm_hour = ds1685_rtc_bcd2bin(rtc, hours, in ds1685_rtc_read_alarm()
[all …]
/linux/Documentation/ABI/testing/
H A Dsysfs-class-power-gaokun9 for delay hours, battery charging will follow the rules of
16 Valid values: In hours (non-negative)
H A Drtc-cdev17 RTCs that support alarms. Can be set up to 24 hours in the
22 powerful interface, which can issue alarms beyond 24 hours and
/linux/drivers/power/supply/
H A Dmax14577_charger.c207 unsigned long hours) in max14577_set_fast_charge_timer() argument
211 switch (hours) { in max14577_set_fast_charge_timer()
213 reg_data = hours - 3; in max14577_set_fast_charge_timer()
221 hours); in max14577_set_fast_charge_timer()
H A Dmax77693_charger.c355 unsigned long hours) in max77693_set_fast_charge_timer() argument
367 switch (hours) { in max77693_set_fast_charge_timer()
369 data = (hours - 4) / 2 + 1; in max77693_set_fast_charge_timer()
/linux/arch/m68k/apollo/
H A Dconfig.c187 t->tm_hour=rtc->hours; in dn_dummy_hwclk()
197 rtc->hours=t->tm_hour; in dn_dummy_hwclk()
/linux/tools/docs/
H A Dtest_doc_build.py339 hours, minutes = divmod(elapsed_time, 3600)
342 hours = int(hours)
/linux/arch/arm64/boot/dts/qcom/
H A Dmsm8916-wingtech-wt865x8.dtsi43 energy-full-design-microwatt-hours = <8740000>;
44 charge-full-design-microamp-hours = <2300000>;
H A Dmsm8916-lg-m216.dts29 energy-full-design-microwatt-hours = <8800000>;
30 charge-full-design-microamp-hours = <2300000>;
H A Dsdm845-google-crosshatch.dts13 charge-full-design-microamp-hours = <3480000>;
H A Dmsm8916-gplus-fl8005a.dts32 energy-full-design-microwatt-hours = <13690000>;
33 charge-full-design-microamp-hours = <3700000>;
H A Dmsm8996-oneplus3t.dts25 charge-full-design-microamp-hours = <3400000>;
H A Dmsm8996-oneplus3.dts24 charge-full-design-microamp-hours = <3000000>;
H A Dmsm8939-asus-z00t.dts28 energy-full-design-microwatt-hours = <11500000>;
29 charge-full-design-microamp-hours = <3000000>;
H A Dsdm845-google-blueline.dts13 charge-full-design-microamp-hours = <2970000>;
/linux/drivers/gpu/drm/ci/xfails/
H A Di915-jsl-skips.txt14 # GEM tests takes ~1000 hours, so skip it
H A Di915-whl-skips.txt14 # GEM tests takes ~1000 hours, so skip it
H A Di915-cml-skips.txt14 # GEM tests takes ~1000 hours, so skip it
H A Di915-amly-skips.txt16 # GEM tests takes ~1000 hours, so skip it
H A Di915-apl-skips.txt18 # GEM tests takes ~1000 hours, so skip it
H A Di915-tgl-skips.txt23 # GEM tests takes ~1000 hours, so skip it
/linux/tools/testing/selftests/arm64/fp/
H A DREADME60 Ideally, the test should be allowed to run for many minutes or hours
95 Again, the test should be allowed to run for many minutes or hours to
/linux/Documentation/devicetree/bindings/rtc/
H A Dmicrochip,pic32-rtc.txt3 The RTCC keeps time in hours, minutes, and seconds, and one half second. It
/linux/arch/m68k/include/asm/
H A Dapollohw.h46 unsigned char hours, alarm_hours; member
/linux/include/trace/events/
H A Dv4l2.h139 __entry->timecode_hours = buf->timecode.hours;
216 __entry->timecode_hours = vbuf->timecode.hours;

12345