Searched full:need (Results 1 – 25 of 1058) sorted by relevance
12345678910>>...43
| /Documentation/devicetree/bindings/sound/ |
| D | sirf-audio.txt | 9 - hp-pa-gpios: Need to be present if the board need control external
11 - spk-pa-gpios: Need to be present if the board need control external
13 - hp-switch-gpios: Need to be present if the board capable to detect jack
|
| /Documentation/core-api/ |
| D | idr.rst | 31 If you need to change the pointer associated with an ID, you can call
37 Some users need to allocate IDs larger than ``INT_MAX``. So far all of
39 :c:func:`idr_alloc_u32`. If you need IDs that will not fit in a u32,
42 If you need to allocate IDs sequentially, you can use
48 iterator-style :c:func:`idr_for_each_entry`. You may need to use
60 If you need to take a lock while allocating a new ID from the IDR,
61 you may need to pass a restrictive set of GFP flags, which can lead
|
| /Documentation/networking/ |
| D | ipddp.txt | 27 will need to turn on AppleTalk-IP driver support. Then you will need to
40 need to consult the supporting documentation for each set of tools.
42 Decapsulation - You will need to download a software package called
52 Encapsulation - You will need to download a software daemon called ipddpd.
54 You will also need to add the proper routes to route your Linux box's IP
|
| D | ltpc.txt | 3 In order to use it, you will need at least version 1.3.3 of the
34 need to add a line such as:
44 printers, you need to set up netatalk to "seed". The way I do this
50 in my atalkd.conf. What is going on here is that I need to fool
55 compiled as a module, you will need to refer to it as "dummy0" or some
59 it, then you don't need to fool around with this -- the appropriate
|
| D | ax25.txt | 1 To use the amateur radio protocols within Linux you will need to get a
9 of the message, the subject field is ignored. You don't need to be
|
| D | tc-actions-env-rules.txt | 8 or intentionally branches by redirecting a packet, then you need to
21 returned, then all is great and you don't need to do anything.
|
| D | z8530book.rst | 50 configure a Z8530 interface you need to detect the board and to identify
54 Having identified the chip you need to fill in a struct z8530_dev,
107 you need to attach a network device to each channel that is present and
108 in use. In addition to use the generic HDLC you need to follow some
114 device points to your private data - you will need to be able to find
122 If you wish to use the generic HDLC then you need to register the HDLC
125 Before you register your network device you will also need to provide
150 register values. It may need to reload values. You should therefore be
226 Should you need to retarget the Z8530 driver to another architecture the
227 only code that should need changing are the port I/O functions. At the
|
| D | arcnet.txt | 108 All you will need to do in order to install the driver is:
116 your current kernel, you will need to first copy arcnet.c over the one in
194 If you're using a loadable module, you need to use insmod to load it, and
234 If you have the chipset support built as a loadable module, then you need to
249 you never know what you might need.
251 With AmiTCP (and possibly others), you may need to set the following
263 initialization. In fact, if you use it on a 386+ you REALLY need
283 ARCnet packets. If you use ODI, you'll need to use the 'arc0'
285 See the "Multiprotocol Support" section below if you need arc0e,
286 you're completely insane, and/or you need to build some kind of
[all …]
|
| /Documentation/filesystems/ |
| D | journalling.rst | 10 The journalling layer is easy to use. You need to first of all create a
20 Once you have got your journal_t object you need to 'mount' or load the
25 does not need to be processed (or even need not have valid contents), it
38 You still need to actually journal your filesystem changes, this is done
39 by wrapping them into transactions. Additionally you also need to wrap
52 Inside each transaction you need to wrap the modifications to the
54 need to call :c:func:`jbd2_journal_get_create_access()` /
60 buffer, and once you are have done so you need to call
100 strategy. Why? Because, if you do a delete, you need to ensure you
116 that need processing when the transaction commits.
|
| D | bfs.txt | 8 In order to access /stand partition under Linux you obviously need to
18 When you have finished using it and umounted you need to also deallocate
32 /proc/mounts. You will need to do it manually using "-d" switch of
35 To create the BFS image under UnixWare you need to find out first which
|
| D | xfs-delayed-logging-design.txt | 135 need to ensure application level data integrity is maintained.
163 changes to the log buffers, we need to ensure that the object we are formatting
192 Hence we avoid the need to lock items when we need to flush outstanding
222 The memory buffer and associated vector need to be passed as a single object,
223 but still need to be associated with the parent object so if the object is
230 are in the item, so we'd need a new encapsulation method for regions in the log
236 Hence we need to keep the vector, but by attaching the memory buffer to it and
247 them to be used without limitations, we need to be able to track and accumulate
284 We need to write these items in the order that they exist in the CIL, and they
285 need to be written as an atomic transaction. The need for all the objects to be
[all …]
|
| /Documentation/driver-api/usb/ |
| D | typec_bus.rst | 11 every alternate mode, so every alternate mode will need a custom driver.
31 needed from the port drivers, but the port drivers need to provide the operation
33 drivers need to provide them for the partner alternate mode devices.
52 in need to reconfigure the pins on the connector, the alternate mode driver
57 chain to notify the external drivers about the state of the connector that need
86 The drivers for the components that the alternate modes are designed for need to
89 example, the GPU drivers will need to know those details. In case of
90 Thunderbolt alternate mode, the thunderbolt drivers will need to know them, and
|
| /Documentation/devicetree/bindings/display/tegra/ |
| D | nvidia,tegra114-mipi.txt | 11 that need to be calibrated for a given device.
13 User nodes need to contain an nvidia,mipi-calibrate property that has a
15 that need to be calibrated.
|
| /Documentation/scheduler/ |
| D | sched-arch.rst | 11 locked. This is usually not a problem unless switch_to may need to
24 Your cpu_idle routines need to obey the following rules:
31 threads need only ever query need_resched, and may never set or
37 4. The only time interrupts need to be disabled when checking
52 need an interrupt to wake them up when need_resched goes high.
|
| /Documentation/devicetree/bindings/mfd/ |
| D | twl4030-audio.txt | 12 - codec { }: Need to be present if the audio functionality is used. Within this
14 - ti,digimic_delay: Delay need after enabling the digimic to reduce artifacts
23 - ti,enable-vibra: Need to be set to <1> if the vibra functionality is used. if
|
| /Documentation/media/kapi/ |
| D | v4l2-device.rst | 19 Drivers that want integration with the media device framework need to set
45 to notify you of events. Whether you need to set this depends on the
66 This does *not* unregister the subdevs, so you still need to call the
68 hotpluggable, then there is no need to call :c:func:`v4l2_device_disconnect`.
70 Sometimes you need to iterate over all devices registered by a specific
104 Sometimes you need to keep a running counter of the device instance. This is
138 Since the initial refcount is 1 you also need to call
|
| /Documentation/driver-api/ |
| D | device_connection.rst | 10 could be a PCI device, may need to be able to get a reference to its PHY
12 drivers need to be able to control the clocks or the GPIOs for their devices,
30 descriptions are "built-in", and need to be added separately.
|
| /Documentation/RCU/ |
| D | listRCU.rst | 20 Therefore, once the route has been computed, there is no need to hold
145 can therefore be eliminated, since use of RCU eliminates the need for
165 otherwise, the added fields would need to be filled in)::
237 Why does the search function need to return holding the per-entry lock for
242 If the system-call audit module were to ever need to reject stale data,
272 audit_upd_rule() would need additional memory barriers to ensure
275 The audit_del_rule() function would need to set the "deleted"
283 /* Do not need to use the _rcu iterator here, since this
313 Why does the search function need to return holding the per-entry
318 is really OK to be processing stale data, then you don't need a
[all …]
|
| /Documentation/gpu/ |
| D | todo.rst | 31 There is a conversion guide for atomic and all you need is a GPU for a
35 As part of this drivers also need to convert to universal plane (which means
77 ``GFP_NOFAIL`` behind the scenes. All legacy paths need to start allocating
103 Core GEM doesn't have a need for ``struct_mutex`` any more since kernel 4.8,
107 For drivers that need ``struct_mutex`` it should be replaced with a driver-
173 which means drivers need to have a special framebuffer for fbdev. Which prevents
179 emulation. It would need to fully wrap the existing mmap ops, forwarding
182 - In the drm_fbdev_fb_mmap helper, if we need defio, change the
215 We also need a 2nd version of the CMA define that doesn't require the
277 these igt tests need to be fixed: kms_fbcon_fbt@psr and
[all …]
|
| /Documentation/trace/ |
| D | ftrace-design.rst | 37 You will need to implement the mcount and the ftrace_stub functions.
119 Deep breath ... time to do some real work. Here you will need to update the
243 You need very few things to get the syscalls tracing in an arch.
272 You will first need HAVE_FTRACE_MCOUNT_RECORD and HAVE_FUNCTION_TRACER, so
275 Once those are out of the way, you will need to implement:
291 First you will need to fill out some arch details in your asm/ftrace.h.
297 Since no one else will have a decl for that function, you will need to::
301 You will also need the helper function ftrace_call_adjust(). Most people
311 Lastly you will need the custom dyn_arch_ftrace structure. If you need
359 runtime patching. You'll need a little knowledge of your arch's opcodes in
[all …]
|
| /Documentation/scsi/ |
| D | 53c700.txt | 8 Since the 53c700 must be interfaced to a bus, you need to wrapper the
12 The comments in the 53c700.[ch] files tell you which parts you need to
31 driver, you need to know three things about the way the chip is wired
38 Optionally, you may also need to know other things, like how to read
65 In the detect routine, you need to allocate a struct
|
| /Documentation/locking/ |
| D | spinlocks.rst | 21 lock. This works well even under UP also, so the code does _not_ need to
32 The above is usually pretty simple (you usually need and want only one
35 sequences that you **know** need to be split up: avoid it at all cost if you
88 time need to do any changes (even if you don't do it every time), you have
103 than they'd need to be, because they do have to disable interrupts
136 (This is also the reason why the irq-versions of the spinlocks only need
|
| /Documentation/i2c/ |
| D | gpio-fault-injection.rst | 58 This file is write only and you need to write the address of an existing I2C
70 Similar to above, this file is write only and you need to write the address of
95 This file is write only and you need to write the duration of the arbitration
103 There doesn't need to be a device at this address because arbitration lost
124 This file is write only and you need to write the delay between the detected
135 Note that there doesn't need to be a device listening to the address you are
|
| /Documentation/ |
| D | DMA-ISA-LPC.txt | 14 To do ISA style DMA you need to include two headers::
34 (You usually need a special buffer for DMA transfers instead of
58 is really all you need. Remember that even though the DMA controller
89 Before you use any ISA DMA routines you need to claim the DMA lock
97 (and everyone else) uses the locking functions then you only need to
|
| /Documentation/pcmcia/ |
| D | devicetable.rst | 17 If you want to match product ID strings, you also need to pass the crc32
19 string 1, you need to use
|
12345678910>>...43