Searched full:usually (Results 1 – 25 of 643) sorted by relevance
12345678910>>...26
| /Documentation/ABI/testing/ |
| D | sysfs-ibft | 6 Usually this contains the Initiator name.
13 Usually this contains the target's IP address, boot LUN,
23 Usually this contains the IP address, MAC, and gateway of the NIC.
|
| /Documentation/sound/soc/ |
| D | dai.rst | 15 The bit clock (BCLK) is always driven by the CODEC (usually 12.288MHz) and the
16 frame (FRAME) (usually 48kHz) is always driven by the controller. Each AC97
30 usually varies depending on the sample rate and the master system clock
53 receive the audio data. Bit clock usually varies depending on sample rate
|
| D | clocking.rst | 24 The Digital Audio Interface is usually driven by a Bit Clock (often referred to
43 audio clocks as it usually gives more accurate sample rates than the CPU.
|
| /Documentation/devicetree/bindings/display/panel/ |
| D | samsung,s6d7aa0.yaml | 36 description: Reset GPIO pin, usually GPIO_ACTIVE_LOW.
41 panels, and is usually somewhere around 3.3-5v.
44 description: VMIPI supply, usually 1.8v.
|
| D | jadard,jd9365da-h3.yaml | 27 description: supply regulator for VDD, usually 3.3V
30 description: supply regulator for VCCIO, usually 1.8V
|
| D | samsung,lms397kf04.yaml | 29 usually around 3.0 V
32 description: regulator that supplies the VCCIO voltage usually
|
| D | samsung,lms380kf01.yaml | 37 usually around 3.0 V
40 description: regulator that supplies the VCCIO voltage usually
|
| D | samsung,s6d27a1.yaml | 36 usually around 3.0 V
39 description: regulator that supplies the VCCIO voltage usually
|
| /Documentation/admin-guide/media/ |
| D | cardlist.rst | 10 The platform-specific drivers are usually present on embedded systems,
11 or are supported by the main board. Usually, setting them is done via
|
| /Documentation/userspace-api/media/v4l/ |
| D | vidioc-g-priority.rst | 60 - Lowest priority, usually applications running in background, for
69 - Medium priority, usually applications started and interactively
77 it blocks any other fd from changing device properties. Usually
|
| /Documentation/devicetree/bindings/remoteproc/ |
| D | ti,davinci-rproc.txt | 7 The TI Davinci family of SoCs usually contains a TI DSP Core sub-system that
11 The processor cores in the sub-system usually contain additional sub-modules
14 core used in Davinci SoCs is usually a C674x DSP CPU.
|
| D | ti,omap-remoteproc.yaml | 13 The OMAP family of SoCs usually have one or more slave processor sub-systems
17 The processor cores in the sub-system are usually behind an IOMMU, and may
21 The OMAP SoCs usually have a DSP processor sub-system and/or an IPU processor
24 sub-system usually contains either a Dual-Core Cortex-M3 or Dual-Core
55 other peripheral device address spaces. This property usually
149 processors. This will usually be a single timer if the
167 will usually be one per executing processor core, even
|
| /Documentation/driver-api/media/ |
| D | dtv-core.rst | 12 - Frontend drivers that are usually implemented as two separate drivers:
16 physical channel. The output of a tuner is usually a baseband or
|
| /Documentation/devicetree/bindings/net/ |
| D | intel,ixp46x-ptp-timer.yaml | 28 PRP timer, usually a GPIO interrupt.
30 PRP timer, usually a GPIO interrupt.
|
| /Documentation/devicetree/bindings/powerpc/4xx/ |
| D | cpm.txt | 23 devices. This is usually just CPM[CPU].
33 be different or the same. Usually for
|
| /Documentation/driver-api/iio/ |
| D | triggered-buffers.rst | 45 /* setup triggered buffer, usually in probe function */
63 processing takes place here. It usually reads data from the device and
|
| /Documentation/networking/devlink/ |
| D | devlink-info.rst | 32 This is usually the serial number of the ASIC, also often available
50 This is usually the serial number of the board, often available in
109 - Version of API between components. API items are usually of limited
187 Unique identifier of the firmware parameter set. These are usually
|
| D | devlink-flash.rst | 16 (usually ``/lib/firmware/``). Drivers may send status updates to inform
50 Devices which require firmware to operate usually store it in non-volatile
61 On-disk firmware files are usually stored in ``/lib/firmware/``.
|
| /Documentation/locking/ |
| D | spinlocks.rst | 32 The above is usually pretty simple (you usually need and want only one
34 lot more complex and even slower and is usually worth it only for
55 If your data accesses have a very natural pattern where you usually tend
|
| /Documentation/devicetree/bindings/power/reset/ |
| D | atmel,sama5d2-shdwc.yaml | 40 Minimum wake-up inputs debouncer period in microseconds. It is usually a
54 Wake-up input nodes. These are usually described in the "board" part of
|
| /Documentation/filesystems/ |
| D | bfs.rst | 8 usually contains the kernel image and a few other files required for the
44 look for the slice with tag "STAND", which is usually slice 10. With this
|
| /Documentation/driver-api/ |
| D | spi.rst | 12 additional chipselect line is usually active-low (nCS); four signals are
32 <spi_board_info>` descriptors which are usually provided by
|
| /Documentation/hwmon/ |
| D | thmc50.rst | 49 accuracy. An alarm is issued (usually to a connected LM78) when the
57 The THMC50 is usually used in combination with LM78-like chips, to measure
|
| /Documentation/devicetree/bindings/display/ |
| D | dsi-controller.yaml | 26 reg-property set to the virtual channel number, usually there is just
67 The best option is usually to run a panel in command mode, as this
|
| /Documentation/devicetree/bindings/watchdog/ |
| D | ziirave-wdt.txt | 5 - reg: i2c slave address of device, usually 0x38
|
12345678910>>...26