Searched full:use (Results 1 – 25 of 2519) sorted by relevance
12345678910>>...101
| /Documentation/userspace-api/media/v4l/ |
| 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 …]
|
| D | dv-timings.rst | 26 device applications use the
29 DV timings for the device applications use the
31 current DV timings they use the
33 the DV timings as seen by the video receiver applications use the
36 Applications can make use of the :ref:`input-capabilities` and
|
| /Documentation/arch/x86/x86_64/ |
| D | boot-options.rst | 39 Do not opt-in to Local MCE delivery. Use legacy method
73 Use IO-APIC. Default
76 Don't use the IO-APIC.
79 Don't use the local APIC
82 Don't use the local APIC (alias for i386 compatibility)
102 Deprecated, use tsc=unstable instead.
105 Don't use the HPET timer.
124 Use the CPU reboot vector for warm reset
132 Use the keyboard controller. cold reset (default)
134 Use the ACPI RESET_REG in the FADT. If ACPI is not configured or
[all …]
|
| /Documentation/admin-guide/mm/ |
| 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 …]
|
| /Documentation/devicetree/bindings/ |
| 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'
42 - DO make 'compatible' properties specific. DON'T use wildcards in compatible
43 strings. DO use fallback compatibles when devices are the same as or a subset
47 - DO use a vendor prefix on device-specific property names. Consider if
54 - DO use common property unit suffixes for properties with scientific units.
75 - If schema includes other schema (e.g. /schemas/i2c/i2c-controller.yaml) use
76 "unevaluatedProperties:false". In other cases, usually use
79 - For sub-blocks/components of bigger device (e.g. SoC blocks) use rather
82 For example use "vendor,soc1234-i2c" instead of "vendor,i2c-v2".
[all …]
|
| /Documentation/devicetree/bindings/serial/ |
| D | atmel,at91-usart.yaml | 69 atmel,use-dma-rx:
71 description: use of PDC or DMA for receiving data
73 atmel,use-dma-tx:
75 description: use of PDC or DMA for transmitting data
102 atmel,use-dma-rx: false
104 atmel,use-dma-tx: false
132 /* use PDC */
140 atmel,use-dma-rx;
141 atmel,use-dma-tx;
156 /* use DMA */
[all …]
|
| /Documentation/i2c/ |
| D | dma-considerations.rst | 13 rarely used. However, it is recommended to use a DMA-safe buffer if your
17 note that other subsystems you use might add requirements. E.g., if your
24 For clients, if you use a DMA safe buffer in i2c_msg, set the I2C_M_DMA_SAFE
27 updated to use this flag will work like before. And like before, they risk
34 of i2c_master_send() and i2c_master_recv() functions can now use DMA safe
42 Bus master drivers wishing to implement safe DMA can use helper functions from
49 bounce buffer. But you don't need to care about that detail, just use the
67 driver can be used as a reference example how to use the above helpers.
69 Final note: If you plan to use DMA with I2C (or with anything else, actually)
|
| /Documentation/timers/ |
| D | timers-howto.rst | 21 You must use the `*delay` family of functions. These
22 functions use the jiffie estimation of clock speed
35 In general, use of mdelay is discouraged and code should
36 be refactored to allow for the use of msleep.
39 You should use the `*sleep[_range]` family of functions.
64 * Use udelay
74 * Use usleep_range
104 * Use msleep or possibly msleep_interruptible
111 early by a signal. In general, just use msleep unless
115 * Use fsleep
|
| /Documentation/core-api/ |
| D | idr.rst | 20 The IDR interface is deprecated; please use the :doc:`XArray <xarray>`
41 these users have been content with a ``UINT_MAX`` limit, and they use
45 If you need to allocate IDs sequentially, you can use
50 either use the callback-based idr_for_each() or the
51 iterator-style idr_for_each_entry(). You may need to use
53 also use idr_get_next() if the iterator doesn't fit your needs.
57 pointed to from the IDR; if you want to do that, use one of the iterators
60 You can use idr_is_empty() to find out whether there are any
|
| D | memory-allocation.rst | 11 `alloc_pages`. It is also possible to use more specialized allocators,
14 Most of the memory allocation APIs use GFP flags to express how that
20 answer, although very likely you should use
41 many other allocations types can use ``GFP_KERNEL``. Note, that
46 handler, use ``GFP_NOWAIT``. This flag prevents direct reclaim and
51 will be stressed unless allocation succeeds, you may use ``GFP_ATOMIC``.
56 * Userspace allocations should use either of the ``GFP_USER``,
77 use new scope APIs described in
84 And even with hardware with restrictions it is preferable to use
134 The most straightforward way to allocate memory is to use a function
[all …]
|
| D | symbol-namespaces.rst | 5 The following document describes how to use Symbol Namespaces to structure the
15 === 3 How to use Symbols exported in Namespaces
16 === 4 Loading Modules that use namespaced Symbols
26 limiting the availability of a set of symbols for use in other parts of the
27 kernel. As of today, modules that make use of symbols exported into namespaces,
47 namespace ``USB_STORAGE``, use::
54 and kernel/module/main.c make use the namespace at build time or module load
66 subsystem and the maintainer's preference, which one to use. The first option
87 3. How to use Symbols exported in Namespaces
90 In order to use symbols that are exported into namespaces, kernel modules need
[all …]
|
| /Documentation/devicetree/bindings/extcon/ |
| D | wlf,arizona.yaml | 30 wlf,use-jd2:
32 Use the additional JD input along with JD1 for dual pin jack detection.
35 wlf,use-jd2-nopull:
47 Use a software comparison to determine mic presence.
105 will use MICDET1 and 0x2000 will use MICDET2.
109 will use MICVDD, 1-3 will use MICBIASx.
|
| /Documentation/fb/ |
| 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 …]
|
| 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 …]
|
| D | tridentfb.rst | 31 How to use it?
47 fp use flat panel related stuff
51 image, otherwise use
54 memsize integer value in KB, use if your card's memory size is misdetected.
60 Only use if your video memory is taken from main memory hence of
61 configurable size. Otherwise use memsize.
67 800 or 1280) and it is not what the driver seems to detect use it.
|
| /Documentation/networking/ |
| D | smc-sysctl.rst | 20 Applications can still use TCP_CORK for optimal behavior when they
26 Controls which type of sndbufs and RMBs to use in later newly created
33 - 0 - Use physically contiguous buffers
34 - 1 - Use virtually contiguous buffers
35 - 2 - Mixed use of the two types. Try physically contiguous buffers first.
36 If not available, use virtually contiguous buffers then.
|
| /Documentation/admin-guide/nfs/ |
| 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 …]
|
| /Documentation/sound/hd-audio/ |
| D | dp-mst.rst | 13 several pins, if we use one pcm per per_pin, there will be many PCMs.
15 per_pin. Driver uses spec->dyn_pcm_assign flag to indicate whether to use
69 Will not use hda_jack but use snd_jack in spec->pcm_rec[pcm_idx].jack directly.
73 Use hda_jack and assign spec->pcm_rec[pcm_idx].jack = jack->jack statically.
88 Use directly snd_jack_report() on spec->pcm_rec[pcm_idx].jack for
96 Use directly snd_jack_report() on spec->pcm_rec[pcm_idx].jack for dyn_pcm_assign.
97 Use hda_jack mechanism to handle jack events.
|
| /Documentation/process/ |
| D | email-clients.rst | 9 These days most developers use ``git send-email`` instead of regular
11 end, maintainers use ``git am`` to apply the patches.
28 It's also strongly recommended that you use plain text in your email body,
56 Don't use PGP/GPG signatures in mail that contains patches.
95 Works. Some people use this successfully for patches.
97 To insert a patch use :menuselection:`Message-->Insert File` (:kbd:`CTRL-I`)
108 Some people use this successfully for patches.
114 Then use:
124 Some people use Kmail successfully for patches.
163 :menuselection:`save as`. You can use the whole email unmodified as a patch
[all …]
|
| /Documentation/driver-api/pci/ |
| D | p2pdma.rst | 23 The second issue is that to make use of existing interfaces in Linux,
38 * Client - A driver which makes use of a resource by setting up a
51 to be used directly (client) and it can also make use of the CMB as
62 then the NVMe Target could use the RNIC's memory instead of the CMB
63 in cases where the NVMe cards in use do not have CMB support.
75 any orchestrator drivers to find and use the memory. When marked in
86 A client driver only has to use the mapping API :c:func:`dma_map_sg()`
97 block device and the RNIC in use. If the orchestrator has access to
98 a specific P2P provider to use it may check compatibility using
104 truly random). This function returns the PCI device to use for the provider
[all …]
|
| /Documentation/arch/arm64/ |
| 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 …]
|
| /Documentation/devicetree/bindings/watchdog/ |
| D | da9062-wdt.txt | 10 - dlg,use-sw-pm: Add this property to disable the watchdog during suspend.
11 Only use this option if you can't use the watchdog automatic suspend
15 POWERDOWN. Can be 0 or 1. Only use this option if you want to change the
|
| /Documentation/devicetree/bindings/sound/ |
| D | rt5640.txt | 41 1: Use GPIO1 for jack-detect
42 2: Use JD1_IN4P for jack-detect
43 3: Use JD2_IN4N for jack-detect
44 4: Use GPIO2 for jack-detect
45 5: Use GPIO3 for jack-detect
46 6: Use GPIO4 for jack-detect
|
| /Documentation/devicetree/bindings/regulator/ |
| D | richtek,rtq2134-regulator.yaml | 38 richtek,use-vsel-dvs:
42 Else, use dvs0 voltage by default.
47 If specified, use shutdown as UV action. Else, hiccup by default.
76 richtek,use-vsel-dvs;
87 richtek,use-vsel-dvs;
98 richtek,use-vsel-dvs;
|
| /Documentation/driver-api/gpio/ |
| D | using-gpio.rst | 7 and preferred way to use GPIO lines is to let kernel hardware drivers deal
24 industrial automation, PLC-type use cases, door controllers, in short a piece
32 Applications that have a good reason to use the industrial I/O (IIO) subsystem
37 any product development projects. If you use it for prototyping, then do not
43 ``/dev/gpiochipN``. Examples of how to directly use the userspace ABI can be
46 For structured and managed applications, we recommend that you make use of the
|
12345678910>>...101