Searched full:more (Results 1 – 25 of 1698) sorted by relevance
12345678910>>...68
| /Documentation/userspace-api/media/v4l/ |
| D | tuner.rst | 13 Video input devices can have one or more tuners demodulating a RF
14 signal. Each tuner is associated with one or more video inputs,
34 current tuner, when there is more than one. The tuner is solely
38 device has one or more tuners.
44 Video output devices can have one or more modulators, that modulate a
46 set or video recorder. Each modulator is associated with one or more
68 is more than one at all. The modulator is solely determined by the
73 one or more modulators.
|
| /Documentation/devicetree/bindings/soundwire/ |
| D | qcom,sdw.txt | 57 More info in MIPI Alliance SoundWire 1.0 Specifications.
64 More info in MIPI Alliance SoundWire 1.0 Specifications.
72 More info in MIPI Alliance SoundWire 1.0 Specifications.
78 More info in MIPI Alliance SoundWire 1.0 Specifications.
87 More info in MIPI Alliance SoundWire 1.0 Specifications.
95 More info in MIPI Alliance SoundWire 1.0 Specifications.
103 More info in MIPI Alliance SoundWire 1.0 Specifications.
112 More info in MIPI Alliance SoundWire 1.0 Specifications.
121 More info in MIPI Alliance SoundWire 1.0 Specifications.
131 More info in MIPI Alliance SoundWire 1.0 Specifications.
[all …]
|
| /Documentation/ABI/stable/ |
| D | sysfs-firmware-opal-elog | 15 Linux if there is no room for more log entries.
19 the service processor needs more room for log entries,
26 The service processor may be able to store more log
34 do more parsing in kernel and add more files to make
36 more information.
|
| /Documentation/devicetree/bindings/ |
| D | graph.txt | 7 control flow to devices, but there can be more complex connections between
13 tree graph bindings described herein abstract more complex devices that can
14 have multiple specifiable ports, each of which can be linked to one or more
32 connected to this port. If a single port is connected to more than one
34 If more than one port is present in a device node or there is more than one
116 If there is more than one 'port' or more than one 'endpoint' node or 'reg'
|
| /Documentation/hwmon/ |
| D | lm83.rst | 61 like to thank here. More testers will be of course welcome.
64 Most motherboards come with more than just temperature sensors for
68 chip, which provides more features. Since systems usually need three
71 won't have to handle more than two temperatures. Thus, ADM1021 clones
88 accuracy is guaranteed to 3.0 degrees (see the datasheet for more
95 The lm83 driver will not update its values more frequently than every
96 other second; reading them more often will do no harm, but will return
|
| D | g760a.rst | 35 speed differs more than 20% with respect to the programmed fan speed;
38 The g760a driver will not update its values more frequently than every
39 other second; reading them more often will do no harm, but will return
|
| D | lm78.rst | 38 the LM78 and LM78-J are exactly identical. The LM79 has one more VID line,
47 as soon as it drops below the Hysteresis value. A more useful behavior
56 the readings more range or accuracy. Not all RPM values can accurately be
79 The LM7* only updates its values each 1.5 seconds; reading it more often
|
| /Documentation/x86/ |
| D | tlb.rst | 15 time. This could potentially cost many more instructions, but
16 it is a much more precise operation, causing no collateral
28 3. The size of the TLB. The larger the TLB, the more collateral
30 more attractive an individual flush looks. Data and
33 cache on modern CPUs, and the global flushes have become more
48 This will cause us to do the global flush for more cases.
|
| /Documentation/filesystems/ |
| D | inotify.rst | 33 An fd-per-watch quickly consumes more file descriptors than are allowed,
34 more fd's than are feasible to manage, and more fd's than are optimally
72 Additionally, it _is_ possible to more than one instance and
73 juggle more than one queue and thus more than one associated fd. There
75 process can easily want more than one queue.
|
| /Documentation/filesystems/nfs/ |
| D | knfsd-stats.rst | 49 Counts how many NFS packets have arrived. More precisely, this
56 on the wire, this may be either more or less than the number
58 However this is a more accurate and less workload-dependent measure
75 case configuring more nfsd threads will probably improve the
92 This statistic counts a circumstance where there are more nfsd
104 i.e. configure a few more nfsds than are currently needed,
119 More chapter
|
| /Documentation/process/ |
| D | 8.Conclusion.rst | 3 For more information
62 project is no more than the sum of what its contributors put into it. The
69 is always more work to do. But, just as importantly, most other
73 the direction of kernel development, and more. It is a situation where
75 more than welcome.
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-i3c | 52 length, etc. See the I3C specification for more details.
62 specification for more details.
74 See the I3C specification for more details.
85 See the I3C specification for more details about these HDR
112 length, etc. See the I3C specification for more details.
120 specification for more details.
130 See the I3C specification for more details.
140 See the I3C specification for more details about these HDR
|
| D | sysfs-driver-input-axp-pek | 5 for more than <startup_time>
11 for more than <shutdown_time>
|
| D | procfs-diskstats | 26 Kernel 4.18+ appends four more fields for discard
36 Kernel 5.5+ appends two more fields for flush requests:
43 For more details refer to Documentation/admin-guide/iostats.rst
|
| D | sysfs-driver-xen-blkfront | 8 is 32 - higher value means more potential throughput but more
|
| D | sysfs-devices-waiting_for_supplier | 10 or 1) reflects whether the device is waiting for one or more
16 is waiting for one or more suppliers to be added before it can
|
| /Documentation/devicetree/bindings/i3c/ |
| D | snps,dw-i3c-master.txt | 12 Documentation/devicetree/bindings/i3c/i3c.txt for more details):
18 Documentation/devicetree/bindings/i3c/i3c.txt for more details):
24 Documentation/devicetree/bindings/i3c/i3c.txt for more details).
|
| D | cdns,i3c-master.txt | 13 Documentation/devicetree/bindings/i3c/i3c.txt for more details):
19 Documentation/devicetree/bindings/i3c/i3c.txt for more details):
25 Documentation/devicetree/bindings/i3c/i3c.txt for more details).
|
| /Documentation/devicetree/ |
| D | writing-schema.rst | 8 is considered more human readable and has some advantages such as allowing
42 more information.
62 For more details on properties sections, see 'Property Schema' section.
72 Optional. A list of one or more DTS hunks implementing the
89 Vendor specific properties will typically need more detailed schema. With the
94 dtc. They are simplified to make them more compact and avoid a bunch of
98 The default for arrays in json-schema is they are variable sized and allow more
|
| /Documentation/devicetree/bindings/pci/ |
| D | cdns-pcie.yaml | 15 One per lane if more than one in the list. If only one PHY listed it must
23 # FIXME: names when more than 1
|
| /Documentation/devicetree/bindings/powerpc/ |
| D | sleep.yaml | 15 this information is more complicated than a cell-index property can
19 The sleep property consists of one or more sleep resources, each of
21 controller-specific sleep specifier of zero or more cells.
|
| /Documentation/devicetree/bindings/clock/ |
| D | ti-clkctrl.txt | 6 gate one or more optional functional clocks for a module, and can have one
7 or more clock muxes. There is a clkctrl clock controller typically for each
15 For more information, please see the Linux clock framework binding at
|
| /Documentation/devicetree/bindings/power/supply/ |
| D | ti,bq24735.txt | 17 is 0x0000h. This number is in mA (e.g. 8192), see spec for more information
21 is 0x0000h. This number is in mV (e.g. 19200), see spec for more information
26 more information about the InputCurrent (0x3fh) register.
|
| /Documentation/userspace-api/media/dvb/ |
| D | fe-get-property.rst | 13 …E_GET_PROPERTY - FE_SET_PROPERTY sets one or more frontend properties. - FE_GET_PROPERTY returns o…
44 - This ioctl is used to set one or more frontend properties.
|
| /Documentation/driver-api/usb/ |
| D | gadget.rst | 24 - Flexible enough to expose more complex USB device capabilities such
32 API. This helps the OTG support, and looks forward to more-symmetric
42 embedded systems are more likely to have USB peripheral hardware. To
43 distinguish drivers running inside such hardware from the more familiar
141 - ... and more
152 side stack, with ``usbcore``, one or more *Host Controller Drivers*
159 viewed as a more battery-friendly kind of device wakeup protocol.
170 hardware-specific, any more than network protocols like X11, HTTP, or
180 involves enabling one or more of the struct usb_ep objects exposed by
181 the gadget, and submitting one or more struct usb_request buffers to
[all …]
|
12345678910>>...68