/linux-4.4.14/drivers/scsi/ |
D | sd_dif.c | 170 unsigned int j, intervals; in sd_dif_complete() local 178 intervals = good_bytes / scsi_prot_interval(scmd); in sd_dif_complete() 193 if (intervals == 0) { in sd_dif_complete() 203 intervals--; in sd_dif_complete()
|
/linux-4.4.14/drivers/cpuidle/governors/ |
D | menu.c | 129 unsigned int intervals[INTERVALS]; member 214 unsigned int value = data->intervals[i]; in get_typical_interval() 230 unsigned int value = data->intervals[i]; in get_typical_interval() 439 data->intervals[data->interval_ptr++] = measured_us; in menu_update()
|
/linux-4.4.14/drivers/infiniband/hw/usnic/ |
D | usnic_uiom.c | 197 static void usnic_uiom_unmap_sorted_intervals(struct list_head *intervals, in usnic_uiom_unmap_sorted_intervals() argument 203 list_for_each_entry_safe(interval, tmp, intervals, link) { in usnic_uiom_unmap_sorted_intervals() 246 static int usnic_uiom_map_sorted_intervals(struct list_head *intervals, in usnic_uiom_map_sorted_intervals() argument 264 list_for_each_entry(interval_node, intervals, link) { in usnic_uiom_map_sorted_intervals() 332 usnic_uiom_unmap_sorted_intervals(intervals, pd); in usnic_uiom_map_sorted_intervals()
|
D | usnic_uiom_interval_tree.h | 87 void usnic_uiom_put_interval_set(struct list_head *intervals);
|
D | usnic_uiom_interval_tree.c | 171 void usnic_uiom_put_interval_set(struct list_head *intervals) in usnic_uiom_put_interval_set() argument 174 list_for_each_entry_safe(interval, tmp, intervals, link) in usnic_uiom_put_interval_set()
|
/linux-4.4.14/Documentation/ABI/stable/ |
D | sysfs-bus-w1 | 7 100 ms - hence the tens-to-hundreds milliseconds scan intervals
|
/linux-4.4.14/block/ |
D | bio-integrity.c | 278 unsigned int intervals; in bio_integrity_prep() local 285 intervals = bio_integrity_intervals(bi, bio_sectors(bio)); in bio_integrity_prep() 288 len = intervals * bi->tuple_size; in bio_integrity_prep()
|
/linux-4.4.14/Documentation/hwmon/ |
D | lm93 | 82 The monitoring intervals for the two #PROCHOT signals is also configurable. 83 These intervals can be found in the sysfs files prochot1_interval and 84 prochot2_interval. The values in these files specify the intervals for 87 intervals are (in seconds): 89 #PROCHOT intervals: 0.73, 1.46, 2.9, 5.8, 11.7, 23.3, 46.6, 93.2, 186, 372 240 Ramp Times: 0 (disabled, h/w default) to 0.75 in 0.05 second intervals
|
D | nct6775 | 144 intervals.
|
/linux-4.4.14/drivers/net/wireless/ti/wl12xx/ |
D | scan.h | 84 __le32 intervals[SCAN_MAX_CYCLE_INTERVALS]; member
|
D | scan.c | 353 cfg->intervals[i] = cpu_to_le32(req->scan_plans[0].interval * in wl1271_scan_sched_scan_config()
|
/linux-4.4.14/include/sound/ |
D | pcm.h | 237 struct snd_interval intervals[SNDRV_PCM_HW_PARAM_LAST_INTERVAL - member 253 return &constrs->intervals[var - SNDRV_PCM_HW_PARAM_FIRST_INTERVAL]; in constrs_interval() 892 return ¶ms->intervals[var - SNDRV_PCM_HW_PARAM_FIRST_INTERVAL]; in hw_param_interval() 904 return ¶ms->intervals[var - SNDRV_PCM_HW_PARAM_FIRST_INTERVAL]; in hw_param_interval_c()
|
/linux-4.4.14/drivers/net/wireless/p54/ |
D | fwio.c | 620 for (i = 0; i < ARRAY_SIZE(psm->intervals); i++) { in p54_set_ps() 621 psm->intervals[i].interval = in p54_set_ps() 623 psm->intervals[i].periods = cpu_to_le16(1); in p54_set_ps()
|
D | lmac.h | 478 struct p54_psm_interval intervals[4]; member
|
/linux-4.4.14/Documentation/filesystems/ |
D | automount-support.txt | 57 It may prove simplest to simply call this at regular intervals, using
|
/linux-4.4.14/drivers/media/usb/uvc/ |
D | uvc_driver.c | 333 __u32 **intervals, unsigned char *buffer, int buflen) in uvc_parse_format() argument 455 frame->dwFrameInterval = *intervals; in uvc_parse_format() 456 *(*intervals)++ = 1; in uvc_parse_format() 515 frame->dwFrameInterval = *intervals; in uvc_parse_format() 536 *(*intervals)++ = interval ? interval : 1; in uvc_parse_format()
|
/linux-4.4.14/Documentation/scheduler/ |
D | sched-bwc.txt | 69 - nr_periods: Number of enforcement intervals that have elapsed.
|
/linux-4.4.14/Documentation/usb/ |
D | ehci.txt | 83 and prevent use of polling intervals of less than one frame. 130 Also, some values in device descriptors (such as polling intervals for
|
D | URB.txt | 253 in intervals that are powers of two (1, 2, 4 etc) units. Units are frames
|
D | proc_usb_info.txt | 272 transfer intervals and sizes provided by URBs, which can be less
|
/linux-4.4.14/sound/core/ |
D | pcm_native.c | 47 struct snd_interval intervals[SNDRV_PCM_HW_PARAM_TICK_TIME - member 3559 memcpy(params->intervals, oparams->intervals, sizeof(oparams->intervals)); in snd_pcm_hw_convert_from_old_params() 3578 memcpy(oparams->intervals, params->intervals, sizeof(oparams->intervals)); in snd_pcm_hw_convert_to_old_params()
|
D | pcm_compat.c | 81 …struct snd_interval intervals[SNDRV_PCM_HW_PARAM_LAST_INTERVAL - SNDRV_PCM_HW_PARAM_FIRST_INTERVAL… member
|
/linux-4.4.14/tools/perf/Documentation/ |
D | examples.txt | 174 analysis done over ten 1-second intervals:
|
D | perf-stat.txt | 140 The overhead percentage could be high in some cases, for instance with small, sub 100ms intervals. …
|
/linux-4.4.14/Documentation/locking/ |
D | locktorture.txt | 96 to run and pause for (roughly) five-second intervals.
|
/linux-4.4.14/Documentation/accounting/ |
D | taskstats-struct.txt | 127 * Uses time intervals seen by the kernel i.e. no adjustment
|
/linux-4.4.14/drivers/staging/unisys/Documentation/ |
D | overview.txt | 109 called at specific intervals to enable the driver to poll the device 121 * The channel_interrupt() function is called at frequent intervals to
|
/linux-4.4.14/include/uapi/sound/ |
D | asound.h | 381 struct snd_interval intervals[SNDRV_PCM_HW_PARAM_LAST_INTERVAL - member
|
/linux-4.4.14/drivers/media/pci/solo6x10/ |
D | solo6x10-core.c | 403 __ATTR_RO(intervals),
|
/linux-4.4.14/Documentation/watchdog/ |
D | watchdog-api.txt | 21 regular intervals. When such a notification occurs, the driver will
|
/linux-4.4.14/Documentation/cpu-freq/ |
D | governors.txt | 147 intervals the CPU needs to be on average more than 95% in use to then
|
/linux-4.4.14/Documentation/networking/ |
D | netdev-FAQ.txt | 70 is fed back to Linus at regular (~weekly) intervals. Meaning that the
|
D | can.txt | 645 possible transmit intervals can be altered.
|
D | ip-sysctl.txt | 158 entries' time-to-live and time intervals between garbage collection
|
/linux-4.4.14/Documentation/RCU/ |
D | torture.txt | 136 to run and pause for (roughly) five-second intervals.
|
D | stallwarn.txt | 161 longer intervals, so that the time between (say) the first and second
|
/linux-4.4.14/Documentation/devicetree/bindings/thermal/ |
D | thermal.txt | 6 such as trip points, polling intervals, sensors and cooling devices
|
/linux-4.4.14/arch/s390/ |
D | Kconfig | 796 intervals, once the timer is started.
|
/linux-4.4.14/drivers/watchdog/ |
D | Kconfig | 273 then watchdog intervals of over approximately 20seconds are 1047 userspace is still alive, at regular intervals.
|
/linux-4.4.14/drivers/platform/x86/ |
D | Kconfig | 918 intervals. If a user enables this functionality under Windows and
|
/linux-4.4.14/Documentation/virtual/kvm/ |
D | timekeeping.txt | 544 timespec - but which advances in much larger granularity intervals, sometimes
|
/linux-4.4.14/Documentation/video4linux/ |
D | vivid.txt | 947 frequency intervals. Depending on the frequency of the radio receiver a
|
/linux-4.4.14/lib/ |
D | Kconfig.debug | 1358 printed at more widely spaced intervals.
|