| /linux-6.15/Documentation/maintainer/ |
| D | pull-requests.rst | 22 To start with you will need to have all the changes you wish to include in
23 the pull request on a separate branch. Typically you will base this branch
40 that will create a signed tag called ``char-misc-4.15-rc1`` based on the
44 Linus will only accept pull requests based on a signed tag. Other
47 When you run the above command ``git`` will drop you into an editor and ask
50 any, testing has been done. All of this information will end up in the tag
52 merge the pull request. So write it up well, as it will be in the kernel
65 that you don't maintain, explain _why_. I will see it in the
72 I will take both what you write in the email pull request _and_ in
74 describe your work in the signed tag (which will also automatically
[all …]
|
| /linux-6.15/Documentation/i2c/ |
| D | slave-testunit-backend.rst | 35 After that, you will have the device listening. Reading will return a single
55 DELAY is a generic parameter which will delay the execution of the test in CMD.
56 While a command is running (including the delay), new commands will not be
59 The commands are described in the following section. An invalid command will
89 access the bus at the same time, the bus will be busy. Example to read 128
110 Also needs master mode. This test will send an SMBUS_HOST_NOTIFY message to the
133 - 0x01 (i.e. one further byte will be written)
137 Partial command. This test will respond to a block process call as defined by
139 will be sent back in the following read transfer. Note that in this read
140 transfer, the testunit will prefix the length of the bytes to follow. So, if
[all …]
|
| /linux-6.15/Documentation/hid/ |
| D | hidraw.rst | 26 use the HID specification, hidraw will be expanded to add support for these
30 create hidraw device nodes. Udev will typically create the device nodes
44 read() will read a queued report received from the HID device. On USB
46 on the INTERRUPT IN endpoint. By default, read() will block until there is
52 will be the report number; the report data follows, beginning in the second
54 will begin at the first byte.
58 The write() function will write a report to the device. For USB devices, if
59 the device has an INTERRUPT OUT endpoint, the report will be sent on that
60 endpoint. If it does not, the report will be sent over the control endpoint,
74 This ioctl will get the size of the device's report descriptor.
[all …]
|
| /linux-6.15/Documentation/mm/ |
| D | free_page_reporting.rst | 11 it will allocate and initialize a page_reporting_dev_info structure. The
12 field within the structure it will populate is the "report" function
15 call to the function. A call to page_reporting_register will register the
19 Once registered the page reporting API will begin reporting batches of
20 pages to the driver. The API will start reporting pages 2 seconds after
21 the interface is registered and will continue to do so 2 seconds after any
24 Pages reported will be stored in the scatterlist passed to the reporting
26 While pages are being processed by the report function they will not be
28 the pages will be returned to the free area from which they were obtained.
33 reporting removed. Doing this will prevent further reports from being
|
| /linux-6.15/Documentation/trace/ |
| D | stm.rst | 29 are consistent with what decoder expects, it will be able to properly
50 with "user" identification string will be allocated a master and
54 under "user" directory from the example above and this new rule will
67 stm core will try to find a policy node with the name matching the
68 task's name (e.g., "syslogd") and if one exists, it will be used.
70 catch-all entry "default" will be used, if it exists. This entry also
74 will return a error (EINVAL).
80 will help programmers and sysadmins identify gaps in configuration
85 mmu) will usually contain multiple channels' mmios, so the user will
109 Each stm_source device will need to assume a master and a range of
[all …]
|
| /linux-6.15/drivers/iio/magnetometer/ |
| D | Kconfig | 21 will be called af8133j.
34 will be called ak8974.
47 will be called ak8975.
68 module will be called als31300.
89 To compile this driver as a module, choose M here: the module will be
106 To compile this driver as a module, choose M here: the module will be
119 will be called mag3110.
140 will be called mmc35240.
163 will be called st_magn_i2c.
174 will be called st_magn_spi.
[all …]
|
| /linux-6.15/Documentation/ABI/testing/ |
| D | sysfs-bus-pci | 6 Writing a device location to this file will cause
22 Writing a device location to this file will cause the
38 Writing a device ID to this file will attempt to
47 Upon successfully adding an ID, the driver will probe
57 Writing a device ID to this file will remove an ID
64 removing an ID, the driver will no longer support the
74 Writing a non-zero value to this attribute will
84 is a bridge, MSI and MSI-X will be disallowed for future
118 Writing a non-zero value to this attribute will
125 Writing a non-zero value to this attribute will
[all …]
|
| D | sysfs-class-rc | 30 Writing "+proto" will add a protocol to the list of enabled
33 Writing "-proto" will remove a protocol from the list of enabled
36 Writing "proto" will enable only "proto".
38 Writing "none" will disable all protocols.
53 the filter will be ignored. Otherwise the write will fail with
70 the filter will be ignored. Otherwise the write will fail with
93 Writing "proto" will use "proto" for wakeup events.
95 Writing "none" will disable wakeup.
113 scancodes which match the filter will wake the system from e.g.
116 Otherwise the write will fail with an error.
[all …]
|
| /linux-6.15/Documentation/infiniband/ |
| D | user_mad.rst | 9 "issm" device attached. For example, a two-port HCA will have two
10 umad devices and two issm devices, while a switch will have one
19 request succeeds, a 32-bit id will be returned in the structure.
30 ioctl. Also, all agents registered through a file descriptor will
77 fields will be filled in with information on the received MAD. For
78 example, the remote LID will be in mad.lid.
80 If a send times out, a receive will be generated with mad.status set
82 mad.status will be 0.
115 the kernel and will be overwritten before a MAD is sent.
124 compatibility with older applications, this new layout will not be used
[all …]
|
| /linux-6.15/Documentation/filesystems/ |
| D | ocfs2.rst | 64 atime_quantum=60(*) OCFS2 will not update atime unless this number
76 will be chosen. Invalid values will be ignored.
79 This means that if you lose your power, you will lose
81 filesystem will not be damaged though, thanks to the
83 will hurt performance, but it's good for data-safety.
84 Setting it to 0 will have the same effect as leaving
86 Setting it to very large values will improve
89 large, the fs will silently revert it to the default.
93 will result in inode numbers occupying more than 32
99 resv_level=2 (*) Set how aggressive allocation reservations will be.
[all …]
|
| /linux-6.15/tools/testing/selftests/tc-testing/creating-testcases/ |
| D | AddingTestCases.txt | 9 will help prevent conflicts when updating the repository. Refer to
13 option will generate a unique ID for that test case.
15 tdc will recursively search the 'tc-tests' subdirectory (or the
17 files you create in these directories will automatically be included.
25 will be used by python. So the match pattern will be a python regular
37 then tdc will not execute the test case in question. However,
38 this test case will still appear in the results output but
53 will be expected.
56 tdc will compare this value against the actual returned value.
74 will be expected.
[all …]
|
| /linux-6.15/drivers/iio/potentiometer/ |
| D | Kconfig | 17 module will be called ad5110.
27 module will be called ad5272.
37 module will be called ds1803.
48 module will be called max5432.
59 module will be called max5481.
70 module will be called max5487.
81 module will be called mcp4018.
99 module will be called mcp4131.
113 module will be called mcp4531.
125 module will be called mcp41010.
[all …]
|
| /linux-6.15/Documentation/admin-guide/ |
| D | sysrq.rst | 9 It is a 'magical' key combo you can hit which the kernel will respond to
87 This way, all characters will be processed. E.g.::
99 ``b`` Will immediately reboot the system without syncing or unmounting
102 ``c`` Will perform a system crash and a crashdump will be taken
109 ``f`` Will call the oom killer to kill a memory hog process, but do not
114 ``h`` Will display help (actually any other key than those listed
115 here will display help. but ``h`` is easy to remember :-)
126 ``m`` Will dump current memory info to your console.
130 ``o`` Will shut your system off (if configured and supported).
132 ``p`` Will dump the current registers and flags to your console.
[all …]
|
| /linux-6.15/Documentation/driver-api/nfc/ |
| D | nfc-hci.rst | 25 HCI events can also be received from the host controller. They will be handled
26 and a translation will be forwarded to NFC Core as needed. There are hooks to
38 support proprietary gates. This is the reason why the driver will pass a list
39 of proprietary gates that must be part of the session. HCI will ensure all
108 are required to send data to the tag. Some tag types will require custom
114 - check_presence() is an optional entry point that will be called regularly
116 not implemented, the core will not be able to push tag_lost events to the user
122 using nfc_hci_recv_frame(). HCI will take care of re-aggregation and handling
233 will be the syscall context. skb will return the result that was received in
238 The wait is not interruptible because it is guaranteed that the command will
[all …]
|
| /linux-6.15/Documentation/admin-guide/device-mapper/ |
| D | dm-dust.rst | 15 in the "bad block list" will fail with EIO ("Input/output error").
17 Writes of blocks in the "bad block list will result in the following:
25 Normally, a drive that is encountering bad sectors will most likely
30 configured "bad blocks" will be treated as bad, or bypassed.
72 will be passed through to the underlying device; "verbose" indicates that
73 bad block additions, removals, and remaps will be verbosely logged)::
102 These bad blocks will be stored in the "bad block list".
103 While the device is in "bypass" mode, reads and writes will succeed::
120 block will encounter an "Input/output error"::
128 ...and writing to the bad blocks will remove the blocks from the list,
[all …]
|
| /linux-6.15/include/linux/ |
| D | regmap.h | 241 * will return false. If a register belongs to a yes range, the corresponding
242 * check function will return true. "no_ranges" are searched first.
262 * multiple of this value. If set to 0, a value of 1 will be
265 * operations. Any positive number will be downshifted, and negative
266 * values will be upshifted
307 * @reg_read: Optional callback that if filled will be used to perform
313 * @reg_update_bits: Optional callback that if filled will be used to perform
318 * @read: Optional callback that if filled will be used to perform all the
366 * @use_relaxed_mmio: If set, MMIO R/W operations will not use memory barriers.
377 * write operations, if clear multi write requests will be
[all …]
|
| /linux-6.15/Documentation/timers/ |
| D | timekeeping.rst | 10 If you grep through the kernel source you will find a number of architecture-
27 a Linux system will eventually read the clock source to determine exactly
30 Typically the clock source is a monotonic, atomic counter which will provide
32 It will ideally NEVER stop ticking as long as the system is running. It
63 You will find a number of helper functions in the clock source code intended
67 clocksource_register_khz() which will help out assigning both shift and mult
71 there is nowadays even clocksource_mmio_init() which will take a memory
76 Since a 32-bit counter at say 100 MHz will wrap around to zero after some 43
77 seconds, the code handling the clock source will have to compensate for this.
80 code knows when the counter will wrap around and can insert the necessary
[all …]
|
| /linux-6.15/drivers/usb/atm/ |
| D | Kconfig | 12 modem to your computer's USB port. You will then need to choose your
16 module will be called usbatm.
25 modem. In order to use your modem you will need to install the
30 module will be called speedtch.
37 AccessRunner chipset. In order to use your modem you will need to
42 module will be called cxacru.
49 or eagle chipset. In order to use your modem you will need to
54 module will be called ueagle-atm.
60 another USB DSL drivers. In order to use your modem you will need to
66 module will be called xusbatm.
|
| /linux-6.15/Documentation/admin-guide/nfs/ |
| D | nfs-idmapper.rst | 11 NFS will attempt to call /sbin/request-key first. If this succeeds, the
12 result will be cached using the generic request-key cache. This call should
18 configured with the id_resolver key type), then the idmapper will ask the
19 legacy rpc.idmap daemon for the id mapping. This result will be stored
26 The file /etc/request-key.conf will need to be modified so /sbin/request-key can
34 This will direct all id_resolver requests to the program /usr/sbin/nfs.idmap.
35 The last parameter, 600, defines how many seconds into the future the key will
37 is not specified, nfs.idmap will default to 600 seconds.
57 request-key will find the first matching line and corresponding program. In
58 this case, /some/other/program will handle all uid lookups and
[all …]
|
| /linux-6.15/Documentation/driver-api/ |
| D | ipmi.rst | 41 properly provides the SMBIOS info for IPMI, the driver will detect it
43 will generally be either "KCS", "SMIC", or "BT", consult your hardware
46 support this, but it is unknown if it will work on every board. For
48 figuring to see if it will work on your system if the SMBIOS/APCI
74 'IPMI Poweroff' to do this. The driver will auto-detect if the system
226 will have no place to put the message.
228 Messages coming up from the message handler in kernelland will come in
244 /* Call this when done with the message. It will presumably free
285 piece of data, the handler_data, that will be passed back to you on
318 If the message cannot fit into the data you provide, you will get an
[all …]
|
| /linux-6.15/Documentation/admin-guide/sysctl/ |
| D | vm.rst | 118 huge pages although processes will also directly compact memory as required.
125 background. Write of a non zero value to this tunable will immediately
162 flusher threads will start writeback.
176 flusher threads will start writing out dirty data.
185 will itself start writeback.
193 value lower than this limit will be ignored and the old configuration will be
203 interval will be written out next time a flusher thread wakes up.
211 generating disk writes will itself start writing out dirty data.
220 an updated timestamp will never get chance to be written out. And, if the
222 by an atime update, a worker will be scheduled to make sure that inode
[all …]
|
| /linux-6.15/drivers/hwtracing/coresight/ |
| D | Kconfig | 20 module will be called coresight.
32 modules will be called coresight-funnel and coresight-replicator.
46 module will be called coresight-tmc.
60 module will be called coresight-catu.
74 module will be called coresight-tpiu.
85 module will be called coresight-etb10.
98 module will be called coresight-etm3x.
112 module will be called coresight-etm4x.
134 module will be called coresight-stm.
146 module will be called coresight-ctcu.
[all …]
|
| /linux-6.15/Documentation/driver-api/md/ |
| D | raid5-cache.rst | 19 In both modes, all writes to the array will hit cache disk first. This means
31 resync completes, any system crash will expose the chance of real data
34 The write-through cache will cache all data on cache disk first. After the data
35 is safe on the cache disk, the data will be flushed onto RAID disks. The
36 two-step write will guarantee MD can recover correct data after unclean
55 which are sequential but not dispatched in the same time will suffer from this
56 overhead too. Write-back cache will aggregate the data and flush the data to
57 RAID disks only after the data becomes a full stripe write. This will
63 disks later after specific conditions met. So cache disk failure will cause
73 Too small cache disk will make the write aggregation less efficient in this
[all …]
|
| /linux-6.15/net/bridge/ |
| D | Kconfig | 12 If you say Y here, then your Linux box will be able to act as an
14 is connected to will appear as one Ethernet to the participants.
17 As this is a standard, Linux bridges will cooperate properly with
27 iptables will then see the IP packets being bridged, so you need to
29 Enabling arptables support when bridging will let arptables see
33 will be called bridge.
43 If you say Y here, then the Ethernet bridge will be able selectively
57 If you say Y here, then the Ethernet bridge will be able selectively
70 If you say Y here, then the Ethernet bridge will be able to run MRP
81 If you say Y here, then the Ethernet bridge will be able to run CFM
|
| /linux-6.15/Documentation/hwmon/ |
| D | acpi_power_meter.rst | 30 Both `power[1-*]_average_{min,max}` must be set before the trip points will work.
31 When both of them are set, an ACPI event will be broadcast on the ACPI netlink
32 socket and a poll notification will be sent to the appropriate
40 the case, the `power[1-*]_cap` and related sysfs files will appear. When the
41 average power consumption exceeds the cap, an ACPI event will be broadcast on
42 the netlink event socket and a poll notification will be sent to the
44 hardware has taken action to reduce power consumption. Most likely this will
48 all cases the ACPI event will be broadcast on the ACPI netlink event socket as
52 `power[1-*]_cap` will be notified if the firmware changes the power cap.
53 `power[1-*]_interval` will be notified if the firmware changes the averaging
|