/Linux-v5.4/include/linux/ |
D | zconf.h | 11 /* The memory requirements for deflate are (in bytes): 15 the default memory requirements from 256K to 128K, compile with 19 The memory requirements for inflate are (in bytes) 1 << windowBits
|
/Linux-v5.4/Documentation/gpu/ |
D | drm-uapi.rst | 38 Open-Source Userspace Requirements 41 The DRM subsystem has stricter requirements than most other kernel subsystems on 43 explains what exactly those requirements are, and why they exist. 78 leads to a few additional requirements: 94 requirements by doing a quick fork. 96 - The kernel patch can only be merged after all the above requirements are met, 101 These are fairly steep requirements, but have grown out from years of shared 243 Testing Requirements for userspace API
|
/Linux-v5.4/arch/mips/tools/ |
D | generic-board-config.sh | 8 # generic MIPS kernel. It checks each for requirements specified using 10 # fragments which have no unmet requirements. 12 # An example of requirements in your board config fragment might be:
|
/Linux-v5.4/Documentation/kbuild/ |
D | Kconfig.recursion-issue-02 | 12 # annotate those requirements, ie, some drivers use "depends on" while others 19 # core requirements are not carefully synced, as drivers evolve features 20 # they select or depend on end up becoming shared requirements which cannot be
|
/Linux-v5.4/Documentation/media/uapi/v4l/ |
D | pixfmt-compressed.rst | 48 then the decoder has no requirements since it can parse all the 100 then the decoder has no requirements since it can parse all the 109 then the decoder has no requirements since it can parse all the 189 then the decoder has no requirements since it can parse all the
|
/Linux-v5.4/drivers/gpu/drm/xen/ |
D | xen_drm_front.h | 29 * Depending on the requirements for the para-virtualized environment, namely 30 * requirements dictated by the accompanying DRM/(v)GPU drivers running in both 53 * requirements for display buffers it is possible to allocate such buffers
|
/Linux-v5.4/Documentation/devicetree/bindings/display/panel/ |
D | olimex,lcd-olinuxino.txt | 11 - AT24C16C EEPROM holding panel identification and timing requirements 17 device information (id, serial, etc.) and timing requirements.
|
/Linux-v5.4/Documentation/power/regulator/ |
D | design.rst | 15 have different power requirements, and not all components with power 16 requirements are visible to software.
|
/Linux-v5.4/Documentation/devicetree/bindings/iio/adc/ |
D | vf610-adc.txt | 16 requirements. Three values are required, depending on conversion mode: 23 operating requirements. A safe default across a wide range of R_as and
|
/Linux-v5.4/drivers/gpu/drm/msm/disp/dpu1/ |
D | dpu_rm.c | 19 * struct dpu_rm_requirements - Reservation requirements parameter bundle 292 * proposed use case requirements, incl. hardwired dependent blocks like 296 * @reqs: proposed use case requirements 300 * NULL if pp was not available, or not matching requirements. 302 * as well as satisfying all other requirements 303 * @Return: true if lm matches all requirements, false otherwise 627 DPU_ERROR("failed to populate hw requirements\n"); in dpu_rm_reserve()
|
/Linux-v5.4/Documentation/power/ |
D | pm_qos_interface.rst | 196 certain protocol requirements or target frame or sample rates etc. 207 latency tolerance requirements for the device is empty, the callback is expected 222 requirements from the kernel side in the device's list. 226 latency tolerance requirements for devices.
|
/Linux-v5.4/Documentation/networking/device_drivers/intel/ |
D | igbvf.rst | 23 For questions related to hardware requirements, refer to the documentation 24 supplied with your Intel adapter. All hardware requirements listed apply to use
|
D | ixgbevf.rst | 20 For questions related to hardware requirements, refer to the documentation 21 supplied with your Intel adapter. All hardware requirements listed apply to use
|
/Linux-v5.4/drivers/scsi/mpt3sas/ |
D | Kconfig | 62 parameter will reduce memory requirements on a per controller instance. 74 parameter will reduce memory requirements on a per controller instance.
|
/Linux-v5.4/Documentation/doc-guide/ |
D | sphinx.rst | 32 There's a script that checks for the Sphinx requirements. Please see 62 (sphinx_1.7.9) $ pip install -r Documentation/sphinx/requirements.txt 109 pip install -r Documentation/sphinx/requirements.txt 113 By default, it checks all the requirements for both html and PDF, including 114 the requirements for images, math expressions and LaTeX build, and assumes
|
/Linux-v5.4/Documentation/RCU/Design/Requirements/ |
D | Requirements.html | 4 <head><title>A Tour Through RCU's Requirements [LWN.net]</title> 7 <h1>A Tour Through RCU's Requirements</h1> 29 raises the question of exactly what RCU's requirements are. 32 This document therefore summarizes RCU's requirements, and can be thought 36 in fact, I learned about many of these requirements the hard way. 43 All that aside, here are the categories of currently known RCU requirements: 47 <li> <a href="#Fundamental Requirements"> 48 Fundamental Requirements</a> 49 <li> <a href="#Fundamental Non-Requirements">Fundamental Non-Requirements</a> 52 <li> <a href="#Quality-of-Implementation Requirements"> [all …]
|
/Linux-v5.4/drivers/misc/cb710/ |
D | sgbuf2.c | 85 * Same requirements as in sg_miter_next(). 128 * Same requirements as in sg_miter_next().
|
/Linux-v5.4/drivers/gpu/drm/panfrost/ |
D | panfrost_job.c | 108 if (job->requirements & PANFROST_JD_REQ_FS) in panfrost_job_get_slot() 113 if (job->requirements & PANFROST_JD_REQ_ONLY_COMPUTE) { in panfrost_job_get_slot() 114 if ((job->requirements & PANFROST_JD_REQ_CORE_GRP_MASK) && in panfrost_job_get_slot() 125 u32 requirements, in panfrost_job_write_affinity() argument 164 panfrost_job_write_affinity(pfdev, job->requirements, js); in panfrost_job_hw_submit()
|
/Linux-v5.4/Documentation/networking/ |
D | multiqueue.txt | 5 Section 1: Base driver requirements for implementing multiqueue support 12 Section 1: Base driver requirements for implementing multiqueue support
|
/Linux-v5.4/Documentation/process/ |
D | license-rules.rst | 35 which does not extend the GPL requirements to any software which uses it to 264 The metatag requirements for 'other' licenses are identical to the 265 requirements of the `Preferred licenses`_. 312 The metatag requirements for 'other' licenses are identical to the 313 requirements of the `Preferred licenses`_.
|
/Linux-v5.4/Documentation/filesystems/ |
D | files.txt | 51 the memory barrier requirements for lock-free dereference. 63 take care of barrier requirements due to lock-free lookup.
|
/Linux-v5.4/drivers/staging/mt7621-dma/ |
D | TODO | 3 - ensure device-tree requirements are documented
|
/Linux-v5.4/drivers/staging/mt7621-pinctrl/ |
D | TODO | 4 - ensure device-tree requirements are documented
|
/Linux-v5.4/tools/perf/scripts/python/bin/ |
D | event_analyzing_sample-record | 5 # the tracepoints, so no special record requirements, just record what
|
D | stackcollapse-record | 5 # the tracepoints, so no special record requirements, just record what
|