Home
last modified time | relevance | path

Searched refs:points (Results 1 – 200 of 289) sorted by relevance

12

/linux-4.1.27/arch/mn10300/unit-asb2364/
Dleds.c39 void peripheral_leds7x4_display_dec(unsigned int val, unsigned int points) in peripheral_leds7x4_display_dec() argument
50 leds |= points^0x01010101; in peripheral_leds7x4_display_dec()
55 void peripheral_leds7x4_display_hex(unsigned int val, unsigned int points) in peripheral_leds7x4_display_hex() argument
66 leds |= points^0x01010101; in peripheral_leds7x4_display_hex()
94 void peripheral_leds7x4_display_dec(unsigned int val, unsigned int points) { } in peripheral_leds7x4_display_dec() argument
95 void peripheral_leds7x4_display_hex(unsigned int val, unsigned int points) { } in peripheral_leds7x4_display_hex() argument
/linux-4.1.27/arch/mn10300/unit-asb2305/
Dleds.c36 void peripheral_leds7x4_display_dec(unsigned int val, unsigned int points) in peripheral_leds7x4_display_dec() argument
47 leds |= points^0x01010101; in peripheral_leds7x4_display_dec()
52 void peripheral_leds7x4_display_hex(unsigned int val, unsigned int points) in peripheral_leds7x4_display_hex() argument
63 leds |= points^0x01010101; in peripheral_leds7x4_display_hex()
82 void peripheral_leds7x4_display_minssecs(unsigned int time, unsigned int points) in peripheral_leds7x4_display_minssecs() argument
93 leds |= points^0x01010101; in peripheral_leds7x4_display_minssecs()
/linux-4.1.27/mm/
Doom_kill.c152 long points; in oom_badness() local
172 points = get_mm_rss(p->mm) + get_mm_counter(p->mm, MM_SWAPENTS) + in oom_badness()
181 points -= (points * 3) / 100; in oom_badness()
185 points += adj; in oom_badness()
191 return points > 0 ? points : 1; in oom_badness()
304 unsigned int points; in select_bad_process() local
320 points = oom_badness(p, NULL, nodemask, totalpages); in select_bad_process()
321 if (!points || points < chosen_points) in select_bad_process()
324 if (points == chosen_points && thread_group_leader(chosen)) in select_bad_process()
328 chosen_points = points; in select_bad_process()
[all …]
Dmemcontrol.c1530 unsigned int points = 0; in mem_cgroup_out_of_memory() local
1571 points = oom_badness(task, memcg, NULL, totalpages); in mem_cgroup_out_of_memory()
1572 if (!points || points < chosen_points) in mem_cgroup_out_of_memory()
1575 if (points == chosen_points && in mem_cgroup_out_of_memory()
1582 chosen_points = points; in mem_cgroup_out_of_memory()
1590 points = chosen_points * 1000 / totalpages; in mem_cgroup_out_of_memory()
1591 oom_kill_process(chosen, gfp_mask, order, points, totalpages, memcg, in mem_cgroup_out_of_memory()
/linux-4.1.27/Documentation/thermal/
Dx86_pkg_temperature_thermal19 zone with maximum two user mode configurable trip points. Number of trip points
31 This contains two trip points:
39 Any value other than 0 in these trip points, can trigger thermal notifications.
Dsysfs-api.txt45 trips: the total number of trip points this thermal zone supports.
54 - "disabled" will prevent kernel thermal driver action upon trip points
61 different threshold temperature points.
66 whether trip points have been crossed (0 for interrupt driven systems).
233 trip points so that user application can take full
316 ACPI thermal zone may support multiple trip points like critical, hot,
319 thermal_zone_device (thermal_zone1) with 4 trip points in all.
393 For CRITICAL and HOT trip points, this notifies the respective drivers,
394 and does actual throttling for other trip points i.e ACTIVE and PASSIVE.
Dintel_powerclamp.txt307 certain temperature (below most active trip points).
/linux-4.1.27/Documentation/devicetree/bindings/cpufreq/
Darm_big_little_dt.txt15 - operating-points: Refer to Documentation/devicetree/bindings/power/opp.txt
32 operating-points = <
51 operating-points = <
Dcpufreq-exynos5440.txt9 - operating-points: Table of frequencies and voltage CPU could be transitioned into,
24 operating-points = <
Dcpufreq-dt.txt14 - operating-points: Refer to Documentation/devicetree/bindings/power/opp.txt for
35 operating-points = <
/linux-4.1.27/Documentation/locking/
Dlockstat.txt61 It also tracks 4 contention points per class. A contention point is a call site
122 short separator (line 08, 13) from the contention points.
124 Lines 09-12 show the first 4 recorded contention points (the code
126 contended points (the lock holder). It is possible that the max
130 short separator. The contention points don't match the column descriptors,
132 points are the points we're contending with.
/linux-4.1.27/Documentation/devicetree/bindings/power/
Dopp.txt8 - operating-points: An array of 2-tuples items, and each item consists
19 operating-points = <
/linux-4.1.27/Documentation/devicetree/bindings/sound/
Darmada-370db-audio.txt11 * marvell,audio-controller: a phandle that points to the audio
14 * marvell,audio-codec: a set of three phandles that points to:
/linux-4.1.27/arch/m68k/fpsp040/
Dsint.S8 | Entry points sint and sintrz are called from do_func
12 | Input: (Entry points sint and sintrz) Double-extended
212 | ;assumes a0 points to operand
232 | ;Input: a0 points to operand to
234 | ;Output: a0 points to normalized
Dx_unfl.S157 lea WBTEMP(%a6),%a0 |a0 now points to operand
202 | Input: a0 points to input operand
206 | Output: a0 points to rounded operand
Dutil.S161 | Input a0 points to an operand in the internal extended format
162 | Output a0 points to the result in the internal extended format
176 | a0 points to operand in internal extended format
178 | a0 points to result in internal extended format
486 | a0 points to input operand in the internal extended format
489 | a0 points to correct internal extended precision result.
Dsgetem.S40 | handler. It points a0 to the input operand.
66 | handler. It points a0 to the input operand.
Dround.S23 | a0 points to the input operand in the internal extended format
403 | a0 points to the operand to be denormalized
408 | a0 points to the denormalized result
488 | a0 points to the operand to be denormalized
492 | a0 points to the denormalized operand
Dx_store.S8 | a6 = points to fp value to be stored.
Dkernel_ex.S133 | On entry, a0 points to the exceptional operand. The final exceptional
Dsetox.S503 |--a0 points to 2^(J/64), D0 is biased expo. of 2^(M)
669 |--a0 points to 2^(J/64), D0 and a1 both contain M
/linux-4.1.27/drivers/staging/iio/Documentation/
Dsysfs-bus-iio-impedance-analyzer-ad593312 frequency points along the sweep.
18 Number of frequency points (steps) in the frequency sweep.
/linux-4.1.27/arch/m68k/ifpsp060/
DTEST.DOC49 This will allow the calling routines to access the entry points
89 no symbol names, this section contains function entry points that are fixed
90 with respect to the top of the package. The currently defined entry-points
91 are listed in section "68060{ISP,FPSP}-TEST entry points" below. A calling
137 68060ISP-TEST Entry-points:
141 68060FPSP-TEST Entry-points:
147 The floating-point unit test has 3 entry points which will require
Dfplsp.doc59 This will allow calling routines to access the entry points
71 below in "68060FPLSP entry points" that corresponds to the desired
79 There are 3 entry-points for each instruction type: single precision,
124 The fabs/fadd/fdiv/fint/fintrz/fmul/fneg/fsqrt/fsub entry points
129 68060FPLSP entry points:
Disp.doc63 This will allow calling routines to access the entry points
102 no symbol names, this section contains function entry points that are fixed
103 with respect to the top of the package. The currently defined entry-points
104 are listed in section "68060 ISP entry points" below. A calling routine
160 68060ISP entry points:
Dfpsp.doc55 This will allow calling routines to access the entry points
94 no symbol names, this section contains function entry points that are fixed
95 with respect to the top of the package. The currently defined entry-points
96 are listed in section "68060 FPSP entry points" below. A calling routine
150 68060FPSP entry points:
Dilsp.doc58 This will allow calling routines to access the entry points
136 68060ILSP entry points:
/linux-4.1.27/net/core/
Ddrop_monitor.c160 if (!memcmp(&location, msg->points[i].pc, sizeof(void *))) { in trace_drop_common()
161 msg->points[i].count++; in trace_drop_common()
172 memcpy(msg->points[msg->entries].pc, &location, sizeof(void *)); in trace_drop_common()
173 msg->points[msg->entries].count = 1; in trace_drop_common()
/linux-4.1.27/Documentation/usb/
Dmisc_usbsevseg.txt39 The device has either 6 or 8 decimal points.
42 To set multiple decimals points sum up each power.
/linux-4.1.27/drivers/thermal/
DKconfig11 Each thermal zone contains its own temperature, trip points,
198 management framework. A thermal zone with several trip points will be
199 created. Cooling devices can be bound to the trip points to cool this
200 thermal zone if trip points reached.
227 bound to thermal zone trip points. When a trip point reached, the
249 two trip points which can be set by user to get notifications via thermal
259 thermal zone. There are two trip points. One of the trip point can
/linux-4.1.27/arch/arm/boot/dts/
Dimx6dl.dtsi29 operating-points = <
35 fsl,soc-operating-points = <
Dexynos5440.dtsi94 operating-points = <
246 #include "exynos5440-trip-points.dtsi"
250 #include "exynos5440-trip-points.dtsi"
254 #include "exynos5440-trip-points.dtsi"
Dimx6sx-sdb.dts16 operating-points = <
22 fsl,soc-operating-points = <
Dimx6q.dtsi29 operating-points = <
37 fsl,soc-operating-points = <
Domap34xx.dtsi19 operating-points = <
Domap443x.dtsi17 operating-points = <
Ddra74x.dtsi24 operating-points = <
Domap4460.dtsi16 operating-points = <
Domap36xx.dtsi23 operating-points = <
Dexynos5420.dtsi837 #include "exynos5420-trip-points.dtsi"
841 #include "exynos5420-trip-points.dtsi"
845 #include "exynos5420-trip-points.dtsi"
849 #include "exynos5420-trip-points.dtsi"
853 #include "exynos5420-trip-points.dtsi"
Dhighbank.dts40 operating-points = <
Dr8a73a4-ape6evm.dts163 operating-points = <
Dsun4i-a10-olinuxino-lime.dts65 operating-points = <
Dimx1.dtsi47 operating-points = <200000 1900000>;
Dsh73a0-kzm9g.dts31 operating-points = <
Dzynq-7000.dtsi29 operating-points = <
Dimx6sl.dtsi45 operating-points = <
51 fsl,soc-operating-points = <
Drk3188.dtsi34 operating-points = <
Drk3066a.dtsi34 operating-points = <
Dimx27.dtsi67 operating-points = <
Dimx51.dtsi87 operating-points = <
Datlas6.dtsi31 operating-points = <
Dsun5i-a13.dtsi48 operating-points = <
Dprima2.dtsi33 operating-points = <
Dimx6sx.dtsi60 operating-points = <
66 fsl,soc-operating-points = <
/linux-4.1.27/arch/sh/lib/
Dmemcpy.S20 add r6,r0 ! From here, r0 points the end of copying point
/linux-4.1.27/include/uapi/linux/
Dnet_dropmon.h36 struct net_dm_drop_point points[0]; member
/linux-4.1.27/Documentation/hwmon/
Dacpi_power_meter19 interval, an optional capping mechanism, and a couple of trip points. The
27 Both power[1-*]_average_{min,max} must be set before the trip points will work.
Df71882fg95 vica versa. So the temperature zone trip points 1-4 (or 1-2) go from high temp
127 You can define a number of temperature/fan speed trip points, which % the
129 standard sysfs interface. The number and type of trip points is chip
Dlm8370 two other points of the motherboard. We suspect these points to be the
Dw83l785ts23 on several points including this one.
Dit87236 This interface implements 4 temperature vs. PWM output trip points.
238 at full speed) while the PWM output of the other 3 trip points can be
239 freely chosen. The temperature of all 4 trip points can be freely chosen.
250 Trip points must be set properly before switching to automatic fan speed
Dw83792d150 W83792D also provides a special mode for fan. Four temperature points are
172 sf2_point[1-4]_fan[1-3] - four temperature points for each fan for Smart Fan II
Df71805f156 You define 3 temperature/fan speed trip points using the
158 relationship between temperature and fan speed with two additional points
Dnct6775171 There are up to seven data points depending on the chip type. Subsequent data
172 points should be set to higher temperatures and higher pwm values to achieve
Dsysfs-interface277 Define the PWM vs temperature curve. Number of trip points is
278 chip-dependent. Use this for chips which associate trip points
285 Define the PWM vs temperature curve. Number of trip points is
286 chip-dependent. Use this for chips which associate trip points
290 There is a third case where trip points are associated to both PWM output
Dadt747596 The driver exposes two trip points per PWM channel.
Dw8379389 trip points, defining a PWM/temperature curve which the chip will follow.
Dvt1211174 that even though there are 2 sets of 4 auto points each, they map to the same
Dlm85171 temperature configuration points:
Dpmbus-core118 - Several function entry points are provided to support overriding and/or
Ddme1737253 zone[1-3]_auto_point[1-3]_temp RW Auto PWM temp points. Auto_point1 is
/linux-4.1.27/kernel/
DKconfig.preempt23 "explicit preemption points" to the kernel code. These new
24 preemption points have been selected to reduce the maximum
/linux-4.1.27/Documentation/driver-model/
Dbinding.txt62 A symlink is created in the bus's 'devices' directory that points to
65 A symlink is created in the driver's 'devices' directory that points
69 symlink is created in that directory that points to the device's
Dclass.txt93 that points to the driver's directory (under its bus directory):
102 Each device gets a symlink in the devices/ directory that points to the
Ddevres.txt37 needs to handle multiple entry points.
/linux-4.1.27/Documentation/devicetree/bindings/powerpc/fsl/
Dcache_sram.txt11 - fsl,cache-sram-ctlr-handle : points to the L2 controller
Dsrio.txt36 Definition: A single <phandle> value that points to the RMU.
Ddcsr.txt90 Definition: A single <phandle> value that points
/linux-4.1.27/net/irda/irlan/
DKconfig10 The IrLAN protocol can be used to talk with infrared access points
/linux-4.1.27/Documentation/x86/
Dentry_64.txt8 kernel code. Most of these entry points are registered in
12 syscall entry points and thus provides for 32-bit processes the
103 generate all 'normal' entry points with the regular (faster) paranoid=0
D00-INDEX10 - Describe (some of the) kernel entry points for x86.
Dintel_mpx.txt37 points the "bndcfgu" register to the directory (must also set the valid
72 * points the hardware BNDCFGU register at the directory
118 frequent. They potentially happen every time a register points to
Dexception-tables.txt53 Since we jump to the contents of fixup, fixup obviously points
/linux-4.1.27/Documentation/virtual/kvm/devices/
Dvfio.txt21 For each, kvm_device_attr.addr points to an int32_t file descriptor
/linux-4.1.27/arch/frv/kernel/
Dentry-table.S258 # miscellaneous user mode entry points
277 # miscellaneous kernel mode entry points
309 # miscellaneous debug mode entry points
/linux-4.1.27/arch/arm/mach-omap2/
Dsleep34xx.S104 adr r3, api_params @ r3 points to parameters
441 add r3, r3, r0 @ r3 points to dummy parameters
457 ldr r3, [r4, #0xBC] @ r3 points to parameters
472 adds r3, r3, #8 @ r3 points to parameters
/linux-4.1.27/include/linux/
Doom.h61 unsigned int points, unsigned long totalpages,
/linux-4.1.27/Documentation/crypto/
Dasync-tx-api.txt17 4.1 Conformance points
76 The return value is non-NULL and points to a 'descriptor' when the operation
169 4.1 Conformance points:
170 There are a few conformance points required in dmaengine drivers to
Ddescore-readme.txt297 m points to a 128byte block, k points to an 8 byte des key
/linux-4.1.27/Documentation/devicetree/bindings/watchdog/
Dsamsung-wdt.txt19 In case of Exynos5250 and 5420 this property points to syscon node holding the PMU
/linux-4.1.27/Documentation/devicetree/bindings/drm/msm/
Dgpu.txt15 - qcom,gpu-pwrlevels: list of operating points
/linux-4.1.27/Documentation/ABI/testing/
Dsysfs-devices-memory77 points to the corresponding NUMA node directory.
90 points to the corresponding /sys/devices/system/memory/memoryY
Dsysfs-devices-soc57 the system. Each symlink points back into the aforementioned
Dsysfs-bus-pci146 The symbolic link points to the PCI device sysfs entry of the
156 The symbolic link points to the PCI device sysfs entry of
164 The symbolic link points to the PCI device sysfs entry of the
171 This symbolic link points to the PCI hotplug controller driver
Dsysfs-class-cxl60 prefault what it points to.
Dsysfs-devices-system-cpu61 When CONFIG_NUMA is enabled, a symbolic link that points
Dsysfs-class-regulator246 This points to the parent or supply regulator if one exists.
/linux-4.1.27/Documentation/devicetree/bindings/thermal/
Dthermal.txt6 such as trip points, polling intervals, sensors and cooling devices
18 - trip points: describe key temperatures at which cooling is recommended. The
19 set of points should be chosen based on hardware limits.
20 - cooling maps: used to describe links between trip points and cooling devices;
80 * Trip points
105 get assigned to trip points of the zone. The cooling devices are expected
214 operating-points = <
Ddb8500-thermal.txt9 - num-trips : number of total trip points, this is required, set it 0 if none,
Dtegra-soctherm.txt5 on temperature trip points, and handling external overcurrent
/linux-4.1.27/Documentation/devicetree/bindings/drm/imx/
Dhdmi.txt14 The phandle points to the iomuxc-gpr region containing the HDMI
Dldb.txt17 The phandle points to the iomuxc-gpr region containing the LVDS
/linux-4.1.27/Documentation/networking/
Dalias.txt21 Please note: The route always points to the base interface.
Dcxacru.txt15 named device points to the USB interface device's directory which contains
Dnetif-msg.txt46 The recommendation is the following points
Dradiotap-headers.txt96 /* buf points to the start of the radiotap header part */
Dray_cs.txt71 points.
Dlapb-module.txt100 The LAPB module provides a number of function entry points.
Dspider_net.txt42 descriptor pointer (GDACTDPA). The GDACTDPA points at the descr
/linux-4.1.27/Documentation/devicetree/bindings/x86/
Dce4100.txt19 The reg property describes the CPU number. The lapic property points to
/linux-4.1.27/Documentation/trace/
Dkprobetrace.txt18 current_tracer. Instead of that, add probe points via
140 This clears all probe points.
146 This clears probe points selectively.
Dring-buffer-design.txt193 since the reader page still points to the next location in the ring
281 The commit pointer points to the last write location that was
286 The commit page points to the page that has the last full commit.
287 The tail page points to the page with the last write (before
542 Another important point: The page that the reader page points back to
543 by its previous pointer (the one that now points to the new head page)
544 never points back to the reader page. That is because the reader page is
Duprobetracer.txt13 current_tracer. Instead of that, add probe points via
/linux-4.1.27/arch/mips/include/asm/mach-ip27/
Dkernel-entry-init.h92 ld t0, 0(t0) # t0 points to kern_vars struct
/linux-4.1.27/fs/cachefiles/
DKconfig33 execution as there are a number of points at which data is gathered,
/linux-4.1.27/Documentation/fault-injection/
Dprovoke-crashes.txt4 crashing points, but can also crash the kernel directly without KRPOBE
/linux-4.1.27/Documentation/filesystems/
Dqnx6.txt99 '.' inode number points to the directory inode
100 '..' inode number points to the parent directory inode
114 The directory entry file inode pointer points to the target file inode.
Dfiles.txt30 and files->fdtab points to the new structure. The fdtable
Dpath-lookup.txt60 name in the name string, and require some recursive path walking. Mount points
70 - traverse mount points;
299 lookups, and to assume dentry mount points and mount roots are stable up and
D9p.txt47 mount points. Each 9P export is seen by the client as a virtio device with an
Dhpfs.txt95 in chmoding file where symlink points. These symlinks are just for Linux use and
288 Reschedule points added so that it doesn't lock CPU long time
Daffs.txt143 might be "User", "WB" and "Graphics", the mount points /amiga/User,
Dmandatory-locking.txt112 below are just as valid as any others, so long as the main points seem to
Dautofs4-mount-control.txt103 above and so the mount points can be covered by a mount.
118 for these potentially covered autofs mount points. Rather than just
/linux-4.1.27/Documentation/scsi/
Dlibsas.txt72 sas_addr -- this normally points to an array holding the sas
97 port -- this points to the sas_port if the phy belongs
98 to a port -- the LLDD only reads this. It points to the
139 memory allocation, etc, this points to statically
356 points to a domain device, this is how the SAS LLDD knows
Dufs.txt71 service access points for higher layers.
85 MIPI UniPro and MIPI M-PHY. UIC provides 2 service access points
/linux-4.1.27/drivers/thermal/ti-soc-thermal/
DKconfig21 This includes trip points definitions, extrapolation rules and
/linux-4.1.27/tools/thermal/tmon/
DREADME12 devices, zones, sensors, and trip points. They can also change dynamically.
/linux-4.1.27/tools/perf/Documentation/
Dperf-probe.txt38 Specify module name in which perf-probe searches probe points
106 Set the maximum number of probe points for an event. Default is 128.
127 Probe points are defined by following syntax.
/linux-4.1.27/Documentation/parisc/
Ddebugging37 instruction that cleared the Q bit, if you're not it points anywhere
/linux-4.1.27/arch/arm/nwfpe/
Dfpmodule.inl26 instruction, and points 4 bytes beyond the actual instruction
/linux-4.1.27/drivers/net/wireless/ath/ath6kl/
DKconfig52 enablable trace points.
/linux-4.1.27/fs/fscache/
DKconfig39 execution as there are a number of points at which data is gathered,
/linux-4.1.27/Documentation/devicetree/bindings/arm/bcm/
Dbrcm,brcmstb.txt87 A phandle / integer array that points to the syscon node which describes
/linux-4.1.27/Documentation/leds/
Dledtrig-oneshot.txt5 no clear trap points to put standard led-on and led-off settings. Using this
/linux-4.1.27/Documentation/security/
Dcredentials.txt279 Each task points to its credentials by a pointer called 'cred' in its
287 (2) the reference count on the group_info struct it points to may be changed;
289 (3) the reference count on the security data it points to may be changed;
291 (4) the reference count on any keyrings it points to may be changed;
293 (5) any keyrings it points to may be revoked, expired or have their security
296 (6) the contents of any keyrings to which it points may be changed (the whole
Dkeys-request-key.txt46 The main difference between the access points is that the in-kernel interface
/linux-4.1.27/arch/mn10300/kernel/
Dswitch_to.S133 # back in (A1 points to the new thread_struct).
Dentry.S3 # MN10300 Exception and interrupt entry points
276 # NMI exception entry points
/linux-4.1.27/Documentation/
Dinit.txt18 (and root= kernel parameter points to the correct partition),
Dio-mapping.txt30 return value points to a single page in CPU address space.
Dassoc_array.txt114 will then be passed to call_rcu() to free it and any dead stuff it points
137 This points to a number of methods, all of which need to be provided:
462 the metadata key prefix must be in the subtree that the metadata pointer points
515 slot in that parent that points to it. None-recursive iteration uses these to
Drobust-futex-ABI.txt40 The pointer 'head' points to a structure in the threads address space
56 to itself, 'head'. The last 'lock entry' points back to the 'head'.
DDMA-attributes.txt51 necessary sync points for this memory in the driver.
Dkprobes.txt89 Kprobes then points the saved instruction pointer at the jprobe's
434 regs is as described for kprobe.pre_handler. ri points to the
438 - rp: points to the corresponding kretprobe object
439 - task: points to the corresponding task struct
440 - data: points to per return-instance private data; see "Kretprobe
Dsysfs-rules.txt31 Parsing /proc/mounts is a waste of time. Other mount points are a
Dunaligned-memory-access.txt182 This code will cause unaligned accesses every time the data parameter points
/linux-4.1.27/Documentation/video4linux/
Dsh_mobile_ceu_camera.txt39 In the above chart minuses and slashes represent "real" data amounts, points and
DREADME.pvrusb2179 and USB core entry points are here. This is our "main".
/linux-4.1.27/Documentation/power/
Dnotifiers.txt11 points). The solution may be to load the firmware into memory before processes
Dsuspend-and-interrupts.txt84 of the points where the suspend thread looks for pending wakeup events).
Dsuspend-and-cpuhotplug.txt154 Important files and functions/entry points:
/linux-4.1.27/Documentation/power/regulator/
Dconsumer.txt71 voltage to match system operating points. e.g. CPUfreq drivers can scale
101 current limit to match system operating points. e.g. LCD backlight driver can
/linux-4.1.27/Documentation/devicetree/bindings/crypto/
Dfsl-sec4.txt105 Definition: A single <phandle> value that points
168 Definition: A single <phandle> value that points
338 Definition: A single <phandle> value that points
/linux-4.1.27/Documentation/networking/mac80211_hwsim/
DREADME30 point and a station) or large scale tests (multiple access points with
/linux-4.1.27/drivers/leds/trigger/
DKconfig28 sporadic events, when there are no clear begin and end trap points,
/linux-4.1.27/Documentation/devicetree/bindings/soc/ti/
Dkeystone-navigator-dma.txt35 managers. Note that these addresses though points to queue managers,
/linux-4.1.27/Documentation/input/
Dalps.txt223 3) There doesn't seem to be a count of the contact points anywhere in the v4
224 protocol packets. Deriving a count of contact points must be done by
229 the count of contact points can only be updated every third packet as
Dff.txt99 "effect" points to a structure describing the effect to upload. The effect is
Dmulti-touch-protocol.txt308 tool axis points towards the touch point [1]. Otherwise, the tool axes are
325 contact. The sequence of points forms a polygon which defines the shape of
/linux-4.1.27/Documentation/devicetree/bindings/
Dgraph.txt90 Each endpoint should contain a 'remote-endpoint' phandle property that points
/linux-4.1.27/Documentation/devicetree/bindings/video/
Dsimple-framebuffer.txt20 hw node the "display" property points to, otherwise it must point directly
/linux-4.1.27/Documentation/cpu-freq/
Dcore.txt74 The third argument, a void *pointer, points to a struct cpufreq_policy
/linux-4.1.27/arch/arm/mach-bcm/
DKconfig45 wifi access points, it's internal name is Northstar.
/linux-4.1.27/arch/m68k/math-emu/
Dfp_entry.S109 | Entry points to get/put a register. Some of them can be get/put
/linux-4.1.27/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/
Dqe.txt82 should define an fsl,firmware-phandle property that points to the firmware node
/linux-4.1.27/Documentation/filesystems/cifs/
DTODO84 1) existing symbolic links (Windows reparse points) are recognized but
/linux-4.1.27/Documentation/vm/
Dactive_mm.txt32 - "tsk->mm" points to the "real address space". For an anonymous process,
/linux-4.1.27/arch/mn10300/
DKconfig.debug76 This causes debugging messages to be displayed at various points
/linux-4.1.27/Documentation/RCU/
Dlockdep.txt107 or the RCU-protected data that it points to can change concurrently.
/linux-4.1.27/Documentation/development-process/
D7.AdvancedTopics104 generally only at specific release points (such as a mainline -rc
163 Different developers will review code from different points of view. Some
/linux-4.1.27/Documentation/ia64/
Dmca.txt52 assume that current points into the struct task, switching to a new
131 * x86 has a separate struct task which points to one of multiple kernel
/linux-4.1.27/Documentation/virtual/kvm/
Dmmu.txt110 is not related to a translation directly. It points to other shadow pages.
200 parent_ptes bit 0 is zero, only one spte points at this pages and
201 parent_ptes points at this single spte, otherwise, there exists multiple
202 sptes pointing at this page and (parent_ptes & ~0x1) points at a data
/linux-4.1.27/drivers/net/wireless/p54/
Dlmac.h377 } points[3] __packed; member
/linux-4.1.27/arch/m68k/ifpsp060/src/
Dilsp.S31 # and contains the entry points into the package. The user, in
80 # 0x10(sp) = points to location of remainder/quotient. #
496 # 0xc(sp) = points to location of 64-bit result #
/linux-4.1.27/Documentation/frv/
Dmmu-layout.txt167 segment table entries of 4 bytes apiece. Each PME "points to" a page table. In practice, each STE
168 points to a subset of the page table, the first to PT+0x0000, the second to PT+0x0100, the third to
/linux-4.1.27/drivers/gpu/drm/qxl/
Dqxl_dev.h774 struct qxl_point_fix points[0]; member
/linux-4.1.27/drivers/cpufreq/
DKconfig.arm83 defined trip points.
/linux-4.1.27/arch/arm/kernel/
Dentry-header.S103 @ r9 currently points to the memory location just above the auto saved
Dentry-armv.S1033 * SP points to a minimal amount of processor-private memory, the address
/linux-4.1.27/Documentation/fmc/
Dcarrier.txt274 points 0 through 3 (even if the test points on the PCB are called
/linux-4.1.27/Documentation/devicetree/
Dof_unittest.txt74 parent points to root node)
/linux-4.1.27/arch/frv/mm/
Dtlb-miss.S157 # - DAMLR4 points to the virtual address of the appropriate page table
/linux-4.1.27/Documentation/arm/
Dkernel_user_helpers.txt13 warning. Only the entry points and their results as documented here are
/linux-4.1.27/Documentation/pcmcia/
Ddriver-changes.txt147 services. In 2.6, all of those entry points are exported and called
/linux-4.1.27/kernel/locking/
Dlockdep.c161 static int lock_point(unsigned long points[], unsigned long ip) in lock_point() argument
166 if (points[i] == 0) { in lock_point()
167 points[i] = ip; in lock_point()
170 if (points[i] == ip) in lock_point()
/linux-4.1.27/Documentation/i2c/
Dslave-interface166 this time of writing. Some points to keep in mind when using buffers:
/linux-4.1.27/Documentation/powerpc/
Dtransactional_memory.txt46 Between these points the processor is in 'Transactional' state; any memory
/linux-4.1.27/fs/cifs/
DKconfig162 points. If unsure, say N.
/linux-4.1.27/arch/cris/arch-v10/
DREADME.mm236 check if the PGD entry points anywhere - if not, a page table page is
/linux-4.1.27/arch/arc/kernel/
Dentry.S645 ; All 2 entry points to here already disable interrupts
/linux-4.1.27/arch/parisc/kernel/
Dperf_asm.S1355 ;* arg1 points to is loaded and moved into the staging register.
/linux-4.1.27/fs/proc/
Dbase.c385 unsigned long points = 0; in proc_oom_score() local
389 points = oom_badness(task, NULL, NULL, totalpages) * in proc_oom_score()
392 seq_printf(m, "%lu\n", points); in proc_oom_score()
/linux-4.1.27/Documentation/arm/pxa/
Dmfp.txt46 to this new MFP mechanism, here are several key points:
/linux-4.1.27/drivers/media/usb/pwc/
Dphilips.txt172 Some points worth knowing:
/linux-4.1.27/Documentation/timers/
Dtimekeeping.txt15 the basic timeline, whereas clock events shoot interrupts on certain points
/linux-4.1.27/arch/x86/crypto/
Dsha512-avx-asm.S91 # WK_2(t) points to 1 of 2 qwords at frame.WK depdending on t being odd/even
Dsha512-ssse3-asm.S88 # WK_2(t) points to 1 of 2 qwords at frame.WK depdending on t being odd/even
/linux-4.1.27/Documentation/acpi/
Dnamespace.txt27 Description Table). The XSDT always points to the FADT (Fixed ACPI

12