Home
last modified time | relevance | path

Searched refs:DM (Results 1 – 25 of 34) sorted by relevance

12

/linux-5.19.10/Documentation/ABI/testing/
Dsysfs-block-dm14 Read-only string containing DM-UUID or empty string
15 if DM-UUID is not set.
36 request-based DM's merge heuristic and associated extra
38 bio-based DM devices so it will only ever report 0 for
/linux-5.19.10/Documentation/admin-guide/device-mapper/
Dstatistics.rst2 DM statistics
6 regions of a DM device. If no regions are defined no statistics are
7 collected so there isn't any performance impact. Only bio-based DM
20 the @stats_print message to the appropriate DM device via dmsetup.
30 request and process statistics for the same DM device without stepping
33 The creation of DM statistics will allocate memory via kmalloc or
35 memory may be allocated by DM statistics. The admin can see how much
205 Subdivide the DM device 'vol' into 100 pieces and start collecting
Ddm-init.rst41 activation of certain DM targets without first using userspace tools to check
Dcache-policies.rst55 DM table that is using the cache target. Doing so will cause all of the
/linux-5.19.10/drivers/staging/gdm724x/
DKconfig12 used for AT commands and DM monitoring applications.
/linux-5.19.10/Documentation/gpu/amdgpu/display/
Ddisplay-manager.rst18 :doc: DM Lifecycle
Dindex.rst12 2. **Display Manager (DM)** contains the OS-dependent components. Hooks to the
/linux-5.19.10/drivers/isdn/mISDN/
Dlayer2.h101 #define DM 0x0f macro
/linux-5.19.10/Documentation/admin-guide/media/
Domap3isp.rst85 DM 3730 TRM:
/linux-5.19.10/drivers/tty/
Dn_gsm.c306 #define DM 0x0F macro
599 case DM: in gsm_print_packet()
1809 } else if (!dlci->addr && gsm->control == (DM | PF)) { in gsm_dlci_t1()
2160 gsm_response(gsm, address, DM|PF); in gsm_queue()
2170 gsm_response(gsm, address, DM|PF); in gsm_queue()
2193 case DM: /* DM can be valid unsolicited */ in gsm_queue()
2194 case DM|PF: in gsm_queue()
2206 gsm_response(gsm, address, DM|PF); in gsm_queue()
/linux-5.19.10/Documentation/devicetree/bindings/spi/
Dspi-davinci.txt3 Links on DM:
/linux-5.19.10/Documentation/translations/zh_CN/video4linux/
Domap3isp.txt268 DM 3730 TRM:
/linux-5.19.10/Documentation/devicetree/bindings/memory-controllers/
Drockchip,rk3399-dmc.yaml163 (including DQS/DQ/DM line) drive strength.
211 (including DQS/DQ/DM line) drive strength.
274 (including DQS/DQ/DM line) drive strength.
/linux-5.19.10/include/trace/events/
Drdma_core.h279 ib_mr_type_item(DM) \
/linux-5.19.10/Documentation/filesystems/
Dubifs-authentication.rst32 layer, the dm-integrity or dm-verity subsystems [DM-INTEGRITY, DM-VERITY]
442 [DM-INTEGRITY] https://www.kernel.org/doc/Documentation/device-mapper/dm-integrity.rst
444 [DM-VERITY] https://www.kernel.org/doc/Documentation/device-mapper/verity.rst
/linux-5.19.10/drivers/md/
DKconfig498 bool "DM \"dm-mod.create=\" parameter support"
510 bool "DM uevents"
513 Generate udev events for DM events.
648 bool "DM audit events"
/linux-5.19.10/Documentation/scsi/
DChangeLog.arcmsr94 ** while Linux XFS over DM-CRYPT.
/linux-5.19.10/drivers/scsi/sym53c8xx_2/
Dsym_defs.h156 #define DM 0x04 /* sta: DIFFSENS mismatch (895/6 only) */ macro
/linux-5.19.10/sound/firewire/
DKconfig106 * Tascam IF-FW/DM
/linux-5.19.10/Documentation/devicetree/bindings/usb/
Dqcom,dwc3.yaml101 - description: Wakeup event on DM line.
/linux-5.19.10/arch/arm/mach-omap2/
DKconfig2 menu "TI OMAP/AM/DM/DRA Family"
/linux-5.19.10/Documentation/networking/device_drivers/ethernet/intel/
De1000e.rst286 - Intel(R) 82578DM Gigabit Network Connection
301 - Intel(R) 82566DM Gigabit Network Connection
/linux-5.19.10/arch/arm64/boot/dts/ti/
Dk3-am625-sk.dts272 /* WKUP UART0 is used by DM firmware */
/linux-5.19.10/drivers/scsi/
Dncr53c8xx.h677 #define DM 0x04 /* sta: DIFFSENS mismatch (895/6 only) */ macro
/linux-5.19.10/Documentation/networking/
Dlapb-module.rst102 connected, it sends DM without polls set, every T1. The upper case constant

12