| /kernel/linux/linux-5.10/drivers/gpu/drm/exynos/ |
| D | Kconfig | 23 Choose this option if you want to use Exynos FIMD for DRM.
28 Choose this option if you want to use Exynos5433 DECON for DRM.
34 Choose this option if you want to use Exynos DECON for DRM.
39 Choose this option if you want to use Exynos Mixer for DRM.
44 Choose this option if you want to use Exynos VIDI for DRM.
79 Choose this option if you want to use Exynos HDMI for DRM.
85 Choose this option if you want to use Exynos MIC for DRM.
94 Choose this option if you want to use Exynos G2D for DRM.
103 Choose this option if you want to use Exynos FIMC for DRM.
109 Choose this option if you want to use Exynos Rotator for DRM.
[all …]
|
| /kernel/linux/linux-5.10/arch/arm/boot/dts/ |
| D | at91-kizbox3_common.dtsi | 259 atmel,use-dma-rx;
260 atmel,use-dma-tx;
268 atmel,use-dma-rx;
269 atmel,use-dma-tx;
276 atmel,use-dma-rx;
277 atmel,use-dma-tx;
284 atmel,use-dma-rx;
285 atmel,use-dma-tx;
292 atmel,use-dma-rx;
293 atmel,use-dma-tx;
[all …]
|
| D | at91-sama5d27_wlsom1_ek.dts | 83 atmel,use-dma-rx;
84 atmel,use-dma-tx;
93 atmel,use-dma-rx;
94 atmel,use-dma-tx;
232 atmel,use-dma-rx;
233 atmel,use-dma-tx;
240 atmel,use-dma-rx;
241 atmel,use-dma-tx;
|
| D | at91-wb50n.dtsi | 76 dmas = <0>, <0>; /* Do not use DMA for dbgu */
81 atmel,use-dma-rx;
82 atmel,use-dma-tx;
89 atmel,use-dma-rx;
90 atmel,use-dma-tx;
101 atmel,use-dma-rx;
102 atmel,use-dma-tx;
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/mfd/ |
| D | atmel-usart.txt | 36 - atmel,use-dma-rx: use of PDC or DMA for receiving data
37 - atmel,use-dma-tx: use of PDC or DMA for transmitting data
39 It will use specified PIO instead of the peripheral function pin for the USART feature.
50 - use PDC:
57 atmel,use-dma-rx;
58 atmel,use-dma-tx;
67 - use DMA:
74 atmel,use-dma-rx;
75 atmel,use-dma-tx;
|
| /kernel/linux/linux-5.10/net/x25/ |
| D | x25_route.c | 151 struct x25_route *rt, *use = NULL; in x25_get_route() local
160 if (!use) in x25_get_route()
161 use = rt; in x25_get_route()
162 else if (rt->sigdigits > use->sigdigits) in x25_get_route()
163 use = rt; in x25_get_route()
167 if (use) in x25_get_route()
168 x25_route_hold(use); in x25_get_route()
171 return use; in x25_get_route()
|
| /kernel/linux/linux-5.10/drivers/usb/serial/ |
| 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 …]
|
| /kernel/linux/linux-5.10/Documentation/vm/ |
| D | swap_numa.rst | 8 information, we can make use of this information to decide which swap
9 device to use in get_swap_pages() to get better performance.
12 How to use this feature
16 use of automatically binding, there is no need to manipulate priority settings
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::
46 node 1 will use them in the order of::
50 node 2 will use them in the order of::
57 node 3 will use them in the order of::
[all …]
|
| /kernel/linux/linux-5.10/scripts/coccinelle/api/ |
| D | device_attr_show.cocci | 4 /// show() must not use snprintf() when formatting the value to be
6 /// will never happen you can use sprintf() otherwise you must use
49 coccilib.report.print_report(p[0], "WARNING: use scnprintf or sprintf")
55 coccilib.org.print_todo(p[0], "WARNING: use scnprintf or sprintf")
|
| /kernel/linux/linux-5.10/drivers/w1/slaves/ |
| 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 …]
|
| /kernel/linux/linux-5.10/Documentation/networking/device_drivers/ethernet/ti/ |
| D | tlan.rst | 75 the adapter to use the AUI interface instead of the 10 Base T
76 interface. This is also what to do if you want to use the BNC
89 5. You have to use speed=X duplex=Y together now. If you just
94 6. If the driver is built into the kernel, you can use the 3rd
107 0x02 use half duplex
108 0x04 use full duplex
109 0x08 use 10BaseT
110 0x10 use 100BaseTx
118 use the above options on a per adapter basis. To force a 100Mbit/HD
119 link with your eth1 adapter use::
[all …]
|
| /kernel/linux/linux-5.10/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 | 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.
|
| 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
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
114 not work for you and you use a X server, you'll probably want to
118 nocrtc Do not use CRTC timings while setting the video mode. This option
[all …]
|
| /kernel/linux/linux-5.10/tools/usb/usbip/ |
| D | configure.ac | 54 AC_MSG_CHECKING([whether to use the libwrap (TCP wrappers) library])
57 [use the libwrap (TCP wrappers) library])],
69 [use tcp wrapper]) wrap_LIB="-lwrap"],
83 AC_DEFINE([HAVE_LIBWRAP], [1], [use tcp wrapper])],
93 # use _FORTIFY_SOURCE
94 AC_MSG_CHECKING([whether to use fortify])
97 [use _FORTIFY_SROUCE option when compiling)])],
|
| /kernel/linux/linux-5.10/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
87 routine to use the mapping function :c:func:`pci_p2pdma_map_sg()` instead
91 The client may also, optionally, make use of
92 :c:func:`is_pci_p2pdma_page()` to determine when to use the P2P mapping
93 functions and when to use the regular mapping functions. In some
[all …]
|
| /kernel/linux/linux-5.10/drivers/staging/axis-fifo/ |
| D | axis-fifo.txt | 50 - xlnx,use-rx-cut-through: Should be <0x0> (this feature isn't supported)
51 - xlnx,use-rx-data: <0x1> if RX FIFO is enabled, <0x0> otherwise
52 - xlnx,use-tx-ctrl: Should be <0x0> (this feature isn't supported)
53 - xlnx,use-tx-cut-through: Should be <0x0> (this feature isn't supported)
54 - xlnx,use-tx-data: <0x1> if TX FIFO is enabled, <0x0> otherwise
88 xlnx,use-rx-cut-through = <0x0>;
89 xlnx,use-rx-data = <0x0>;
90 xlnx,use-tx-ctrl = <0x0>;
91 xlnx,use-tx-cut-through = <0x0>;
92 xlnx,use-tx-data = <0x1>;
|
| /kernel/linux/linux-5.10/arch/microblaze/boot/dts/ |
| D | system.dts | 66 xlnx,dcache-use-fsl = <0x1>;
83 xlnx,icache-use-fsl = <0x1>;
103 xlnx,use-barrel = <0x1>;
104 xlnx,use-dcache = <0x1>;
105 xlnx,use-div = <0x1>;
106 xlnx,use-ext-brk = <0x1>;
107 xlnx,use-ext-nm-brk = <0x1>;
108 xlnx,use-extended-fsl-instr = <0x0>;
109 xlnx,use-fpu = <0x2>;
110 xlnx,use-hw-mul = <0x2>;
[all …]
|
| /kernel/linux/linux-5.10/include/linux/netfilter/ |
| D | nf_conntrack_common.h | 27 atomic_t use; member
33 if (nfct && atomic_dec_and_test(&nfct->use)) in nf_conntrack_put()
39 atomic_inc(&nfct->use); in nf_conntrack_get()
|
| /kernel/linux/linux-5.10/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.
66 - DO use non-empty 'ranges' to limit the size of child buses/devices. 64-bit
|
| /kernel/linux/linux-5.10/drivers/staging/media/ipu3/ |
| D | ipu3-css-params.h | 8 struct ipu3_uapi_flags *use,
14 struct ipu3_uapi_flags *use,
19 struct ipu3_uapi_flags *use,
|
| /kernel/linux/linux-5.10/Documentation/core-api/ |
| 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 …]
|
| /kernel/linux/linux-5.10/drivers/staging/sm750fb/ |
| D | readme | 14 and use a 800x600 mode :
20 and user can use con2fb to link fbX and ttyX
33 refresh rate, kernel driver will defaulty use 16bpp and 60hz
37 and this driver will use fb1, fb2. In that case, you need to configure your X-server
38 to use fb1. Another simple althernative is to disable vesafb from your config.
|
| /kernel/linux/linux-5.10/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)
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/ |
| 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
|