/linux-4.1.27/drivers/rtc/ |
D | rtc-ds1685.c | 255 u8 seconds, minutes, hours, wday, mday, month, years; in ds1685_rtc_read_time() local 261 hours = rtc->read(rtc, RTC_HRS); in ds1685_rtc_read_time() 279 tm->tm_hour = ds1685_rtc_bcd2bin(rtc, hours, RTC_HRS_24_BCD_MASK, in ds1685_rtc_read_time() 304 u8 ctrlb, seconds, minutes, hours, wday, mday, month, years, century; in ds1685_rtc_set_time() local 311 hours = ds1685_rtc_bin2bcd(rtc, tm->tm_hour, RTC_HRS_24_BIN_MASK, in ds1685_rtc_set_time() 353 rtc->write(rtc, RTC_HRS, hours); in ds1685_rtc_set_time() 381 u8 seconds, minutes, hours, mday, ctrlb, ctrlc; in ds1685_rtc_read_alarm() local 387 hours = rtc->read(rtc, RTC_HRS_ALARM); in ds1685_rtc_read_alarm() 418 if (unlikely(hours >= 0xc0)) in ds1685_rtc_read_alarm() 421 alrm->time.tm_hour = ds1685_rtc_bcd2bin(rtc, hours, in ds1685_rtc_read_alarm() [all …]
|
/linux-4.1.27/drivers/power/ |
D | max14577_charger.c | 217 unsigned long hours) in max14577_set_fast_charge_timer() argument 221 switch (hours) { in max14577_set_fast_charge_timer() 223 reg_data = hours - 3; in max14577_set_fast_charge_timer() 231 hours); in max14577_set_fast_charge_timer()
|
D | max77693_charger.c | 312 unsigned long hours) in max77693_set_fast_charge_timer() argument 324 switch (hours) { in max77693_set_fast_charge_timer() 326 data = (hours - 4) / 2 + 1; in max77693_set_fast_charge_timer()
|
/linux-4.1.27/arch/m68k/apollo/ |
D | config.c | 221 t->tm_hour=rtc->hours; in dn_dummy_hwclk() 229 rtc->hours=t->tm_hour; in dn_dummy_hwclk()
|
/linux-4.1.27/Documentation/ABI/testing/ |
D | sysfs-class-power | 33 - 5, 6 or 7 (hours), 47 - 4 - 16 (hours), step by 2 (rounded down)
|
D | sysfs-platform-dell-laptop | 52 The timeouts are expressed in seconds, minutes, hours and
|
/linux-4.1.27/arch/m68k/include/asm/ |
D | apollohw.h | 45 unsigned char hours, alarm_hours; member
|
/linux-4.1.27/drivers/platform/x86/ |
D | dell-laptop.c | 995 u8 hours; member 1072 info->hours = (buffer->output[3] >> 16) & 0xFF; in kbd_get_info() 1288 if (kbd_info.hours > 63) in kbd_init_info() 1289 kbd_info.hours = 63; in kbd_init_info() 1402 if (value > kbd_info.hours) in kbd_led_timeout_store() 1444 } else if (value / (60 * 60) <= kbd_info.hours && kbd_info.hours) { in kbd_led_timeout_store()
|
/linux-4.1.27/drivers/lguest/ |
D | README | 7 But be warned; this is an arduous journey of several hours or more! And as we
|
/linux-4.1.27/sound/drivers/ |
D | mts64.c | 154 u8 hours, u8 minutes, 368 u8 hours, u8 minutes, in mts64_smpte_start() argument 382 mts64_write_command(p, hours); in mts64_smpte_start()
|
/linux-4.1.27/include/trace/events/ |
D | v4l2.h | 139 __entry->timecode_hours = buf->timecode.hours; \
|
/linux-4.1.27/Documentation/ |
D | rtc.txt | 31 only issue an alarm up to 24 hours in the future, other hardware may 176 24 hours in the future. (Use RTC_WKALM_* by preference.) 179 the next 24 hours use a slightly more powerful API, which supports
|
D | stable_kernel_rules.txt | 109 - The review committee has 48 hours in which to ACK or NAK the patch.
|
D | magic-number.txt | 23 to the kernel! It has saved me countless hours of debugging,
|
D | BUG-HUNTING | 138 If you get it down to a routine, you'll probably get a fix in 24 hours.
|
D | iostats.txt | 54 your observations are measured in large numbers of minutes or hours,
|
D | HOWTO | 522 barely a second glance. However, a 500 line patch may take hours to
|
D | CodingStyle | 25 at your screen for 20 straight hours, you'll find it a lot easier to see
|
/linux-4.1.27/tools/testing/ktest/ |
D | ktest.pl | 566 my $hours = 0; 570 $hours = int($time / 3600); 571 $time -= $hours * 3600; 578 if ($hours > 0) { 579 doprint "$hours hour"; 580 doprint "s" if ($hours > 1);
|
/linux-4.1.27/Documentation/scsi/ |
D | qlogicfas.txt | 69 the computer was left on for a few hours. It was worse with longer
|
D | aic7xxx.txt | 335 408-957-2550, 24 hours a day, 7 days a week.
|
D | aic79xx.txt | 438 408-957-2550, 24 hours a day, 7 days a week.
|
D | st.txt | 434 (3.9 hours). For erase this value is further multiplied by
|
/linux-4.1.27/sound/pci/asihpi/ |
D | hpi_internal.h | 954 u16 hours; member 962 u16 hours; member
|
/linux-4.1.27/Documentation/usb/ |
D | gadget_multi.txt | 95 Failing to comply may cause brain damage after wondering for hours why
|
/linux-4.1.27/Documentation/filesystems/nfs/ |
D | knfsd-stats.txt | 134 remains constant for hours at a time, this counter is unlikely
|
/linux-4.1.27/Documentation/laptops/ |
D | laptop-mode.txt | 136 20 seconds (value 4) for BATT_HD and 2 hours (value 244) for AC_HD. The 200 of his regular 3 to 3.5 hours) using a spindown time of 5 seconds (BATT_HD=1). 301 # Default is 2 hours on AC (AC_HD=244) and 20 seconds for battery (BATT_HD=4).
|
/linux-4.1.27/Documentation/arm/ |
D | Booting | 174 you many hours of debug.
|
/linux-4.1.27/fs/reiserfs/ |
D | README | 88 Vladimir Saveljev was one of the programmers, and he worked long hours
|
/linux-4.1.27/Documentation/arm64/ |
D | booting.txt | 128 you many hours of debug.
|
/linux-4.1.27/drivers/scsi/esas2r/ |
D | atvda.h | 954 u8 hours; member
|
/linux-4.1.27/sound/pci/rme9652/ |
D | hdspm.c | 4757 int a, ltc, frames, seconds, minutes, hours; in snd_hdspm_proc_read_tco() local 4851 hours = ltc & 0xF; in snd_hdspm_proc_read_tco() 4853 hours += (ltc & 0x3) * 10; in snd_hdspm_proc_read_tco() 4856 hours, minutes, seconds, frames); in snd_hdspm_proc_read_tco()
|
/linux-4.1.27/include/uapi/linux/ |
D | videodev2.h | 639 __u8 hours; member
|
/linux-4.1.27/Documentation/input/ |
D | event-codes.txt | 205 consecutive events is reliable on a reasonable time scale (hours).
|
/linux-4.1.27/Documentation/filesystems/ |
D | xfs-self-describing-metadata.txt | 24 weren't the ultimate cause of a corruption event. It may take a few hours to a
|
/linux-4.1.27/Documentation/mtd/ |
D | nand_ecc.txt | 5 I felt there was room for optimisation. I bashed the code for a few hours
|
/linux-4.1.27/drivers/media/platform/vivid/ |
D | vivid-vid-cap.c | 229 tc->hours = (seq / (60 * 60 * fps)) % 24; in vid_cap_buf_finish()
|
/linux-4.1.27/Documentation/vm/ |
D | unevictable-lru.txt | 64 spending 100% of their time in vmscan for hours or days on end, with the system
|
/linux-4.1.27/Documentation/cgroups/ |
D | memory.txt | 109 its processing over a period of hours, days, months or years, but with
|
/linux-4.1.27/drivers/media/v4l2-core/ |
D | v4l2-ioctl.c | 469 tc->hours, tc->minutes, tc->seconds, in v4l_print_buffer()
|
/linux-4.1.27/Documentation/networking/ |
D | ip-sysctl.txt | 317 Default: 2hours.
|