Searched +full:non +full:- +full:descriptive (Results 1 – 8 of 8) sorted by relevance
| /Documentation/devicetree/bindings/display/panel/ |
| D | panel-common.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/display/panel/panel-common.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Thierry Reding <thierry.reding@gmail.com>
11 - Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
23 # Descriptive Properties
24 width-mm:
29 height-mm:
43 non-descriptive information. For instance an LCD panel in a system that
[all …]
|
| /Documentation/doc-guide/ |
| D | kernel-doc.rst | 1 Writing kernel-doc comments
5 comments in the kernel-doc format to describe the functions, types
6 and design of the code. It is easier to keep documentation up-to-date
9 .. note:: The kernel-doc format is deceptively similar to javadoc,
10 gtk-doc or Doxygen, yet distinctively different, for historical
11 reasons. The kernel source contains tens of thousands of kernel-doc
14 The kernel-doc structure is extracted from the comments, and proper
16 generated from them. The descriptions are filtered for special kernel-doc
17 highlights and cross-references. See below for details.
19 .. _Sphinx C Domain: http://www.sphinx-doc.org/en/stable/domains.html
[all …]
|
| /Documentation/process/ |
| D | coding-style.rst | 19 --------------
31 Now, some people will claim that having 8-character indentations makes
33 80-character terminal screen. The answer to that is that if you need
37 In short, 8-char indents make things easier to read, and have the added
43 instead of ``double-indenting`` the ``case`` labels. E.g.:
45 .. code-block:: c
67 .. code-block:: c
82 ----------------------------------
94 with a long argument list. However, never break user-visible strings such as
99 ----------------------------
[all …]
|
| D | submitting-patches.rst | 14 Also, read :ref:`Documentation/process/submit-checklist.rst <submitchecklist>`
17 :ref:`Documentation/process/submitting-drivers.rst <submittingdrivers>`;
19 Documentation/devicetree/bindings/submitting-patches.txt.
28 -------------------------------
45 1) ``diff -up``
46 ---------------
48 If you must generate your patches by hand, use ``diff -up`` or ``diff -uprN``
54 create it in "unified diff" format, as supplied by the ``-u`` argument
56 Also, please use the ``-p`` argument which shows which C function each
57 change is in - that makes the resultant ``diff`` a lot easier to read.
[all …]
|
| /Documentation/driver-api/gpio/ |
| D | legacy.rst | 13 A "General Purpose Input/Output" (GPIO) is a flexible software-controlled
21 System-on-Chip (SOC) processors heavily rely on GPIOs. In some cases, every
22 non-dedicated pin can be configured as a GPIO; and most chips have at least
27 Most PC southbridges have a few dozen GPIO-capable pins (with only the BIOS
32 - Output values are writable (high=1, low=0). Some chips also have
34 value might be driven ... supporting "wire-OR" and similar schemes
37 - Input values are likewise readable (1, 0). Some chips support readback
38 of pins configured as "output", which is very useful in such "wire-OR"
40 input de-glitch/debounce logic, sometimes with software controls.
42 - Inputs can often be used as IRQ signals, often edge triggered but
[all …]
|
| /Documentation/media/kapi/ |
| D | v4l2-dev.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 :c:type:`video_device` struct (``v4l2-dev.h``). This struct can either be
12 .. code-block:: c
17 return -ENOMEM;
19 vdev->release = video_device_release;
24 .. code-block:: c
26 struct video_device *vdev = &my_vdev->vdev;
28 vdev->release = my_vdev_release;
42 - :c:type:`video_device`->v4l2_dev: must be set to the :c:type:`v4l2_device`
45 - :c:type:`video_device`->name: set to something descriptive and unique.
[all …]
|
| /Documentation/devicetree/bindings/arm/ |
| D | idle-states.txt | 6 1 - Introduction
10 where cores can be put in different low-power states (ranging from simple
12 the range of dynamic idle states that a processor can enter at run-time, can be
19 - Running
20 - Idle_standby
21 - Idle_retention
22 - Sleep
23 - Off
29 wake-up capabilities, hence it is not considered in this document).
39 2 - idle-states definitions
[all …]
|
| /Documentation/driver-api/ |
| D | pinctl.rst | 9 - Enumerating and naming controllable pins
11 - Multiplexing of pins, pads, fingers (etc) see below for details
13 - Configuration of pins, pads, fingers (etc), such as software-controlled
14 biasing and driving mode specific pins, such as pull-up/down, open drain,
17 Top-level interface
22 - A pin controller is a piece of hardware, usually a set of registers, that
28 - PINS are equal to pads, fingers, balls or whatever packaging input or
32 be sparse - i.e. there may be gaps in the space with numbers where no
98 See for example arch/arm/mach-u300/Kconfig for an example.
197 the groups is up to the driver, this is just a simple example - in practice you
[all …]
|