Searched full:requirements (Results 1 – 25 of 247) sorted by relevance
12345678910
| /Documentation/RCU/ |
| D | index.rst | 29 Design/Requirements/Requirements
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-iio-dma-buffer | 9 This property reports the alignment requirements in bytes.
13 The alignment requirements in number of sample sets will depend
|
| /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
|
| /Documentation/power/regulator/ |
| D | design.rst | 15 have different power requirements, and not all components with power
16 requirements are visible to software.
|
| /Documentation/process/ |
| D | maintainer-soc-clean-dts.rst | 4 SoC Platforms with DTS Compliance Requirements
12 MAINTAINERS impose additional requirements listed below.
|
| /Documentation/gpu/ |
| D | drm-uapi.rst | 49 Open-Source Userspace Requirements
52 The DRM subsystem has stricter requirements than most other kernel subsystems on
54 explains what exactly those requirements are, and why they exist.
89 leads to a few additional requirements:
105 requirements by doing a quick fork.
107 - The kernel patch can only be merged after all the above requirements are met,
112 These are fairly steep requirements, but have grown out from years of shared
218 The goal raises at least the following requirements for the kernel and
221 Requirements for KMS UAPI
240 Requirements for Render and Cross-Device UAPI
[all …]
|
| /Documentation/devicetree/bindings/display/panel/ |
| D | olimex,lcd-olinuxino.yaml | 21 - AT24C16C EEPROM holding panel identification and timing requirements
27 device information (id, serial, etc.) and timing requirements.
|
| /Documentation/rust/ |
| D | quick-start.rst | 9 Requirements: Building
14 Some of these requirements might be available from Linux distributions
19 To easily check whether the requirements are met, the following target
124 Requirements: Developing
212 above), as long as the other requirements are met. In turn, this will make
|
| /Documentation/devicetree/bindings/iio/adc/ |
| D | fsl,vf610-adc.yaml | 47 Maximum frequencies from datasheet operating requirements.
59 operating requirements. A safe default across a wide range of R_as and
|
| /Documentation/networking/device_drivers/ethernet/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
|
| /Documentation/devicetree/bindings/sound/ |
| D | ics43432.txt | 4 host connection is the I2S interface. Apart from requirements on clock
|
| /Documentation/devicetree/bindings/display/armada/ |
| D | marvell,dove-lcd.txt | 19 Further clocks may be added in the future according to requirements of
|
| /Documentation/userspace-api/media/v4l/ |
| D | pixfmt-compressed.rst | 47 then the decoder has no requirements since it can parse all the
103 then the decoder has no requirements since it can parse all the
112 then the decoder has no requirements since it can parse all the
203 then the decoder has no requirements since it can parse all the
|
| D | pixfmt-v4l2-mplane.rst | 38 alignment requirements or minimum/maximum size requirements.
|
| /Documentation/power/ |
| D | pm_qos_interface.rst | 188 certain protocol requirements or target frame or sample rates etc.
199 latency tolerance requirements for the device is empty, the callback is expected
214 requirements from the kernel side in the device's list.
218 latency tolerance requirements for devices.
|
| /Documentation/security/ |
| D | lsm-development.rst | 11 LSMs suit their requirements.
|
| /Documentation/driver-api/firmware/ |
| D | introduction.rst | 22 Which one you use vary depending on your requirements, the rule of thumb
|
| /Documentation/devicetree/bindings/interconnect/ |
| D | qcom,rpmh-common.yaml | 14 RPMh interconnect providers support system bandwidth requirements through
|
| D | qcom,msm8974.yaml | 14 bandwidth requirements between various network-on-chip fabrics.
|
| D | qcom,sc8280xp-rpmh.yaml | 14 RPMh interconnect providers support system bandwidth requirements through
|
| D | qcom,sa8775p-rpmh.yaml | 13 RPMh interconnect providers support system bandwidth requirements through
|
| /Documentation/riscv/ |
| D | boot.rst | 4 RISC-V Kernel Boot Requirements and Constraints
16 Pre-kernel Requirements and Constraints
105 Early Boot Requirements and Constraints
|
| /Documentation/devicetree/bindings/spi/ |
| D | icpdas-lp8841-spi-rtc.txt | 21 Requirements to SPI slave nodes:
|
| /Documentation/devicetree/bindings/reset/ |
| D | xlnx,zynqmp-reset.yaml | 16 input to the device and that all internal reset requirements are met
|
12345678910