Home
last modified time | relevance | path

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

12

/linux/Documentation/ABI/testing/
H A 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/Documentation/admin-guide/device-mapper/
H A 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
H A Ddm-init.rst41 activation of certain DM targets without first using userspace tools to check
H A Dcache-policies.rst55 DM table that is using the cache target. Doing so will cause all of the
/linux/Documentation/gpu/amdgpu/display/
H A Ddisplay-manager.rst18 :doc: DM Lifecycle
131 (DM) to program the blending configuration of the Multiple Pipe/Plane Combined
149 DM then maps the elements of `enum mpcc_alpha_blend_mode` to those in the DRM
172 1. When updating a :c:type:`drm_plane_state <drm_plane_state>`, DM calls
H A Dindex.rst12 #. **Display Manager (DM)** contains the OS-dependent components. Hooks to the
/linux/drivers/staging/gdm724x/
H A DKconfig12 used for AT commands and DM monitoring applications.
/linux/arch/arm64/boot/dts/ti/
H A Dk3-am62p.dtsi113 <0x00 0x78000000 0x00 0x78000000 0x00 0x00008000>, /* DM R5 ATCM*/
114 <0x00 0x78100000 0x00 0x78100000 0x00 0x00008000>; /* DM R5 BTCM*/
H A Dk3-am62a-wakeup.dtsi75 /* Used by DM firmware */
H A Dk3-am62-wakeup.dtsi100 /* Used by DM firmware */
H A Dk3-j722s.dtsi219 <0x00 0x78000000 0x00 0x78000000 0x00 0x00008000>, /* DM R5 ATCM*/
220 <0x00 0x78100000 0x00 0x78100000 0x00 0x00008000>; /* DM R5 BTCM*/
H A Dk3-am62p-j722s-common-wakeup.dtsi78 /* Used by DM firmware */
/linux/drivers/isdn/mISDN/
H A Dlayer2.h101 #define DM 0x0f macro
/linux/Documentation/admin-guide/media/
H A Domap3isp.rst85 DM 3730 TRM:
/linux/Documentation/devicetree/bindings/spi/
H A Dspi-davinci.txt3 Links on DM:
/linux/Documentation/translations/zh_CN/video4linux/
H A Domap3isp.txt268 DM 3730 TRM:
/linux/drivers/tty/
H A Dn_gsm.c377 #define DM 0x0F macro
732 case DM: in gsm_print_packet()
2250 } else if (!dlci->addr && gsm->control == (DM | PF)) { in gsm_dlci_t1()
2792 gsm_response(gsm, address, DM|PF); in gsm_queue()
2802 gsm_response(gsm, address, DM|PF); in gsm_queue()
2825 case DM: /* DM can be valid unsolicited */ in gsm_queue()
2826 case DM|PF: in gsm_queue()
2838 gsm_response(gsm, address, DM|PF); in gsm_queue()
/linux/include/trace/events/
H A Drdma_core.h279 ib_mr_type_item(DM) \
/linux/Documentation/filesystems/
H A 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/drivers/md/
H A DKconfig478 bool "DM \"dm-mod.create=\" parameter support"
490 bool "DM uevents"
493 Generate udev events for DM events.
637 bool "DM audit events"
/linux/Documentation/scsi/
H A DChangeLog.arcmsr94 ** while Linux XFS over DM-CRYPT.
/linux/drivers/scsi/sym53c8xx_2/
H A Dsym_defs.h156 #define DM 0x04 /* sta: DIFFSENS mismatch (895/6 only) */ macro
/linux/arch/arm/mach-omap2/
H A DKconfig2 menu "TI OMAP/AM/DM/DRA Family"
/linux/sound/firewire/
H A DKconfig106 * Tascam IF-FW/DM
/linux/Documentation/security/
H A Dipe.rst27 2. DM-Verity
29 Both options were carefully considered, however the choice to use DM-Verity
50 With DM-Verity, as the xattrs are saved as part of the Merkel tree, if

12