Searched full:prepared (Results 1 – 25 of 79) sorted by relevance
1234
| /Documentation/w1/masters/ |
| D | mxc-w1.rst | 16 Originally based on Freescale code, prepared for mainline by
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-event_source-devices-format | 12 Userspace must be prepared for the possibility that attributes
|
| /Documentation/filesystems/ext4/ |
| D | bigalloc.rst | 8 ext4 code is not prepared to handle the case where the block size
|
| /Documentation/firmware-guide/acpi/ |
| D | acpi-lid.rst | 70 If the userspace hasn't been prepared to ignore the unreliable "opened"
96 If the userspace has been prepared to ignore the unreliable "opened" events
|
| /Documentation/admin-guide/ |
| D | edid.rst | 26 individually prepared or corrected EDID data set in the /lib/firmware
|
| D | filesystem-monitoring.rst | 46 must be prepared to skip over unknown records. Please refer to
|
| /Documentation/hwmon/ |
| D | submitting-patches.rst | 20 messages, please be prepared to explain.
131 * Your driver should be buildable as module. If not, please be prepared to
|
| /Documentation/admin-guide/LSM/ |
| D | tomoyo.rst | 32 Materials we prepared for seminars and symposiums are available at
|
| /Documentation/driver-api/nvdimm/ |
| D | firmware-activate.rst | 64 from 'armed' to 'idle' when the system is prepared to activate firmware,
|
| /Documentation/filesystems/smb/ |
| D | ksmbd.rst | 43 parallel. After receiving each command a separated kernel workitem is prepared
59 NetServerGetInfo. Complete DCE/RPC response is prepared from the user space
|
| /Documentation/userspace-api/media/mediactl/ |
| D | request-api.rst | 165 Once the request is fully prepared, it can be queued to the driver:
245 Once the request is fully prepared, it can be queued to the driver:
|
| /Documentation/devicetree/bindings/clock/ |
| D | samsung,exynos7885-clock.yaml | 23 CMU_TOP is a top-level CMU, where all base clocks are prepared using PLLs and
|
| D | samsung,exynosautov9-clock.yaml | 23 CMU_TOP is a top-level CMU, where all base clocks are prepared using PLLs and
|
| /Documentation/driver-api/mmc/ |
| D | mmc-async-req.rst | 66 The first request in a series of requests can't be prepared in parallel
|
| /Documentation/devicetree/bindings/memory-controllers/ |
| D | mediatek,smi-common.yaml | 24 base). Besides that, the smi async clock should be prepared and enabled for
|
| /Documentation/networking/ |
| D | xdp-rx-metadata.rst | 96 currently supported, which has to be prepared by the initial XDP program
|
| /Documentation/gpu/rfc/ |
| D | xe.rst | 84 not yet prepared to handle the 1-to-1 relationship between drm_gpu_scheduler and
213 this document and the Xe driver prepared for the changes, if necessary.
|
| /Documentation/driver-api/pm/ |
| D | devices.rst | 262 devices have been suspended. Device drivers must be prepared to cope with such
414 prepared for generating hardware wakeup signals to trigger a system wakeup event
494 Drivers must also be prepared to notice that the device has been removed
529 not be prepared to generate wakeup events.
560 prepared for the upcoming system shutdown. This is much like suspending them
607 devices managed by the boot kernel need to be prepared for passing control back
862 driver must be prepared to cope with the invocation of its system-wide resume
|
| /Documentation/driver-api/usb/ |
| D | callbacks.rst | 106 time after the physical disconnection. Thus your driver must be prepared
|
| /Documentation/driver-api/dmaengine/ |
| D | provider.rst | 328 The data from the provided metadata buffer should be prepared for the DMA
392 for the transfer being prepared, and should create a hardware
562 - The descriptor should be prepared for reuse by invoking
|
| /Documentation/driver-api/ |
| D | connector.rst | 104 so caller is warned that it must be prepared. That is why the struct
|
| /Documentation/sound/designs/ |
| D | channel-mapping-api.rst | 163 This operation is allowed only at PCM PREPARED state. When called in
|
| /Documentation/arch/x86/i386/ |
| D | IO-APIC.rst | 114 Be prepared that it might happen that you need some strange pirq line::
|
| /Documentation/bpf/ |
| D | bpf_prog_run.rst | 116 packet contents, it has to be prepared to see either the original content or
|
| /Documentation/driver-api/pci/ |
| D | p2pdma.rst | 118 struct pages to code that isn't prepared for it. At this time, the kernel
|
1234