Home
last modified time | relevance | path

Searched full:s (Results 1 – 25 of 2341) sorted by relevance

12345678910>>...94

/Documentation/sphinx/
Dparse-headers.pl45 $ln =~ s,/\*.*(\*/),,g;
47 $is_comment = 1 if ($ln =~ s,/\*.*,,);
49 if ($ln =~ s,^(.*\*/),,) {
56 if ($is_enum && $ln =~ m/^\s*([_\w][\w\d_]+)\s*[\,=]?/) {
57 my $s = $1;
62 $enum_symbols{$s} = "\\ :ref:`$s <$n>`\\ ";
69 if ($ln =~ m/^\s*#\s*define\s+([_\w][\w\d_]+)\s+_IO/) {
70 my $s = $1;
74 $ioctls{$s} = "\\ :ref:`$s <$n>`\\ ";
78 if ($ln =~ m/^\s*#\s*define\s+([_\w][\w\d_]+)\s+/) {
[all …]
Dmaintainers_include.py16 specific to the Linux kernel's standard "MAINTAINERS" file, in an
50 # Poor man's state machine.
80 pat = r'(Documentation/([^\s\?\*]*)\.rst)'
84 line = re.sub(pat, ':doc:`%s <../%s>`' % (m.group(2), m.group(2)), line)
90 output = "| %s" % (line.replace("\\", "\\\\"))
93 m = re.search(r"\s(\S):\s", line)
115 heading = re.sub(r"\s+", " ", line)
116 output = output + "%s\n%s" % (heading, "~" * len(heading))
130 details = '``%s``' % (details)
140 field_content = ":%s:" % (fields.get(field, field))
[all …]
/Documentation/driver-api/mtd/
Dspi-nor.rst14 flash's parameters and settings. If the flash defines the SFDP tables
15 it's likely that you won't need a flash entry at all, and instead
30 Do all the tests from below and paste them in the commit's comments
81 1S-1S-1S
85 1S-1S-1S (fast read)
89 1S-1S-2S
93 1S-2S-2S
97 1S-1S-4S
101 1S-4S-4S
105 4S-4S-4S
[all …]
/Documentation/filesystems/
Didmappings.rst26 To see what this looks like in practice, let's take the following idmapping::
137 permission checks and are stored in an inode's ``i_uid`` and ``i_gid`` field.
183 would be mapped to id ``k1000``. So an inode's ``i_uid`` and ``i_gid`` field
187 then ``u1000`` read from disk would be mapped to ``k11000``. So an inode's
234 Let's assume the filesystem was mounted with an idmapping of
237 the inode's ``i_uid`` and ``i_gid`` field.
241 according to the filesystem's idmapping as this would give the wrong owner if
244 So the kernel will map the id back up in the idmapping of the caller. Let's
256 Let's look at an example. We are given the following two idmappings::
348 When creating a filesystem object the caller will look at the caller's
[all …]
/Documentation/driver-api/driver-model/
Dbinding.rst26 When a new device is added, the bus's list of drivers is iterated over
37 If a match is found, the device's driver field is set to the driver
38 and the driver's probe callback is called. This gives the driver a
40 it's in a working state.
47 class, and that is set in the driver's devclass field.
50 class's register_dev callback.
57 driver's list of devices.
63 A symlink is created in the bus's 'devices' directory that points to
64 the device's directory in the physical hierarchy.
66 A symlink is created in the driver's 'devices' directory that points
[all …]
/Documentation/trace/postprocess/
Dtrace-pagealloc-postprocess.pl79 # Defaults for dynamically discovered regex's
87 my $regex_traceevent = '\s*([a-zA-Z0-9-]*)\s*(\[[0-9]*\])\s*([0-9.]*):\s*([a-zA-Z_]*):\s*(.*)';
88 my $regex_statname = '[-0-9]*\s\((.*)\).*';
89 my $regex_statppid = '[-0-9]*\s\(.*\)\s[A-Za-z]\s([0-9]*).*';
103 if ($line =~ /^print fmt:\s"(.*)",.*/) {
105 $regex =~ s/%p/\([0-9a-f]*\)/g;
106 $regex =~ s/%d/\([-0-9]*\)/g;
107 $regex =~ s/%lu/\([0-9]*\)/g;
114 foreach $tuple (split /\s/, $regex) {
119 $regex =~ s/$key=\((.*)\)/$key=$1/;
[all …]
/Documentation/arch/arm/nwfpe/
Dnetwinder-fpe.rst5 The following describes the current state of the NetWinder's floating point
13 <S|D|E> = <single|double|extended>, no default
24 <LDF|STF>{cond}<S|D|E> Fd, Rn
25 <LDF|STF>{cond}<S|D|E> Fd, [Rn, #<expression>]{!}
26 <LDF|STF>{cond}<S|D|E> Fd, [Rn], #<expression>
33 <LFM|SFM>{cond}<S|D|E> Fd, <count>, [Rn]
34 <LFM|SFM>{cond}<S|D|E> Fd, <count>, [Rn, #<expression>]{!}
35 <LFM|SFM>{cond}<S|D|E> Fd, <count>, [Rn], #<expression>
51 FLT{cond}<S,D,E>{P,M,Z} Fn, Rd Convert integer to floating point
80 ADF{cond}<S|D|E>{P,M,Z} Fd, Fn, <Fm,#value> - add
[all …]
Dtodo.rst6 POW{cond}<S|D|E>{P,M,Z} Fd, Fn, <Fm,#value> - power
7 RPW{cond}<S|D|E>{P,M,Z} Fd, Fn, <Fm,#value> - reverse power
8 POL{cond}<S|D|E>{P,M,Z} Fd, Fn, <Fm,#value> - polar angle (arctan2)
10 LOG{cond}<S|D|E>{P,M,Z} Fd, <Fm,#value> - logarithm to base 10
11 LGN{cond}<S|D|E>{P,M,Z} Fd, <Fm,#value> - logarithm to base e
12 EXP{cond}<S|D|E>{P,M,Z} Fd, <Fm,#value> - exponent
13 SIN{cond}<S|D|E>{P,M,Z} Fd, <Fm,#value> - sine
14 COS{cond}<S|D|E>{P,M,Z} Fd, <Fm,#value> - cosine
15 TAN{cond}<S|D|E>{P,M,Z} Fd, <Fm,#value> - tangent
16 ASN{cond}<S|D|E>{P,M,Z} Fd, <Fm,#value> - arcsine
[all …]
/Documentation/ABI/stable/
Dsysfs-devices-system-cpu34 Description: the CPU die ID of cpuX. Typically it is the hardware platform's
35 identifier (rather than the kernel's). The actual value is
40 Description: the CPU core ID of cpuX. Typically it is the hardware platform's
41 identifier (rather than the kernel's). The actual value is
46 Description: the cluster ID of cpuX. Typically it is the hardware platform's
47 identifier (rather than the kernel's). The actual value is
52 Description: the book ID of cpuX. Typically it is the hardware platform's
53 identifier (rather than the kernel's). The actual value is
54 architecture and platform dependent. it's only used on s390.
58 Description: the drawer ID of cpuX. Typically it is the hardware platform's
[all …]
/Documentation/userspace-api/media/v4l/
Dpixfmt-packed-hsv.rst14 The *saturation* (s) and the *value* (v) are measured in percentage of the
103 - s\ :sub:`7`
104 - s\ :sub:`6`
105 - s\ :sub:`5`
106 - s\ :sub:`4`
107 - s\ :sub:`3`
108 - s\ :sub:`2`
109 - s\ :sub:`1`
110 - s\ :sub:`0`
134 - s\ :sub:`7`
[all …]
/Documentation/filesystems/nfs/
Dlocalio.rst18 The LOCALIO auxiliary protocol's implementation, which uses the same
38 The performance advantage realized from LOCALIO's ability to bypass
43 4K read: IOPS=979k, BW=3825MiB/s (4011MB/s)(74.7GiB/20002msec)
44 4K write: IOPS=165k, BW=646MiB/s (678MB/s)(12.6GiB/20002msec)
45 128K read: IOPS=402k, BW=49.1GiB/s (52.7GB/s)(982GiB/20002msec)
46 128K write: IOPS=11.5k, BW=1433MiB/s (1503MB/s)(28.0GiB/20004msec)
49 4K read: IOPS=79.2k, BW=309MiB/s (324MB/s)(6188MiB/20003msec)
50 4K write: IOPS=59.8k, BW=234MiB/s (245MB/s)(4671MiB/20002msec)
51 128K read: IOPS=33.9k, BW=4234MiB/s (4440MB/s)(82.7GiB/20004msec)
52 128K write: IOPS=11.5k, BW=1434MiB/s (1504MB/s)(28.0GiB/20011msec)
[all …]
/Documentation/devicetree/bindings/clock/
Dmicrochip,mpfs-ccc.yaml24 - description: PLL0's control registers
25 - description: PLL1's control registers
26 - description: DLL0's control registers
27 - description: DLL1's control registers
31 The CCC PLL's have two input clocks. It is required that even if the input
35 - description: PLL0's refclk0
36 - description: PLL0's refclk1
37 - description: PLL1's refclk0
38 - description: PLL1's refclk1
39 - description: DLL0's refclk
[all …]
/Documentation/driver-api/media/drivers/ccs/
Dmk-ccs-regs16 GetOptions("ccsregs|c=s" => \$ccsregs,
17 "header|e=s" => \$header,
18 "regarray|r=s" => \$regarray,
19 "limitc|l=s" => \$limitc,
20 "limith|L=s" => \$limith,
71 $uc_header =~ s/[^A-Z0-9]/_/g;
160 $uc_limith =~ s/[^A-Z0-9]/_/g;
202 $args = [split /,\s*/, $args];
204 $t =~ s/[\(\)]//g;
205 $t =~ s/\//\\\//g;
[all …]
/Documentation/devicetree/bindings/thermal/
Dqcom-tsens.yaml127 - pattern: '^s[0-9]+_p1$'
128 - pattern: '^s[0-9]+_p2$'
129 - pattern: '^s[0-9]+_p1$'
130 - pattern: '^s[0-9]+_p2$'
131 - pattern: '^s[0-9]+_p1$'
132 - pattern: '^s[0-9]+_p2$'
133 - pattern: '^s[0-9]+_p1$'
134 - pattern: '^s[0-9]+_p2$'
135 - pattern: '^s[0-9]+_p1$'
136 - pattern: '^s[0-9]+_p2$'
[all …]
/Documentation/scheduler/
Dsched-rt-group.rst60 Let's consider an example: a frame fixed real-time renderer must deliver 25
61 frames a second, which yields a period of 0.04s per frame. Now say it will also
64 * 0.04s = 0.032s.
66 This way the graphics group will have a 0.04s period with a 0.032s run time
67 limit. Now if the audio thread needs to refill the DMA buffer every 0.005s, but
68 needs only about 3% CPU time to do so, it can do with a 0.03 * 0.005s =
69 0.00015s. So this group can be scheduled with a period of 0.005s and a run time
70 of 0.00015s.
110 The default values for sched_rt_period_us (1000000 or 1s) and
111 sched_rt_runtime_us (950000 or 0.95s). This gives 0.05s to be used by
[all …]
/Documentation/ABI/testing/
Dsysfs-kernel-mm-damon152 What: /sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/action
158 What: /sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/target_nid
161 Description: Action's target NUMA node id. Supported by only relevant
164 What: /sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/apply_interval_us
171 What: /sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/access_pattern/sz/min
175 size of the scheme's target regions in bytes.
177 What: /sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/access_pattern/sz/max
181 size of the scheme's target regions in bytes.
183 What: /sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/access_pattern/nr_accesses/…
187 'nr_accesses' of the scheme's target regions.
[all …]
Dsysfs-class-led-trigger-netdev28 If set to 0 (default), the LED's normal state is off.
30 If set to 1, the LED's normal state reflects the link state
85 If set to 0 (default), the LED's normal state is off.
87 If set to 1, the LED's normal state reflects the link state
100 If set to 0 (default), the LED's normal state is off.
102 If set to 1, the LED's normal state reflects the link state
115 If set to 0 (default), the LED's normal state is off.
117 If set to 1, the LED's normal state reflects the link state
130 If set to 0 (default), the LED's normal state is off.
132 If set to 1, the LED's normal state reflects the link state
[all …]
/Documentation/trace/
Devents-power.rst8 - Power state switch which reports events related to suspend (S-states),
54 clock_enable "%s state=%lu cpu_id=%lu"
55 clock_disable "%s state=%lu cpu_id=%lu"
56 clock_set_rate "%s state=%lu cpu_id=%lu"
67 power_domain_target "%s state=%lu cpu_id=%lu"
78 pm_qos_update_target "action=%s prev_value=%d curr_value=%d"
79 pm_qos_update_flags "action=%s prev_value=0x%x curr_value=0x%x"
88 dev_pm_qos_add_request "device=%s type=%s new_value=%d"
89 dev_pm_qos_update_request "device=%s type=%s new_value=%d"
90 dev_pm_qos_remove_request "device=%s type=%s new_value=%d"
Dfunction-graph-fold.vim3 " To use, :source this file while viewing a function_graph trace, or use vim's
4 " -S option to load from the command-line together with a trace. You can then
29 let s = split(getline(v:foldstart), '|', 1)
31 let s[2] = ' task switch '
34 let s[2] = e[2]
36 return join(s, '|')
/Documentation/staging/
Dlzo.rst2 LZO stream format as understood by Linux's LZO decompressor
133 the instruction's opcode or distance), the instruction is a copy of a
139 0 0 0 0 D D S S (0..15) : copy 2 bytes from <= 1kB distance
141 state = S (copy S literals after this block)
149 0 0 0 0 D D S S (0..15) : copy 3 bytes from 2..3 kB distance
151 state = S (copy S literals after this block)
158 Always followed by exactly one LE16 : D D D D D D D D : D D D D D D S S
160 state = S (copy S literals after this block)
175 Always followed by exactly one LE16 : D D D D D D D D : D D D D D D S S
177 state = S (copy S literals after this block)
[all …]
/Documentation/bpf/
Dllvm_reloc.rst56 Offset Info Type Symbol's Value Symbol's Name
66 The following is the symbol table with ``llvm-readelf -s test.o``::
107 ``S`` represents the value of the symbol in the symbol table::
111 1 R_BPF_64_64 ld_imm64 insn 32 r_offset + 4 S + A
112 2 R_BPF_64_ABS64 normal data 64 r_offset S + A
113 3 R_BPF_64_ABS32 normal data 32 r_offset S + A
114 4 R_BPF_64_NODYLD32 .BTF[.ext] data 32 r_offset S + A
115 10 R_BPF_64_32 call insn 32 r_offset + 4 (S + A) / 8 - 1
139 ``(S + A) / 8 - 1``.
211 Offset Info Type Symbol's Value Symbol's Name
[all …]
/Documentation/devicetree/bindings/input/touchscreen/
Dazoteq,iqs7211.yaml31 Specifies the GPIO connected to the device's active-low RDY output. The
32 pin doubles as the IQS7211E's active-low MCLR input, in which case this
38 Specifies the GPIO connected to the device's active-low MCLR input. The
52 Indicates if the device's OTP memory enables (1) or disables (0) forced
153 Specifies the device's core clock frequency as follows:
161 description: Specifies the device's core clock frequency trim.
201 Specifies the order of the CRx pin(s) associated with the trackpad.
211 Specifies the order of the CTx pin(s) associated with the trackpad.
232 description: Specifies the trackpad's ATI fine fractional divider.
238 description: Specifies the trackpad's ATI coarse fractional multiplier.
[all …]
/Documentation/admin-guide/media/
Dcx88-cardlist.rst166 - Hauppauge Nova-S-Plus DVB-S
170 - Hauppauge Nova-SE2 DVB-S
174 - KWorld DVB-S 100
226 - Geniatech DVB-S
230 - Hauppauge WinTV-HVR3000 TriMode Analog/DVB-S/DVB-T
290 - Hauppauge WinTV-HVR4000 DVB-S/S2/T/Hybrid
294 - Hauppauge WinTV-HVR4000(Lite) DVB-S/S2
298 - TeVii S460 DVB-S/S2
302 - Omicom SS4 DVB-S/S2 PCI
306 - TBS 8920 DVB-S/S2
[all …]
/Documentation/gpu/
Ddrm-vm-bind-locking.rst7 This document attempts to describe what's needed to get VM_BIND locking right,
42 of the backing store resident and making sure the gpu_vma's
58 dma_fence representing the GPU command's activity with all affected
60 it's worth mentioning that an exec function may also be the
64 single VM. Local GEM objects share the gpu_vm's dma_resv.
72 One of the benefits of VM_BIND is that local GEM objects share the gpu_vm's
79 * The ``gpu_vm->lock`` (optionally an rwsem). Protects the gpu_vm's
81 gpu_vm's list of userptr gpu_vmas. With a CPU mm analogy this would
86 userptr gpu_vma on the gpu_vm's userptr list, and in write mode during mmu
96 * The ``gpu_vm->resv`` lock. Protects the gpu_vm's list of gpu_vmas needing
[all …]
/Documentation/process/
Dembargoed-hardware-issues.rst39 S/MIME encrypted and must be signed with the reporter's PGP key or S/MIME
40 certificate. The list's PGP key and S/MIME certificate are available from
44 - S/MIME: https://www.kernel.org/static/files/hardware-security.crt
63 Linux Foundation's IT infrastructure. By providing this service, members
64 of Linux Foundation's IT operations personnel technically have the
68 kernel.org's infrastructure.
70 The Linux Foundation's current director of IT Project infrastructure is
166 that the expert is also part of the entity's response team.
235 vendor’s response team. The representative must notify the kernel
241 The silicon vendor’s response team can distribute these patches to
[all …]

12345678910>>...94