Home
last modified time | relevance | path

Searched +full:panel +full:- +full:specific (Results 1 – 25 of 36) sorted by relevance

12

/Documentation/devicetree/bindings/display/panel/
Dpanel-common.yaml1 # 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>
18 When referenced from panel device tree bindings the properties defined in this
19 document are defined as follows. The panel device tree bindings are
24 width-mm:
29 height-mm:
[all …]
Dpanel-dpi.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/display/panel/panel-dpi.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Generic MIPI DPI Panel
10 - Sam Ravnborg <sam@ravnborg.org>
13 - $ref: panel-common.yaml#
18 Shall contain a panel specific compatible and "panel-dpi"
21 - {}
22 - const: panel-dpi
[all …]
Dpanel-dsi-cm.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/display/panel/panel-dsi-cm.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Tomi Valkeinen <tomi.valkeinen@ti.com>
11 - Sebastian Reichel <sre@kernel.org>
17 panel is assumed to have native backlight support.
18 The panel may use an OF graph binding for the association
23 - $ref: panel-common.yaml#
29 - enum:
[all …]
/Documentation/devicetree/bindings/display/hisilicon/
Ddw-dsi.txt1 Device-Tree bindings for DesignWare DSI Host Controller v1.20a driver
4 HDMI converter or panel.
7 - compatible: value should be "hisilicon,hi6220-dsi".
8 - reg: physical base address and length of dsi controller's registers.
9 - clocks: contains APB clock phandle + clock-specifier pair.
10 - clock-names: should be "pclk".
11 - ports: contains DSI controller input and output sub port.
13 The output port with the reg value "1", it could connect to panel or
17 A example of HiKey board hi6220 SoC and board specific DT entry:
20 SoC specific:
[all …]
/Documentation/fb/
Dsa1100fb.rst8 This is a driver for a graphic framebuffer for the SA-1100 LCD
20 16. LCCR values are display-specific and should be computed as
21 documented in the SA-1100 Developer's Manual, Section 11.7. Dual-panel
23 are used for the lower panel.
/Documentation/gpu/
Dtodo.rst11 ----------
18 subsystem, or some specific GPU/display graphics knowledge. For debugging issue
27 refactorings already and are an expert in the specific area
29 Subsystem-wide refactorings
33 ---------------------------------------------
45 --------------------------------------------------
53 non-converted driver. The "Atomic mode setting design overview" series [2]_
60 .. [1] https://blog.ffwll.ch/2014/11/atomic-modeset-support-for-kms-drivers.html
69 ---------------------------------------------------------
75 avoid confusion - the other helpers in that file are all deprecated legacy
[all …]
Dtegra.rst11 supports the built-in GPU, comprised of the gr2d and gr3d engines. Starting
18 - A host1x driver that provides infrastructure and access to the host1x
21 - A KMS driver that supports the display controllers as well as a number of
24 - A set of custom userspace IOCTLs that can be used to submit jobs to the
40 device using a driver-provided function which will set up the bits specific to
45 the subsystem specific bits are torn down and the clients destroyed in turn.
48 -------------------------------
50 .. kernel-doc:: include/linux/host1x.h
52 .. kernel-doc:: drivers/gpu/host1x/bus.c
56 --------------------------
[all …]
/Documentation/devicetree/bindings/display/
Dsimple-framebuffer.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/display/simple-framebuffer.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Hans de Goede <hdegoede@redhat.com>
13 A simple frame-buffer describes a frame-buffer setup by firmware or
19 sub-nodes of the chosen node (*). Simplefb nodes must be named
29 If a panel node is given, then the driver uses this to configure the
30 physical width and height of the display. If no panel node is given,
41 interaction, then the chosen node stdout-path property should point
[all …]
Damlogic,meson-g12a-dw-mipi-dsi.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
4 ---
5 $id: http://devicetree.org/schemas/display/amlogic,meson-g12a-dw-mipi-dsi.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
8 title: Amlogic specific extensions to the Synopsys Designware MIPI DSI Host Controller
11 - Neil Armstrong <neil.armstrong@linaro.org>
15 - A Synopsys DesignWare MIPI DSI Host Controller IP
16 - A TOP control block controlling the Clocks & Resets of the IP
19 - $ref: dsi-controller.yaml#
24 - amlogic,meson-g12a-dw-mipi-dsi
[all …]
/Documentation/devicetree/bindings/display/bridge/
Dsnps,dw-mipi-dsi.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/display/bridge/snps,dw-mipi-dsi.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Philippe CORNU <philippe.cornu@foss.st.com>
15 by itself but is meant to be referenced by platform-specific device tree
23 - $ref: ../dsi-controller.yaml#
31 clock-names: true
36 reset-names:
49 description: DSI output node to panel.
[all …]
Dfsl,imx93-mipi-dsi.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/display/bridge/fsl,imx93-mipi-dsi.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Freescale i.MX93 specific extensions to Synopsys Designware MIPI DSI
10 - Liu Ying <victor.liu@nxp.com>
15 and extensions to them are controlled by i.MX93 media blk-ctrl.
18 - $ref: snps,dw-mipi-dsi.yaml#
22 const: fsl,imx93-mipi-dsi
26 - description: apb clock
[all …]
/Documentation/gpu/amdgpu/display/
Ddc-glossary.rst7 'Documentation/gpu/amdgpu/amdgpu-glossary.rst'; if you cannot find it anywhere,
19 Application-Specific Integrated Circuit
49 Cathode Ray Tube Controller - commonly called "Controller" - Generates
108 Display Micro-Controller Unit
111 Display Micro-Controller Unit, version B
210 Panel Self Refresh
225 Transition-Minimized Differential Signaling
Ddisplay-contributing.rst4 AMDGPU - Display Contributions
21 - https://gitlab.freedesktop.org/drm/amd
37 issue; it is necessary to analyze case-by-case.
41 .. _IGT: https://gitlab.freedesktop.org/drm/igt-gpu-tools
47 ------------------------
55 -------------------------------------------------
57 Linux has a User-mode Linux (UML) feature, and the kernel can be compiled to
68 -----------------------------------------------------------
92 -----------------------
96 a modular design, making the bring-up for new hardware fast. Over the years,
[all …]
/Documentation/admin-guide/
Dindex.rst5 The following is a collection of user-oriented documents that have been
18 kernel-parameters
30 hw-vuln/index
38 reporting-issues
39 reporting-regressions
40 quickly-build-trimmed-linux
41 verify-bugs-and-bisect-regressions
42 bug-hunting
43 bug-bisect
44 tainted-kernels
[all …]
/Documentation/driver-api/
Dipmb.rst14 the front panel interface, monitoring the baseboard,
15 hot-swapping disk drivers in the system chassis, etc...
27 ----------------------------
29 ipmb-dev-int - This is the driver needed on a Satellite MC to
43 --------------------
55 Name (_HID, "<Vendor-Specific HID>") // Vendor-Specific HID
72 compatible = "ipmb-dev";
74 i2c-protocol;
79 then "i2c-protocol" needs to be defined as above.
83 modprobe ipmb-dev-int
[all …]
/Documentation/arch/arm/omap/
Ddss.rst7 TV-out and multiple display support, but there are lots of small improvements
10 The DSS2 driver (omapdss module) is in arch/arm/plat-omap/dss/, and the FB,
11 panel and controller drivers are in drivers/video/omap2/. DSS1 and DSS2 live
15 --------
19 - MIPI DPI (parallel) output
20 - MIPI DSI output in command mode
21 - MIPI DBI (RFBI) output
22 - SDI output
23 - TV output
24 - All pieces can be compiled as a module or inside kernel
[all …]
/Documentation/devicetree/bindings/arm/
Dqcom.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Bjorn Andersson <bjorn.andersson@linaro.org>
90 https://docs.kernel.org/arch/arm/google/chromebook-boot-flow.html
97 - items:
98 - enum:
99 - qcom,apq8016-sbc
100 - schneider,apq8016-hmibsc
101 - const: qcom,apq8016
[all …]
/Documentation/userspace-api/media/v4l/
Dextended-controls.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
3 .. _extended-controls:
22 relating to how the video is encoded into an MPEG stream are specific to
71 it also allows for 64-bit values and pointers to be passed.
75 such as N-dimensional arrays and/or structures. You need to specify the
83 particular, this ioctl gives the dimensions of the N-dimensional array if
110 .. code-block:: c
125 If you want to get all controls within a specific control class, then
131 .. code-block:: c
141 The 32-bit ``qctrl.id`` value is subdivided into three bit ranges: the
[all …]
Dcontrol.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
9 Devices typically have a number of user-settable controls such as
19 for specific purposes. Drivers can also implement their own custom
21 pre-defined control IDs have the prefix ``V4L2_CID_``, and are listed in
22 :ref:`control-id`. The ID is used when querying the attributes of a
27 the user is supposed to understand. When the purpose is non-intuitive
28 the driver writer should provide a user manual, a user interface plug-in
29 or a driver specific panel application. Predefined IDs were introduced
51 ``V4L2_EVENT_CTRL``), panel applications might want to make use of that
57 .. _control-id:
[all …]
Dopen.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
22 the hardware, which may also expose device nodes, called V4L2 sub-devices.
24 When such V4L2 sub-devices are exposed, they allow controlling those
25 other hardware components - usually connected via a serial bus (like
26 I²C, SMBus or SPI). Depending on the bridge driver, those sub-devices
29 :ref:`V4L2 sub-devices <subdev>`.
32 :ref:`Media Controller <media_controller>` are called **MC-centric**
34 are called **video-node-centric**.
36 Userspace can check if a V4L2 hardware peripheral is MC-centric by
38 :ref:`device_caps field <device-capabilities>`.
[all …]
/Documentation/devicetree/bindings/display/msm/
Ddsi-controller-main.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/display/msm/dsi-controller-main.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Krishna Manikandan <quic_mkrishn@quicinc.com>
15 - items:
16 - enum:
17 - qcom,apq8064-dsi-ctrl
18 - qcom,msm8226-dsi-ctrl
19 - qcom,msm8916-dsi-ctrl
[all …]
/Documentation/networking/devlink/
Ddevlink-linecard.rst1 .. SPDX-License-Identifier: GPL-2.0
10 The ``devlink-linecard`` mechanism is targeted for manipulation of
15 * Provision of a slot with specific line card type.
21 the switch ASIC modules and physical front panel ports.
36 - Device driver would instruct the ASIC to prepare all
41 being physically connected or powered-up
44 - As on the ordinary ports, user may provision a splitter
51 * Line card is not inserted or powered-down
53 - The carrier is always down
56 - The carrier is decided as for ordinary port netdevice
[all …]
/Documentation/networking/dsa/
Ddsa.rst22 An Ethernet switch typically comprises multiple front-panel ports and one
27 gateways, or even top-of-rack switches. This host Ethernet controller will
32 using upstream and downstream Ethernet links between switches. These specific
36 For each front-panel port, DSA creates specialized network devices which are
37 used as controlling and data-flowing endpoints for use by the Linux networking
42 which is a hardware feature making the switch insert a specific tag for each
43 Ethernet frame it receives to/from specific ports to help the management
46 - what port is this frame coming from
47 - what was the reason why this frame got forwarded
48 - how to send CPU originated traffic to specific ports
[all …]
/Documentation/sound/cards/
Dhdspm.rst2 Software Interface ALSA-DSP MADI Driver
5 (translated from German, so no good English ;-),
7 2004 - winfried ritsch
11 the Controls and startup-options are ALSA-Standard and only the
19 ------------------
21 * number of channels -- depends on transmission mode
29 * Single Speed -- 1..64 channels
37 * Double Speed -- 1..32 channels
40 Note: Choosing the 56-channel mode for
41 transmission/receive-mode , only 28 are transmitted/received
[all …]
/Documentation/devicetree/bindings/iio/
Dmount-matrix.txt2 * is the definition of +/- values practical or counterintuitive?
13 that produce three-dimensional data in relation to the world where it is
23 relative to some specific device frame of reference.
37 reference. This means that the sensor may be flipped upside-down, left-right,
47 Device-to-world examples for some three-dimensional sensor types:
49 - Accelerometers have their world frame of reference toward the center of
57 as the gravity vector is projected 1:1 onto the sensors (z)-axis.
60 is projected onto the (x,y) plane of the display panel.
67 +--------+ +--------+
69 +--------+ +--------+
[all …]

12