Searched full:relevant (Results 1 – 25 of 284) sorted by relevance
12345678910>>...12
| /Documentation/virt/kvm/devices/ |
| D | mpic.rst | 31 to the relevant MSIIR.
42 byte offset of the relevant IVPR from EIVPR0, divided by 32.
|
| /Documentation/process/ |
| D | cve.rst | 70 change lies solely with the maintainers of the relevant subsystem
107 large numbers of assigned CVEs are not relevant for their systems.
111 specific CVE is relevant for your system.
120 might be relevant to take.
|
| /Documentation/userspace-api/media/v4l/ |
| D | vidioc-enum-fmt.rst | 198 colorspace. This flag is relevant only for capture devices.
205 transfer function. This flag is relevant only for capture devices.
212 Y'CbCr encoding. This flag is relevant only for capture devices.
219 HSV encoding. This flag is relevant only for capture devices.
226 quantization. This flag is relevant only for capture devices.
|
| /Documentation/devicetree/bindings/soc/fsl/ |
| D | fsl,qman-fqd.yaml | 25 The following constraints are relevant to the FQD and PFDR private memory:
31 configured via the Reset Configuration Word (RCW) and that are relevant to a
|
| /Documentation/devicetree/bindings/net/can/ |
| D | st,stm32-bxcan.yaml | 24 Primary mode of the bxCAN peripheral is only relevant if the chip has
34 Secondary mode of the bxCAN peripheral is only relevant if the chip
|
| /Documentation/gpu/amdgpu/display/ |
| D | dc-debug.rst | 84 an issue arises is some generic timeout error. So, to get more relevant
85 information, we can trace DMUB commands by enabling the relevant bits in
116 enabling the relevant bits in the mask before reproducing the issue and
|
| /Documentation/tools/rtla/ |
| D | common_timerlat_description.rst | 9 handler. It also enable the trace of the most relevant information via
|
| /Documentation/ABI/testing/ |
| D | sysfs-devices-waiting_for_supplier | 9 information is no longer relevant). The number read from it (0
|
| D | sysfs-class-net-statistics | 7 This value might not be relevant with all MAC layers.
32 network device. This value might only be relevant for interfaces
161 this might only be relevant for devices that support
|
| /Documentation/devicetree/bindings/rtc/ |
| D | fsl,scu-rtc.yaml | 13 Client nodes are maintained as children of the relevant IMX-SCU device node.
|
| /Documentation/gpu/rfc/ |
| D | index.rst | 10 considerations. Especially for uapi make sure you Cc: all relevant project
|
| /Documentation/devicetree/bindings/watchdog/ |
| D | fsl,scu-wdt.yaml | 13 Client nodes are maintained as children of the relevant IMX-SCU device node.
|
| /Documentation/devicetree/bindings/thermal/ |
| D | fsl,scu-thermal.yaml | 13 Client nodes are maintained as children of the relevant IMX-SCU device node.
|
| /Documentation/devicetree/bindings/input/ |
| D | fsl,scu-key.yaml | 13 Client nodes are maintained as children of the relevant IMX-SCU device node.
|
| /Documentation/firmware-guide/acpi/dsd/ |
| D | leds.rst | 20 referring to the "reg" property of the relevant LED, is used to identify
33 show below. Objects not relevant for LEDs or the references to them have been
|
| /Documentation/devicetree/bindings/spi/ |
| D | nxp,sc18is.yaml | 27 relevant and needed only if the chip has an external oscillator
|
| /Documentation/devicetree/bindings/power/ |
| D | fsl,scu-pd.yaml | 13 Client nodes are maintained as children of the relevant IMX-SCU device node.
|
| /Documentation/arch/arc/ |
| D | arc.rst | 10 ARC processors and relevant open source projects.
13 Good place to start to find relevant FOSS projects, toolchain releases,
|
| /Documentation/devicetree/bindings/nvmem/ |
| D | fsl,scu-ocotp.yaml | 13 Client nodes are maintained as children of the relevant IMX-SCU device node.
|
| /Documentation/devicetree/bindings/clock/ |
| D | fsl,scu-clk.yaml | 13 Client nodes are maintained as children of the relevant IMX-SCU device node.
|
| /Documentation/devicetree/bindings/iommu/ |
| D | pkvm,pviommu.yaml | 33 by that device into the relevant SMMU.
|
| /Documentation/usb/ |
| D | ohci.rst | 32 work on while the OS is getting around to the relevant IRQ processing.
|
| /Documentation/devicetree/bindings/i2c/ |
| D | i2c-opal.txt | 13 the relevant OPAL functions.
|
| /Documentation/devicetree/bindings/sifive/ |
| D | sifive-blocks-ip-versioning.txt | 24 register interface and functionality associated with the relevant
|
| /Documentation/scsi/ |
| D | 53c700.rst | 79 the relevant request_*_region function and place the register base
93 where host is the return from the relevant NCR_700_detect() routine.
|
12345678910>>...12