| /Linux-v5.10/fs/nfs/blocklayout/ |
| D | extent_tree.c | 26 ext_tree_prev(struct pnfs_block_extent *be) in ext_tree_prev() argument
28 struct rb_node *node = rb_prev(&be->be_node); in ext_tree_prev()
33 ext_tree_next(struct pnfs_block_extent *be) in ext_tree_next() argument
35 struct rb_node *node = rb_next(&be->be_node); in ext_tree_next()
40 ext_f_end(struct pnfs_block_extent *be) in ext_f_end() argument
42 return be->be_f_offset + be->be_length; in ext_f_end()
49 struct pnfs_block_extent *be = NULL; in __ext_tree_search() local
52 be = ext_node(node); in __ext_tree_search()
53 if (start < be->be_f_offset) in __ext_tree_search()
55 else if (start >= ext_f_end(be)) in __ext_tree_search()
[all …]
|
| /Linux-v5.10/drivers/hwmon/ |
| D | Kconfig | 23 This support can also be built as a module. If so, the module
24 will be called hwmon.
51 This driver can also be built as a module. If so, the module
52 will be called abx500-temp.
61 chip can be found on Abit uGuru featuring motherboards (most modern
66 This driver can also be built as a module. If so, the module
67 will be called abituguru.
76 uGuru chip can be found on recent Abit motherboards (since end
80 This driver can also be built as a module. If so, the module
81 will be called abituguru3.
[all …]
|
| /Linux-v5.10/drivers/hwmon/pmbus/ |
| D | Kconfig | 12 This driver can also be built as a module. If so, the module will
13 be called pmbus_core.
26 This driver can also be built as a module. If so, the module will
27 be called pmbus.
37 This driver can also be built as a module. If so, the module will
38 be called adm1266.
47 This driver can also be built as a module. If so, the module will
48 be called adm1275.
56 This driver can also be built as a module. If so, the module will
57 be called bel-pfe.
[all …]
|
| /Linux-v5.10/drivers/rtc/ |
| D | Kconfig | 20 be allowed to plug one or more RTCs to your system. You will
29 If you say yes here, the system time (wall clock) will be set using
38 The RTC device that will be used to (re)initialize the system
44 This clock should be battery-backed, so that it reads the correct
49 be useful to reinitialize system time when resuming from system
57 If you say yes here, the system time (wall clock) will be stored
105 Other RTCs will not be available through that API.
120 can be accessed as /dev/rtc, which is a name
142 RTC test driver. It's a software RTC which can be
149 This driver can also be built as a module. If so, the module
[all …]
|
| /Linux-v5.10/drivers/i2c/busses/ |
| D | Kconfig | 16 If you say yes to this option, support will be included for the SMB
21 This driver can also be built as a module. If so, the module
22 will be called i2c-ali1535.
28 If you say yes to this option, support will be included for the SMB
33 This driver can also be built as a module. If so, the module
34 will be called i2c-ali1563.
40 If you say yes to this option, support will be included for the
43 This driver can also be built as a module. If so, the module
44 will be called i2c-ali15x3.
50 If you say yes to this option, support will be included for the AMD
[all …]
|
| /Linux-v5.10/tools/perf/util/ |
| D | genelf_debug.c | 46 buffer_ext_dump(struct buffer_ext *be, const char *msg) in buffer_ext_dump() argument
50 for (i = 0 ; i < be->cur_pos; i++) in buffer_ext_dump()
51 warnx("%4zu 0x%02x", i, (((char *)be->data)[i]) & 0xff); in buffer_ext_dump()
55 buffer_ext_add(struct buffer_ext *be, void *addr, size_t sz) in buffer_ext_add() argument
58 size_t be_sz = be->max_sz; in buffer_ext_add()
61 if ((be->cur_pos + sz) < be_sz) { in buffer_ext_add()
62 memcpy(be->data + be->cur_pos, addr, sz); in buffer_ext_add()
63 be->cur_pos += sz; in buffer_ext_add()
72 tmp = realloc(be->data, be_sz); in buffer_ext_add()
76 be->data = tmp; in buffer_ext_add()
[all …]
|
| /Linux-v5.10/drivers/iio/adc/ |
| D | Kconfig | 39 To compile this driver as a module, choose M here: the module will be
52 module will be called ad7192.
64 To compile this driver as a module, choose M here: the module will be
75 module will be called ad7291.
85 module will be called ad7292.
97 module will be called ad7298.
113 module will be called ad7476.
129 module will be called ad7606_parallel.
140 module will be called ad7606_spi.
151 To compile this driver as a module, choose M here: the module will be
[all …]
|
| /Linux-v5.10/Documentation/filesystems/caching/ |
| D | netfs-api.rst | 59 This first two fields should be filled in before registration, and the third
60 will be filled in by the registration function; any other fields should just be
68 entire in-cache hierarchy for this netfs will be scrapped and begun
71 (3) The cookie representing the primary index will be allocated according to
105 (1) Any index containing non-index objects should be restricted to a single
106 cache. Any such objects created within an index will be created in the
107 first cache only. The cache in which an index is created can be
110 (2) The entry data must be atomically journallable, so it is limited to about
111 400 bytes at present. At least 400 bytes will be available.
113 (3) The depth of the index tree should be judged with care as the search
[all …]
|
| D | backend-api.rst | 7 The FS-Cache system provides an API by which actual caches can be supplied to
17 To start off, a cache definition must be initialised and registered for each
21 The cache definition (struct fscache_cache) should be initialised by calling::
39 The cache should then be registered with FS-Cache by passing a pointer to the
46 Two extra arguments should also be supplied:
49 master index in this cache. Netfs primary index entries will be created
53 * "tagname" which, if given, should be a text string naming this cache. If
54 this is NULL, the identifier will be used instead. For CacheFS, the
55 identifier is set to name the underlying block device and the tag can be
59 is already in use. 0 will be returned on success.
[all …]
|
| /Linux-v5.10/Documentation/security/keys/ |
| D | core.rst | 6 user mappings, and similar to be cached in the kernel for the use of
13 The key service can be configured on by enabling:
46 * Each key is of a defined "type". Types must be registered inside the
48 can be added or used. Userspace programs cannot define new types directly.
51 number of operations that can be performed on a key of that type.
53 Should a type be removed from the system, all the keys of that type will
54 be invalidated.
56 * Each key has a description. This should be a printable string. The key
62 whether a kernel service will be able to find the key.
64 * Each key can be set to expire at a specific time by the key type's
[all …]
|
| /Linux-v5.10/net/sched/ |
| D | Kconfig | 17 is a FIFO (first come, first served). If you say Y here, you will be
19 then be attached to different network devices. This is useful for
23 This code is considered to be experimental.
37 If you say Y here and to "/proc file system" below, you will be able
63 module will be called sch_cbq.
77 module will be called sch_htb.
86 module will be called sch_hfsc.
100 module will be called sch_atm.
109 module will be called sch_prio.
118 module will be called sch_multiq.
[all …]
|
| /Linux-v5.10/Documentation/networking/ |
| D | rxrpc.rst | 8 that can be used to perform RxRPC remote operations. This is done over sockets
68 manage security on the client end. The server end must of necessity be
99 endpoint, thus allowing the endpoints to be shared, even to the same
103 to multiple services. A service may be considered the RxRPC equivalent of
106 (#) Client-originating packets are marked, thus a transport endpoint can be
110 (#) Up to a billion connections may be supported concurrently between one
123 billion calls, but only up to four calls may be in progress on a
143 connection lapse before the client, the security will be renegotiated if
152 been received but may yet be discarded and re-requested. The sender may
162 (#) An call may be aborted by either end at any time up to its completion.
[all …]
|
| /Linux-v5.10/fs/btrfs/ |
| D | ref-verify.c | 27 * be used to verify the extent tree is consistent as these should all match
45 * were called with since it could be different from ref_root. We also store
76 struct block_entry *be) in insert_block_entry() argument
85 if (entry->bytenr > be->bytenr) in insert_block_entry()
87 else if (entry->bytenr < be->bytenr) in insert_block_entry()
93 rb_link_node(&be->node, parent_node, p); in insert_block_entry()
94 rb_insert_color(&be->node, root); in insert_block_entry()
232 static void free_block_entry(struct block_entry *be) in free_block_entry() argument
239 while ((n = rb_first(&be->roots))) { in free_block_entry()
241 rb_erase(&re->node, &be->roots); in free_block_entry()
[all …]
|
| /Linux-v5.10/Documentation/arm64/ |
| D | booting.rst | 20 hypervisor code, or it may just be a handful of instructions for
50 The device tree blob (dtb) must be placed on an 8-byte boundary and must
51 not exceed 2 megabytes in size. Since the dtb will be mapped cacheable
52 using blocks of up to 2 megabytes in size, it must not be placed within
53 any 2M region which must be mapped with any specific attributes.
55 NOTE: versions prior to v4.2 also require that the DTB be placed within
64 therefore requires decompression (gzip etc.) to be performed by the boot
103 little-endian and must be respected. Where image_size is zero,
104 text_offset can be assumed to be 0x80000.
110 Bit 0 Kernel endianness. 1 if BE, 0 if LE.
[all …]
|
| D | acpi_object_usage.rst | 34 Must be supplied if RAS support is provided by the platform. It
35 is recommended this table be supplied.
41 Microsoft only table, will not be supported.
68 License has changed and should be usable. Optional if used instead
75 Microsoft only table, will not be supported.
91 x86 only table, will not be supported.
103 Optional, not currently supported, but could be used on ARM if and
106 need to be modified in the ACPI specification.
114 if it had actually occurred. However, this table should not be
115 shipped with a production system; it should be dynamically loaded
[all …]
|
| /Linux-v5.10/Documentation/admin-guide/ |
| D | md.rst | 7 Tools that manage md devices can be found at
82 This autodetection may be suppressed with the kernel parameter
84 superblock can be autodetected and run at boot time.
94 ``dirty`` means that the parity cannot be trusted, and the fact that it
96 be reconstructed (due to no parity).
108 arrays to be started.
136 be accessed.
138 An array should be created by a user-space tool. This will write
147 format is to be used. The minor number might be used to tune handling
157 Once started, new devices can be added. They should have an
[all …]
|
| /Linux-v5.10/drivers/input/misc/ |
| D | Kconfig | 8 Say Y here, and a list of miscellaneous input drivers will be displayed.
24 will be called 88pm860x_onkey.
34 will be called 88pm80x_onkey.
44 will be called ab8500-ponkey.
54 module will be called ad714x.
64 module will be called ad714x-i2c.
74 module will be called ad714x-spi.
84 module will be called arizona-haptics.
98 module will be called atmel_captouch.
108 module will be called bma150.
[all …]
|
| /Linux-v5.10/drivers/net/xen-netback/ |
| D | xenbus.c | 13 static int connect_data_rings(struct backend_info *be,
15 static void connect(struct backend_info *be);
16 static int read_xenbus_vif_flags(struct backend_info *be);
17 static int backend_create_xenvif(struct backend_info *be);
18 static void unregister_hotplug_status_watch(struct backend_info *be);
20 static void set_backend_state(struct backend_info *be,
206 struct backend_info *be = dev_get_drvdata(&xdev->dev); in netback_uevent() local
208 if (!be) in netback_uevent()
211 if (add_uevent_var(env, "script=%s", be->hotplug_script)) in netback_uevent()
214 if (!be->vif) in netback_uevent()
[all …]
|
| /Linux-v5.10/drivers/i2c/muxes/ |
| D | Kconfig | 14 If you say yes to this option, support will be included for an
19 This driver can also be built as a module. If so, the module
20 will be called i2c-arb-gpio-challenge.
26 If you say yes to this option, support will be included for a
31 This driver can also be built as a module. If so, the module
32 will be called i2c-mux-gpio.
39 If you say yes to this option, support will be included for a
44 This driver can also be built as a module. If so, the module
45 will be called i2c-mux-gpmux.
55 This driver can also be built as a module. If so, the module
[all …]
|
| /Linux-v5.10/Documentation/process/ |
| D | 4.Coding.rst | 6 While there is much to be said for a solid and community-oriented design
8 code. It is the code which will be examined by other developers and merged
34 the standard; many developers will request that the code be reformatted
42 win before the code can be merged. Putting code into the kernel means
53 on it for other reasons, but coding style changes should not be made for
56 The coding style document also should not be read as an absolute law which
57 can never be transgressed. If there is a good reason to go against the
77 But experience has shown that excessive or premature abstraction can be
78 just as harmful as premature optimization. Abstraction should be used to
89 patches to remove unused arguments; they should, in general, not be added
[all …]
|
| /Linux-v5.10/drivers/nvmem/ |
| D | Kconfig | 32 This driver can also be built as a module. If so, the module
33 will be called nvmem-imx-iim.
44 This driver can also be built as a module. If so, the module
45 will be called nvmem-imx-ocotp.
65 will be called nvmem_jz4780_efuse.
75 will be called nvmem_lpc18xx_eeprom.
85 will be called nvmem_lpc18xx_otp.
96 This driver can also be built as a module. If so, the module
97 will be called nvmem-mxs-ocotp.
107 This driver can also be built as a module. If so, the module
[all …]
|
| /Linux-v5.10/sound/soc/ |
| D | soc-pcm.c | 97 struct snd_soc_pcm_runtime *be = dpcm->be; in dpcm_show_state() local
101 "- %s\n", be->dai_link->name); in dpcm_show_state()
105 dpcm_state_string(be->dpcm[stream].state)); in dpcm_show_state()
107 if ((be->dpcm[stream].state >= SND_SOC_DPCM_STATE_HW_PARAMS) && in dpcm_show_state()
108 (be->dpcm[stream].state <= SND_SOC_DPCM_STATE_STOP)) in dpcm_show_state()
179 name = kasprintf(GFP_KERNEL, "%s:%s", dpcm->be->dai_link->name, in dpcm_create_debugfs_state()
215 * Should typically be called when a stream is opened.
217 * Must be called with the rtd->card->pcm_mutex being held
234 * @rtd: The ASoC PCM runtime that should be checked.
236 * This function checks whether the power down delay should be ignored for a
[all …]
|
| /Linux-v5.10/drivers/staging/comedi/ |
| D | Kconfig | 30 be requested by a userspace program without root privileges.
37 Enable comedi misc drivers to be built
54 To compile this driver as a module, choose M here: the module will be
61 This driver is mainly for testing purposes, but can also be used to
65 To compile this driver as a module, choose M here: the module will be
76 To compile this driver as a module, choose M here: the module will be
85 To compile this driver as a module, choose M here: the module will be
93 Enable comedi ISA and PC/104 drivers to be built
107 To compile this driver as a module, choose M here: the module will be
128 To compile this driver as a module, choose M here: the module will be
[all …]
|
| /Linux-v5.10/drivers/iio/light/ |
| D | Kconfig | 21 be called acpi-als.
32 This driver can also be built as a module. If so, the module
33 will be called adjd_s311.
44 module will be called adux1020.
54 module will be called al3010.
64 module will be called al3320a.
74 module will be called apds9300.
87 module will be called apds9960
101 This driver can also be built as a module. If so, the module
102 will be called as73211.
[all …]
|
| /Linux-v5.10/Documentation/driver-api/ |
| D | vme.rst | 12 be provided to the registration function. Along with the maximum number of
16 :c:type:`struct vme_driver <vme_driver>` should be correctly set. The '.name'
19 The '.match' function allows control over which VME devices should be registered
20 with the driver. The match function should return 1 if a device should be
40 driver. The bridge number (or bus number) can be accessed using
44 :c:func:`vme_unregister_driver` and should usually be called from the device
52 be called the number of times specified during the registration. If a match
53 succeeds, a non-zero value should be returned. A zero return value indicates
56 device structure. This pointer should be saved, it will be required for
62 driver to request a specific window or DMA channel (which may be used by a
[all …]
|
