Searched full:documented (Results 1 – 25 of 661) sorted by relevance
12345678910>>...27
| /linux-6.12.1/Documentation/userspace-api/media/v4l/ |
| D | v4l2.rst | 45 - Documented libv4l, designed and added v4l2grab example, Remote Controller chapter.
53 - Documented the memory-to-memory decoder interface.
54 - Documented the memory-to-memory encoder interface.
62 - Documented the Digital Video timings API.
66 - Documented the memory-to-memory decoder interface.
67 - Documented the memory-to-memory encoder interface.
71 - Designed and documented the multi-planar API.
83 - Designed and documented the VIDIOC_ENUM_FRAMESIZES and VIDIOC_ENUM_FRAMEINTERVALS ioctls.
87 …- Documented the fielded V4L2_MPEG_STREAM_VBI_FMT_IVTV MPEG stream embedded, sliced VBI data forma…
91 …- Designed and documented the VIDIOC_LOG_STATUS ioctl, the extended control ioctls, major parts of…
[all …]
|
| /linux-6.12.1/scripts/ |
| D | check-sysctl-docs | 23 # documented: maps documented entries (each key is an entry)
47 if (documented[entry]) {
48 printf " (documented)"
54 # Stage 1: build the list of documented entries
76 documented[trimpunct($i)]++
149 for (entry in documented) {
|
| /linux-6.12.1/Documentation/userspace-api/media/ |
| D | videodev2.h.rst.exceptions | 11 # having something not documented at the uAPI.
19 # Documented enum v4l2_field
31 # Documented enum v4l2_buf_type
47 # Documented enum v4l2_tuner_type
53 # Documented enum v4l2_memory
59 # Documented enum v4l2_colorspace
75 # Documented enum v4l2_xfer_func
87 # Documented enum v4l2_ycbcr_encoding
99 # Documented enum v4l2_hsv_encoding
103 # Documented enum v4l2_quantization
[all …]
|
| D | cec.h.rst.exceptions | 20 # Shouldn't them be documented?
29 # Part of CEC 2.0 spec - shouldn't be documented too?
48 # IMHO, those should also be documented
|
| /linux-6.12.1/arch/m68k/ifpsp060/ |
| D | fpsp.doc | 169 - documented in 3.5 of 060SP spec.
177 - documented in 3.5 of 060SP spec.
185 - documented in 3.7 of 060SP spec.
193 - documented in 3.6 of 060SP spec.
202 - documented in 3.4 of 060SP spec.
214 - documented in 3.4 of 060SP spec.
227 - not fully documented in 060SP spec.
264 - documented in 3.1 of 060SP spec.
286 - documented in 3.3 of 060 spec.
|
| /linux-6.12.1/Documentation/process/ |
| D | submit-checklist.rst | 32 default to off unless they meet the exception criteria documented in
47 2) All new ``/proc`` entries are documented under ``Documentation/``
49 3) All new kernel boot parameters are documented in
52 4) All new module parameters are documented with ``MODULE_PARM_DESC()``
54 5) All new userspace interfaces are documented in ``Documentation/ABI/``.
|
| D | embargoed-hardware-issues.rst | 36 according to our documented process.
142 Memorandum of Understanding and the documented process. These developers
151 adhere to this documented process and the Memorandum of Understanding.
237 have and maintain their own documented security process for any
243 silicon vendor’s documented security process. Feedback from the
|
| /linux-6.12.1/Documentation/driver-api/tty/ |
| D | tty_driver.rst | 78 The registration routines are documented as follows:
102 The linking routines are documented here:
113 All members of struct tty_driver are documented here. The required members are
114 noted at the end. struct tty_operations are documented next.
|
| /linux-6.12.1/drivers/net/ethernet/renesas/ |
| D | ravb.h | 170 GCPT = 0x03B4, /* Documented for R-Car Gen3 only */
239 CSR_OPS_STANDBY = 0x00000008, /* Documented for R-Car Gen3 only */
544 TIC_FTE0 = 0x00000001, /* Documented for R-Car Gen3 only */
545 TIC_FTE1 = 0x00000002, /* Documented for R-Car Gen3 only */
552 TIS_FTF0 = 0x00000001, /* Documented for R-Car Gen3 only */
553 TIS_FTF1 = 0x00000002, /* Documented for R-Car Gen3 only */
561 ISS_FRS = 0x00000001, /* Documented for R-Car Gen3 only */
562 ISS_FTS = 0x00000004, /* Documented for R-Car Gen3 only */
622 GIC_PTCE = 0x00000001, /* Documented for R-Car Gen3 only */
628 GIS_PTCF = 0x00000001, /* Documented for R-Car Gen3 only */
[all …]
|
| /linux-6.12.1/Documentation/devicetree/bindings/nvmem/ |
| D | zii,rave-sp-eeprom.txt | 6 parent RAVE SP device (as documented in
21 documented in Documentation/devicetree/bindings/nvmem/nvmem.txt
|
| /linux-6.12.1/drivers/platform/mellanox/ |
| D | mlxbf-bootctl.h | 15 * returned as documented below.
33 * values. Non-zero errors are returned as documented below.
55 * reset. Non-zero errors are returned as documented below.
|
| /linux-6.12.1/Documentation/driver-api/firmware/ |
| D | direct-fs-lookup.rst | 7 filesystem in the paths documented in the section 'Firmware search paths'.
15 documented below.
|
| /linux-6.12.1/Documentation/filesystems/ext4/ |
| D | verity.rst | 17 - The Merkle tree, as documented in
25 - The verity descriptor, as documented in
|
| /linux-6.12.1/Documentation/devicetree/bindings/media/xilinx/ |
| D | video.txt | 9 tree using bindings documented in this directory. Connections between the IP
13 tree using bindings documented in ./xlnx,video.txt.
|
| /linux-6.12.1/Documentation/virt/kvm/ |
| D | review-checklist.rst | 13 - the API must be documented in Documentation/virt/kvm/api.rst
36 11. New guest visible features must either be documented in a hardware manual
|
| /linux-6.12.1/Documentation/devicetree/bindings/display/imx/ |
| D | fsl-imx-drm.txt | 29 - reg: should be register base and length as documented in the
67 - reg: should be register base and length as documented in the
93 - reg: should be register base and length as documented in the
|
| /linux-6.12.1/drivers/net/phy/ |
| D | dp83tg720.c | 35 /* Power modes are documented as bit fields but used as values */
76 * This sequence is based on the documented procedure for the DP83TG720 PHY.
87 * Most of the registers are not documented. Some of register names in dp83tg720_cable_test_start()
319 * The wait value of one 1ms is documented in "DP83TG720S-Q1 1000BASE-T1 in dp83tg720_config_init()
|
| /linux-6.12.1/Documentation/devicetree/bindings/leds/ |
| D | leds-lm36274.txt | 8 Parent device properties are documented in
11 Regulator properties are documented in
|
| /linux-6.12.1/arch/powerpc/include/asm/ |
| D | heathrow.h | 58 #define HRW_BMAC_IO_ENABLE 0x60000000 /* two bits, not documented in OF */
59 #define HRW_BMAC_RESET 0x80000000 /* not documented in OF */
|
| /linux-6.12.1/drivers/sbus/char/ |
| D | display7seg.c | 34 * documented driver features (ref Sun doc 806-0180-03).
35 * By default, this module supports the documented driver
48 "Disables documented functionality omitted from Solaris driver");
|
| /linux-6.12.1/Documentation/devicetree/bindings/ |
| D | submitting-patches.rst | 50 previously documented in the corresponding DT binding file
57 7) If a documented compatible string is not yet matched by the
|
| /linux-6.12.1/Documentation/rust/ |
| D | coding-guidelines.rst | 108 Rust kernel code is not documented like C kernel code (i.e. via kernel-doc).
117 This is how a well-documented Rust function may look like:
149 the documented item does. Further explanations must go in extra paragraphs.
|
| /linux-6.12.1/Documentation/firmware-guide/acpi/dsd/ |
| D | leds.rst | 14 Referring to LEDs in Device tree is documented in [video-interfaces], in
21 ACPI nodes is documented in [data-node-ref].
|
| /linux-6.12.1/Documentation/doc-guide/ |
| D | kernel-doc.rst | 200 Members of structs, unions and enums should be documented the same way
277 is named, the member ``bar`` inside it should be documented as
280 should be documented as ``@bar:``
285 The structure members may also be documented in-line within the definition.
330 Typedefs with function prototypes can also be documented::
|
| /linux-6.12.1/Documentation/ABI/testing/ |
| D | sysfs-class-iommu-amd-iommu | 6 IOMMU capability header as documented in the AMD IOMMU
|
12345678910>>...27