Home
last modified time | relevance | path

Searched refs:use (Results 1 – 25 of 2855) sorted by relevance

12345678910>>...115

/linux/drivers/gpu/drm/nouveau/nvkm/core/
H A Dsubdev.c57 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()
179 mutex_lock(&subdev->use.mutex); in nvkm_subdev_oneinit()
181 mutex_unlock(&subdev->use.mutex); in nvkm_subdev_oneinit()
[all …]
/linux/tools/perf/Documentation/
H A Dtips.txt16 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 {}: perf record -e {cycles,branches}' ...
40 To compute metrics for samples use perf record -e '{cycles,instructions}' ... ; perf script -F +metric
43 When collecting LBR backtraces use
[all...]
/linux/arch/arm/boot/dts/microchip/
H A Dat91-kizbox3_common.dtsi259 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 …]
H A Dat91-wb50n.dtsi76 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;
/linux/net/x25/
H A Dx25_route.c137 struct x25_route *rt, *use = NULL; in x25_get_route() local
143 if (!use) in x25_get_route()
144 use = rt; in x25_get_route()
145 else if (rt->sigdigits > use->sigdigits) in x25_get_route()
146 use = rt; in x25_get_route()
150 if (use) in x25_get_route()
151 x25_route_hold(use); in x25_get_route()
154 return use; in x25_get_route()
/linux/Documentation/ABI/testing/
H A Dsysfs-platform-asus-wmi66 DEPRECATED, WILL BE REMOVED SOON: please use asus-armoury
79 DEPRECATED, WILL BE REMOVED SOON: please use asus-armoury
89 DEPRECATED, WILL BE REMOVED SOON: please use asus-armoury
101 DEPRECATED, WILL BE REMOVED SOON: please use asus-armoury
111 DEPRECATED, WILL BE REMOVED SOON: please use asus-armoury
122 DEPRECATED, WILL BE REMOVED SOON: please use asus-armoury
132 DEPRECATED, WILL BE REMOVED SOON: please use asus-armoury
143 DEPRECATED, WILL BE REMOVED SOON: please use asus-armoury
151 DEPRECATED, WILL BE REMOVED SOON: please use asus-armoury
162 DEPRECATED, WILL BE REMOVED SOON: please use asus-armoury
[all …]
/linux/drivers/usb/serial/
H A DKconfig16 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/driver-api/
H A Dwbrf.rst13 frequencies in use and consumers can use this information to avoid using
19 * Producers with this _DSM will be able to advertise the frequencies in use.
21 frequencies in use.
27 Consumer: such component who can adjust its in-use frequency in
31 To make the mechanism function, those producers should notify active use
38 Although initially used by for wifi + dGPU use cases, the ACPI interface
47 * 1: record RF bands in use
48 * 2: retrieve RF bands in use
/linux/drivers/w1/slaves/
H A DKconfig23 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/fb/
H A Dsisfb.rst38 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 …]
H A Dtridentfb.rst31 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.
H A Duvesafb.rst11 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 …]
/linux/Documentation/networking/device_drivers/ethernet/ti/
H A Dtlan.rst75 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 …]
/linux/Documentation/dev-tools/kunit/
H A Drun_manual.rst7 If we do not want to use kunit_tool (For example: we want to integrate
11 .. note:: KUnit is not designed for use in a production system. It is
65 mounted at /sys/kernel/debug/kunit. You can use this filesystem to perform
71 You can use debugfs to retrieve KUnit test results. The test results are
84 You can use the debugfs filesystem to trigger built-in tests to run after
85 boot. To run the test suite, you can use the following command to write to
95 However, this feature is not available with KUnit suites that use init data,
97 suites that use init data should be defined using the
100 Also, you cannot use this feature to run tests concurrently. Instead a test
105 For test authors, to use this feature, tests will need to correctly initialise
/linux/tools/usb/usbip/
H A Dconfigure.ac54 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_SOURCE=2 option when compiling)])],
/linux/arch/microblaze/boot/dts/
H A Dsystem.dts66 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 …]
/linux/drivers/staging/axis-fifo/
H A Daxis-fifo.txt53 - xlnx,use-rx-cut-through: Should be <0x0> (this feature isn't supported)
54 - xlnx,use-rx-data: <0x1> if RX FIFO is enabled, <0x0> otherwise
55 - xlnx,use-tx-ctrl: Should be <0x0> (this feature isn't supported)
56 - xlnx,use-tx-cut-through: Should be <0x0> (this feature isn't supported)
57 - xlnx,use-tx-data: <0x1> if TX FIFO is enabled, <0x0> otherwise
91 xlnx,use-rx-cut-through = <0x0>;
92 xlnx,use-rx-data = <0x0>;
93 xlnx,use-tx-ctrl = <0x0>;
94 xlnx,use-tx-cut-through = <0x0>;
95 xlnx,use-tx-data = <0x1>;
/linux/drivers/crypto/intel/keembay/
H A DKconfig10 SM4 cipher hardware acceleration for use with Crypto API.
24 AES/SM4 ECB mode hardware acceleration for use with Crypto API.
28 Intel does not recommend use of ECB mode with AES/SM4.
35 AES/SM4 CBC with CTS mode hardware acceleration for use with
40 Intel does not recommend use of CTS mode with AES/SM4.
51 Elliptic Curve Cryptography (ECC) hardware acceleration for use with
70 Control Unit (HCU) hardware acceleration for use with Crypto API.
85 Keem Bay OCS HCU driver. Intel recommends not to use these
/linux/Documentation/core-api/
H A Didr.rst20 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
/linux/Documentation/i2c/
H A Ddma-considerations.rst13 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)
/linux/Documentation/trace/
H A Duser_events.rst17 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 …]
/linux/drivers/staging/sm750fb/
H A Dreadme14 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.
/linux/drivers/net/slip/
H A DKconfig10 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
20 to be able to use it, but there is now a SLIP emulator called SLiRP
23 allows you to use SLIP over a regular dial up shell connection. If
24 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
53 answer Y, just in case. You will still be able to use plain SLIP. If
54 you plan to use SLiRP, the SLIP emulator (available from
56 allows you to use SLIP over a regular dial up shell connection, you
75 bit. Saying Y here adds an extra mode you can use with SLIP:
/linux/include/linux/netfilter/
H A Dnf_conntrack_common.h28 refcount_t use; member
36 if (nfct && refcount_dec_and_test(&nfct->use)) in nf_conntrack_put()
42 refcount_inc(&nfct->use); in nf_conntrack_get()
/linux/net/atm/
H A Dmpoa_caches.c44 refcount_inc(&entry->use); in in_cache_get()
65 refcount_inc(&entry->use); in in_cache_get_with_mask()
86 refcount_inc(&entry->use); in in_cache_get_by_vcc()
109 refcount_set(&entry->use, 1); in in_cache_add_entry()
125 refcount_inc(&entry->use); in in_cache_add_entry()
182 if (refcount_dec_and_test(&entry->use)) { in in_cache_put()
341 refcount_inc(&entry->use); in eg_cache_get_by_cache_id()
362 refcount_inc(&entry->use); in eg_cache_get_by_tag()
384 refcount_inc(&entry->use); in eg_cache_get_by_vcc()
404 refcount_inc(&entry->use); in eg_cache_get_by_src_ip()
[all …]

12345678910>>...115