/linux-4.1.27/arch/mips/sgi-ip27/ |
D | ip27-smp.c | 57 static int do_cpumask(cnodeid_t cnode, nasid_t nasid, int highest) in do_cpumask() argument 74 if (cpuid > highest) in do_cpumask() 75 highest = cpuid; in do_cpumask() 94 return highest; in do_cpumask() 99 int i, highest = 0; in cpu_node_probe() local 124 highest = do_cpumask(i, nasid, highest); in cpu_node_probe() 127 printk("Discovered %d cpus on %d nodes\n", highest + 1, num_online_nodes()); in cpu_node_probe()
|
/linux-4.1.27/Documentation/virtual/kvm/devices/ |
D | xics.txt | 27 Zero is the highest priority, 255 means no interrupt is pending. 30 Zero is the highest priority, 255 means no IPI is pending. 36 Zero is the highest priority, meaning no interrupts can be 51 the highest priority and 255 is the lowest. An interrupt with a
|
/linux-4.1.27/drivers/sh/clk/ |
D | core.c | 94 unsigned long highest, lowest, freq; in clk_rate_round_helper() local 98 highest = 0; in clk_rate_round_helper() 102 if (freq > highest) in clk_rate_round_helper() 103 highest = freq; in clk_rate_round_helper() 117 if (rounder->rate >= highest) in clk_rate_round_helper() 118 rate_best_fit = highest; in clk_rate_round_helper()
|
/linux-4.1.27/block/ |
D | partition-generic.c | 418 int p, highest, res; in rescan_partitions() local 469 for (p = 1, highest = 0; p < state->limit; p++) in rescan_partitions() 471 highest = p; in rescan_partitions() 473 disk_expand_part_tbl(disk, highest); in rescan_partitions()
|
/linux-4.1.27/arch/powerpc/platforms/powernv/ |
D | subcore-asm.S | 60 li r5, (HID0_POWER8_4LPARMODE | HID0_POWER8_2LPARMODE)@highest
|
/linux-4.1.27/Documentation/devicetree/bindings/mips/cavium/ |
D | cib.txt | 13 - cavium,max-bits: The index (zero based) of the highest numbered bit
|
/linux-4.1.27/drivers/input/misc/ |
D | ad714x.c | 455 int first_before, highest, first_after; in ad714x_wheel_cal_abs_pos() local 459 highest = sw->highest_stage; in ad714x_wheel_cal_abs_pos() 462 a_param = ad714x->sensor_val[highest] * in ad714x_wheel_cal_abs_pos() 463 (highest - hw->start_stage) + in ad714x_wheel_cal_abs_pos() 465 (highest - hw->start_stage - 1) + in ad714x_wheel_cal_abs_pos() 467 (highest - hw->start_stage + 1); in ad714x_wheel_cal_abs_pos() 468 b_param = ad714x->sensor_val[highest] + in ad714x_wheel_cal_abs_pos()
|
/linux-4.1.27/Documentation/devicetree/bindings/interrupt-controller/ |
D | atmel,aic.txt | 19 (highest).
|
/linux-4.1.27/Documentation/x86/x86_64/ |
D | mm.txt | 24 The direct mapping covers all memory in the system up to the highest
|
/linux-4.1.27/arch/blackfin/mach-bf533/ |
D | Kconfig | 89 highest priority number 7 to UART or any other device.
|
/linux-4.1.27/Documentation/block/ |
D | ioprio.txt | 32 to the cpu nice levels just more coarsely implemented. 0 is the highest 53 will run ls at the best-effort scheduling class at the highest priority.
|
/linux-4.1.27/drivers/pinctrl/nomadik/ |
D | pinctrl-abx500.c | 1121 unsigned int highest = 0; in abx500_get_gpio_num() local 1143 highest = gend; in abx500_get_gpio_num() 1147 if (gend > highest) in abx500_get_gpio_num() 1148 highest = gend; in abx500_get_gpio_num() 1152 npins = highest - lowest + 1; in abx500_get_gpio_num()
|
/linux-4.1.27/arch/blackfin/mach-bf537/ |
D | Kconfig | 111 highest priority number 7 to UART or any other device.
|
/linux-4.1.27/drivers/net/wireless/brcm80211/brcmfmac/ |
D | core.c | 888 int highest; in brcmf_get_next_free_bsscfgidx() local 892 highest = 2; in brcmf_get_next_free_bsscfgidx() 896 bsscfgidx = highest + 1; in brcmf_get_next_free_bsscfgidx() 897 else if (drvr->iflist[ifidx]->bssidx > highest) in brcmf_get_next_free_bsscfgidx() 898 highest = drvr->iflist[ifidx]->bssidx; in brcmf_get_next_free_bsscfgidx()
|
/linux-4.1.27/arch/mips/include/asm/ |
D | stackframe.h | 92 lui k1, %highest(kernelsp) 132 lui k1, %highest(kernelsp)
|
/linux-4.1.27/arch/blackfin/mach-bf538/ |
D | Kconfig | 159 highest priority number 7 to UART or any other device.
|
/linux-4.1.27/Documentation/device-mapper/ |
D | log-writes.txt | 65 <#logged entries> <highest allocated sector> 68 highest allocated sector : Highest allocated sector
|
D | thin-provisioning.txt | 385 <nr mapped sectors> <highest mapped sector>
|
/linux-4.1.27/Documentation/hwmon/ |
D | f71882fg | 94 to the border between the highest and one but highest temperature zones, and
|
D | pc87360 | 71 slowest accuracy highest 82 * highest accurate speed: sqrt(clock*100)
|
D | dme1737 | 300 6: highest of zone[2-3] 301 7: highest of zone[1-3]
|
D | lm85 | 209 123 Controlled by highest temp of Zone 1, 2 or 3
|
D | sysfs-interface | 296 The actual result is up to the chip, but in general the highest candidate
|
/linux-4.1.27/arch/powerpc/kernel/ |
D | head_64.S | 442 lis r25,PAGE_OFFSET@highest /* compute virtual base of kernel */ 705 li r12,(MSR_64BIT | MSR_ISF)@highest
|
D | exceptions-64e.S | 1573 lis r3,PAGE_OFFSET@highest
|
/linux-4.1.27/Documentation/devicetree/bindings/iio/adc/ |
D | at91_adc.txt | 25 atmel,adc-res-names property. If not specified, the highest
|
/linux-4.1.27/Documentation/locking/ |
D | rt-mutex-design.txt | 34 processes, let's call them processes A, B, and C, where A is the highest 109 top waiter - The highest priority process waiting on a specific mutex. 111 top pi waiter - The highest priority process waiting on one of the mutexes 195 highest priority item in the list. Obviously this is useful to store processes 222 The top of the task's PI list is always the highest priority task that 396 always contains the highest priority task that is waiting on a mutex owned 469 task's entry in the owner's pi_list. If the task is the highest priority 531 The PI code is to help with real-time processes, and to let the highest 672 add the waiter to the wait_list. If the current process is the highest 703 highest priority task on the wait_list.
|
D | rt-mutex.txt | 64 pending-ownership is assigned to the first (highest priority) waiter of
|
/linux-4.1.27/Documentation/cpu-freq/ |
D | governors.txt | 50 set the frequency statically to the lowest or highest frequency, 88 highest frequency within the borders of scaling_min_freq and 140 The highest value of kernel and HW latency restrictions is shown and
|
D | pcc-cpufreq.txt | 129 When the driver loads, it merely prints the lowest and the highest CPU
|
D | cpu-drivers.txt | 184 target_freq. ("H for highest, but no higher than")
|
/linux-4.1.27/arch/frv/kernel/ |
D | head-uc-fr451.S | 68 # - start with the highest numbered registers
|
D | head-uc-fr401.S | 253 # - start with the highest numbered registers
|
D | head-uc-fr555.S | 241 # - start with the highest numbered registers
|
D | head.S | 572 sub.p gr5,gr6,gr6 ; bit number of highest set bit (1MB=>20)
|
/linux-4.1.27/Documentation/ABI/testing/ |
D | sysfs-driver-hid-lenovo | 35 Values are decimal integers from 1 (lowest sensitivity) to 255 (highest sensitivity).
|
/linux-4.1.27/arch/blackfin/mach-bf561/ |
D | Kconfig | 206 highest priority number 7 to UART or any other device.
|
/linux-4.1.27/Documentation/devicetree/bindings/c6x/ |
D | interrupt.txt | 19 4 is highest priority and 15 is lowest priority.
|
/linux-4.1.27/drivers/cpufreq/ |
D | Kconfig | 62 the frequency statically to the highest frequency supported by 111 highest available CPU frequency.
|
/linux-4.1.27/drivers/devfreq/ |
D | Kconfig | 47 the DEVFREQ framework returns the highest frequency available
|
/linux-4.1.27/tools/testing/selftests/powerpc/pmu/ebb/ |
D | ebb_handler.S | 73 lis reg,(expr)@highest; \
|
/linux-4.1.27/Documentation/filesystems/pohmelfs/ |
D | info.txt | 68 Change IO priority to 123 (node with the highest priority gets read requests).
|
/linux-4.1.27/Documentation/video4linux/bttv/ |
D | README.quirks | 28 often. However, the audio will have highest bus access priority. Thus
|
/linux-4.1.27/Documentation/prctl/ |
D | seccomp_filter.txt | 86 call will always use the highest precedent value. (For example, 145 given system call will always use the highest precedent value.
|
/linux-4.1.27/arch/mn10300/ |
D | Kconfig | 394 comment "[!] NOTE: A lower number/level indicates a higher priority (0 is highest, 6 is lowest)" 425 int "The highest interrupt priority excluded by local_irq_disable() (2-6)"
|
/linux-4.1.27/arch/blackfin/mach-bf518/ |
D | Kconfig | 313 highest priority number 7 to UART or any other device.
|
/linux-4.1.27/arch/blackfin/mach-bf527/ |
D | Kconfig | 318 highest priority number 7 to UART or any other device.
|
/linux-4.1.27/drivers/mtd/ubi/ |
D | Kconfig | 18 This parameter defines the maximum difference between the highest
|
/linux-4.1.27/arch/powerpc/include/asm/ |
D | ppc_asm.h | 333 lis reg,(expr)@highest; \ 428 lis ra,INIT_PPR@highest; /* default ppr=3 */ \
|
/linux-4.1.27/Documentation/ |
D | futex-requeue-pi.txt | 19 implementation would wake the highest-priority waiter, and leave the
|
D | applying-patches.txt | 240 These are the base stable releases released by Linus. The highest numbered 280 If no 2.6.x.y kernel is available, then the highest numbered 2.6.x kernel is
|
D | vfio.txt | 13 access ("device assignment") when configured for the highest possible
|
D | edac.txt | 701 2 for the highest
|
D | HOWTO | 275 If no 4.x.y kernel is available, then the highest numbered 4.x
|
/linux-4.1.27/arch/blackfin/mach-bf548/ |
D | Kconfig | 376 highest priority number 7 to UART or any other device.
|
/linux-4.1.27/Documentation/power/ |
D | opp.txt | 21 need to function at their highest performing frequency all the time. To 164 Example: To find the highest opp for a device:
|
D | pci.txt | 185 determines the highest power (lowest number) state the device can be put 189 lowest power (highest number) state it can be put into is also determined by the 375 The low-power state to put the device into is the lowest-power (highest number) 477 The low-power state to put the device into is the lowest-power (highest number)
|
/linux-4.1.27/Documentation/laptops/ |
D | sony-laptop.txt | 64 sets the highest screen brightness for the next and later reboots,
|
D | thinkpad-acpi.txt | 1157 adjacent levels often map to the same fan speed. 7 is the highest 1271 scale of 0-255. 0 means fan stopped, 255 means highest normal
|
/linux-4.1.27/Documentation/filesystems/caching/ |
D | backend-api.txt | 379 highest byte it's willing to store for an object. 574 (*) Set highest store limit: 579 This sets the limit FS-Cache imposes on the highest byte it's willing to
|
/linux-4.1.27/Documentation/filesystems/ |
D | qnx6.txt | 66 information (total number of filesystem blocks) or by taking the highest
|
D | ext4.txt | 306 highest priority) which should be used for I/O
|
/linux-4.1.27/Documentation/scheduler/ |
D | sched-stats.txt | 15 the highest numbered one typically arbitrates balancing across all the
|
/linux-4.1.27/Documentation/security/ |
D | keys-request-key.txt | 194 Only if all these fail does the whole thing fail with the highest priority
|
/linux-4.1.27/arch/m68k/ifpsp060/src/ |
D | pfpsp.S | 1320 # we determine the highest priority exception(if any) set by the 1347 bfffo %d0{&24:&8},%d0 # find highest priority exception 1865 # we determine the highest priority exception(if any) set by the 1925 bfffo %d0{&24:&8},%d0 # find highest priority exception 2105 # determine the highest priority exception(if any) set by the 2617 # we determine the highest priority exception(if any) set by the
|
D | fpsp.S | 1321 # we determine the highest priority exception(if any) set by the 1348 bfffo %d0{&24:&8},%d0 # find highest priority exception 1866 # we determine the highest priority exception(if any) set by the 1926 bfffo %d0{&24:&8},%d0 # find highest priority exception 2106 # determine the highest priority exception(if any) set by the 2618 # we determine the highest priority exception(if any) set by the 4182 bfffo %d0{&24:&8},%d0 # find highest priority exception
|
/linux-4.1.27/Documentation/networking/ |
D | 6pack.txt | 71 can build in one yourself that switches over the highest address pin
|
D | cxgb.txt | 35 settings to achieve the highest performance during various types of network
|
D | e1000.txt | 351 supported speed and duplex combinations, and it links at the highest
|
D | packet_mmap.txt | 34 highest bandwidth. By using a shared buffer between the kernel and the user
|
D | bonding.txt | 218 occurs. This keeps the aggregator with the highest availability 639 among the group of highest speed slaves in the bond.
|
/linux-4.1.27/Documentation/arm64/ |
D | booting.txt | 13 mode. EL3 is the highest priority level and exists only in secure mode.
|
D | acpi_object_usage.txt | 540 reported, this is sufficient. The NMI is emulated as the highest priority
|
/linux-4.1.27/Documentation/cgroups/ |
D | unified-hierarchy.txt | 404 be understood as an underflow into the highest possible value, -2 or 408 indicate and set the highest possible value.
|
/linux-4.1.27/net/netfilter/ipvs/ |
D | Kconfig | 159 connections to the server with the highest weight that is
|
/linux-4.1.27/Documentation/x86/ |
D | boot.txt | 31 Protocol 2.03: (Kernel 2.4.18-pre1) Explicitly makes the highest possible 99 It is desirable to keep the "memory ceiling" -- the highest point in 551 address is defined as the address of the highest safe byte, so if
|
/linux-4.1.27/drivers/md/ |
D | dm-thin.c | 3956 dm_block_t mapped, highest; in thin_status() local 3976 r = dm_thin_get_highest_mapped_block(tc->td, &highest); in thin_status() 3984 DMEMIT("%llu", ((highest + 1) * in thin_status()
|
/linux-4.1.27/mm/ |
D | page_alloc.c | 5109 unsigned int highest = 0; in setup_nr_node_ids() local 5112 highest = node; in setup_nr_node_ids() 5113 nr_node_ids = highest + 1; in setup_nr_node_ids()
|
D | Kconfig | 633 and metag arch). The stack will be located at the highest memory
|
/linux-4.1.27/Documentation/scsi/ |
D | scsi_eh.txt | 217 highest-severity action means EH failure and results in offlining of
|
/linux-4.1.27/Documentation/input/ |
D | joystick-parport.txt | 53 needed, and I'd recommend pin 9 for that, the highest data bit. On the other
|
D | atarikbd.txt | 95 highest resolution available, and merely generates a pair of cursor key events
|
/linux-4.1.27/kernel/trace/ |
D | Kconfig | 221 This tracer tracks the latency of the highest priority task
|
/linux-4.1.27/Documentation/vm/ |
D | numa_memory_policy.txt | 208 after it reaches the highest specified node. This will tend to
|
/linux-4.1.27/Documentation/trace/ |
D | ftrace.txt | 522 the highest priority task to get scheduled after 1412 The tracer only traces the highest priority task in the system 1425 wakeup time it takes for the highest priority task that is woken
|
/linux-4.1.27/Documentation/netlabel/ |
D | draft-ietf-cipso-ipsecurity-01.txt | 410 highest numbered category followed by the 2 octet index of the lowest
|
/linux-4.1.27/Documentation/development-process/ |
D | 2.Process | 169 your patch may not be their highest priority. If your patch is
|
/linux-4.1.27/Documentation/sysctl/ |
D | vm.txt | 315 Note: # of this elements is one fewer than number of zones. Because the highest
|
D | kernel.txt | 653 - minimum_console_loglevel: minimum (highest) value to which
|
/linux-4.1.27/Documentation/virtual/kvm/ |
D | timekeeping.txt | 507 As the highest precision time source available, the cycle counter of the CPU
|
/linux-4.1.27/Documentation/m68k/ |
D | kernel-options.txt | 616 usually 7, the highest possible ID. Every ID on the SCSI bus must
|
/linux-4.1.27/drivers/scsi/aic7xxx/ |
D | aic7xxx.seq | 854 * flag in the highest byte of the data count. We cannot
|
/linux-4.1.27/arch/arm/ |
D | Kconfig | 1477 # a multiplatform kernel, we just want the highest value required by the
|
/linux-4.1.27/init/ |
D | Kconfig | 689 RCU_KTHREAD_PRIO to a priority higher than the highest-priority
|
/linux-4.1.27/Documentation/devicetree/ |
D | booting-without-of.txt | 437 should always generate a structure of the highest version defined
|