Searched full:covered (Results 1 – 25 of 130) sorted by relevance
123456
| /Documentation/devicetree/bindings/sound/ |
| D | max9860.txt | 10 the device, as covered in bindings/regulator/regulator.txt
|
| D | cs53l30.txt | 10 as covered in Documentation/devicetree/bindings/regulator/regulator.txt.
|
| D | cs43130.txt | 11 power supplies for the device, as covered in
|
| D | cs35l32.txt | 11 as covered in Documentation/devicetree/bindings/regulator/regulator.txt.
|
| D | cs42l56.txt | 10 as covered in Documentation/devicetree/bindings/regulator/regulator.txt.
|
| D | cs35l34.txt | 10 as covered in
|
| /Documentation/arch/x86/ |
| D | booting-dt.rst | 18 does not parse / consider data which is already covered by the boot
|
| /Documentation/process/ |
| D | code-of-conduct-interpretation.rst | 93 sent to those mailing lists are considered covered by the Code of
109 Interaction in other forums is covered by whatever rules apply to said
110 forums and is in general not covered by the Code of Conduct. Exceptions
|
| D | 1.Intro.rst | 19 the patch development, review, and merging cycle are covered. There is some
29 patches are covered, and there is an introduction to some of the tools
236 In practice, that means that all code contributions are covered either by
239 which are not covered by a compatible license will not be accepted into the
|
| /Documentation/arch/xtensa/ |
| D | booting.rst | 21 physical addresses covered by the default KSEG mapping (XCHAL_KSEG_PADDR..
|
| /Documentation/devicetree/bindings/mtd/ |
| D | hisi504-nand.txt | 18 - nand-ecc-step-size: Number of data bytes covered by a single ECC step.
|
| D | nand-chip.yaml | 59 Number of data bytes covered by a single ECC step.
|
| /Documentation/devicetree/bindings/gpio/ |
| D | sodaville.txt | 5 which is covered by the gpio.txt file in this folder.
|
| /Documentation/core-api/ |
| D | tracepoint.rst | 30 unregistering probes with these callback sites is covered in the
|
| /Documentation/security/tpm/ |
| D | tpm_tis.rst | 12 drivers. Originally Linux had only a driver called tpm_tis, which covered
|
| /Documentation/devicetree/bindings/pci/ |
| D | aardvark-pci.txt | 21 - bus-range: PCI bus numbers covered
|
| D | hisilicon-histb-pcie.txt | 18 - bus-range: PCI bus numbers covered.
|
| D | mobiveil-pcie.txt | 27 - bus-range: PCI bus numbers covered
|
| /Documentation/filesystems/iomap/ |
| D | design.rst | 91 Each iomap operation will be covered in more detail below.
92 This library was covered previously by an `LWN article
177 bytes, covered by this mapping.
279 * ``folio_ops`` will be covered in the section on pagecache operations.
|
| /Documentation/devicetree/bindings/access-controllers/ |
| D | access-controllers.yaml | 19 resources covered by the access controller.
|
| /Documentation/scsi/ |
| D | scsi-changer.rst | 61 wasn't covered by the NetBSD ioctl API.
158 find the correct values as they are not covered by the SCSI-2
|
| /Documentation/networking/ |
| D | udplite.rst | 134 always wants the whole of the packet covered. In this case, all
135 partially covered packets are dropped and an error is logged.
188 payload in the first packet, the second packet is fully covered. Note
|
| /Documentation/arch/arm/ |
| D | booting.rst | 139 overwrite it, while remaining within the region which will be covered
154 while also with the region which will be covered by the kernel's
|
| /Documentation/userspace-api/media/v4l/ |
| D | format.rst | 30 format. The data formats supported by the V4L2 API are covered in the
|
| /Documentation/admin-guide/device-mapper/ |
| D | vdo-design.rst | 413 hashtable is also covered by the implicit physical zone lock. The
416 sub-component of the slab and are thus also covered by the implicit
436 tracked in step 2. This hashtable is covered by the implicit lock on
442 also covered by the implicit hash zone lock. The hash lock agent will
541 on the block map cache structures, covered by the implicit logical zone
554 holding a lock on the affected physical slab, covered by its implicit
|
123456