/linux/drivers/gpu/drm/msm/registers/ |
H A D | rules-fd.xsd | 65 <attribute name="name" type="string" use="required" /> 66 <attribute name="email" type="string" use="required" /> 73 <attribute name="name" type="string" use="required" /> 92 <attribute name="file" type="string" use="required" /> 105 <attribute name="year" type="nonNegativeInteger" use="optional" /> 117 <attribute name="name" type="NMTOKEN" use="required" /> 118 <attribute name="prefix" type="NMTOKENS" use="optional" /> 119 <attribute name="width" type="rng:DomainWidth" use="optional" /> 120 <attribute name="varset" type="NMTOKEN" use="optional" /> 121 <attribute name="variants" type="string" use="optional" /> [all …]
|
/linux/rust/kernel/ |
H A D | prelude.rs | 11 //! use kernel::prelude::*; 15 pub use core::pin::Pin; 17 pub use ::ffi::{ 22 pub use crate::alloc::{flags::*, Box, KBox, KVBox, KVVec, KVec, VBox, VVec, Vec}; 25 pub use macros::{export, kunit_tests, module, vtable}; 27 pub use pin_init::{init, pin_data, pin_init, pinned_drop, InPlaceWrite, Init, PinInit, Zeroable}; 29 pub use super::{build_assert, build_error}; 33 pub use super::dbg; 34 pub use super::{dev_alert, dev_crit, dev_dbg, dev_emerg, dev_err, dev_info, dev_notice, dev_warn}; 35 pub use super::{pr_alert, pr_crit, pr_debug, pr_emerg, pr_err, pr_info, pr_notice, pr_warn}; [all …]
|
H A D | sync.rs | 8 use crate::prelude::*; 9 use crate::types::Opaque; 10 use pin_init; 21 pub use arc::{Arc, ArcBorrow, UniqueArc}; 22 pub use completion::Completion; 23 pub use condvar::{new_condvar, CondVar, CondVarTimeoutResult}; 24 pub use lock::global::{global_lock, GlobalGuard, GlobalLock, GlobalLockBackend, GlobalLockedBy}; 25 pub use lock::mutex::{new_mutex, Mutex, MutexGuard}; 26 pub use lock::spinlock::{new_spinlock, SpinLock, SpinLockGuard}; 27 pub use locked_by::LockedBy; [all …]
|
H A D | init.rs | 9 //! to its documentation to better understand how to use it. Additionally, there are many examples 21 //! [`Opaque<T>`] field by just delegating to the supplied closure. You can use these in 34 //! use kernel::types::Opaque; 35 //! use pin_init::pin_init_from_closure; 71 //! use kernel::{prelude::*, types::Opaque}; 72 //! use core::{ptr::addr_of_mut, marker::PhantomPinned, pin::Pin}; 129 use crate::{ 133 use pin_init::{init_from_closure, pin_init_from_closure, Init, PinInit}; 139 /// If a type already implicitly pins its pointee, `Pin<Self>` is unnecessary. In this case use 140 /// `Self`, otherwise just use `Pin<Self>`. [all …]
|
/linux/tools/perf/Documentation/ |
H A D | tips.txt | 11 Use parent filter to see specific call path: perf report -p <regex> 14 Use --symfs <dir> if your symbol files are in non-standard locations 16 To see call chains by final symbol taking CPU time (bottom up) use perf report -G 20 To show assembler sample context control flow use perf record -b / perf report --samples 10 and then browse context 21 To adjust path to source files to local file system use perf report --prefix=... --prefix-strip=... 23 Show estimate cycles per function and IPC in annotate use perf record -b ... ; perf report --total-cycles 36 To show information about system the samples were collected on use perf report --header 37 To only collect call graph on one event use perf record -e cpu/cpu-cycles,callgraph=1/,branches ; perf report --show-ref-call-graph 38 To set sampling period of individual events use perf record -e cpu/cpu-cycles,period=100001/,cpu/branches,period=10001/ ... 39 To group events which need to be collected together for accuracy use {} [all...] |
/linux/drivers/usb/serial/ |
H A D | Kconfig | 16 supported, and on how to use them. 27 If you say Y here, it will be possible to use a USB to serial 41 kernel will automatically use the first USB to serial converter 49 Say Y here if you want to use the generic USB serial driver. Please 58 Say Y here to use the USB serial "simple" driver. This driver 82 Say Y here if you want to use USB AIRcable Bluetooth Dongle. 90 Say Y here if you want to use a ARK Micro 3116 USB to Serial 99 Say Y here if you want to use a Belkin USB Serial single port 109 Say Y here if you want to use a Winchiphead CH341 single port 119 Say Y here if you want to use a ConnectTech WhiteHEAT 4 port [all …]
|
/linux/Documentation/userspace-api/media/v4l/ |
H A D | colorspaces-defs.rst | 27 two basic ways to do it: Divide the angular value by 2 (0-179), or use the 87 - Use the default transfer function as defined by the colorspace. 89 - Use the Rec. 709 transfer function. 91 - Use the sRGB transfer function. 93 - Use the opRGB transfer function. 95 - Use the SMPTE 240M transfer function. 97 - Do not use a transfer function (i.e. use linear RGB values). 99 - Use the DCI-P3 transfer function. 101 - Use the SMPTE 2084 transfer function. See :ref:`xf-smpte-2084`. 116 - Use the default Y'CbCr encoding as defined by the colorspace. [all …]
|
/linux/drivers/video/fbdev/via/ |
H A D | tblDPASetting.c | 15 /* LCK/VCK < 30000000 will use this value */ 18 /* 30000000 < LCK/VCK < 50000000 will use this value */ 21 /* 50000000 < LCK/VCK < 70000000 will use this value */ 24 /* 70000000 < LCK/VCK < 100000000 will use this value */ 27 /* 100000000 < LCK/VCK < 15000000 will use this value */ 30 /* 15000000 < LCK/VCK will use this value */ 40 /* LCK/VCK < 30000000 will use this value */ 42 /* 30000000 < LCK/VCK < 50000000 will use this value */ 44 /* 50000000 < LCK/VCK < 70000000 will use this value */ 46 /* 70000000 < LCK/VCK < 100000000 will use this value */ [all …]
|
/linux/include/linux/platform_data/ |
H A D | adp8870.h | 118 u8 l1_daylight_max; /* use BL_CUR_mA(I) 0 <= I <= 30 mA */ 119 u8 l1_daylight_dim; /* typ = 0, use BL_CUR_mA(I) 0 <= I <= 30 mA */ 120 u8 l2_bright_max; /* use BL_CUR_mA(I) 0 <= I <= 30 mA */ 121 u8 l2_bright_dim; /* typ = 0, use BL_CUR_mA(I) 0 <= I <= 30 mA */ 122 u8 l3_office_max; /* use BL_CUR_mA(I) 0 <= I <= 30 mA */ 123 u8 l3_office_dim; /* typ = 0, use BL_CUR_mA(I) 0 <= I <= 30 mA */ 124 u8 l4_indoor_max; /* use BL_CUR_mA(I) 0 <= I <= 30 mA */ 125 u8 l4_indor_dim; /* typ = 0, use BL_CUR_mA(I) 0 <= I <= 30 mA */ 126 u8 l5_dark_max; /* use BL_CUR_mA(I) 0 <= I <= 30 mA */ 127 u8 l5_dark_dim; /* typ = 0, use BL_CUR_mA(I) 0 <= I <= 30 mA */ [all …]
|
/linux/drivers/gpu/drm/nouveau/nvkm/core/ |
H A D | subdev.c | 7 * the rights to use, copy, modify, merge, publish, distribute, sublicense, 19 * ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR 57 const char *action = suspend ? "suspend" : subdev->use.enabled ? "fini" : "reset"; in nvkm_subdev_fini() 71 subdev->use.enabled = false; in nvkm_subdev_fini() 130 if (subdev->use.enabled) { in nvkm_subdev_init_() 142 subdev->use.enabled = true; in nvkm_subdev_init_() 162 mutex_lock(&subdev->use.mutex); in nvkm_subdev_init() 163 if (refcount_read(&subdev->use.refcount) == 0) { in nvkm_subdev_init() 165 mutex_unlock(&subdev->use.mutex); in nvkm_subdev_init() 170 mutex_unlock(&subdev->use.mutex); in nvkm_subdev_init() [all …]
|
/linux/Documentation/devicetree/bindings/ |
H A D | writing-bindings.rst | 24 - DO use node names matching the class of the device. Many standard names are 34 - DON'T use 'syscon' alone without a specific compatible string. A 'syscon' 44 - DON'T use wildcards or device-family names in compatible strings. 46 - DO use fallback compatibles when devices are the same as or a superset of 51 - DO use a SoC-specific compatible for all SoC devices, followed by a 55 - DON'T use bus suffixes to encode the type of interface device is using. 59 - DO use a vendor prefix on device-specific property names. Consider if 69 - DO use common property unit suffixes for properties with scientific units. 96 - If schema includes other schema (e.g. /schemas/i2c/i2c-controller.yaml) use 97 "unevaluatedProperties:false". In other cases, usually use [all …]
|
/linux/include/media/ |
H A D | v4l2-mc.h | 38 * hardware should not use this routine, as it will not build the right graph. 43 * v4l_enable_media_source() - Hold media source for exclusive use 49 * media source is free for use. The enable_source handler is 75 * v4l_vb2q_enable_media_tuner - Hold media source for exclusive use 143 * v4l2_pipeline_pm_get - Increase the use count of a pipeline 146 * THIS FUNCTION IS DEPRECATED. DO NOT USE IN NEW DRIVERS. USE RUNTIME PM 149 * Update the use count of all entities in the pipeline and power entities on. 152 * struct media_entity.use_count to track the power status. The use 160 * v4l2_pipeline_pm_put - Decrease the use count of a pipeline 163 * THIS FUNCTION IS DEPRECATED. DO NOT USE IN NEW DRIVERS. USE RUNTIME PM [all …]
|
/linux/arch/m68k/include/asm/ |
H A D | MC68VZ328.h | 380 #define PB_CSB0 0x01 /* Use CSB0 as PB[0] */ 381 #define PB_CSB1 0x02 /* Use CSB1 as PB[1] */ 382 #define PB_CSC0_RAS0 0x04 /* Use CSC0/RAS0 as PB[2] */ 383 #define PB_CSC1_RAS1 0x08 /* Use CSC1/RAS1 as PB[3] */ 384 #define PB_CSD0_CAS0 0x10 /* Use CSD0/CAS0 as PB[4] */ 385 #define PB_CSD1_CAS1 0x20 /* Use CSD1/CAS1 as PB[5] */ 386 #define PB_TIN_TOUT 0x40 /* Use TIN/TOUT as PB[6] */ 387 #define PB_PWMO 0x80 /* Use PWMO as PB[7] */ 404 #define PC_LD0 0x01 /* Use LD0 as PC[0] */ 405 #define PC_LD1 0x02 /* Use LD1 as PC[1] */ [all …]
|
/linux/drivers/tty/serial/ |
H A D | Kconfig | 37 Say Y here if you wish to use an AMBA PrimeCell UART as the system 65 Say Y here if you wish to use an AMBA PrimeCell UART as the system 121 If you say Y here, it will be possible to use a serial port as the 145 Say Y here if you wish to use an on-chip UART on a Atmel 155 Say Y here if you wish to use the PDC to do DMA transfers to 157 actually use DMA transfers, make sure that the use_dma_tx 163 this matters don't use DMA. 177 To use this, you should create suitable ttyATn device nodes in 196 Say Y here if you wish to use a Amlogic MesonX UART as the 246 Allow selection of the S3C24XX on-board serial ports for use as [all …]
|
/linux/drivers/w1/slaves/ |
H A D | Kconfig | 23 Say Y or M here if you want to use a DS2405 1-wire 31 Say Y here if you want to use a 1-wire 47 Say Y here if you want to use a 1-wire 54 Say Y or M here if you want to use a 1-wire 66 Say Y here if you want to use a 1-wire 72 Say Y here if you want to use a 1-wire 80 Say Y here if you want to use a 1-wire 256bit EEPROM 88 Say Y here if you want to use a 1-wire 94 Say Y here if you want to use a 1-wire 109 Say Y here if you want to use a 1-wire [all …]
|
/linux/Documentation/arch/arm64/ |
H A D | acpi_object_usage.rst | 68 Optional, not currently supported, with no real use-case for an 206 ARM-specific error sources have been defined; please use those or the 208 Bridge), or use type 9 (Generic Hardware Error Source). Firmware first 258 descriptions and power states on ARM platforms should use the DSDT 317 use. Since these are not meant to be of general use but are limited 318 to very specific end users, they are not recommended for use and are 325 Recommend for use on arm64; use of PCC is recommended when using CPPC 428 for use with devices that can be added to a running system, but can 463 Optional, not currently supported. No known use case for arm64, 528 _CID 6.1.2 Use as needed, see also _HID. [all …]
|
/linux/rust/pin-init/src/ |
H A D | lib.rs | 10 //! This library's main use-case is in [Rust-for-Linux]. Although this version can be used 59 //! Throughout the examples we will often make use of the `CMutex` type which can be found in 66 //! If you want to use [`PinInit`], then you will have to annotate your `struct` with 75 //! # #[path = "../examples/mutex.rs"] mod mutex; use mutex::*; 76 //! # use core::pin::Pin; 77 //! use pin_init::{pin_data, pin_init, InPlaceInit}; 93 //! `foo` now is of the type [`impl PinInit<Foo>`]. We can now use any smart pointer that we like 99 //! # #[path = "../examples/mutex.rs"] mod mutex; use mutex::*; 100 //! # use core::{alloc::AllocError, pin::Pin}; 101 //! # use pin_init::*; [all …]
|
/linux/arch/nios2/include/asm/ |
H A D | asm-macros.h | 16 * You cannnot use the same register for reg1 & reg2. 36 * It is safe to use the same register for reg1 & reg2. 55 * It is safe to use the same register for reg1 & reg2. 75 * It is safe to use the same register for reg1 & reg2. 94 * It is safe to use the same register for reg1 & reg2. 106 * It is safe to use the same register for reg1 & reg2. 118 * It is NOT safe to use the same register for reg1 & reg2. 139 * It is NOT safe to use the same register for reg1 & reg2. 160 * It is NOT safe to use the same register for reg1 & reg2. 182 * It is NOT safe to use the same register for reg1 & reg2. [all …]
|
/linux/Documentation/admin-guide/mm/ |
H A D | swap_numa.rst | 6 information, we can make use of this information to decide which swap 7 device to use in get_swap_pages() to get better performance. 10 How to use this feature 14 use of automatically binding, there is no need to manipulate priority settings 22 Then node 0 will use the two swap devices in the order of swapA then swapB and 23 node 1 will use the two swap devices in the order of swapB then swapA. Note 38 Then node 0 will use them in the order of:: 44 node 1 will use them in the order of:: 48 node 2 will use them in the order of:: 55 node 3 will use them in the order of:: [all …]
|
/linux/drivers/input/keyboard/ |
H A D | Kconfig | 58 Say Y here if you want to use a ADP5588/87 attached to your 112 Say Y here if you want to use a standard AT or PS/2 keyboard. Usually 123 bool "Use HP keyboard scancodes" 127 Say Y here if you have a PA-RISC machine and want to use an AT or 131 Say N if you use a standard keyboard. 134 bool "Use PrecisionBook keyboard scancodes" 138 If you have an RDI PrecisionBook, say Y here if you want to use its 152 If you say N here, and use the PrecisionBook keyboard, then each key 156 If you say Y here, and use an external keyboard, then each key in the 165 Say Y here if you want to use Microchip AT42QT1050 QTouch [all …]
|
/linux/Documentation/admin-guide/nfs/ |
H A D | nfsroot.rst | 18 In order to use a diskless system, such as an X-terminal or printer server for 23 following text describes on how to use NFS for the root filesystem. For the rest 33 In order to use nfsroot, NFS client support needs to be selected as 48 told what root fs device to use. And in the case of nfsroot, where to find 55 real device but just a synonym to tell the kernel to use NFS instead of 65 (see below). This parameter allows the use of different 103 autoconfiguration will take place. The most common way to use this 144 <device> Name of network device to use. 151 <autoconf> Method to use for autoconfiguration. 161 off or none: don't use autoconfiguration [all …]
|
/linux/net/sched/ |
H A D | Kconfig | 31 This Quality of Service (QoS) support will enable you to use 51 Say Y here if you want to use the Hierarchical Token Buckets (HTB) 65 Say Y here if you want to use the Hierarchical Fair Service Curve 74 Say Y here if you want to use an n-band priority queue packet 83 Say Y here if you want to use an n-band queue packet scheduler 92 Say Y here if you want to use the Random Early Detection (RED) 103 Say Y here if you want to use the Stochastic Fair Blue (SFB) 114 Say Y here if you want to use the Stochastic Fairness Queueing (SFQ) 125 Say Y here if you want to use the True Link Equalizer (TLE) packet 137 Say Y here if you want to use the Token Bucket Filter (TBF) packet [all …]
|
/linux/Documentation/fb/ |
H A D | uvesafb.rst | 11 Unlike other drivers, uvesafb makes use of a userspace helper called 25 order for uvesafb to work properly. If you want to use uvesafb during 27 either compile it into the kernel or use it as an initrd. 40 video mode you want to use. This can be especially painful with 80 vgapal Use the standard VGA registers for palette changes. 82 pmipal Use the protected mode interface for palette changes. 95 nomtrr Do not use memory type range registers. 102 amount of video RAM, use this option to override the BIOS (in MiB). 109 vbemode:x Force the use of VBE mode x. The mode will only be set if it's 113 HINT: If you use this option because normal <mode> parameter does [all …]
|
H A D | sisfb.rst | 38 Well, it depends: If compiled statically into the kernel, use lilo's append 52 A common mistake is that folks use a wrong parameter format when using the 55 (or whatever mode you want to use, alternatively using any other format 58 want to use). Using a "=" for a ":" (and vice versa) is a huge difference! 65 How do I use it? 81 - or simply use the VESA mode number in hexadecimal or decimal. 90 use either "mode" or "vesa" but not both. 95 resolution is used. If you want to switch to a different mode, use the fbset 100 you want to switch to another mode, use the stty shell command. 106 You should *not* compile-in vesafb. And please do not use the "vga=" keyword [all …]
|
/linux/Documentation/trace/ |
H A D | user_events.rst | 17 Programs can also use /sys/kernel/tracing/dynamic_events to register and 47 /* Input: Bit in enable address to use */ 53 /* Input: Flags to use, if any */ 62 /* Output: Index of the event to use when writing data */ 77 + flags: The flags to use, if any. 78 Callers should first attempt to use flags and retry without flags to ensure 82 + enable_addr: The address of the value to use to reflect event status. This 91 closing. Callers may use this if an event should exist even after the 97 format changes and they wish to use the same name. When this flag is used the 100 and format. This means if several processes use the same name and format, [all …]
|