| /linux-5.10/drivers/misc/eeprom/ |
| D | Kconfig | 32 will be called at24.
45 will be called at25.
55 This driver is deprecated and will be removed soon, please use the
59 will be called eeprom.
72 will be called max6875.
95 will be called eeprom_93xx46.
105 EEPROM 93XX46 driver. sysfs entries will be created for that
119 will be called idt_89hpesx.
130 will be called ee1004.
|
| /linux-5.10/Documentation/PCI/endpoint/ |
| D | pci-endpoint-cfs.rst | 26 functions. Every EPC device present in the system will have an entry in
28 will have an entry in the *functions* directory.
38 Every registered EPF driver will be listed in controllers directory. The
39 entries corresponding to EPF driver will be created by the EPF core.
75 Every registered EPC device will be listed in controllers directory. The
76 entries corresponding to EPC device will be created by the EPC core.
89 The <EPC Device> directory will have a list of symbolic links to
93 The <EPC Device> directory will also have a *start* field. Once
94 "1" is written to this field, the endpoint device will be ready to
|
| /linux-5.10/Documentation/networking/ |
| D | af_xdp.rst | 44 to fill in with RX packet data. References to these frames will then
61 with as well as its own newly created XSK socket. The new process will
86 hand, if the driver has support for XDP, it will be used by the AF_XDP
135 is a setup with four sockets (all doing TX and RX). Then there will be
162 running the application with aligned chunk mode, the kernel will mask
164 the addr will be masked off, meaning that 2048, 2050 and 3000 refers
166 chunks mode, then the incoming addr will be left untouched.
190 descriptors will (or can) appear on the RX ring.
221 user. It will make your program a lot simpler.
234 not match the queue configuration and netdev, the frame will be
[all …]
|
| /linux-5.10/include/linux/ |
| D | fscache.h | 107 * - the page will have been marked with PG_fscache before this is
118 * - all other fields will be set during registration
128 * - a file will only appear in one cache
372 * backing cache. The auxiliary data on the cookie will be updated first if
394 * cookie. The auxiliary data on the cookie will be updated first if @aux_data
441 * changed. This includes the data size. These attributes will be obtained
524 * it can't be, -ENOBUFS will be returned and nothing more will be done for
527 * Else, if that page is backed by the cache, a read will be initiated directly
528 * to the netfs's page and 0 will be returned by this function. The
529 * end_io_func() callback will be invoked when the operation terminates on a
[all …]
|
| /linux-5.10/Documentation/core-api/ |
| D | genalloc.rst | 26 A call to gen_pool_create() will create a pool. The granularity of
29 So, if min_alloc_order is passed as 3, then all allocations will be a
36 specific device. Among other things, it will automatically clean up the
45 given pool, this function will take the rather extreme step of invoking
58 A call to gen_pool_add() will place the size bytes of memory
62 address with the memory; this is only necessary if the pool will be used
77 As one would expect, gen_pool_alloc() will allocate size< bytes
80 address in the space pointed to by dma. This will only work if the memory
88 return. If that sort of control is needed, the following functions will be
111 size. A 60-byte allocation will thus be 64-byte aligned, for example.
[all …]
|
| D | circular-buffers.rst | 56 Typically, items will all be of the same unit size, but this isn't strictly
110 Each of these macros will nominally return a value between 0 and buffer_size-1,
114 they will return a lower bound as the producer controls the head index,
118 To the consumer it will show an upper bound as the producer may be busy
122 will return a lower bound as the consumer controls the tail index, but the
126 To the producer it will show an upper bound as the consumer may be busy
132 situation will merely be a guess, and may even be negative.
154 The producer will look something like this::
171 /* wake_up() will make sure that the head is committed before
178 This will instruct the CPU that the contents of the new item must be written
[all …]
|
| /linux-5.10/Documentation/driver-api/ |
| D | console.rst | 9 This type will be called 'system driver', and only one system driver is allowed
13 The second type has to be explicitly loaded and unloaded. This will be called
18 call do_take_over_console() will succeed in the takeover regardless of the type
21 released by the console, the system driver will take over.
26 give_up_console() - unload driver; it will only work if driver
81 hand, will bind the driver to the consoles that are currently occupied by a
93 unbinding will not succeed. An example of an application that sets the
113 be fully unbound for this call to succeed. con_is_bound() will check if the
123 or do_take_over_console(). do_register_con_driver() will just add the driver
125 console. do_take_over_console(), as it name implies, will also take over (or
[all …]
|
| /linux-5.10/tools/testing/selftests/powerpc/tm/ |
| D | tm-poison.c | 5 * This test will spawn two processes. Both will be attached to the same
6 * CPU (CPU 0). The child will be in a loop writing to FP register f31 and
9 * Parent will set f31 and vr31 to 1 and in a loop will check if f31 and
11 * present child's poison will leak into parent's f31 or vr31 registers,
12 * otherwise, poison will never leak into parent's f31 and vr31 registers.
114 * On leak 'unknown' will contain 'poison' value from child, in tm_poison_test()
115 * otherwise (no leak) 'unknown' will contain the same value in tm_poison_test()
162 * On leak 'unknown' will contain 'poison' value from child, in tm_poison_test()
163 * otherwise (no leak) 'unknown' will contain the same value in tm_poison_test()
|
| /linux-5.10/Documentation/admin-guide/laptops/ |
| D | sony-laptop.rst | 20 Additionally, loading the driver with the debug option will report all events
30 If your laptop model supports it, you will find sysfs files in the
32 directory. You will be able to query and set the current screen
38 actual_brightness reading from this file will query the HW
46 Loading the sony-laptop module will create a
56 brightness_default screen brightness which will be set
57 when the laptop will be rebooted
104 such a laptop you will find the necessary rfkill devices under
121 In your kernel logs you will find the list of all ACPI methods
124 * For new models you will see a long list of meaningless method names,
[all …]
|
| /linux-5.10/drivers/of/unittest-data/ |
| D | overlay_bad_add_dup_prop.dts | 9 * Thus the property "rpm_avail" in each fragment will
11 * This will result in an error and the overlay apply
12 * will fail.
18 * will occur if the overlay is removed. Since the overlay apply
19 * fails, the memory leak does actually occur, and kmemleak will
22 * memory leak and thus people who use kmemleak will not
|
| /linux-5.10/arch/um/drivers/ |
| D | Kconfig | 37 you telnet to that portal will be unpredictable.
47 will be announced in the kernel message log.
63 lines to xterms. Each UML device so assigned will be brought up in
76 will be attached by default. This value can be overridden from the
86 except the main console will be attached by default. This value can
98 will be attached by default. This value can be overridden from the
108 This option enables UML sound support. If enabled, it will pull in
170 NOTE: THIS TRANSPORT IS DEPRECATED AND WILL BE REMOVED SOON!!! Please
180 packets with the host over a TUN/TAP device. This option will only
187 NOTE: THIS TRANSPORT IS DEPRECATED AND WILL BE REMOVED SOON!!! Please
[all …]
|
| /linux-5.10/drivers/net/ethernet/aquantia/atlantic/macsec/ |
| D | macsec_api.h | 50 * rec - [OUT] The raw table row data will be unpacked into the fields of rec.
68 * rec - [OUT] The raw table row data will be unpacked into the fields of rec.
86 * rec - [OUT] The raw table row data will be unpacked into the fields of rec.
104 * rec - [OUT] The raw table row data will be unpacked into the fields of rec.
122 * rec - [OUT] The raw table row data will be unpacked into the fields of rec.
140 * rec - [OUT] The raw table row data will be unpacked into the fields of rec.
158 * rec - [OUT] The raw table row data will be unpacked into the fields of rec.
176 * rec - [OUT] The raw table row data will be unpacked into the fields of rec.
194 * rec - [OUT] The raw table row data will be unpacked into the fields of rec.
212 * rec - [OUT] The raw table row data will be unpacked into the fields of rec.
[all …]
|
| /linux-5.10/drivers/regulator/ |
| D | devres.c | 104 * this function will not need to be called and the resource management
105 * code will ensure that the resource is freed.
140 * consumers in one operation with management, the regulators will
143 * allocated will be freed before returning to the caller.
182 * error. The regulator will automatically be released when the device
224 * Normally this function will not need to be called and the resource
225 * management code will ensure that the resource is freed.
268 * The supply alias will automatically be unregistered when the source
308 * will not need to be called and the resource management code
309 * will ensure that the resource is freed.
[all …]
|
| /linux-5.10/drivers/misc/habanalabs/include/common/ |
| D | cpucp_if.h | 62 * communication from the host's driver to CpuCP will *always* be in
63 * synchronous mode, meaning that the host will send a single message and poll
74 * The message, inputs/outputs (if relevant) and fence object will be located
75 * on the device DDR at an address that will be determined by the host's driver.
76 * During device initialization phase, the host will pass to CpuCP that address.
77 * Most of the message types will contain inputs/outputs inside the message
78 * itself. The common part of each message will contain the opcode of the
81 * When the host's driver wishes to send a message to CPU CP, it will write the
85 * Upon receiving the interrupt (#121), CpuCP will read the message from the
86 * DDR. In case the message is a SET operation, CpuCP will first perform the
[all …]
|
| /linux-5.10/arch/sparc/include/asm/ |
| D | estate.h | 27 * 1) As the result of an instruction fetch, will generate instruction_access_error
28 * 2) As the result of a load etc. will generate data_access_error.
29 * 3) As the result of store merge completion, writeback, or copyout will
39 * reads resulting in a hardware corrected data or MTAG ECC error will generate an
42 * This same trap will also be generated when a hardware corrected ECC error results
46 /* In general, if the trap enable bits above are disabled the AFSR bits will still
47 * log the events even though the trap will not be generated by the processor.
|
| /linux-5.10/lib/ |
| D | Kconfig.debug | 43 Default loglevel to determine what will be printed on the console.
61 will be used as the loglevel. IOW passing "quiet" will be the
184 If you say Y here, the kernel's printf implementation will
206 If you say Y here the resulting kernel image will include
274 Turning this on expects presence of pahole tool, which will convert
282 scripts will be automatically imported by gdb as well, and
306 Setting this too low will cause a lot of warnings.
330 This option will install uapi headers (headers exported to user-space)
361 If you say N here, the build process will fail if there are any
371 bump (regression or improvement). Enable this option will help to
[all …]
|
| /linux-5.10/Documentation/kbuild/ |
| D | makefiles.rst | 131 file will be used.
150 foo.o. foo.o will be built from foo.c or foo.S.
160 If CONFIG_FOO is neither y nor m, then the file will not be compiled
172 This is a thin archive without a symbol table. It will be later
176 the lists are allowed: the first instance will be linked into
177 built-in.a and succeeding instances will be ignored.
180 (module_init() / __initcall) will be called during boot in the
222 In this example, the module name will be isdn.o. Kbuild will
244 the syntax above will also work. So, if you have CONFIG_EXT2_FS=y,
245 kbuild will build an ext2.o file for you out of the individual
[all …]
|
| /linux-5.10/Documentation/scsi/ |
| D | scsi_fc_transport.rst | 51 interact with the Fabric Port to join multiple fabrics. The port will
52 obtain an N_Port_ID on each fabric it joins. Each fabric will have its
61 expected. Once instantiated by one of the above methods, it will have a
63 The fc_host associated with the physical adapter will export the ability
64 to create vports. The transport will create the vport object within the
66 virtual port. Typically, the driver will create a new scsi_host instance
69 each will appear as a unique scsi_host with its own target and lun space.
75 discussion will concentrate on NPIV.
92 object corresponding to the physical adapter. The LLDD will allocate
99 a symbolic link to the vport object will be placed in the physical
[all …]
|
| /linux-5.10/Documentation/process/ |
| D | stable-api-nonsense.rst | 20 will not break. I have old programs that were built on a pre 0.9something
54 kernel source interfaces. They both depend on each other, but we will
65 data structures will contain different alignment of structures, and
81 There is no way that binary drivers from one architecture will run
94 different options), so for even a single release you will need to create
97 Trust me, you will go insane over time if you try to support this kind
139 relatively little pain. If Linux had to ensure that it will preserve a
176 it will be fixed up by the person who did the kernel change in the first
183 - The quality of the driver will rise as the maintenance costs (to the
184 original developer) will decrease.
[all …]
|
| /linux-5.10/Documentation/filesystems/ |
| D | tmpfs.rst | 10 Everything in tmpfs is temporary in the sense that no files will be
26 pages will be shown as "Shmem" in /proc/meminfo and "Shared" in
33 1) There is always a kernel internal mount which you will not see at
68 oversize your tmpfs instances the machine will deadlock
69 since the OOM handler will not be able to free that memory.
82 If nr_blocks=0 (or size=0), blocks will not be limited in that instance;
83 if nr_inodes=0, inodes will not be limited. It is generally unwise to
107 A memory policy with a valid NodeList will be saved, as specified, for
109 system, the mount option memory policy will be applied with a NodeList,
113 memory policy for the file will revert to "default" policy.
[all …]
|
| D | adfs.rst | 25 on a RISC OS Filecore filesystem, but will allow the data within files
35 uid=nnn All files in the partition will be owned by
37 gid=nnn All files in the partition will be in group
40 will be nnn. Default 0700.
42 will be nnn. Default 0077.
43 ftsuffix=n When ftsuffix=0, no file type suffix will be applied.
45 the RISC OS file type will be added. Default 0.
77 not a UnixExec filetype, then the permissions will be::
106 Mounting an ADFS disc with option ftsuffix=1 will cause appropriate file
108 ftsuffix option is zero or omitted, no file type suffixes will be added.
|
| /linux-5.10/tools/include/uapi/linux/ |
| D | stat.h | 67 * parameter to statx(). What statx() actually got will be indicated in
74 * - the bit will be cleared, and
76 * - the datum will be set to an appropriate fabricated value if one is
79 * - the field will be cleared;
83 * - the datum will be synchronised to the server if AT_STATX_FORCE_SYNC is
86 * - the field will be filled in and the bit will be set;
89 * effort, it will be filled in anyway, and the bit will be set upon return
90 * (it might not be up to date, however, and no attempt will be made to
93 * - otherwise the field and the bit will be cleared before returning.
96 * will have values installed for compatibility purposes so that stat() and
|
| /linux-5.10/include/uapi/linux/ |
| D | stat.h | 67 * parameter to statx(). What statx() actually got will be indicated in
74 * - the bit will be cleared, and
76 * - the datum will be set to an appropriate fabricated value if one is
79 * - the field will be cleared;
83 * - the datum will be synchronised to the server if AT_STATX_FORCE_SYNC is
86 * - the field will be filled in and the bit will be set;
89 * effort, it will be filled in anyway, and the bit will be set upon return
90 * (it might not be up to date, however, and no attempt will be made to
93 * - otherwise the field and the bit will be cleared before returning.
96 * will have values installed for compatibility purposes so that stat() and
|
| /linux-5.10/drivers/uio/ |
| D | Kconfig | 26 will be called uio_cif.
73 If you compile this as a module, it will be called uio_aec.
80 Automata GmbH. The userspace part of this driver will be
86 If you compile this as a module, it will be called uio_sercos3.
95 If you compile this as a module, it will be called uio_pci_generic.
106 will be called uio_netx.
121 This will add support for netX 51/52 devices connected via eLBC/GPCM.
144 will be called uio_pruss.
157 If you compile this as a module, it will be called uio_mf624.
167 If you compile this as a module, it will be called uio_hv_generic.
|
| /linux-5.10/fs/xfs/ |
| D | Kconfig | 21 module will be called xfs. Be aware, however, that if the file
43 This option will become default N in September 2025. Support for the
44 V4 format will be removed entirely in September 2030. Distributors
55 If you say Y here, you will be able to set limits for disk usage on
82 If you say Y here you will be able to mount and use XFS filesystems
101 If you say Y here you will be able to check metadata on a
118 If you say Y here you will be able to repair metadata on a
136 It converts ASSERT checks to WARN, so will log any out-of-bounds
138 lighter weight than XFS_DEBUG and does not modify algorithms and will
152 Note that the resulting code will be HUGE and SLOW, and probably
|