Searched full:needs (Results 1 – 25 of 837) sorted by relevance
12345678910>>...34
| /Documentation/block/ |
| D | writeback_cache_control.rst | 12 system needs to force data out to the non-volatile storage when it performs
57 For devices with volatile write caches the driver needs to tell the block layer
63 bit the block layer needs to be told to pass on the REQ_FUA bit by also setting
75 needs to handle them.
78 _not_ set. Any bio based driver that sets BLK_FEAT_WRITE_CACHE also needs to
82 devices, and a global flush needs to be implemented for bios with the
|
| /Documentation/devicetree/bindings/mux/ |
| D | mux-consumer.yaml | 28 If it is required to provide the state that the mux controller needs to
34 the consumers want to control the mux controller. If the consumer needs
35 needs to set multiple states in a mux controller, then property
36 "mux-controls" can be used. If the consumer needs to set the mux
|
| /Documentation/ABI/testing/ |
| D | sysfs-platform-kim | 21 UART configurations, so the baud-rate needs to be set
47 by the sysfs_notify. The value would be '1' when UART needs
49 is no more required and needs to be closed.
|
| D | sysfs-bus-event_source-devices-hv_gpci | 94 * User needs root privileges to read data from this sysfs file.
126 * User needs root privileges to read data from this sysfs file.
158 * User needs root privileges to read data from this sysfs file.
190 * User needs root privileges to read data from this sysfs file.
222 * User needs root privileges to read data from this sysfs file.
|
| /Documentation/kbuild/ |
| D | Kconfig.recursion-issue-01 | 10 # Kconfig needs to address. We iterate over what Kconfig needs to address
11 # by stepping through the questions it needs to address sequentially.
|
| /Documentation/devicetree/bindings/firmware/ |
| D | intel,stratix10-svc.txt | 5 configured from HPS, there needs to be a way for HPS to notify SDM the
9 To meet the whole system security needs and support virtual machine requesting
12 exception layers must channel through the EL3 software whenever it needs
|
| /Documentation/admin-guide/nfs/ |
| D | pnfs-block-server.rst | 12 system needs to support the pNFS block layouts (currently just XFS), and the
14 to the clients in addition to the MDS. As of now the file system needs to
23 If the nfsd server needs to fence a non-responding client it calls
|
| D | pnfs-scsi-server.rst | 13 system needs to support the pNFS SCSI layouts (currently just XFS), and the
15 addition to the MDS. As of now the file system needs to sit directly on the
|
| /Documentation/driver-api/ |
| D | sync_file.rst | 47 When a driver needs to send an out-fence userspace it creates a sync_file.
54 first step, next it needs to install an fd on sync_file->file. So it gets an
65 If the creation process fail, or the sync_file needs to be released by any
71 When userspace needs to send an in-fence to the driver it passes file descriptor
|
| D | ipmb.rst | 45 The driver needs to be loaded at boot time or manually first.
79 then "i2c-protocol" needs to be defined as above.
108 by the user space program. The device needs to be instantiated
|
| /Documentation/devicetree/bindings/sound/ |
| D | nuvoton,nau8325.yaml | 48 FS range is from 8kHz to 96kHz. And also needs to detect the ratio
49 MCLK_SRC/LRCK of 256, 400 or 500, and needs to detect the BCLK
50 to make sure data is present. There needs to be at least 8 BCLK
|
| /Documentation/watchdog/ |
| D | convert_drivers_to_kernel_api.rst | 24 close preparations) can simply go. Device specific stuff needs to go to the
42 Needs the status-callback defined, otherwise returns 0
45 Needs the bootstatus member properly set. Make sure it is 0 if you
65 It needs get_timeleft() callback to be defined. Otherwise it
176 used. This needs to be converted by initializing the status variable of the
186 The module parameter itself needs to stay, everything else related to nowayout
209 The entry for the driver now needs to select WATCHDOG_CORE:
|
| /Documentation/networking/devlink/ |
| D | index.rst | 19 Drivers are encouraged to use the devlink instance lock for their own needs.
22 taking RTNL lock at the same time. Devlink instance lock needs to be taken
32 - Lock ordering should be maintained. If driver needs to take instance
|
| /Documentation/process/ |
| D | botching-up-ioctls.rst | 70 needs a new driver feature flags.
92 * The ioctl must check for array overflows. Also it needs to check for
165 and suiting to your needs.
172 the given GPU platforms. This means a driver needs to expose tons of handles
178 needs to be shared across processes - fd-passing over unix domain sockets
194 command submission ioctl. But then if objects are shareable userspace needs
205 Not every problem needs a new ioctl:
217 maybe only your testsuite needs this interface, and then debugfs with its
|
| /Documentation/bpf/standardization/ |
| D | abi.rst | 24 R0 - R5 are scratch registers and BPF programs needs to spill/fill them if
27 The BPF program needs to store the return value into register R0 before doing an
|
| /Documentation/devicetree/bindings/ |
| D | common-properties.txt | 15 know the peripheral always needs to be accessed in big endian (BE) mode.
18 peripheral always needs to be accessed in little endian (LE) mode.
71 by all of its devices. The driver needs to know how many devices the
|
| /Documentation/admin-guide/ |
| D | dell_rbu.rst | 40 The rbu driver needs to have an application (as mentioned above) which will
73 In the packet update mechanism, the user needs to create a new file having
78 packet, the user needs to create more such packets out of the entire BIOS
124 After updating the BIOS image a user mode application needs to execute
|
| /Documentation/devicetree/bindings/mmc/ |
| D | ti-omap-hsmmc.txt | 43 - ti,needs-special-reset: Requires a special softreset sequence
44 - ti,needs-special-hs-handling: HSMMC IP needs special setting
117 not every application needs SDIO irq, e.g. MMC cards.
|
| /Documentation/driver-api/usb/ |
| D | writing_usb_driver.rst | 24 needs to be created. Some vendors are open with their USB protocols and
35 different pieces and what needs to be done to customize it to your
49 The first thing a Linux USB driver needs to do is register itself with
83 this user-space interaction. The skeleton driver needs this kind of
107 When the driver is unloaded from the system, it needs to deregister
148 The driver now needs to verify that this device is actually one that it
159 function is called with the device pointer. The driver needs to clean
266 it. It needs to be able to shut down any current reads and writes and
|
| /Documentation/filesystems/xfs/ |
| D | xfs-self-describing-metadata.rst | 79 As a primary concern, self describing metadata needs some form of overall
90 could be used, it is more than sufficient for our needs and has relatively
96 Self describing metadata needs to contain enough information so that the
98 look at any other metadata. This means it needs to contain location information.
123 Self describing metadata also needs to contain some indication of when it was
166 For read verification, the caller needs to specify the expected type of metadata
169 marks the object being read as EFSCORRUPTED. The caller needs to catch this
170 error (same as for IO errors), and if it needs to take special action due to a
192 A typical on-disk structure needs to contain the following information::
353 repair will probably complain about it - but it needs to be fixed.
|
| /Documentation/devicetree/bindings/usb/ |
| D | chipidea,usb2-common.yaml | 108 value. It needs to be very carefully for setting this property, it
121 bytes, software needs to make sure it does not send more than 90%
140 In this case, the "idle" state needs to pull down the data and
141 strobe pin and the "active" state needs to pull up the strobe pin.
|
| D | atmel-usb.txt | 16 - atmel,vbus-gpio: If present, specifies a gpio that needs to be
18 - atmel,oc-gpio: If present, specifies a gpio that needs to be
70 - atmel,vbus-gpio: If present, specifies a gpio that needs to be
|
| /Documentation/networking/ |
| D | xfrm_device.rst | 132 When ready to send, the driver needs to inspect the Tx packet for the
141 packet data, the offload just needs to do the encryption and fix up the
146 decryption, the driver needs to add a reference to the decoded SA into
186 hardware needs.
195 occuried, the driver needs to call to xfrm_state_check_expire() to make sure
|
| /Documentation/arch/arm64/ |
| D | kdump.rst | 21 large chunk of memomy can be found. The low memory reservation needs to
63 sufficient for the low memory needs of the kdump kernel.
73 crashkernel=size. They allows the user to specify how much memory needs
|
| /Documentation/rust/ |
| D | quick-start.rst | 157 in the kernel, which means LLVM needs to be installed; like when the kernel
214 thus nothing needs to be done. If another profile is being used, the component
230 thus nothing needs to be done. If another profile is being used, the component
250 thus nothing needs to be done.
262 ``rust-analyzer`` needs a configuration file, ``rust-project.json``, which
271 ``Rust support`` (``CONFIG_RUST``) needs to be enabled in the ``General setup``
|
12345678910>>...34