Searched full:typically (Results 1 – 25 of 400) sorted by relevance
12345678910>>...16
| /Documentation/media/uapi/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/devicetree/bindings/net/can/ |
| D | can-transceiver.txt | 4 CAN transceiver typically limits the max speed in standard CAN and CAN FD
5 modes. Typically these limitations are static and the transceivers themselves
|
| /Documentation/ |
| D | IRQ.txt | 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/RCU/ |
| D | rculist_nulls.txt | 84 lock_chain(); // typically a spin_lock()
93 unlock_chain(); // typically a spin_unlock()
103 lock_chain(); // typically a spin_lock()
105 unlock_chain(); // typically a spin_unlock()
161 lock_chain(); // typically a spin_lock()
172 unlock_chain(); // typically a spin_unlock()
|
| /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/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/admin-guide/ |
| D | cputopology.rst | 11 physical package id of cpuX. Typically corresponds to a physical
17 the CPU die ID of cpuX. Typically it is the hardware platform's
23 the CPU core ID of cpuX. Typically it is the hardware platform's
29 the book ID of cpuX. Typically it is the hardware platform's
35 the drawer ID of cpuX. Typically it is the hardware platform's
|
| D | thunderbolt.rst | 34 approval is needed. In BIOS settings this is typically called
41 In BIOS settings this is typically called *Unique ID*.
48 typically called *One time saved key*.
53 typically called *Display Port Only*.
62 the Thunderbolt domain the host controller manages. There is typically
161 Typically OEMs provide this firmware from their support site.
|
| /Documentation/media/uapi/ |
| D | gen-errors.rst | 42 typically return while device is streaming, and an ioctl tried to
46 the problem first (typically: stop the stream before retrying).
86 - I/O error. Typically used when there are problems communicating with
|
| /Documentation/devicetree/bindings/power/supply/ |
| D | bq24190.txt | 16 phase (typically 20% of battery capacity).
19 this setting (typically 10% of battery capacity).
|
| /Documentation/filesystems/ |
| D | ubifs.txt | 16 rather large size, typically about 128KiB. Block devices consist of
17 small blocks, typically 512 bytes.
25 typically 100K-1G for SLC NAND and NOR flashes, and 1K-10K for MLC
28 deal with this. Blocks on hard drives typically do not become bad,
|
| /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/driver-api/ |
| D | edac.rst | 21 typically 72 bits, in order to provide 64 bits + 8 bits of ECC data.
43 It is typically the highest hierarchy on a Fully-Buffered DIMM memory
44 controller. Typically, it contains two channels. Two channels at the
56 one 64 bits parallel access. Typically used with SDR, DDR, DDR2 and DDR3
|
| /Documentation/devicetree/bindings/bus/ |
| D | ti-sysc.txt | 16 target module and typically are named REVISION, SYSCONFIG and SYSSTATUS.
73 TRM for SYSSTATUS registers, typically 1 with some devices
79 typically available for all interconnect targets on TI SoCs
|
| /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/iio/magnetometer/ |
| D | hmc5843.txt | 10 - reg : the I2C address of the magnetometer - typically 0x1e
|
| /Documentation/devicetree/bindings/arm/omap/ |
| D | counter.txt | 6 - ti,hwmods: Name of the hwmod associated to the counter, which is typically
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-gnss | 13 Note that also non-"NMEA" type receivers typically support a
|
| /Documentation/media/uapi/v4l/ |
| D | ext-ctrls-image-process.rst | 60 are multiplied by. Typically the digital gain applied is the
63 configuration is also typically the default.
|
| /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/devicetree/bindings/media/ |
| D | tango-ir.txt | 8 - clocks: spec for IR clock (typically the crystal oscillator)
|
| /Documentation/media/v4l-drivers/ |
| D | soc-camera.rst | 13 of connecting to a variety of systems and interfaces, typically uses i2c for
15 - camera host - an interface, to which a camera is connected. Typically a
87 soc-camera core when a video-device is opened, the host driver would typically
98 Sensor drivers can use struct soc_camera_link, typically provided by the
|
| /Documentation/admin-guide/pm/ |
| D | strategies.rst | 38 "runtime active" and that situation typically corresponds to the maximum power
45 typically the system can spend much more time in a sleep state than it can be
|
12345678910>>...16