Home
last modified time | relevance | path

Searched full:needs (Results 1 – 25 of 631) sorted by relevance

12345678910>>...26

/Documentation/filesystems/nfs/
Dpnfs-block-server.txt10 system needs to support the pNFS block layouts (currently just XFS), and the
12 to the clients in addition to the MDS. As of now the file system needs to
21 If the nfsd server needs to fence a non-responding client it calls
Dpnfs-scsi-server.txt12 system needs to support the pNFS SCSI layouts (currently just XFS), and the
14 addition to the MDS. As of now the file system needs to sit directly on the
/Documentation/ABI/testing/
Dsysfs-platform-kim20 UART configurations, so the baud-rate needs to be set
46 by the sysfs_notify. The value would be '1' when UART needs
48 is no more required and needs to be closed.
/Documentation/devicetree/bindings/firmware/
Dintel,stratix10-svc.txt5 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/kbuild/
DKconfig.recursion-issue-0110 # 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/pinctrl/
Datmel,at91-pinctrl.txt89 PULL_UP (1 << 0): indicate this pin needs a pull up.
90 MULTIDRIVE (1 << 1): indicate this pin needs to be configured as multi-drive.
92 DEGLITCH (1 << 2): indicate this pin needs deglitch.
93 PULL_DOWN (1 << 3): indicate this pin needs a pull down.
94 DIS_SCHMIT (1 << 4): indicate this pin needs to the disable schmitt trigger.
104 DEBOUNCE (1 << 16): indicate this pin needs debounce.
/Documentation/devicetree/bindings/iio/pressure/
Dzpa2326.txt14 - vref-supply: an optional regulator that needs to be on to provide VREF
16 - vdd-supply: an optional regulator that needs to be on to provide VDD
/Documentation/devicetree/bindings/display/panel/
Dkoe,tx14d24vm1bpa.txt11 This panel needs single power supply voltage. Its backlight is conntrolled
31 Then one needs to extend the dispX node:
/Documentation/driver-api/
Dsync_file.rst47 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
Ddell_rbu.rst40 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/arm/samsung-s3c24xx/
Dcpufreq.rst29 framework needs to supply at least basic details of what is required.
65 The board needs to supply information about whether it needs the IO bank
/Documentation/watchdog/
Dconvert_drivers_to_kernel_api.rst24 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
177 used. This needs to be converted by initializing the status variable of the
187 The module parameter itself needs to stay, everything else related to nowayout
210 The entry for the driver now needs to select WATCHDOG_CORE:
/Documentation/ioctl/
Dbotching-up-ioctls.rst70 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/vm/
Dhighmem.rst17 at all times. This means the kernel needs to start using temporary mappings of
56 physical pages into a contiguous virtual space. It needs global
59 * kmap(). This permits a short duration mapping of a single page. It needs
131 * Linux needs a page-frame structure for each page in the system and the
136 worth of pages; the kernel, however, needs to store more than just
/Documentation/devicetree/bindings/
Dcommon-properties.txt15 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/block/
Dwriteback_cache_control.rst12 system needs to force data out to the non-volatile storage when it performs
55 bits need to be propagated to underlying devices, and a global flush needs
71 driver needs to tell the block layer that it supports flushing caches by
79 layer. For devices that also support the FUA bit the block layer needs
Dinline-encryption.rst29 en/decrypting a struct bio, and a device driver (like UFS) needs to be able
57 On the device driver end of the interface, the device driver needs to tell the
65 referencing that keyslot). When a new encryption context needs a keyslot, it
79 present a unified view of encryption to the FS (so FS only needs to specify
85 Blk-crypto needs to ensure that the encryption context is programmed into the
141 It then simply needs to check if the bio's ``bc_ksm`` is the device's
/Documentation/networking/dsa/
Dconfiguration.rst91 # The master interface needs to be brought up before the slave ports.
104 # The master interface needs to be brought up before the slave ports.
131 # The master interface needs to be brought up before the slave ports.
175 # The master interface needs to be brought up before the slave ports.
219 # The master interface needs to be brought up before the slave ports.
260 # The master interface needs to be brought up before the slave ports.
/Documentation/networking/
Dxfrm_device.txt89 When ready to send, the driver needs to inspect the Tx packet for the
98 packet data, the offload just needs to do the encryption and fix up the
103 decryption, the driver needs to add a reference to the decoded SA into
134 hardware needs.
/Documentation/devicetree/bindings/mmc/
Dti-omap-hsmmc.txt43 - 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/
Dwriting_usb_driver.rst24 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
80 this user-space interaction. The skeleton driver needs this kind of
104 When the driver is unloaded from the system, it needs to deregister
145 The driver now needs to verify that this device is actually one that it
156 function is called with the device pointer. The driver needs to clean
261 it. It needs to be able to shut down any current reads and writes and
/Documentation/filesystems/
Dxfs-delayed-logging-design.txt97 but only one of those copies needs to be there - the last one "D", as it
169 running. For example, a transaction has object A locked and modified, but needs
234 region state that needs to be placed into the headers during the log write.
266 committed item tracking needs it's own locks, lists and state fields in the log
342 buffer and log vector attached to each log item needs to be attached to the
441 checkpoint sequence needs to be committed before they can continue. As a
442 result, the code that forces the log to a specific LSN now needs to ensure that
515 1MB of log space consumed (512 bytes per 32k) and the reservation needs to be
517 reservation needs to be made before the checkpoint is started, and we need to
521 A static reservation needs to manipulate the log grant counters - we can take a
[all …]
Dxfs-self-describing-metadata.txt75 As a primary concern, self describing metadata needs some form of overall
86 could be used, it is more than sufficient for our needs and has relatively
92 Self describing metadata needs to contain enough information so that the
94 look at any other metadata. This means it needs to contain location information.
119 Self describing metadata also needs to contain some indication of when it was
162 For read verification, the caller needs to specify the expected type of metadata
165 marks the object being read as EFSCORRUPTED. The caller needs to catch this
166 error (same as for IO errors), and if it needs to take special action due to a
188 A typical on-disk structure needs to contain the following information:
349 repair will probably complain about it - but it needs to be fixed.
/Documentation/sound/designs/
Dcompress-offload.rst62 cycles. The new API needs to provide a generic way of listing these
122 used by userspace to define how much needs to be written in the ring
139 the average bitrate, figure out if the ring buffer needs to be
164 music content. The decoder needs to know the encoder delay and encoder padding.
167 interface to pass this information to the DSP. Also DSP and userspace needs to
174 decoder to strip the silence. This needs to be set before the data in the track
/Documentation/gpu/
Dvkms.rst89 - Variable refresh rate/freesync support. This probably needs prime buffer
91 testing. Also needs support to specify the EDID.
109 This needs a bunch of features (plane compositing, multiple outputs, ...)

12345678910>>...26