Searched refs:REGION (Results 1 – 2 of 2) sorted by relevance
| /Linux-v4.19/sound/drivers/opl4/ |
| D | yrw801.c | 926 #define REGION(num) { ARRAY_SIZE(regions ## num), regions ## num } macro
928 REGION(_00), REGION(_01), REGION(_02), REGION(_03),
929 REGION(_04), REGION(_05), REGION(_06), REGION(_07),
930 REGION(_08), REGION(_09), REGION(_0a), REGION(_0b),
931 REGION(_0c), REGION(_0d), REGION(_0e), REGION(_0f),
932 REGION(_10), REGION(_11), REGION(_12), REGION(_13),
933 REGION(_14), REGION(_15), REGION(_16), REGION(_17),
934 REGION(_18), REGION(_19), REGION(_1a), REGION(_1b),
935 REGION(_1c), REGION(_1d), REGION(_1e), REGION(_1f),
936 REGION(_20), REGION(_21), REGION(_22), REGION(_23),
[all …]
|
| /Linux-v4.19/Documentation/nvdimm/ |
| D | nvdimm.txt | 191 reasons to allow multiple BLK namespaces per REGION is so that each
209 (a) (b) DIMM BLK-REGION
418 A generic REGION device is registered for each PMEM range or BLK-aperture
424 LIBNVDIMM provides a built-in driver for these REGION devices. This driver
431 and "size" the REGION device also exports some convenience attributes.
515 types that we should simply name REGION devices with something derived
517 REGION name generic and expects userspace to always consider the
520 1. There are already more than two REGION and "namespace" types. For
537 for the REGION level of the device-hierarchy old userspace
605 A REGION, after resolving DPA aliasing and LABEL specified boundaries,
|
