Searched refs:requirements (Results 1 – 25 of 201) sorted by relevance
123456789
/Linux-v4.19/Documentation/power/regulator/ |
D | design.txt | 14 have different power requirements, and not all components with power 15 requirements are visible to software.
|
/Linux-v4.19/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-v4.19/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-v4.19/drivers/staging/mt7621-spi/ |
D | TODO | 3 - ensure device-tree requirements are documented
|
/Linux-v4.19/drivers/staging/mt7621-dma/ |
D | TODO | 3 - ensure device-tree requirements are documented
|
/Linux-v4.19/drivers/staging/mt7621-pinctrl/ |
D | TODO | 4 - ensure device-tree requirements are documented
|
/Linux-v4.19/drivers/staging/mt7621-mmc/ |
D | TODO | 3 - ensure device-tree requirements are documented
|
/Linux-v4.19/Documentation/devicetree/bindings/serio/ |
D | ps2-gpio.txt | 12 of the tough timing requirements.
|
/Linux-v4.19/drivers/staging/mt7621-pci/ |
D | TODO | 10 - ensure device-tree requirements are documented
|
/Linux-v4.19/Documentation/devicetree/bindings/serial/ |
D | qca,ar9330-uart.txt | 14 Additional requirements:
|
/Linux-v4.19/Documentation/devicetree/bindings/sound/ |
D | ics43432.txt | 4 host connection is the I2S interface. Apart from requirements on clock
|
/Linux-v4.19/Documentation/security/ |
D | LSM.rst | 11 LSMs suit their requirements.
|
/Linux-v4.19/arch/arm/boot/dts/ |
D | lpc4350.dtsi | 7 * You can choose the licence that better fits your requirements.
|
D | lpc4357.dtsi | 7 * You can choose the licence that better fits your requirements.
|
/Linux-v4.19/Documentation/networking/ |
D | igbvf.txt | 29 of the driver. For questions related to hardware requirements, refer to the 31 requirements listed apply to use with Linux.
|
D | multiqueue.txt | 5 Section 1: Base driver requirements for implementing multiqueue support 12 Section 1: Base driver requirements for implementing multiqueue support
|
/Linux-v4.19/drivers/soc/rockchip/ |
D | Kconfig | 22 In order to meet high performance and low power requirements, a power
|
/Linux-v4.19/ |
D | README | 18 requirements for building and running the kernel, and information about
|
/Linux-v4.19/Documentation/driver-api/firmware/ |
D | introduction.rst | 22 Which one you use vary depending on your requirements, the rule of thumb
|
/Linux-v4.19/net/dcb/ |
D | Kconfig | 12 requirements (highly reliable, no drops vs. best effort vs. low
|
/Linux-v4.19/Documentation/devicetree/bindings/display/armada/ |
D | marvell,dove-lcd.txt | 19 Further clocks may be added in the future according to requirements of
|
/Linux-v4.19/drivers/iio/dummy/ |
D | Kconfig | 12 tristate "An example driver with no hardware requirements"
|
/Linux-v4.19/Documentation/devicetree/bindings/net/ |
D | mdio.txt | 15 on all PHY requirements (maximum value of all per-PHY RESET pulse widths).
|
/Linux-v4.19/drivers/scsi/mpt3sas/ |
D | Kconfig | 61 parameter will reduce memory requirements on a per controller instance. 73 parameter will reduce memory requirements on a per controller instance.
|
/Linux-v4.19/Documentation/gpu/ |
D | drm-uapi.rst | 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: 92 requirements by doing a quick fork. 94 - The kernel patch can only be merged after all the above requirements are met, 99 These are fairly steep requirements, but have grown out from years of shared
|
123456789