/Linux-v5.15/Documentation/ABI/testing/ |
D | debugfs-hisi-sec | 44 Available for both PF and VF, and take no other effect on SEC. 50 Available for both PF and VF, and take no other effect on SEC. 56 Available for both PF and VF, and take no other effect on SEC. 62 Available for both PF and VF, and take no other effect on SEC. 68 Available for both PF and VF, and take no other effect on SEC. 75 Available for both PF and VF, and take no other effect on SEC. 81 Available for both PF and VF, and take no other effect on SEC. 87 Available for both PF and VF, and take no other effect on SEC. 93 Available for both PF and VF, and take no other effect on SEC. 100 Available for both PF and VF, and take no other effect on SEC. [all …]
|
D | debugfs-hisi-hpre | 64 Available for both PF and VF, and take no other effect on HPRE. 70 Available for both PF and VF, and take no other effect on HPRE. 76 Available for both PF and VF, and take no other effect on HPRE. 82 Available for both PF and VF, and take no other effect on HPRE. 88 Available for both PF and VF, and take no other effect on HPRE. 95 Available for both PF and VF, and take no other effect on HPRE. 101 Available for both PF and VF, and take no other effect on HPRE. 107 Available for both PF and VF, and take no other effect on HPRE. 114 Available for both PF and VF, and take no other effect on HPRE. 120 Available for both PF and VF, and take no other effect on HPRE. [all …]
|
D | debugfs-hisi-zip | 57 Available for both PF and VF, and take no other effect on ZIP. 63 Available for both PF and VF, and take no other effect on ZIP. 69 Available for both PF and VF, and take no other effect on ZIP. 75 Available for both PF and VF, and take no other effect on ZIP. 81 Available for both PF and VF, and take no other effect on ZIP. 88 Available for both PF and VF, and take no other effect on ZIP. 94 Available for both PF and VF, and take no other effect on ZIP. 100 Available for both PF and VF, and take no other effect on ZIP. 107 Available for both PF and VF, and take no other effect on ZIP. 114 Available for both PF and VF, and take no other effect on ZIP.
|
D | sysfs-bus-event_source-devices-uncore | 7 The 'perf(1)' tool should treat both names the same. 8 They both can be used to access the uncore PMU.
|
D | sysfs-devices-platform-docg3 | 10 writes or both. 27 writes or both.
|
/Linux-v5.15/Documentation/devicetree/bindings/arm/ |
D | secure.txt | 9 space, or visible in both. (One example of that situation would be a 32 secure- bindings only need to be used where both the Secure and Normal 43 both default to "okay". This means the following combinations are 46 /* Neither specified: default to visible in both S and NS */ 47 secure-status = "okay"; /* visible in both */ 48 status = "okay"; /* visible in both */ 49 status = "okay"; secure-status = "okay"; /* visible in both */ 53 status = "disabled"; /* disabled in both */ 54 status = "disabled"; secure-status = "disabled"; /* disabled in both */
|
/Linux-v5.15/Documentation/power/ |
D | apm-acpi.rst | 13 build a kernel with both ACPI and APM enabled (as of 2.3.x ACPI is 18 No, sorry, you cannot have both ACPI and APM enabled and running at 20 would like to use both to get a full set of working features, but you 27 respectively, to be completely functional. Obtain both of these 30 Go ahead and start both. If ACPI or APM is not available on your
|
/Linux-v5.15/Documentation/devicetree/bindings/regmap/ |
D | regmap.txt | 16 On SoCs that can be operated in both big-endian and little-endian 17 modes, with a single hardware switch controlling both the endianness 20 blob in both cases.
|
/Linux-v5.15/tools/testing/selftests/firmware/ |
D | fw_filesystem.sh | 509 test_batched_request_firmware $i both 513 test_batched_request_firmware_into_buf $i both 517 test_batched_request_firmware_direct $i both 521 test_request_firmware_nowait_uevent $i both 525 test_request_firmware_nowait_custom $i both
|
/Linux-v5.15/drivers/usb/musb/ |
D | Kconfig | 17 or the USB host role, or both. 58 both host and gadget features are enabled. 89 depends on NOP_USB_XCEIV = USB_MUSB_HDRC # both built-in or both modules 166 depends on USB_MUSB_TUSB6010 = USB_MUSB_HDRC # both built-in or both modules
|
/Linux-v5.15/drivers/net/wireless/cisco/ |
D | Kconfig | 30 This driver support both the standard Linux Wireless Extensions 31 and Cisco proprietary API, so both the Linux Wireless Tools and the 55 This driver support both the standard Linux Wireless Extensions 56 and Cisco proprietary API, so both the Linux Wireless Tools and the
|
/Linux-v5.15/Documentation/userspace-api/media/v4l/ |
D | tuner.rst | 35 determined by the current video input. Drivers must support both ioctls 57 A video or radio device cannot support both a tuner and a modulator. Two 69 current video output. Drivers must support both ioctls and set the 81 :ref:`VIDIOC_S_FREQUENCY <VIDIOC_G_FREQUENCY>` ioctl which both take 84 both ioctls when the tuner or modulator ioctls are supported, or when
|
D | dev-mem2mem.rst | 17 supports both output (sending frames from memory to the hardware) 20 both sides and finally call :ref:`VIDIOC_STREAMON <VIDIOC_STREAMON>` 21 for both capture and output to start the hardware.
|
/Linux-v5.15/Documentation/networking/dsa/ |
D | lan9303.rst | 18 The LAN9303 can be managed both via MDIO and I2C, both supported by this driver. 24 When both user ports are joined to the same bridge, the normal HW MAC learning
|
/Linux-v5.15/Documentation/devicetree/bindings/sound/ |
D | fsl-sai.txt | 42 with Rx) which means both the transmitter and the 48 means both transmitter and receiver will send and 63 - If both fsl,sai-asynchronous and fsl,sai-synchronous-rx are absent, the 64 default synchronous mode (sync Rx with Tx) will be used, which means both
|
D | adi,axi-i2s.txt | 4 (capture) or both directions enabled. 15 the core. The core expects two dma channels if both transmit and receive are
|
/Linux-v5.15/fs/fat/ |
D | dir.c | 555 struct fat_ioctl_filldir_callback *both) in __fat_readdir() argument 632 if (!both) in __fat_readdir() 640 both->longname = fill_name; in __fat_readdir() 641 both->long_len = fill_len; in __fat_readdir() 642 both->shortname = bufname; in __fat_readdir() 643 both->short_len = short_len; in __fat_readdir() 763 int short_only, int both) in FAT_IOCTL_FILLDIR_FUNC() 778 short_only, both ? &buf : NULL); in FAT_IOCTL_FILLDIR_FUNC() 792 int short_only, both; in fat_dir_ioctl() local 797 both = 0; in fat_dir_ioctl() [all …]
|
/Linux-v5.15/include/linux/ |
D | futex.h | 50 } both; member 53 #define FUTEX_KEY_INIT (union futex_key) { .both = { .ptr = 0ULL } }
|
/Linux-v5.15/Documentation/devicetree/bindings/phy/ |
D | keystone-usb-phy.txt | 10 gate on the Keystone SOC for both the USB2 and USB3 PHY. Otherwise it is just 11 an NOP PHY driver. Hence this node is referenced as both the usb2 and usb3
|
/Linux-v5.15/net/hsr/ |
D | Kconfig | 19 device will be sent in both directions on the ring (over both slave 26 frames sent over the PRP device will be sent to both networks giving
|
/Linux-v5.15/Documentation/arm/sti/ |
D | overview.rst | 10 ARM Linux. Currently STiH415, STiH416 SOCs are supported with both 17 A generic configuration is provided for both STiH415/416, and can be used as the
|
/Linux-v5.15/Documentation/hwmon/ |
D | ina2xx.rst | 62 interface. The INA219 monitors both shunt drop and supply voltage, with 66 interface. The INA220 monitors both shunt drop and supply voltage. 69 The INA226 monitors both a shunt voltage drop and bus supply voltage. 72 with an I2C interface. The chips monitor both a shunt voltage drop and
|
D | ina3221.rst | 22 side of up to three D.C. power supplies. The INA3221 monitors both shunt drop 71 Affects both Bus- and Shunt-voltage conversion time. 72 Note that setting update_interval to 0ms sets both BC
|
/Linux-v5.15/arch/sparc/kernel/ |
D | unaligned_32.c | 28 both, /* Swap, ldstub, etc. */ enumerator 42 return both; in decode_direction() 245 if(!ok_for_kernel(insn) || dir == both) { in kernel_unaligned_trap()
|
/Linux-v5.15/Documentation/w1/masters/ |
D | omap-hdq.rst | 24 The controller supports operation in both HDQ and 1-wire mode. The essential 41 Please note to load both the modules with a different ID if required, but note 42 that the ID used should be same for both master and slave driver loading.
|