Home
last modified time | relevance | path

Searched refs:point (Results 1 – 200 of 577) sorted by relevance

123

/linux-4.1.27/drivers/input/touchscreen/
Dzforce_ts.c338 struct zforce_point point; in zforce_touch_event() local
350 point.coord_x = in zforce_touch_event()
352 point.coord_y = in zforce_touch_event()
355 if (point.coord_x > pdata->x_max || in zforce_touch_event()
356 point.coord_y > pdata->y_max) { in zforce_touch_event()
358 point.coord_x, point.coord_y); in zforce_touch_event()
359 point.coord_x = point.coord_y = 0; in zforce_touch_event()
362 point.state = payload[9 * i + 5] & 0x03; in zforce_touch_event()
363 point.id = (payload[9 * i + 5] & 0xfc) >> 2; in zforce_touch_event()
366 point.area_major = max(payload[9 * i + 6], in zforce_touch_event()
[all …]
Dauo-pixcir-ts.c135 struct auo_point_t *point) in auo_pixcir_collect_data() argument
160 point[i].coord_x = in auo_pixcir_collect_data()
162 point[i].coord_y = in auo_pixcir_collect_data()
165 if (point[i].coord_x > pdata->x_max || in auo_pixcir_collect_data()
166 point[i].coord_y > pdata->y_max) { in auo_pixcir_collect_data()
168 point[i].coord_x, point[i].coord_y); in auo_pixcir_collect_data()
169 point[i].coord_x = point[i].coord_y = 0; in auo_pixcir_collect_data()
173 point[i].area_major = max(raw_area[2 * i], raw_area[2 * i + 1]); in auo_pixcir_collect_data()
174 point[i].area_minor = min(raw_area[2 * i], raw_area[2 * i + 1]); in auo_pixcir_collect_data()
175 point[i].orientation = raw_area[2 * i] > raw_area[2 * i + 1]; in auo_pixcir_collect_data()
[all …]
/linux-4.1.27/drivers/ntb/
DKconfig6 The PCI-E Non-transparent bridge hardware is a point-to-point PCI-E bus
9 ntb Linux driver uses this point-to-point communication as a method to
/linux-4.1.27/arch/arm/nwfpe/
Dsoftfloat-specialize5 This C source fragment is part of the SoftFloat IEC/IEEE Floating-point
12 of this code was written as part of a project to build a fixed-point vector
42 Raises the exceptions specified by `flags'. Floating-point traps can be
78 Returns 1 if the single-precision floating-point value `a' is a NaN;
91 Returns 1 if the single-precision floating-point value `a' is a signaling
104 Returns the result of converting the single-precision floating-point NaN
124 precision floating-point format.
136 Takes two single-precision floating-point values `a' and `b', one of which
170 Returns 1 if the double-precision floating-point value `a' is a NaN;
183 Returns 1 if the double-precision floating-point value `a' is a signaling
[all …]
Dfpa11.inl24 /* Read and write floating point status register */
38 /* Read and write floating point control register */
Dsoftfloat-macros5 This C source fragment is part of the SoftFloat IEC/IEEE Floating-point
12 of this code was written as part of a project to build a fixed-point vector
96 fixed-point value with binary point between `a0' and `a1'. This fixed-point
221 to form a fixed-point value with binary point between `a1' and `a2'. This
222 fixed-point value is shifted right by the number of bits given in `count',
DChangeLog20 floating point registers. Therefore, any changes to the
59 task. This should happen on the first floating point exception
/linux-4.1.27/arch/m68k/ifpsp060/
Dfskeleton.S58 | This is the main exit point for the 68060 Floating-Point
70 | This is the exit point for the 060FPSP when an enabled overflow exception
71 | is present. The routine below should point to the operating system handler
89 | This is the exit point for the 060FPSP when an enabled underflow exception
90 | is present. The routine below should point to the operating system handler
107 | This is the exit point for the 060FPSP when an enabled operand error exception
108 | is present. The routine below should point to the operating system handler
126 | This is the exit point for the 060FPSP when an enabled signalling NaN exception
127 | is present. The routine below should point to the operating system handler
145 | This is the exit point for the 060FPSP when an enabled divide-by-zero exception
[all …]
Disp.doc100 The second section, the "Entry-point" section, is used by external routines
106 entry-point.
116 point is located 0 bytes from the top of the "Entry-point" section.)
118 The third section is the code section. After entering through an "Entry-point",
177 _060_isp_unimp() entry point of the ISP.
184 made, by the system integrator, to point directly back into the package
185 through the "Entry-point"s _060_isp_cas() or _060_isp_cas2().
196 "Entry-point" _060_isp_cas_finish() or _060_isp_cas2_finish().
Diskeleton.S58 | This is and example main exit point for the Unimplemented Integer
84 | This is an alternate exit point for the Unimplemented Integer
119 | This is an alternate exit point for the Unimplemented Integer
128 | stack frame and branches to the _real_trace() entry point.
161 | Entry point for the selected cas emulation code implementation.
172 | Entry point for the selected cas2 emulation code implementation.
183 | Entry point for the operating system`s routine to "lock" a page
252 | Entry point for the operating system`s routine to "unlock" a
DTEST.DOC87 The second section, the "Entry-point" section, is used by external routines
93 function entry-point.
101 section is 128 bytes long; and the 68060ISP test entry point is located
102 0 bytes from the top of the "Entry-point" section.)
104 The third section is the code section. After entering through an "Entry-point",
147 The floating-point unit test has 3 entry points which will require
201 # ftest.sa starts here; start of "Entry-point" section.
Dfpsp.doc92 The second section, the "Entry-point" section, is used by external routines
98 entry-point.
106 section is 128 bytes long; and the F-Line FPSP handler entry point is located
107 48 bytes from the top of the "Entry-point" section.)
109 The third section is the code section. After entering through an "Entry-point",
Dilsp.doc71 function. A branch instruction located at the selected entry point
74 The entry point addresses at the beginning of the package will remain
79 do a "bsr" or "jsr" to the entry point defined by
133 point to the correct instruction, the user will at least be able
Dfplsp.doc72 function. A branch instruction located at the selected entry point
75 The entry point addresses at the beginning of the package will remain
110 this exception using implemented floating-point instructions.
112 floating-point Operand Error exception, then the library routine
/linux-4.1.27/Documentation/devicetree/bindings/thermal/
Ddb8500-thermal.txt11 - tripN-temp : temperature of trip point N, should be in ascending order;
12 - tripN-type : type of trip point N, should be one of "active" "passive" "hot"
15 point N, this is required if trip point N is defined, set it 0 if none,
17 - tripN-cdev-nameM : name of the No. M cooling device of trip point N;
Dthermal.txt82 The trip node is a node to describe a point in the temperature domain
83 in which the system takes an action. This node describes just the point,
96 "active": A trip point to enable active cooling
97 "passive": A trip point to enable passive cooling
98 "hot": A trip point to notify emergency
114 - trip: A phandle of a trip point node within the same thermal
116 trip point node
120 Type: unsigned referred cooling device at the referred trip point.
151 - trips: A sub-node which is a container of only trip point nodes
301 from its minimum to 4, when it reaches trip point 'cpu_alert0'
[all …]
Dexynos-thermal.txt54 - samsung,tmu_first_point_trim: First point trimming value
55 - samsung,tmu_second_point_trim: Second point trimming value
/linux-4.1.27/arch/m68k/fpsp040/
Dslog2.S4 | The entry point slog10 computes the base-10
13 | OUTPUT: log_10(X) or log_2(X) returned in floating-point
34 | Notes: Default means round-to-nearest mode, no floating-point
49 | Notes: Default means round-to-nearest mode, no floating-point
63 | Notes: Default means round-to-nearest mode, no floating-point
78 | Notes: Default means round-to-nearest mode, no floating-point
117 |--entry point for Log10(X), X is denormalized
129 |--entry point for Log10(X), X is normalized
143 |--entry point for Log2(X), X is denormalized
156 |--entry point for Log2(X), X is normalized
Dsrem_mod.S4 | The entry point sMOD computes the floating point MOD of the
5 | input values X and Y. The entry point sREM computes the floating
6 | point (IEEE) REM of the input values X and Y.
18 | FREM(X,Y) or FMOD(X,Y), depending on entry point.
42 | Step 4. At this point, R = X - QY = MOD(X,Y). Set
60 | Step 9. At this point, R = 2^(-j)*X - Q Y = Y. Thus,
219 |..At this point R = 2^(-L)X; Q = 0; k = 0; and k+j = L
226 |..At this point carry = 0, R = (D1,D2), Y = (D4,D5)
232 |..At this point, R = Y
248 |..At this point, Carry=0, R < Y. R = 2^(k-L)X - QY; k+j = L; j >= 0.
[all …]
Dsint.S4 | The entry point sINT computes the rounded integer
10 | respectively. Entry point sintdo is used by bindec.
13 | number X in the ETEMP space in the floating-point
15 | (Entry point sintdo) Double-extended number X in
17 | (Entry point sintd) Double-extended denormalized
18 | number X in the ETEMP space in the floating-point
Dx_ovfl.S6 | Overflow occurs when a floating-point intermediate result is
7 | too large to be represented in a floating-point data register,
8 | or when storing to memory, the contents of a floating-point
Dsgetem.S4 | The entry point sGETEXP returns the exponent portion
10 | The entry point sGETMAN extracts the mantissa of the
17 | the floating-point save stack.
39 | This entry point is used by the unimplemented instruction exception
65 | This entry point is used by the unimplemented instruction exception
Dsacos.S4 | Description: The entry point sAcos computes the inverse cosine of
11 | Output: The value arccos(X) returned in floating-point register Fp0.
Dx_fline.S7 | floating point instructions. If so, let fpsp_unimp handle it.
54 | ;a6 can point correctly to the stack frame
85 fmovel EXC_PC(%a6),%FPIAR |point FPIAR to fline inst
Dsmovecr.S4 | The entry point sMOVECR returns the constant at the
Dsto_res.S7 | correct floating-point destination register. fp0 and fp1
16 | Modifies: destination floating point register
Dsasin.S4 | Description: The entry point sAsin computes the inverse sine of
11 | Output: The value arcsin(X) returned in floating-point register Fp0.
Dsatanh.S4 | The entry point satanh computes the inverse
12 | Output: The value arctanh(X) returned in floating-point register Fp0.
Dskeleton.S7 | Each entry point for exception 'xxxx' begins with a 'jmp fpsp_xxxx'.
10 | the 'fpsp_xxxx' handler entry point should be placed in the exception
13 | return from the package by a 'jmp real_xxxx'. At that point
60 | All dz exceptions are 'real', hence no fpsp_dz entry point.
397 | The supervisor source address is guaranteed to point into the supervisor
Dscosh.S4 | The entry point sCosh computes the hyperbolic cosine of
11 | Output: The value cosh(X) returned in floating-point register Fp0.
Dres_func.S85 | At this point, only opclass 0 and 2 possible
93 | At this point:
102 | At this point, fabs, fneg, fsmove, fdmove, ftst, fsqrt, fssqrt, and
602 | operations which are not restorable into the floating-point
764 leal WBTEMP(%a6),%a0 |point a0 to memory location
853 leal WBTEMP(%a6),%a0 |point a0 to wbtemp in frame
883 leal WBTEMP(%a6),%a0 |point a0 to wbtemp in frame
1058 leal WBTEMP(%a6),%a0 |point a0 to wbtemp in frame
1232 lea WBTEMP(%a6),%a0 |point a0 to memory location
1503 | at this point, the answer is between the largest pos and neg values
[all …]
Dssinh.S4 | The entry point sSinh computes the hyperbolic sine of
11 | Output: The value sinh(X) returned in floating-point register Fp0.
Dscale.S4 | The entry point sSCALE computes the destination operand
9 | The entry point sscale is called from do_func to emulate
41 | This entry point is used by the unimplemented instruction exception
Dstanh.S4 | The entry point sTanh computes the hyperbolic tangent of
11 | Output: The value tanh(X) returned in floating-point register Fp0.
Ddecbin.S9 | Output: Exact floating-point representation of the packed bcd value.
32 | The mantissa digits will be converted with the decimal point
128 | (i.e., all digits assumed left of the decimal point.)
Dx_unimp.S7 | Invoked when the user program encounters a floating-point
Dbinstr.S9 | in d0. (This pointer must point to byte 4 of the first
15 | The 64-bit binary is assumed to have a decimal point before
Dsatan.S4 | The entry point satan computes the arctangent of an
11 | Output: Arctan(X) returned in floating-point register Fp0.
Dsetox.S4 | The entry point setox computes the exponential of a value.
16 | exp(X) or exp(X)-1 returned in floating-point register fp0.
65 | To avoid the use of floating-point comparisons, a
620 |--entry point for EXPM1(X), here X is denormalized
627 |--entry point for EXPM1(X), here X is finite, non-zero, non-NaN
Dx_snan.S200 movel %a7,%a0 |point to low word
221 movel %a7,%a0 |point to source byte
Dbindec.S47 | after the decimal point which are to be included as
96 | such that the decimal point is to the left of bit 63.
280 | original decimal point which are to be included as
551 | the size to extended. The sintdo entry point in the sint
/linux-4.1.27/drivers/net/wireless/ath/ath5k/
Deeprom.c720 u8 pier, point, idx; in ath5k_eeprom_convert_pcal_info_5111() local
769 for (point = 0; point < pd->pd_points; point++) { in ath5k_eeprom_convert_pcal_info_5111()
772 pd->pd_pwr[point] = 2 * pcinfo->pwr[point]; in ath5k_eeprom_convert_pcal_info_5111()
775 pd->pd_step[point] = pcinfo->pcdac[point]; in ath5k_eeprom_convert_pcal_info_5111()
908 unsigned int pier, pdg, point; in ath5k_eeprom_convert_pcal_info_5112() local
954 for (point = 1; point < pd->pd_points; in ath5k_eeprom_convert_pcal_info_5112()
955 point++) { in ath5k_eeprom_convert_pcal_info_5112()
957 pd->pd_pwr[point] = in ath5k_eeprom_convert_pcal_info_5112()
958 pcinfo->pwr_x0[point]; in ath5k_eeprom_convert_pcal_info_5112()
961 pd->pd_step[point] = in ath5k_eeprom_convert_pcal_info_5112()
[all …]
/linux-4.1.27/Documentation/thermal/
Dsysfs-api.txt25 inputs from thermal zone attributes (the current temperature and trip point
46 mask: Bit string: If 'n'th bit is set, then trip point 'n' is writeable.
57 .get_trip_type: get the type of certain trip point.
58 .get_trip_temp: get the temperature above which the certain trip point
101 point of a thermal zone device.
105 trip: indicates which trip point the cooling devices is associated with
107 upper:the Maximum cooling state for this trip point.
110 lower:the Minimum cooling state can be used for this trip point.
118 trip point of a thermal zone device. This function is usually called in
122 trip: indicates which trip point the cooling devices is associated with
[all …]
Dexynos_thermal22 1. Two point trimming
25 2. One point trimming
Dx86_pkg_temperature_thermal20 depends on the capability of the package. Once the trip point is violated,
Dcpu-cooling-api.txt13 to the caller. The binding of the cooling devices to the trip point is left for
/linux-4.1.27/tools/perf/util/
Dprobe-event.c352 memcpy(tmp, &pev->point, sizeof(*tmp)); in get_alternative_probe_event()
353 memset(&pev->point, 0, sizeof(pev->point)); in get_alternative_probe_event()
354 ret = find_alternative_probe_point(dinfo, tmp, &pev->point, in get_alternative_probe_event()
357 memcpy(&pev->point, tmp, sizeof(*tmp)); in get_alternative_probe_event()
509 tevs[i].point.address -= stext; in add_exec_to_probe_trace_events()
510 tevs[i].point.module = strdup(exec); in add_exec_to_probe_trace_events()
511 if (!tevs[i].point.module) { in add_exec_to_probe_trace_events()
543 tevs[i].point.module = strdup(module); in add_module_to_probe_trace_events()
544 if (!tevs[i].point.module) { in add_module_to_probe_trace_events()
577 if (tevs[i].point.address && !tevs[i].point.retprobe) { in post_process_probe_trace_events()
[all …]
Dprobe-event.h38 struct probe_trace_point point; /* Trace point */ member
74 struct perf_probe_point point; /* Probe point */ member
95 struct probe_trace_point point; /* Actual probepoint */ member
Dprobe-finder.c744 .function = pf->pev->point.function, in find_best_scope()
874 pf->pev->point.lazy_line); in find_probe_point_lazy()
886 struct perf_probe_point *pp = &pf->pev->point; in probe_point_inline_cb()
921 struct perf_probe_point *pp = &pf->pev->point; in probe_point_search_cb()
1000 struct perf_probe_point *pp = &pf->pev->point; in debuginfo__find_probes()
1175 pf->pev->point.retprobe, &tev->point); in add_probe_trace_event()
1179 pr_debug("Probe point found: %s+%lu\n", tev->point.symbol, in add_probe_trace_event()
1180 tev->point.offset); in add_probe_trace_event()
1290 pf->pev->point.retprobe, &vl->point); in add_available_vars()
1294 pr_debug("Probe point found: %s+%lu\n", vl->point.symbol, in add_available_vars()
[all …]
/linux-4.1.27/Documentation/arm/nwfpe/
DREADME.FPE1 The following describes the current state of the NetWinder's floating point
4 In the following nomenclature is used to describe the floating point
35 for each floating point register into the memory location given in the
45 FLT{cond}<S,D,E>{P,M,Z} Fn, Rd Convert integer to floating point
46 FIX{cond}{P,M,Z} Rd, Fn Convert floating point to integer
47 WFS{cond} Rd Write floating point status register
48 RFS{cond} Rd Read floating point status register
49 WFC{cond} Rd Write floating point control register
50 RFC{cond} Rd Read floating point control register
137 hardware, but are handled by the floating point support code. They should
[all …]
DREADME7 working version of all the floating point instructions the compiler
22 The floating point operations are based on SoftFloat Release 2, by
23 John Hauser. SoftFloat is a software implementation of floating-point
24 that conforms to the IEC/IEEE Standard for Binary Floating-point
62 a fixed-point vector processor in collaboration with the University of
DTODO20 hardware, but are handled by the floating point support code. They should
55 [NOTE: pulled out from some docs on ARM floating point, specifically
58 The floating point control register (FPCR) may only be present in some
60 specific manner, for example to disable the floating point system. The user
DNOTES6 will point it out. The ARM calling conventions require floating point
/linux-4.1.27/arch/mn10300/mm/
Dtlb-mn10300.S25 # Instruction TLB Miss handler entry point
62 beq itlb_miss_fault # jump if doesn't point to a page
88 # Data TLB Miss handler entry point
125 beq dtlb_miss_fault # jump if doesn't point to a page
150 # Instruction TLB Address Error handler entry point
/linux-4.1.27/arch/xtensa/lib/
Dstrnlen_user.S109 # NOTE that in several places below, we point to the byte just after
113 addi a4, a4, 3 # point to zero byte
115 addi a4, a4, 1 # point just beyond zero byte
119 addi a4, a4, 1+1 # point just beyond zero byte
123 addi a4, a4, 2+1 # point just beyond zero byte
139 addi a4, a4, 3+1 # point just beyond zero byte
/linux-4.1.27/drivers/video/fbdev/
Dtridentfb.c181 #define point(x, y) ((y) << 16 | (x)) macro
213 writemmr(par, DST1, point(x, y)); in blade_fill_rect()
214 writemmr(par, DST2, point(x + w - 1, y + h - 1)); in blade_fill_rect()
226 writemmr(par, DST1, point(x, y)); in blade_image_blit()
227 writemmr(par, DST2, point(x + w - 1, y + h - 1)); in blade_image_blit()
236 u32 s1 = point(x1, y1); in blade_copy_rect()
237 u32 s2 = point(x1 + w - 1, y1 + h - 1); in blade_copy_rect()
238 u32 d1 = point(x2, y2); in blade_copy_rect()
239 u32 d2 = point(x2 + w - 1, y2 + h - 1); in blade_copy_rect()
314 writemmr(par, OLDDIM, point(h, w)); in xp_fill_rect()
[all …]
/linux-4.1.27/Documentation/fault-injection/
Dprovoke-crashes.txt16 cpoint_name : Crash point where the kernel is to be crashed. It can be
21 cpoint_type : Indicates the action to be taken on hitting the crash point.
26 cpoint_count : Indicates the number of times the crash point is to be hit
/linux-4.1.27/drivers/hwmon/
Df71882fg.c98 #define F71882FG_REG_POINT_PWM(pwm, point) (0xAA + (point) + (16 * (pwm))) argument
99 #define F71882FG_REG_POINT_TEMP(pwm, point) (0xA6 + (point) + (16 * (pwm))) argument
1165 int nr, reg, point; in f71882fg_update_device() local
1224 for (point = 0; point < 5; point++) { in f71882fg_update_device()
1225 data->pwm_auto_point_pwm[nr][point] = in f71882fg_update_device()
1228 (nr, point)); in f71882fg_update_device()
1230 for (point = 0; point < 4; point++) { in f71882fg_update_device()
1231 data->pwm_auto_point_temp[nr][point] = in f71882fg_update_device()
1234 (nr, point)); in f71882fg_update_device()
1905 int point = to_sensor_dev_attr_2(devattr)->nr; in show_pwm_auto_point_pwm() local
[all …]
Dit87.c1197 int point = sensor_attr->index; in show_auto_pwm() local
1200 pwm_from_reg(data, data->auto_pwm[nr][point])); in show_auto_pwm()
1210 int point = sensor_attr->index; in set_auto_pwm() local
1217 data->auto_pwm[nr][point] = pwm_to_reg(data, val); in set_auto_pwm()
1218 it87_write_value(data, IT87_REG_AUTO_PWM(nr, point), in set_auto_pwm()
1219 data->auto_pwm[nr][point]); in set_auto_pwm()
1231 int point = sensor_attr->index; in show_auto_temp() local
1233 return sprintf(buf, "%d\n", TEMP_FROM_REG(data->auto_temp[nr][point])); in show_auto_temp()
1243 int point = sensor_attr->index; in set_auto_temp() local
1250 data->auto_temp[nr][point] = TEMP_TO_REG(val); in set_auto_temp()
[all …]
Dnct6775.c2786 int point = sattr->index; in store_auto_pwm() local
2797 if (point == data->auto_pwm_num) { in store_auto_pwm()
2805 data->auto_pwm[nr][point] = val; in store_auto_pwm()
2806 if (point < data->auto_pwm_num) { in store_auto_pwm()
2808 NCT6775_AUTO_PWM(data, nr, point), in store_auto_pwm()
2809 data->auto_pwm[nr][point]); in store_auto_pwm()
2853 int point = sattr->index; in show_auto_temp() local
2859 return sprintf(buf, "%d\n", data->auto_temp[nr][point] * 1000); in show_auto_temp()
2869 int point = sattr->index; in store_auto_temp() local
2880 data->auto_temp[nr][point] = DIV_ROUND_CLOSEST(val, 1000); in store_auto_temp()
[all …]
/linux-4.1.27/Documentation/devicetree/bindings/arm/msm/
Dssbi.txt3 Some Qualcomm MSM devices contain a point-to-point serial bus used to
/linux-4.1.27/net/irda/irnet/
DKconfig11 uses synchronous PPP over a set of point to point IrDA sockets. You
/linux-4.1.27/net/x25/
DKconfig10 entry point can carry several logical point-to-point connections
/linux-4.1.27/Documentation/networking/mac80211_hwsim/
DREADME16 point, mac80211_hwsim is yet another hardware driver, i.e., no changes
30 point and a station) or large scale tests (multiple access points with
48 one to act as an access point and the other as a station that
51 processing access point side of association.
/linux-4.1.27/arch/x86/kvm/
Dmmu_audit.c235 static void __kvm_mmu_audit(struct kvm_vcpu *vcpu, int point) in __kvm_mmu_audit() argument
242 vcpu->kvm->arch.audit_point = point; in __kvm_mmu_audit()
247 static inline void kvm_mmu_audit(struct kvm_vcpu *vcpu, int point) in kvm_mmu_audit() argument
250 __kvm_mmu_audit(vcpu, point); in kvm_mmu_audit()
/linux-4.1.27/Documentation/filesystems/
Dautofs4-mount-control.txt25 because the point from which the path is constructed has been detached
66 top of this mount point". Since these are always directories we can
106 on the mount point for control operations. The references held by the
140 point dentry (covered or not) has also been added.
188 The ioctlfd field is a mount point file descriptor of an autofs mount
189 point. It is returned by the open call and is used by all calls except
190 the check for whether a given path is a mount point, where it may
192 mount point file descriptor, and when requesting the uid and gid of the
216 not a valid descriptor or doesn't correspond to an autofs mount point
247 with the ioctlfd field set to a valid autofs mount point descriptor
[all …]
Dspufs.txt26 set the user owning the mount point, the default is 0 (root).
29 set the group owning the mount point, the default is 0 (root).
311 event can be a NULL pointer or point to an extended status code that
422 point to a non-existing directory in the mount point of the SPU file
457 point.
464 EINVAL pathname is not a directory in the spufs mount point.
500 pathname must point to a location beneath the mount point of spufs. By
Dpath-lookup.txt49 the path given by the name's starting point (which we know in advance -- eg.
62 refer to), switching from the mount point path to the root of the particular
67 - find the start point of the walk;
92 point to perform the next step of our path walk against.
113 However, when the dentry's list pointers are updated to point to objects in the
267 +---------------------+ At this point we have our destination dentry.
284 When we reach a point where sleeping is required, or a filesystem callout
332 The point is that shared data, where practically possible, is not locked
Dsysfs-tagging.txt24 point to the namespace to which it belongs.
Decryptfs.txt39 files (i.e., /root/crypt). Then, create the mount point directory
Dxfs-delayed-logging-design.txt80 that can be made to the filesystem at any point in time - if all the log
106 From a conceptual point of view, XFS is already doing relogging in memory (where
126 written to the log at any point in time, there may be a much greater amount
179 simply copies the memory these vectors point to into the log buffer during
185 point to the memory buffer rather than the object itself, we now have a copy of
237 rewriting the vector addresses to point at the memory buffer we end up with a
248 them so that they can be written to the log at some later point in time. The
546 up front. This avoids deadlocks and removes a blocking point from the
562 manner that is done for the existing logging method. A discussion point is
653 The second serialisation point is on the transaction commit side where items
[all …]
/linux-4.1.27/arch/arm/vfp/
Dentry.S18 @ VFP entry point.
32 ldr pc, [r4] @ call VFP entry point
/linux-4.1.27/arch/mn10300/kernel/
Dmn10300-watchdog-low.S25 # Watchdog handler entry point
48 # Watchdog touch entry point
Dmn10300-serial-low.S36 # serial port interrupt virtual DMA entry point
59 # serial port receive interrupt virtual DMA entry point
106 # serial port transmit interrupt virtual DMA entry point
Dprofile-low.S29 # Profiling interrupt entry point
Dgdb-io-serial-low.S28 # GDB stub serial receive interrupt entry point
Dgdb-io-ttysm-low.S28 # GDB stub serial receive interrupt entry point
/linux-4.1.27/drivers/s390/net/
DKconfig20 point-to-point networking on IBM System z.
36 link between VM guests. Using ifconfig a point-to-point connection
/linux-4.1.27/drivers/thermal/
DKconfig93 Say 'Y' here if you want to use two point temperature regulation
146 It supports one critical trip point and one passive trip point. The
165 trip point. Cpufreq is used as the cooling device and will throttle
166 CPUs when the Temperature crosses the passive trip point.
227 bound to thermal zone trip points. When a trip point reached, the
259 thermal zone. There are two trip points. One of the trip point can
261 notification methods.The other trip is a critical trip point, which
/linux-4.1.27/Documentation/devicetree/bindings/input/
Dimx-keypad.txt3 The KPP is designed to interface with a keypad matrix with 2-point contact
4 or 3-point contact keys. The KPP is designed to simplify the software task
/linux-4.1.27/net/bluetooth/
Decc.c539 static bool ecc_point_is_zero(const struct ecc_point *point) in ecc_point_is_zero() argument
541 return (vli_is_zero(point->x) && vli_is_zero(point->y)); in ecc_point_is_zero()
690 const struct ecc_point *point, u64 *scalar, in ecc_point_mult() argument
699 vli_set(rx[1], point->x); in ecc_point_mult()
700 vli_set(ry[1], point->y); in ecc_point_mult()
716 vli_mod_mult_fast(z, z, point->x); /* xP * Yb * (X1 - X0) */ in ecc_point_mult()
718 vli_mod_mult_fast(z, z, point->y); /* yP / (xP * Yb * (X1 - X0)) */ in ecc_point_mult()
/linux-4.1.27/Documentation/ABI/stable/
Dvdso13 entry point. The AT_SYSINFO_EHDR entry will point to the vDSO.
Dsysfs-devices-system-xen_memory38 'max_schedule_delay' is reached at which point it
/linux-4.1.27/drivers/net/hippi/
DKconfig10 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
/linux-4.1.27/arch/mn10300/boot/compressed/
Dhead.S26 # Secondary CPUs jump directly to the kernel entry point
/linux-4.1.27/Documentation/networking/
Dppp_generic.txt108 to the user-level process. From that point, the PPP negotiation code
162 point the packets can no longer be reordered, as the decompression
254 to point to a separate object for each open instance of /dev/ppp. In
287 instance the "owner" of the interface. The argument should point to
294 The argument should point to an int containing the unit number.
298 The argument should point to an int containing the channel number.
310 argument should point to an int containing the interface unit
325 The argument should point to an int containing the new MRU value.
351 interface unit. The argument should point to an int where the ioctl
360 decompression. The argument should point to a ppp_option_data
[all …]
Dvxlan.txt14 Unlike most tunnels, a VXLAN is a 1 to N network, not just point
15 to point. A VXLAN device can either dynamically learn the IP address
Dframerelay.txt7 Each DLCI is a point-to-point link between your machine and a remote one.
DPLIP.txt6 At some point T. Thorn will probably contribute text,
13 This device interface allows a point-to-point connection between two
Dspider_net.txt69 pointer, at which point the OS will notice that the head descr is
132 which, from the OS point of view, is empty; the OS will be waiting for
139 A call to show_rx_chain() at this point indicates the nature of the
155 marked xa... which is "empty". Thus, from the OS point of view, there
Dfib_trie.txt136 At this point we backtrack (t->stats.backtrack++) up the trie, continuing to
139 At this point we will repeatedly descend subtries to look for a match, and there
/linux-4.1.27/arch/arm/mach-rpc/include/mach/
Dentry-macro.S8 mov \base, #ioc_base_high @ point at IOC
/linux-4.1.27/tools/perf/Documentation/
Dperf-probe.txt77 Show available local variables at given probe point. The argument
140 …attern (see LAZY MATCHING). Note that ';PTN' must be the end of the probe point definition. In ad…
141 It is also possible to specify a probe point by the source line number or lazy matching by using 'S…
142 'ARG' specifies the arguments of this probe point, (see PROBE ARGUMENT).
151 …so available for NAME, it is expanded to the local variables which can access at given probe point.
177 This provides some sort of flexibility and robustness to probe point definitions against minor code…
Dperf-inject.txt16 point the processing code can inject other events into the event stream - in
/linux-4.1.27/Documentation/devicetree/bindings/video/
Dsimple-framebuffer.txt19 "display" property then the /aliases/display# path must point to the display
20 hw node the "display" property points to, otherwise it must point directly
24 then the chosen node's stdout-path property should point to it, or to the
/linux-4.1.27/arch/s390/kernel/
Dbase.S88 larl %r4,.Lfpctl # Floating point control register
107 larl %r4,.Lfpctl # Restore floating point ctl register
/linux-4.1.27/net/xfrm/
DKconfig40 where mobile nodes change their attachment point to the Internet.
80 change their attachment point to the Internet. Detail
/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/Documentation/x86/
Dboot.txt58 protocol entry point.
82 | Boot loader | <- Boot sector entry point 0000:7C00
99 It is desirable to keep the "memory ceiling" -- the highest point in
112 above the 0x9A000 point; too many BIOSes will break above that point.
131 | Boot loader | <- Boot sector entry point 0000:7C00
199 0264/4 2.11+ handover_offset Offset of handover entry point
424 - If 0, reload the segment registers in the 32bit entry point.
425 - If 1, do not reload the segment registers in the 32bit entry point.
465 this field to point to the load address.
538 command line, in which case you can point this to an empty string
[all …]
Dintel_mpx.txt53 this point, a bounds fault (#BR) is raised, the kernel allocates a
55 in the bounds directory point to the new table.
81 updates the bounds directory to point to the new table. It keeps
232 Certainly users can allocate bounds tables and forcibly point the bounds
237 2) Userspace may not take multiple bounds directory entries and point
Dentry_64.txt28 explicitly point somewhere else gets set to the corresponding
29 value in interrupts. These point to a whole array of
/linux-4.1.27/arch/m68k/
DKconfig.cpu301 At some point in the future, this will cause floating-point math
303 floating-point math coprocessor. Thrill-seekers and chronically
322 This option prevents any floating-point instructions from being
324 floating point context anymore during task switches, so this
325 kernel will only be usable on machines without a floating-point
327 needs to be executed whether a floating-point instruction in the
/linux-4.1.27/drivers/net/wireless/p54/
Deeprom.c287 for (j = 0; j < ARRAY_SIZE(pda->point); j++) { in p54_get_maxpower()
288 struct pda_channel_output_limit_point_longbow *point = in p54_get_maxpower() local
289 &pda->point[j]; in p54_get_maxpower()
291 rawpower, le16_to_cpu(point->val_qpsk)); in p54_get_maxpower()
293 rawpower, le16_to_cpu(point->val_bpsk)); in p54_get_maxpower()
295 rawpower, le16_to_cpu(point->val_16qam)); in p54_get_maxpower()
297 rawpower, le16_to_cpu(point->val_64qam)); in p54_get_maxpower()
Deeprom.h69 struct pda_channel_output_limit_point_longbow point[3]; member
/linux-4.1.27/Documentation/serial/
Dtty.txt15 discipline number and the ldisc structure. At the point of registration the
49 discipline is being unplugged. At the point of
62 flush_buffer() - (optional) May be called at any point between
97 write_wakeup() - May be called at any point between open and close.
217 point then NULL is returned. While this handle is held the ldisc will not
246 close() - Called when a device is closed. At the point of
271 set_ldisc() - Notifier for discipline change. At the point this
/linux-4.1.27/fs/dlm/
DKconfig14 Under the debugfs mount point, the name of each lockspace will
/linux-4.1.27/arch/arm/kvm/
Dinit.S74 @ Set the HTTBR to point to the hypervisor PGD pointer passed
135 @ Set HVBAR to point to the HYP vectors
/linux-4.1.27/Documentation/isdn/
DREADME.diversion81 used on a point-to-point connection. Further the static services are only
87 point-to-point lines.
DREADME.sc165 problems, but the board would not respond beyond that point. When a check was
203 a specific IP address and point to point address
256 specific IP address and point to point address
/linux-4.1.27/Documentation/ABI/testing/
Dsysfs-devices-power_resources_D013 point to.
Dsysfs-devices-power_resources_wakeup13 point to.
Dsysfs-devices-power_resources_D3hot14 they point to.
Dsysfs-bus-i2c-devices-hm63526 point value in degrees.
Dsysfs-devices-power_resources_D114 point to.
Dsysfs-devices-power_resources_D214 point to.
Dsysfs-dev9 the form "<major>:<minor>". These links point to the
Dsysfs-bus-event_source-devices-events84 A string representing a floating point value expressed in
93 This is provided to avoid performing floating point arithmetic
Dsysfs-devices14 on the symlinks there to point to the proper location
Dsysfs-power102 last PM event point in the RTC across reboots, so that you can
105 the last PM event point if this file contains '1'. Initially
115 positives), it is possible that the last PM event point
128 device associated with the last PM event point saved in the RTC
Dsysfs-firmware-gsmi9 historical reasons this different entry-point has been
/linux-4.1.27/drivers/uwb/
DKconfig9 UWB is a high-bandwidth, low-power, point-to-point radio
/linux-4.1.27/Documentation/arm/
Dmem_alignment19 floating point emulation that works about the same way). Fix your code
39 slow (think about the floating point emulator) and
D00-INDEX44 - NWFPE floating point emulator documentation
/linux-4.1.27/Documentation/scsi/
Dufs.txt72 * UDM_SAP: Device manager service access point is exposed to device
75 * UTP_CMD_SAP: Command service access point is exposed to UFS command
77 * UTP_TM_SAP: Task management service access point is exposed to task
Dlibsas.txt37 start OOB (at which point your driver will start calling the
90 this pointer point to it. You copy the frame from your
103 lldd_phy -- you should set this to point to your phy so you
200 lldd_ha -- set this to point to your HA struct. You can also
/linux-4.1.27/Documentation/PCI/
Dpci-error-recovery.txt127 At this point, the device might not be accessible anymore, depending on
130 is the proper "synchronization point", that is, it gives the driver
135 "quiesce" point. See note about interrupts at the end of this doc.
174 >>> attempts I/O at this point, or not. I/O's will fail, returning
243 at this point. It should limit itself to "probing" the device to
292 (re-download firmware, etc.). At this point, the driver may assume
299 at this point. If all device drivers report success on this
350 At this point, if a new error happens, the platform will restart
359 The device driver should, at this point, assume the worst. It should
392 slot_reset callback is called, at which point interrupts are expected
/linux-4.1.27/Documentation/devicetree/bindings/rtc/
Datmel,at91sam9-rtc.txt10 The first cell should point to the GPBR node and the second one
/linux-4.1.27/drivers/power/avs/
DKconfig7 At a given operating point the voltage is adapted depending on
/linux-4.1.27/Documentation/hwmon/
Dadt741034 INT pin to indicate that a minimum or maximum temperature set point has been
36 critical temperature set point has been exceeded. Both pins can be set up with a
Dit87237 The PWM output of trip point 4 is always the maximum value (fan running
240 Additionally, trip point 1 has an hysteresis temperature attached, to
245 between trip point N and trip point N+1 then the PWM output value is
246 the one of trip point N. The automatic control mode is less flexible
/linux-4.1.27/Documentation/devicetree/bindings/phy/
Dapm-xgene-phy.txt23 data earlier than the nominal sampling point. 1 means
24 sample data later than the nominal sampling point.
/linux-4.1.27/drivers/net/wan/
DKconfig322 point to the Frame Relay network, usually at the phone company) can
323 carry several logical point-to-point connections to other computers
339 How many logical point-to-point frame relay connections (the
365 you to open an LAPB point-to-point connection to some other computer
/linux-4.1.27/arch/frv/kernel/
Dswitch_to.S116 # - GR8 will point to the outgoing task_struct
117 # - GR9 will point to the incoming thread_struct
137 # - GR8 will point to the user context to swap in
Dhead.S27 # - if magic is 0xdead1eaf, then command_line is assumed to point to the kernel
439 # point the TBR at the kernel trap table
539 # provide a point for GDB to place a break
/linux-4.1.27/Documentation/dvb/
Dttusb-dec.txt41 For 2.6 kernels the firmware is loaded at the point that the driver module is
/linux-4.1.27/Documentation/usb/
Dfunctionfs.txt3 From kernel point of view it is just a composite function with some
13 From user space point of view it is a file system which when
Dmtouchusb.txt52 Perhaps at some point an abstract function will be placed into evdev so
/linux-4.1.27/arch/mips/kernel/
Dhead.S85 NESTED(kernel_entry, 16, sp) # kernel entry point
/linux-4.1.27/Documentation/devicetree/
Dbooting-without-of.txt15 1) Entry point for arch/arm
16 2) Entry point for arch/powerpc
17 3) Entry point for arch/x86
18 4) Entry point for arch/mips/bmips
128 point and the way a new platform should be added to the kernel. The
155 1) Entry point for arch/arm
158 There is one single entry point to the kernel, at the start
159 of the kernel image. That entry point supports two calling
194 2) Entry point for arch/powerpc
197 There is one single entry point to the kernel, at the start
[all …]
Dchangesets.txt20 a set of changes. No changes to the active tree are made at this point.
/linux-4.1.27/drivers/bcma/
DREADME2 however from programming point of view there is nothing AMBA specific we use.
/linux-4.1.27/net/bridge/netfilter/
Debtables.c191 struct ebt_entry *point; in ebt_do_table() local
217 point = (struct ebt_entry *)(private->hook_entry[hook]->data); in ebt_do_table()
223 if (ebt_basic_match(point, skb, in, out)) in ebt_do_table()
226 if (EBT_MATCH_ITERATE(point, ebt_do_match, skb, &acpar) != 0) in ebt_do_table()
239 EBT_WATCHER_ITERATE(point, ebt_do_watcher, skb, &acpar); in ebt_do_table()
242 (((char *)point) + point->target_offset); in ebt_do_table()
273 point = cs[sp].e; in ebt_do_table()
290 cs[sp].e = ebt_next_entry(point); in ebt_do_table()
301 point = (struct ebt_entry *)chaininfo->data; in ebt_do_table()
306 point = ebt_next_entry(point); in ebt_do_table()
/linux-4.1.27/arch/x86/boot/
Dheader.S290 # offset 512, entry point
481 2: # Now %dx should point to the end of our stack space
/linux-4.1.27/Documentation/acpi/apei/
Doutput_format.txt101 <pcie port type string>* := PCIe end point | legacy PCI end point | \
/linux-4.1.27/arch/arm/common/
Dmcpm_head.S98 @ At this point, the cluster cannot unexpectedly enter the GOING_DOWN
128 @ point onwards will observe INBOUND_COMING_UP and abort.
/linux-4.1.27/Documentation/power/
Dinterface.txt62 /sys/power/pm_trace controls the code which saves the last PM event point in
65 used to save the last PM event point if this file contains '1'. Initially it
/linux-4.1.27/arch/um/
DKconfig.net33 Ethernet network, it's in fact communicating over a point-to-point
68 network with its host over a point-to-point link. Unlike Ethertap,
/linux-4.1.27/Documentation/
Dsvga.txt125 0x0f01 standard with 8-point font: 80x43 on EGA, 80x50 on VGA
126 0x0f02 VGA 80x43 (VGA switched to 350 scanlines with a 8-point font)
127 0x0f03 VGA 80x28 (standard VGA scans, but 14-point font)
129 0x0f05 VGA 80x30 (480 scans, 16-point font)
130 0x0f06 VGA 80x34 (480 scans, 14-point font)
131 0x0f07 VGA 80x60 (480 scans, 8-point font)
DSubmittingDrivers43 to track changes in API's. The final contact point for Linux 2.6
77 endian, people do not all have floating point and you
107 If you want to be the contact and update point for the
Dpadata.txt8 those packets. The crypto developers made a point of writing padata in a
136 parallel() will take responsibility for the task from this point. The work
145 At some point in the future, padata_do_serial() will trigger a call to the
Dnommu-mmap.txt6 as are used in uClinux environments. From the userspace point of view, memory
8 call and the execve() system call. From the kernel's point of view, execve()
62 question get copied before the write actually happens. From that point
222 mapping. It can be rejected at that point. Returning the ENOSYS error will
Drobust-futex-ABI.txt55 as described below. If the list is empty, the pointer will point
122 memory, on various data structures, at a given point in time. Only those
168 any point:
Dmedia-framework.txt35 A link is a point-to-point oriented connection between two pads, either
55 - dev must point to the parent device (usually a pci_dev, usb_interface or
232 /* entity will point to each entity in turn */
/linux-4.1.27/Documentation/devicetree/bindings/leds/
Dleds-pwm.txt10 - pwms : PWM property to point to the PWM device (phandle)/port (id) and to
/linux-4.1.27/Documentation/i2c/busses/
Di2c-ocores20 dev.platform_data of the device should also point to a struct
/linux-4.1.27/arch/alpha/
DKconfig.debug38 This option is required for IEEE compliant floating point arithmetic
/linux-4.1.27/arch/x86/platform/olpc/
Dxo1-wakeup.S54 # Go back to the return point
/linux-4.1.27/arch/arm/kernel/
Dhyp-stub.S194 * initialisation entry point.
/linux-4.1.27/Documentation/driver-model/
Dplatform.txt186 at this point will later on be matched against early platform drivers.
192 User specified early platform devices will be registered at this point.
219 This step can be executed at any point during the early boot. As soon
228 time. The early serial driver performs register_console() at this point.
/linux-4.1.27/Documentation/namespaces/
Dcompatibility-list.txt29 should not be equal from the VFS point of view. In other
/linux-4.1.27/drivers/staging/lustre/lustre/llite/
Drw.c380 static int index_in_window(unsigned long index, unsigned long point, in index_in_window() argument
383 unsigned long start = point - before, end = point + after; in index_in_window()
385 if (start > point) in index_in_window()
387 if (end < point) in index_in_window()
/linux-4.1.27/block/
DKconfig.iosched21 a new point in the service tree and doing a batch of IO from there
/linux-4.1.27/Documentation/filesystems/nfs/
Dnfsd-admin-interfaces.txt27 are thrown away at that point.
/linux-4.1.27/arch/sh/kernel/cpu/sh2a/
Dentry.S40 ! r0 <- point sp
218 mov.l r2,@(OFF_SP,r0) ! point exception frame top
/linux-4.1.27/Documentation/locking/
Dlockstat.txt61 It also tracks 4 contention points per class. A contention point is a call site
127 con-bounces point is missing in the statistics.
Dww-mutex-design.txt63 From a simple semantics point-of-view the _slow functions are not strictly
184 * Move buf to head of the list, this will point
214 a graph from a starting point and then iteratively discovering new edges and
219 as a starting point).
/linux-4.1.27/Documentation/filesystems/caching/
Dobject.txt98 object->state. A cookie may point to a set of objects that are in different
174 Look up the object on disk, using the parent as a starting point.
186 the first known page is uncached - as to that point there can be no data
192 Create an object on disk, using the parent as a starting point. This
/linux-4.1.27/tools/thermal/tmon/
DREADME16 links, trip point bindings, and device instances. To traverse such
/linux-4.1.27/Documentation/development-process/
D6.Followthrough3 At this point, you have followed the guidelines given so far and, with the
65 be easy to become blinded by your own solution to a problem to the point
118 contents visible to the development community as a whole. At this point,
122 What may also happen at this point, depending on the nature of your patch,
199 developer posts a different solution to your problem. At that point,
/linux-4.1.27/Documentation/metag/
Dkernel-ABI.txt167 should always point to the next free address on the stack and should at all
168 times be 64-bit aligned. The following registers are effective at the point of a
217 At this point the stack would look like this:
/linux-4.1.27/Documentation/fmc/
Didentifiers.txt108 The SDB entry point (which acts as a directory listing) cannot live at
116 the sdb entry point, and you must force the FRU data file to be placed
123 example that you may want to use as a starting point (the comments are
DAPI.txt45 entry point. The function is meant to factorize common code, and by
/linux-4.1.27/Documentation/powerpc/
Dtransactional_memory.txt45 The 'tbegin' instruction denotes the start point, and 'tend' the end point.
108 represents the active transactional registers at the point of the signal.
/linux-4.1.27/Documentation/devicetree/bindings/input/touchscreen/
Dbrcm,iproc-touchscreen.txt34 data point is placed into the FIFO
/linux-4.1.27/Documentation/parisc/
Ddebugging36 where exactly it happened. If you're lucky the IAOQ will point to the
/linux-4.1.27/scripts/coccinelle/iterators/
Dfen.cocci2 /// is no point to call of_node_put on the final value.
/linux-4.1.27/Documentation/crypto/
Dasymmetric-keys.txt189 Asymmetric keys point to this with their type_data[0] member.
287 point to the subtype to be used, ->payload should be set to point to the
288 initialised data for that subtype, ->type_data[1] should point to a hex
/linux-4.1.27/Documentation/devicetree/bindings/sound/
Dcs42l56.txt45 …- cirrus,hpf-left-freq, hpf-right-freq : Sets the corner frequency (-3dB point) for the internal H…
/linux-4.1.27/fs/pstore/
DKconfig57 buffer in RAM where it can be read back at some later point.
/linux-4.1.27/Documentation/arm/OMAP/
Domap_pm69 files to point to the corresponding OMAP PM functions:
70 .set_max_dev_wakeup_lat will point to
/linux-4.1.27/net/ax25/
DKconfig26 radio. It is either used by itself for point-to-point links, or to
/linux-4.1.27/Documentation/device-mapper/
Dlog-writes.txt35 cases where a power failure at a particular point in time would create an
85 then replay from that point on doing the fsck check in the
/linux-4.1.27/arch/cris/arch-v32/kernel/
Dentry.S265 ;; R0 contains current at this point and irq's are disabled.
298 ;; PT_r10 in the frame contains -ENOSYS as required, at this point.
488 di ; Need to disable irq's at this point.
/linux-4.1.27/arch/arc/kernel/
Dentry.S613 ; for single exit point from this block
617 ; Disable Interrupts from this point on
742 jl.d [r14] ; kernel thread entry point
/linux-4.1.27/Documentation/virtual/kvm/
Dmmu.txt115 Leaf ptes point at guest pages.
184 sptes in spt point either at guest pages, or at lower-level shadow pages.
185 Specifically, if sp1 and sp2 are shadow pages, then sp1->spt[n] may point
186 at __pa(sp2->spt). sp2 will point back at sp1 through parent_pte.
211 How many sptes in the page point at pages that are unsync (or have
214 A bitmap indicating which sptes in spt point (directly or indirectly) at
382 - the spte must point to a large host page
/linux-4.1.27/arch/metag/lib/
Dmemset.S61 ! D1Ar1 should point to the location required
/linux-4.1.27/Documentation/sound/oss/
DVIBRA1613 A good starting point is that the vibra16x chip full-duplex facility
/linux-4.1.27/kernel/
DKconfig.preempt46 otherwise not be about to reach a natural preemption point.
/linux-4.1.27/Documentation/input/
Dgameport-programming.txt105 the gameport struct to point to your data.
154 If the gameport supports cooked mode, it should point this to its cooked
/linux-4.1.27/Documentation/nfc/
Dnfc-hci.txt18 routed through netlink sockets to NFC Core and then to HCI. From this point,
88 - hci_ready() is an optional entry point that is called right after the hci
101 - complete_target_discovered() is an optional entry point to let the driver
111 - check_presence() is an optional entry point that will be called regularly
/linux-4.1.27/Documentation/netlabel/
Dcipso_ipv4.txt20 CIPSO label can be changed at any point in time, however, it is recommended
/linux-4.1.27/arch/cris/boot/rescue/
Dkimagerescue.S46 ;; This is the entry point of the rescue code
/linux-4.1.27/arch/alpha/lib/
Dmemchr.S120 # Make $18 point to last quad to be accessed (the
/linux-4.1.27/arch/sh/
DKconfig.cpu30 bool "Flush floating point denorms to zero"
/linux-4.1.27/kernel/power/
DKconfig196 This enables code to save the last PM event point across
214 This enables some cheesy code to save the last PM event point in the
247 much point in using this driver and you should say N. If you get
/linux-4.1.27/arch/sh/kernel/cpu/sh2/
Dentry.S40 ! r0 <- point sp
272 mov.l r2,@(OFF_SP,r0) ! point exception frame top
/linux-4.1.27/Documentation/ABI/obsolete/
Dsysfs-driver-hid-roccat-koneplus19 number the decimal point has to be shifted 2 positions to the
/linux-4.1.27/arch/powerpc/kernel/vdso64/
Dsigtramp.S301 # Do we really need to describe the frame at this point? ie. will
/linux-4.1.27/arch/mips/include/asm/mach-cavium-octeon/
Dkernel-entry-init.h124 # Jump to the normal Linux SMP entry point
/linux-4.1.27/Documentation/scheduler/
Dsched-arch.txt72 sparc - IRQs on at this point(?), change local_irq_save to _disable.

123