/linux-5.10/Documentation/fb/ |
D | fbcon.rst | 26 module will be fbcon. 30 systems, they almost universally have VGA cards, so vga16fb and vesafb will 31 always be available. However, using a chipset-specific driver will give you 38 Also, you will need to select at least one compiled-in font, but if 39 you don't do anything, the kernel configuration tool will select one for you, 46 will still get a VGA console. 55 Usually, fbcon will automatically take over your console. The notable 73 You can load them in any order. Once both are loaded, fbcon will take 97 will be:: 116 outside the given range will still be controlled by the standard [all …]
|
D | intel810.rst | 65 select horizontal resolution in pixels. (This parameter will be 73 is enabled, this will be ignored and computed as 3*xres/4. (This 74 parameter will be ignored if 'mode_option' is specified. See 'o' 82 is specified, this will be computed against maximum available memory. 102 be equal to hsync2. If EDID probing is successful, these will be 103 ignored and values will be taken from the EDID block. 111 rate. If EDID probing is successful, these will be ignored and values 112 will be taken from the EDID block. 126 offset (16 MB for a 64 MB aperture, 8 MB for a 32 MB aperture) will 151 if specified, secondary/external VGA output will always be enabled. [all …]
|
/linux-5.10/security/selinux/ |
D | Kconfig | 9 You will also need a policy configuration and a labeled filesystem. 34 SELinux will then remain disabled until the next boot. 40 NOTE: selecting this option will disable the '__ro_after_init' 45 WARNING: this option is deprecated and will be removed in a future 58 kernel will start in permissive mode (log everything, deny nothing) 81 by the application or the protection that will be applied by the 84 SELinux will default to checking the protection that will be applied 85 by the kernel. If this option is set to 1 (one), SELinux will 91 WARNING: this option is deprecated and will be removed in a future 106 will ensure that lookups times are short and stable.
|
/linux-5.10/drivers/net/ethernet/8390/ |
D | Kconfig | 14 kernel: saying N will just cause the configurator to skip all 16 you will be asked for your specific card in the following questions. 29 To compile this driver as a module, choose M here: the module will be 60 will be called xsurf100. 70 will be called hydra. 100 here, the module will be called mcf8390. 115 will be called ne. 122 This driver is for NE2000 compatible PCI cards. It will not work 133 will be called ne2k-pci. 144 will be called apne. [all …]
|
/linux-5.10/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 43 read() will read a queued report received from the HID device. On USB 45 on the INTERRUPT IN endpoint. By default, read() will block until there is 51 will be the report number; the report data follows, beginning in the second 53 will begin at the first byte. 57 The write() function will write a report to the device. For USB devices, if 58 the device has an INTERRUPT OUT endpoint, the report will be sent on that 59 endpoint. If it does not, the report will be sent over the control endpoint, 73 This ioctl will get the size of the device's report descriptor. [all …]
|
/linux-5.10/Documentation/powerpc/ |
D | pmu-ebb.rst | 20 Throughout this document we will refer to an "EBB event" or "EBB events". This 35 EBBs will ever be delivered. 39 and attach an EBB event to the process, which will then cause EBBs to be 49 kernel will in general schedule the EBB event, and perf will be notified that 54 events will be given priority over other events, unless they are also pinned. 56 first will be scheduled and the other will be put in error state. See the 101 EBB event is enabled it will force all other non-pinned events off the PMU. In 102 this case the enable will be successful. However if there is already an event 103 pinned on the PMU then the enable will not be successful. 111 kernel is not able to count the event, and so will return a junk value. [all …]
|
/linux-5.10/Documentation/trace/ |
D | ftrace-uses.rst | 42 as well as what protections the callback will perform and not require 70 The registered callback will start being called some time after the 73 of services. The callback itself will have to handle any synchronization if it 76 The unregister_ftrace_function() will guarantee that the callback is 106 flags are set in the ftrace_ops structure, then this will be pointing 123 support passing of pt_regs to the callback will fail. 128 will not fail with this flag set. But the callback must check if 135 is also traced, ftrace will prevent the callback from being called 148 If this flag is set, it is possible that the callback will also 163 If this is set, then the callback will only be called by functions [all …]
|
/linux-5.10/Documentation/core-api/ |
D | kobject.rst | 17 some terms we will be working with. 30 up and incorrect, and your code will be buggy. So do not do this. 46 approach will be taken, so we'll go back to kobjects. 54 a larger, domain-specific object. To this end, kobjects will be found 77 just a matter of using the kobj member. Code that works with kobjects will 134 NULL in the call to kobject_add() and then the kobject's parent will be the 177 have been initialized properly, as userspace will instantly start to look 181 below), the uevent for **KOBJ_REMOVE** will be automatically created by the 197 A successful call to kobject_get() will increment the kobject's reference 200 When a reference is released, the call to kobject_put() will decrement the [all …]
|
D | assoc_array.rst | 25 already in the array will replace the old object. 34 8. The array can iterated over. The objects will not necessarily come out in 40 problem, the iterator should lock against modification. Objects will not 76 preallocated metadata blocks that will be installed in the internal tree and 77 keeps track of the metadata blocks that will be removed from the tree when the 95 This will perform the edit functions, interpolating various write barriers 97 will then be passed to ``call_rcu()`` to free it and any dead stuff it points 127 *bit* position given by the level argument. The level argument will be a 189 If an object already exists for that key then it will be replaced with the 190 new object and the old one will be freed automatically. [all …]
|
/linux-5.10/tools/testing/ktest/examples/include/ |
D | min-config.conf | 10 # boot your machine, the closer the config you test with will be 16 # In this example, the final config will reside in 20 # The first test creates a MIN_CONFIG that will be the minimum 23 # The second test creates a MIN_CONFIG that will only boot 24 # the target and most likely will not let you ssh to it. (Notice 28 # The ${CONFIG_DIR}/config-skip (and -net) will hold the configs 32 # selected them. Sometimes it is possible that this file will hold 40 # modifying this config, ktest.pl will notice that the config-new-min(-net) 41 # exists, and will use that instead as the starting point. 44 # By using the OUTPUT_MIN_CONFIG as the starting point will allow ktest.pl to
|
D | patchcheck.conf | 3 # This contains a test that takes two git commits and will test each 4 # commit between the two. The build test will look at what files the 6 # the build will fail. 12 # You can use a SHA1, a git tag, or anything that git will accept for a checkout 27 # Change PATCH_CHECKOUT to be the branch you want to test. The test will 40 # will be executed. Usually what is done is to ssh to the target box and 62 # If the variable CREATE_WARNINGS_FILE is set, this config will 64 # before running the patchcheck test, it will create the 83 # fifth patch, set PATCH_START1. This will make the first test start 86 # top config (the one you pass to ktest.pl), and this will use it, [all …]
|
/linux-5.10/drivers/net/wireless/realtek/rtlwifi/ |
D | Kconfig | 7 This option will enable support for the Realtek mac80211-based 24 If you choose to build it as a module, it will be called rtl8192ce 35 If you choose to build it as a module, it will be called rtl8192se 46 If you choose to build it as a module, it will be called rtl8192de 59 If you choose to build it as a module, it will be called rtl8723ae 72 If you choose to build it as a module, it will be called rtl8723be 83 If you choose to build it as a module, it will be called rtl8188ee 95 If you choose to build it as a module, it will be called rtl8192ee 107 If you choose to build it as a module, it will be called rtl8821ae 119 If you choose to build it as a module, it will be called rtl8192cu
|
/linux-5.10/drivers/iio/potentiometer/ |
D | Kconfig | 17 module will be called ad5272. 27 module will be called ds1803. 38 module will be called max5432. 49 module will be called max5481. 60 module will be called max5487. 71 module will be called mcp4018. 89 module will be called mcp4131. 103 module will be called mcp4531. 115 module will be called mcp41010. 127 module will be called tpl0102.
|
/linux-5.10/drivers/net/wireless/ralink/rt2x00/ |
D | Kconfig | 6 This will enable the support for the Ralink drivers, 12 will also be created. That library (when the driver is built as 13 a module) will be called rt2x00lib. 15 Additionally PCI and USB libraries will also be build depending 16 on the types of drivers being selected, these libraries will be 31 When compiled as a module, this driver will be called rt2400pci. 43 When compiled as a module, this driver will be called rt2500pci. 58 When compiled as a module, this driver will be called rt61pci. 76 When compiled as a module, this driver will be called "rt2800pci.ko". 123 When compiled as a module, this driver will be called rt2500usb. [all …]
|
/linux-5.10/Documentation/devicetree/bindings/sound/ |
D | st,sta350.txt | 9 - reset-gpios: a GPIO spec for the reset pin. If specified, it will be 13 it will be deasserted before communication to the codec 27 If parameter is missing, mode 0 will be enabled. 46 If present, then fault recovery will be enabled. 80 channels. If not present, normal PWM spped mode (384 kHz) will be used. 90 If present, a mute output will be activated in ase the volume will 94 If present, the bridge will be switched off immediately after the 95 power-down-gpio goes low. Otherwise, the bridge will wait for 13 103 If present, the power-down pin and I2C power-down functions will 104 act on the master volume. Otherwise, the functions will act on the [all …]
|
/linux-5.10/Documentation/ABI/testing/ |
D | configfs-most | 31 configure type of data that will travel over 35 configure whether this link will be an input 43 configure the number of packets that will be 86 configure type of data that will travel over 90 configure whether this link will be an input 98 configure the number of packets that will be 141 configure type of data that will travel over 145 configure whether this link will be an input 153 configure the number of packets that will be 207 configure type of data that will travel over [all …]
|
/linux-5.10/Documentation/staging/ |
D | rpmsg.rst | 75 and its length (in bytes). The message will be sent on the specified 76 channel, i.e. its source and destination address fields will be 79 In case there are no TX buffers available, the function will block until 98 The message will then be sent to the remote processor to which the 100 dst address (thus the channel's dst address will be ignored). 102 In case there are no TX buffers available, the function will block until 122 The message will then be sent to the remote processor to which the 123 channel belongs, but the channel's src and dst addresses will be 124 ignored (and the user-provided addresses will be used instead). 126 In case there are no TX buffers available, the function will block until [all …]
|
/linux-5.10/Documentation/admin-guide/mm/ |
D | nommu-mmap.rst | 41 - If one exists, the kernel will re-use an existing mapping to the 45 - If possible, the file mapping will be directly on the backing device 52 appropriate bit of the file will be read into a contiguous bit of 53 memory and any extraneous space beyond the EOF will be cleared 84 case, a shared-writable memory mapping will be possible. It will work 86 support, then the mapping request will be denied. 105 provide any such support, then the mapping request will be denied. 115 (#) A request for an anonymous mapping will always be page aligned. If 118 granule but will only discard the excess if appropriately configured as 121 (#) The memory allocated by a request for an anonymous mapping will normally [all …]
|
/linux-5.10/drivers/staging/media/atomisp/pci/ |
D | ia_css_stream_public.h | 10 * This program is distributed in the hope it will be useful, but WITHOUT 49 contiguously or not. \deprecated{Will be false always.}*/ 67 format will be mapped to MIPI data 82 format will be mapped to MIPI data 87 /* Input stream description. This describes how input will flow into the 98 will arrive. Use this field 110 * and will be deprecated. In the future,all platforms will use the N*N method 118 bool online; /** offline will activate RAW copy on SP, use this for 157 * This function will reset the stream configuration to the default state: 177 * This function will create a stream with a given configuration and given pipes. [all …]
|
D | ia_css_pipe_public.h | 10 * This program is distributed in the hope it will be useful, but WITHOUT 89 will OSYS receive, this resolution is equal to the output resolution of GDC 90 if not determined CSS will set output_system_in_res with main osys output pin resolution 111 should be run. Setting this to -1 means it will run until 115 then setting a zoom factor will have no effect. 121 /** Enabling BCI mode will cause yuv_scale binary to be picked up 128 will be done. */ 164 * ~~~** DO NOT ADD NEW FIELD **~~~ This structure will be deprecated. 178 smaller than the input resolution, cropping will be performed by 179 the ISP. The first cropping that will be performed is on the upper [all …]
|
/linux-5.10/Documentation/vm/ |
D | swap_numa.rst | 24 Then node 0 will use the two swap devices in the order of swapA then swapB and 25 node 1 will use the two swap devices in the order of swapB then swapA. Note 40 Then node 0 will use them in the order of:: 44 swapA and swapB will be used in a round robin mode before any other swap device. 46 node 1 will use them in the order of:: 50 node 2 will use them in the order of:: 54 Similaly, swapD and swapE will be used in a round robin mode before any 57 node 3 will use them in the order of:: 73 or the system will pick one starting from -1 then downwards. The priority 79 node, they will all be promoted to priority -1 on that node's plist and will
|
/linux-5.10/Documentation/scheduler/ |
D | sched-bwc.rst | 15 assigned any additional requests for quota will result in those threads being 16 throttled. Throttled threads will not be able to run again until the next 42 Writing any (valid) positive value(s) will enact the specified bandwidth limit. 48 Writing any negative value to cpu.cfs_quota_us will remove the bandwidth limit 51 Any updates to a group's bandwidth specification will result in it becoming 65 Larger slice values will reduce transfer overheads, while smaller values allow 98 In case b) above, even though the child may have runtime remaining it will not 113 relatively moot point because they will naturally consume the entirety of their 116 cpuacct.usage will increase roughly equal to cfs_quota_us in each period. 123 in previous periods. This burst amount will not be transferred between cores. [all …]
|
/linux-5.10/arch/x86/include/asm/ |
D | tlbflush.h | 57 * 6 because 6 should be plenty and struct tlb_state will fit in two cache 71 * which will contain the previous user mm when we're in lazy TLB 74 * During switch_mm_irqs_off(), loaded_mm will be set to 95 * - Actively using an mm. Our CPU's bit will be set in 99 * will not be set in mm_cpumask(&init_mm) and is_lazy == false. 139 * entries came from. As an invariant, the TLB will never 149 * isn't aware of PCID will end up harmlessly flushing 187 * - Fully flush a single mm. .mm will be set, .end will be 188 * TLB_FLUSH_ALL, and .new_tlb_gen will be the tlb_gen to 191 * - Partially flush a single mm. .mm will be set, .start and [all …]
|
/linux-5.10/Documentation/admin-guide/device-mapper/ |
D | thin-provisioning.rst | 36 cases will have different performance characteristics, for example due 53 directly. End users will be advised to use a higher-level volume 77 The amount of metadata you need will vary according to how many blocks 88 a warning will be issued and the excess space will not be used. 95 device when reloading is not forbidden at the moment, things will go 120 will be triggered which a userspace daemon should catch allowing it to 121 extend the pool device. Only one such event will be sent. 129 will trigger a dm event if free space on the metadata device drops below 136 If no such requests are made then commits will occur every second. This 141 If data space is exhausted the pool will either error or queue IO [all …]
|
/linux-5.10/include/linux/ |
D | hwspinlock.h | 88 * required on a given setup, users will still work. 94 * Note: ERR_PTR(-ENODEV) will still be considered a success for NULL-checking 169 * @flags: a pointer to where the caller's interrupt state will be saved at 171 * This function attempts to lock the underlying hwspinlock, and will 192 * This function attempts to lock the underlying hwspinlock, and will 211 * This function attempts to lock an hwspinlock, and will immediately fail 215 * or spinlock to avoid dead-lock, that will let user can do some time-consuming 230 * This function attempts to lock an hwspinlock, and will immediately fail 247 * This function attempts to lock an hwspinlock, and will immediately fail 267 * @flags: a pointer to where the caller's interrupt state will be saved at [all …]
|