/kernel/linux/linux-5.10/include/dt-bindings/reset/ |
D | imx8mq-reset.h | 31 #define IMX8MQ_RESET_OTG2_PHY_RESET 20 /* i.MX8MN does NOT support */ 32 #define IMX8MQ_RESET_MIPI_DSI_RESET_BYTE_N 21 /* i.MX8MN does NOT support */ 33 #define IMX8MQ_RESET_MIPI_DSI_RESET_N 22 /* i.MX8MN does NOT support */ 34 #define IMX8MQ_RESET_MIPI_DSI_DPI_RESET_N 23 /* i.MX8MN does NOT support */ 35 #define IMX8MQ_RESET_MIPI_DSI_ESC_RESET_N 24 /* i.MX8MN does NOT support */ 36 #define IMX8MQ_RESET_MIPI_DSI_PCLK_RESET_N 25 /* i.MX8MN does NOT support */ 37 #define IMX8MQ_RESET_PCIEPHY 26 /* i.MX8MN does NOT support */ 38 #define IMX8MQ_RESET_PCIEPHY_PERST 27 /* i.MX8MN does NOT support */ 39 #define IMX8MQ_RESET_PCIE_CTRL_APPS_EN 28 /* i.MX8MN does NOT support */ 40 #define IMX8MQ_RESET_PCIE_CTRL_APPS_TURNOFF 29 /* i.MX8MN does NOT support */ [all …]
|
/kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/amdzen2/ |
D | other.json | 28 …"BriefDescription": "Cycles where a dispatch group is valid but does not get dispatched due to a t… 34 …"BriefDescription": "Cycles where a dispatch group is valid but does not get dispatched due to a t… 40 …"BriefDescription": "Cycles where a dispatch group is valid but does not get dispatched due to a t… 46 …"BriefDescription": "Cycles where a dispatch group is valid but does not get dispatched due to a t… 52 …"BriefDescription": "Cycles where a dispatch group is valid but does not get dispatched due to a t… 58 …"BriefDescription": "Cycles where a dispatch group is valid but does not get dispatched due to a t… 64 …"BriefDescription": "Cycles where a dispatch group is valid but does not get dispatched due to a t… 70 …"BriefDescription": "Cycles where a dispatch group is valid but does not get dispatched due to a t… 76 …"BriefDescription": "Cycles where a dispatch group is valid but does not get dispatched due to a t… 82 …"BriefDescription": "Cycles where a dispatch group is valid but does not get dispatched due to a t… [all …]
|
/kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/amdzen1/ |
D | other.json | 17 …"BriefDescription": "Cycles where a dispatch group is valid but does not get dispatched due to a t… 23 …"BriefDescription": "Cycles where a dispatch group is valid but does not get dispatched due to a t… 29 …"BriefDescription": "Cycles where a dispatch group is valid but does not get dispatched due to a t… 35 …"BriefDescription": "Cycles where a dispatch group is valid but does not get dispatched due to a t… 41 …"BriefDescription": "Cycles where a dispatch group is valid but does not get dispatched due to a t… 47 …"BriefDescription": "Cycles where a dispatch group is valid but does not get dispatched due to a t… 53 …"BriefDescription": "Cycles where a dispatch group is valid but does not get dispatched due to a t…
|
/kernel/linux/linux-5.10/fs/nls/ |
D | Kconfig | 47 DOS/Windows partitions correctly. This does apply to the filenames 59 DOS/Windows partitions correctly. This does apply to the filenames 71 DOS/Windows partitions correctly. This does apply to the filenames 84 DOS/Windows partitions correctly. This does apply to the filenames 100 DOS/Windows partitions correctly. This does apply to the filenames 115 DOS/Windows partitions correctly. This does apply to the filenames 126 DOS/Windows partitions correctly. This does apply to the filenames 137 DOS/Windows partitions correctly. This does apply to the filenames 148 DOS/Windows partitions correctly. This does apply to the filenames 159 DOS/Windows partitions correctly. This does apply to the filenames [all …]
|
/kernel/linux/linux-5.10/include/xen/interface/ |
D | features.h | 14 * If set, the guest does not need to write-protect its pagetables, and can 20 * If set, the guest does not need to write-protect its segment descriptor 28 * mode the guest does not need to perform phys-to/from-machine translations 37 * If set, the guest does not need to allocate x86 PAE page directories 42 /* x86: Does this Xen host support the MMU_PT_UPDATE_PRESERVE_AD hypercall? */ 45 /* x86: Does this Xen host support the MMU_{CLEAR,COPY}_PAGE hypercall? */ 54 /* x86: Does this Xen host support the HVM callback vector type? */
|
/kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/ |
D | vidioc-g-modulator.rst | 52 this is a write-only ioctl, it does not return the actual audio 135 channels, a down-mix of channel 1 and 2. This flag does not 143 left and right channel. This flag does not combine with 145 driver does not support stereo audio it shall fall back to mono. 151 or secondary language only. This flag does not combine with 153 ``V4L2_TUNER_SUB_SAP``. If the hardware does not support the 154 respective audio matrix, or the current video standard does not 175 hardware does not support the respective audio matrix, or the 176 current video standard does not permit SAP the
|
D | vidioc-g-std.rst | 55 does not return the actual new standard as :ref:`VIDIOC_G_STD <VIDIOC_G_STD>` does. When 56 no flags are given or the current input does not support the requested 59 standards. If the current input or output does not support standard 61 does not set the ``V4L2_IN_CAP_STD`` flag), then ``ENODATA`` error code is
|
D | vidioc-encoder-cmd.rst | 104 this command does nothing. No flags are defined for this command. 116 encoder is already stopped, this command does nothing. 127 already paused, this command does nothing. No flags are defined 133 the encoder is already running, this command does nothing. No 150 Does not apply to :ref:`encoder`.
|
/kernel/linux/linux-5.10/arch/mips/netlogic/ |
D | Kconfig | 11 This DTB will be used if the firmware does not pass in a DTB 21 This DTB will be used if the firmware does not pass in a DTB 31 This DTB will be used if the firmware does not pass in a DTB 41 This DTB will be used if the firmware does not pass in a DTB 50 This DTB will be used if the firmware does not pass in a DTB
|
/kernel/linux/linux-5.10/Documentation/watchdog/ |
D | watchdog-kernel-api.rst | 11 This document does not describe what a WatchDog Timer (WDT) Driver or Device is. 12 It also does not describe the API which can be used by user space to communicate 16 So what does this document describe? It describes the API that can be used by 19 the same code does not have to be reproduced each time. This also means that 84 This is the time after which the system will reboot if user space does 99 seconds. max_hw_heartbeat_ms must be set if a driver does not implement 159 driver supporting such hardware does not have to implement the stop routine. 165 If a watchdog driver does not implement the stop function, it must set 173 Most hardware that does not support this as a separate function uses the 175 the watchdog timer driver core does: to send a keepalive ping to the watchdog [all …]
|
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/serial/ |
D | snps-dw-apb-uart.yaml | 62 parameter. Define this if your UART does not implement the busy functionality. 75 status register. Define this if your serial port does not use this 82 status register. Define this if your serial port does not use this 89 status register. Define this if your serial port does not use this 96 register. Define this if your serial port does not use this pin.
|
/kernel/linux/linux-5.10/tools/testing/selftests/tc-testing/ |
D | TdcPlugin.py | 22 '''run commands before test_runner does one test''' 29 '''run commands after test_runner does one test''' 34 '''run command before test-runner does the execute step''' 39 '''run command after test-runner does the execute step'''
|
/kernel/linux/linux-5.10/arch/mips/include/asm/octeon/ |
D | octeon-feature.h | 47 /* Does this Octeon support the ZIP offload engine? */ 50 /* Does this Octeon support PCI express? */ 52 /* Does this Octeon support SRIOs */ 54 /* Does this Octeon support Interlaken */ 99 * Returns: Non-zero if the feature exists. Zero if the feature does not exist. 114 * Returns Non zero if the feature exists. Zero if the feature does not
|
/kernel/linux/linux-5.10/Documentation/driver-api/md/ |
D | raid5-ppl.rst | 13 this, md by default does not allow starting a dirty degraded array. 29 stripe. It does not require a dedicated journaling drive. Write performance is 31 and the journaling drive does not become a bottleneck or a single point of 35 not a true journal. It does not protect from losing in-flight data, only from
|
/kernel/linux/linux-5.10/Documentation/kbuild/ |
D | Kconfig.select-break | 10 # Kconfig currently does not check the list of symbols listed on a symbol's 16 # However, when A is set, C can be set as well because Kconfig does not 18 # Kconfig does not visit the dependencies, it breaks the dependencies of B
|
/kernel/linux/linux-5.10/tools/power/cpupower/utils/helpers/ |
D | msr.c | 23 * EIO -If the CPU does not support MSRs 24 * ENXIO -If the CPU does not exist 53 * EIO -If the CPU does not support MSRs 54 * ENXIO -If the CPU does not exist
|
/kernel/linux/linux-5.10/include/media/ |
D | cec-notifier.h | 45 * @n: notifier. If NULL, then this function does nothing. 72 * @n: notifier. If NULL, then this function does nothing. 84 * Does nothing if @n == NULL. 94 * Does nothing if @n == NULL. 159 * address. Does nothing if @n == NULL.
|
/kernel/linux/linux-5.10/include/linux/ |
D | of.h | 427 * it. Returns 0 on success, -EINVAL if the property does not exist, 428 * -ENODATA if property does not have a value, and -EOVERFLOW if the 457 * it. Returns 0 on success, -EINVAL if the property does not exist, 458 * -ENODATA if property does not have a value, and -EOVERFLOW if the 488 * it. Returns 0 on success, -EINVAL if the property does not exist, 489 * -ENODATA if property does not have a value, and -EOVERFLOW if the 516 * it. Returns 0 on success, -EINVAL if the property does not exist, 517 * -ENODATA if property does not have a value, and -EOVERFLOW if the 1066 * in it. Returns number of elements on sucess, -EINVAL if the property does 1067 * not exist or its length does not match a multiple of u8 and -ENODATA if the [all …]
|
/kernel/linux/linux-5.10/Documentation/filesystems/ |
D | hfs.rst | 42 Select partition number n from the devices. Does only makes 44 For disk devices the generic partition parsing code does this 54 HFS is not a UNIX filesystem, thus it does not have the usual features you'd 61 HFS does on the other have the concepts of multiple forks per file. These
|
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/timer/ |
D | arm,arch_timer.yaml | 45 only where necessary to work around broken firmware which does not configure 76 description: Firmware does not initialize any of the generic timer CPU 83 description: The main counter does not tick when the system is in 84 low-power system suspend on some SoCs. This behavior does not match the
|
D | arm,arch_timer_mmio.yaml | 39 only where necessary to work around broken firmware which does not configure 50 description: Firmware does not initialize any of the generic timer CPU 57 description: The main counter does not tick when the system is in 58 low-power system suspend on some SoCs. This behavior does not match the
|
/kernel/linux/linux-5.10/Documentation/admin-guide/ |
D | sysfs-rules.rst | 6 by the kernel developers that the Linux kernel does not provide a stable 22 It makes assumptions about sysfs which are not true. Its API does not 96 context properties. If the device ``eth0`` or ``sda`` does not have a 97 "driver"-link, then this device does not have a driver. Its value is empty. 123 can be ignored. If it does not exist, you always have to scan all three 143 device directory does not end in ``/sys/devices/``, you can use the 153 directory does not contain directories for child devices, these links
|
/kernel/linux/linux-5.10/arch/mips/kvm/ |
D | Kconfig | 12 This option alone does not add any kernel code. 43 does not require any special hardware Virtualization support beyond 44 standard MIPS32 r2 or later, but it does require the guest kernel
|
/kernel/linux/linux-5.10/arch/arm/mach-omap2/ |
D | voltage.c | 55 pr_warn("%s: VDD specified does not exist!\n", __func__); in voltdm_get_voltage() 77 pr_warn("%s: VDD specified does not exist!\n", __func__); in voltdm_scale() 128 pr_warn("%s: VDD specified does not exist!\n", __func__); in voltdm_reset() 158 pr_warn("%s: VDD specified does not exist!\n", __func__); in omap_voltage_get_volttable() 186 pr_warn("%s: VDD specified does not exist!\n", __func__); in omap_voltage_get_voltdata() 191 pr_warn("%s: voltage table does not exist for vdd_%s\n", in omap_voltage_get_voltdata() 220 pr_warn("%s: VDD specified does not exist!\n", __func__); in omap_voltage_register_pmic()
|
/kernel/linux/linux-5.10/tools/memory-model/Documentation/ |
D | explanation.txt | 47 for people who want to understand how the model was designed. It does 175 happens, the LKMM does predict this outcome can occur, and the example 215 instance, the MP example code really does sometimes yield r1 = 1 and 245 this outcome to occur, and in fact it does sometimes occur on x86 and 287 The LKMM does not work directly with the C statements that make up 432 value it obtains must somehow affect what the second event does. 550 unaligned accesses in a memory model, but the LKMM currently does not 809 store associated with the release fence does. 848 before W' does. However, for different CPUs C and C', it does not 925 What does it mean to say that a read-modify-write (rmw) update, such [all …]
|