| /linux/Documentation/gpu/rfc/ |
| H A D | i915_small_bar.h | 20 * here, also note that no current region type will ever return -1 here.
30 * Without this (or if this is an older kernel) the value here will
33 * will always equal the @probed_size).
45 * This will be always be <= @probed_size, and the
46 * remainder (if there is any) will not be CPU
49 * On systems without small BAR, the @probed_size will
51 * of it will be CPU accessible.
55 * value here will always equal the @probed_size).
75 * value here will always equal the
79 * accounting. Without this the value here will always
[all …]
|
| /linux/Documentation/admin-guide/laptops/ |
| H A D | disk-shock-protection.rst | 43 Otherwise, writing an integer value to this file will take the heads
47 normal operation will be resumed. The maximal value accepted for a
48 timeout is 30000 milliseconds. Exceeding this limit will return
49 -EOVERFLOW, but heads will be parked anyway and the timeout will be
58 reading from `/sys/block/*/device/unload_heads` will report the number
59 of milliseconds remaining until normal operation will be resumed;
60 otherwise, reading the unload_heads attribute will return 0.
71 will show you how many milliseconds are left before normal operation
72 will be resumed.
78 that this will typically be within 500 milliseconds apparently has
[all …]
|
| /linux/Documentation/admin-guide/mm/ |
| H A D | hugetlbpage.rst | 34 The output of ``cat /proc/meminfo`` will include lines like::
54 guarantee that an application will be able to allocate a
71 will exceed HugePages_Total \* Hugepagesize. To get more
80 pages in the kernel's huge page pool. "Persistent" huge pages will be
137 will result in 256 2M huge pages being allocated and a warning message
139 parameter is preceded by an invalid hugepagesz parameter, it will
146 It will allocate 1 2M hugepage on node0 and 2 2M hugepages on node1.
147 If the node number is invalid, the parameter will be ignored.
172 will all result in 256 2M huge pages being allocated. Valid default
185 This command will try to adjust the number of default sized huge pages in the
[all …]
|
| H A D | userfaultfd.rst | 88 a later API version) which will specify the ``read/POLLIN`` protocol
92 requested features are going to be enabled) will return into
127 bitmask will specify to the kernel which kind of faults to track for
128 the range. The ``UFFDIO_REGISTER`` ioctl will return the
130 userfaults on the range registered. Not all ioctls will necessarily be
153 see a half-populated page, since readers will keep userfaulting until the
158 that waking will be done separately at some later time.
208 Then, in the thread reading from uffd the struct will have
212 set. This wakes up the thread which will continue to run with writes. This
220 former will have ``UFFD_PAGEFAULT_FLAG_WP`` set, the latter
[all …]
|
| /linux/tools/testing/selftests/drivers/net/netdevsim/ |
| H A D | fib_notifications.sh | 112 # Make sure a single notification will be emitted for the programmed
116 # route_addition_check will assign value to RET.
119 # Make sure two notifications will be emitted for the programmed route.
125 # make sure a single notification will be emitted for the programmed
165 # Make sure a single notification will be emitted for the deleted route,
168 # route_deletion_check will assign value to RET.
212 # Make sure a single notification will be emitted for the new route.
215 # route_replacement_check will assign value to RET.
218 # Make sure two notifications will be emitted for the new route.
224 # make sure a single notification will be emitted for the new route.
[all …]
|
| /linux/Documentation/driver-api/usb/ |
| H A D | typec.rst | 15 class. In a normal case the registration will be done by a USB Type-C or PD PHY
30 Every port will be presented as its own device under /sys/class/typec/. The
31 first port will be named "port0", the second "port1" and so on.
33 When connected, the partner will be presented also as its own device under
34 /sys/class/typec/. The parent of the partner device will always be the port it
35 is attached to. The partner attached to port "port0" will be named
41 will be named port0-cable and the plug on the SOP Prime end (see USB Power
42 Delivery Specification ch. 2.4) will be named "port0-plug0" and on the SOP
43 Double Prime end "port0-plug1". The parent of a cable will always be the port,
44 and the parent of the cable plugs will always be the cable.
[all …]
|
| /linux/drivers/md/dm-vdo/ |
| H A D | completion.c | 23 * operation, at most one thread will be operating in any given zone. Each zone has a
30 * "result" field is an error (i.e. not VDO_SUCCESS), the function in its "error_handler" will be
32 * will be invoked. Generally, a completion will not be run directly, but rather will be
33 * "launched." In this case, it will check whether it is operating on the correct thread. If it is,
34 * it will run immediately. Otherwise, it will be enqueue on the vdo_work_queue associated with the
35 * completion's "callback_thread_id". When it is dequeued, it will be on the correct thread, and
36 * will get run. In some cases, the completion should get queued instead of running immediately,
39 * the completion's "requeue" field should be set to true. Doing so will skip the current thread
42 * A completion may be "finished," in which case its "complete" field will be set to true before it
47 * A completion must be "reset" before it can be reused after it has been finished. Resetting will
[all …]
|
| /linux/Documentation/scheduler/ |
| H A D | sched-util-clamp.rst | 18 used, util clamp will influence the CPU frequency selection as well.
31 These two bounds will ensure a task will operate within this performance range
53 Of course a static configuration is possible too. The exact usage will depend
62 heterogeneous systems (e.g. Arm big.LITTLE); the constraint will help bias the
63 background tasks to stay on the little cores which will ensure that:
86 performance point will suffer a delay of ~200ms (PELT HALFIFE = 32ms) for the
88 mobile devices where frames will drop due to slow response time to select the
90 UCLAMP_MIN=1024 will ensure such tasks will always see the highest performance
98 the device doesn't heat up to the point where it will throttle.
136 When a task wakes up on an rq, the utilization signal of the rq will be
[all …]
|
| /linux/Documentation/trace/ |
| H A D | debugging.rst | 31 lighter weight, when possible, it will only record the pointer to the format
33 arguments will be post processed when the ring buffer is read. This way the
39 instead. If a trace_printk() is found in the kernel, the following will
62 The tracing ring buffer, by default, is a circular buffer than will
64 the ring buffer will be all the events that lead up to the crash.
67 this. The first is "ftrace_dump_on_oops". This will dump the tracing ring
92 advantage of using this method, is that the memory for the ring buffer will
98 location 0x284500000. Then the trace_instance option will create a trace
101 megabytes will be broken up evenly between those CPUs. If you have 8 CPUs,
102 each per CPU ring buffer will be 1.5 megabytes in size. Note, that also
[all …]
|
| H A 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/drivers/media/rc/ |
| H A D | Kconfig | 105 will be called ir-rcmm-decoder.
160 module will be called ene_ir.
172 module will be called fintek-cir.
180 To compile this driver as a module, choose M here: the module will
192 To compile this driver as a module, choose M here: the module will
200 To compile this driver as a module, choose M here: the module will be
215 To compile this driver as a module, choose M here: the module will
229 To compile this driver as a module, choose M here: the module will
240 module will be called imon.
250 module will be called imon_raw.
[all …]
|
| /linux/Documentation/mm/ |
| H A 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/Documentation/driver-api/dmaengine/ |
| H A D | provider.rst | 16 entities that will be doing the copy, and requests what endpoints are
21 will want to start a transfer, it will assert a DMA request (DRQ) by
59 transfer, and whenever the transfer is started, the controller will go
62 This collection is usually either a table or a linked list. You will
65 and whenever a DRQ will be asserted, it will go through the collection
69 your hardware. Each DMA controller will require a different structure,
70 but all of them will require, for every chunk, at least the source and
82 support and will be detailed later in this document.
111 structure. Any of the usual memory allocators will do, but you'll also
133 reporting. The framework will only know that a particular
[all …]
|
| /linux/Documentation/userspace-api/media/cec/ |
| H A D | cec-ioc-receive.rst | 43 messages pending, then it will return -1 and set errno to the ``EAGAIN``
46 it will return -1 and set errno to the ``ETIMEDOUT`` error code.
50 1. a message received from another CEC device (the ``sequence`` field will
51 be 0, ``tx_status`` will be 0 and ``rx_status`` will be non-zero).
53 field will be non-zero, ``tx_status`` will be non-zero and ``rx_status``
54 will be 0).
55 3. the reply to an earlier non-blocking transmit (the ``sequence`` field will
56 be non-zero, ``tx_status`` will be 0 and ``rx_status`` will be non-zero).
62 queue, then it will return -1 and set errno to the ``EBUSY`` error code.
64 of 2-byte messages). Note that the CEC kernel framework will also reply
[all …]
|
| /linux/Documentation/maintainer/ |
| H A 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/Documentation/i2c/ |
| H A 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/Documentation/hid/ |
| H A 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/Documentation/infiniband/ |
| H A 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/Documentation/filesystems/ |
| H A 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/drivers/iio/chemical/ |
| H A D | Kconfig | 16 To compile this driver as module, choose M here: the module will be
34 module will be called atlas-ph-sensor.
45 module will be called atlas-ezo-sensor.
118 To compile this driver as a module, choose M here: the module will
130 To compile this driver as a module, choose M here: the module will
141 To compile this driver as a module, choose M here: the module will
152 To compile this driver as a module, choose M here: the module will
163 To compile this driver as a module, choose M here: the module will
176 To compile this driver as a module, choose M here: the module will
186 To compile this driver as a module, choose M here: the module will
[all …]
|
| /linux/tools/testing/selftests/tc-testing/creating-testcases/ |
| H A 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/Documentation/ABI/testing/ |
| H A 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 …]
|
| H A 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 …]
|
| /linux/drivers/iio/potentiometer/ |
| H A 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/drivers/scsi/ |
| H A D | Kconfig | 33 because you will be asked for it.
42 The module will be called scsi_mod.
96 The module will be called sd_mod.
114 <file:Documentation/scsi/scsi.rst>. The module will be called st.
129 The module will be called sr_mod.
152 <file:Documentation/scsi/scsi.rst>. The module will be called sg.
161 Saying Y here will enable generic SG (SCSI generic) v4 support
182 <file:Documentation/scsi/scsi.rst>. The module will be called ch.o.
192 it has an enclosure device. Selecting this option will just allow
199 The error messages regarding your SCSI hardware will be easier to
[all …]
|