Searched full:typically (Results 1 – 25 of 506) sorted by relevance
12345678910>>...21
| /Documentation/userspace-api/media/mediactl/ |
| D | media-types.rst | 283 - typically, /dev/dvb/adapter?/frontend?
287 - typically, /dev/dvb/adapter?/demux?
291 - typically, /dev/dvb/adapter?/dvr?
295 - typically, /dev/dvb/adapter?/ca?
299 - typically, /dev/dvb/adapter?/net?
303 - typically, /dev/video?
307 - typically, /dev/vbi?
311 - typically, /dev/radio?
315 - typically, /dev/v4l-subdev?
319 - typically, /dev/swradio?
[all …]
|
| /Documentation/ABI/stable/ |
| D | sysfs-devices-system-cpu | 28 Description: physical package id of cpuX. Typically corresponds to a physical
34 Description: the CPU die ID of cpuX. Typically it is the hardware platform's
40 Description: the CPU core ID of cpuX. Typically it is the hardware platform's
46 Description: the cluster ID of cpuX. Typically it is the hardware platform's
52 Description: the book ID of cpuX. Typically it is the hardware platform's
58 Description: the drawer ID of cpuX. Typically it is the hardware platform's
|
| /Documentation/accel/ |
| D | introduction.rst | 12 Although these devices are typically designed to accelerate
16 Typically, a compute accelerator will belong to one of the following
21 are typically configured using registers and can work with or without DMA.
32 - Training data-center - Similar to Inference data-center cards, but typically
37 All these devices typically have different runtime user-space software stacks,
40 engines. Typically, the common layer in user-space will be the DL frameworks,
|
| /Documentation/devicetree/bindings/media/i2c/ |
| D | ovti,ov5670.yaml | 36 description: Analog circuit power. Typically 2.8V.
39 description: Digital circuit power. Typically 1.2V.
42 description: Digital I/O circuit power. Typically 2.8V or 1.8V.
|
| /Documentation/core-api/irq/ |
| D | concepts.rst | 11 interrupt source. Typically this is an index into the global irq_desc
16 machine. Typically what is enumerated is the number of input pins on
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | marvell,armada-8k-pic.txt | 6 typically connected to the GIC as the primary interrupt controller.
15 typically the GIC
|
| /Documentation/userspace-api/media/ |
| D | gen-errors.rst | 35 typically return while device is streaming, and an ioctl tried to
39 the problem first (typically: stop the stream before retrying).
79 - I/O error. Typically used when there are problems communicating with
|
| /Documentation/devicetree/bindings/sound/ |
| D | fsl,ssi.txt | 33 codec connected to this SSI. This node is typically
57 playback of audio. This is typically dictated by SOC
61 capture (recording) of audio. This is typically dictated
69 - clock-frequency: The frequency of the input clock, which typically comes
|
| /Documentation/devicetree/bindings/usb/ |
| D | gr-udc.txt | 23 number. If the property is present it typically contains one entry for
29 number. If the property is present it typically contains one entry for
|
| /Documentation/RCU/ |
| D | rculist_nulls.rst | 113 lock_chain(); // typically a spin_lock()
117 unlock_chain(); // typically a spin_unlock()
130 lock_chain(); // typically a spin_lock()
132 unlock_chain(); // typically a spin_unlock()
208 lock_chain(); // typically a spin_lock()
215 unlock_chain(); // typically a spin_unlock()
|
| /Documentation/devicetree/bindings/iio/chemical/ |
| D | senseair,sunrise.yaml | 32 Phandle to the GPIO line connected to the nDRY pin. Typically active low.
37 Phandle to the GPIO line connected to the EN pin. Typically active high.
|
| /Documentation/devicetree/bindings/gnss/ |
| D | brcm,bcm4751.yaml | 35 Main voltage supply, pin name VDD_AUXIN, typically connected
40 IO voltage supply, pin name VDDIO, typically 1.8V
|
| /Documentation/livepatch/ |
| D | system-state.rst | 10 add, and even remove fixes. And it is typically safe to replace any version
122 The system state itself is typically modified in *post_patch()*
160 *pre_unpatch()* typically does symmetric operations to *post_patch()*.
165 *post_unpatch()* typically does symmetric operations to *pre_patch()*.
|
| /Documentation/security/tpm/ |
| D | tpm_event_log.rst | 16 register. Typically, the preboot firmware will hash the components to
25 therefore, attestation is typically more useful when the PCR contents
|
| /Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-image-process.rst | 54 are multiplied by. Typically the digital gain applied is the
57 configuration is also typically the default.
|
| /Documentation/filesystems/ |
| D | ubifs.rst | 22 rather large size, typically about 128KiB. Block devices consist of
23 small blocks, typically 512 bytes.
31 typically 100K-1G for SLC NAND and NOR flashes, and 1K-10K for MLC
34 deal with this. Blocks on hard drives typically do not become bad,
|
| /Documentation/driver-api/mei/ |
| D | mei-client-bus.rst | 57 API. This is typically called at module initialization time.
59 Once the driver is registered and bound to the device, a driver will typically
139 The handler implementation will typically call :c:func:`mei_cldev_recv` and then
|
| /Documentation/devicetree/bindings/power/supply/ |
| D | bq24190.yaml | 55 (typically 20% of battery capacity).
58 setting (typically 10% of battery capacity).
|
| /Documentation/devicetree/bindings/arm/omap/ |
| D | counter.txt | 6 - ti,hwmods: Name of the hwmod associated to the counter, which is typically
|
| /Documentation/devicetree/bindings/iio/magnetometer/ |
| D | yamaha,yas530.yaml | 50 on the VDD pin, typically 1.8 V or 3.0 V.
54 for the I2C interface on the IOVDD pin, typically 1.8 V.
|
| /Documentation/devicetree/bindings/mux/ |
| D | mux-consumer.yaml | 39 mux-ctrl-specifier typically encodes the chip-relative mux controller number.
41 mux-ctrl-specifier can typically be left out.
|
| /Documentation/arch/x86/ |
| D | tdx.rst | 67 The #VE MSRs are typically able to be handled by the hypervisor. Guests
138 A modest amount of memory (typically 512M) is pre-accepted by the firmware
151 fatal. Typically, an unhandled userspace #VE results in a SIGSEGV.
154 Handling nested exceptions on x86 is typically nasty business. A #VE
178 In TDX, MMIO regions typically trigger a #VE exception in the guest. The
241 as input and included in the TDREPORT. Typically it can be some nonce
|
| /Documentation/devicetree/bindings/xillybus/ |
| D | xillybus.txt | 6 - interrupts: Contains one interrupt node, typically consisting of three cells.
|
| /Documentation/devicetree/bindings/reset/ |
| D | reset.txt | 8 Hardware blocks typically receive a reset signal. This signal is generated by
35 #reset-cells: Number of cells in a reset specifier; Typically 0 for nodes
|
| /Documentation/hid/ |
| D | hidraw.rst | 30 create hidraw device nodes. Udev will typically create the device nodes
147 specific report number. Typically, this is used to request the initial states of
157 output reports, but is added for completeness. Typically, this is used to set
166 endpoint. Typically, this is used to retrieve the initial state of
|
12345678910>>...21