Home
last modified time | relevance | path

Searched +full:dual +full:- +full:link (Results 1 – 25 of 841) sorted by relevance

12345678910>>...34

/kernel/linux/linux-5.10/drivers/gpu/drm/
Ddrm_of.c1 // SPDX-License-Identifier: GPL-2.0-only
27 * drm_of_crtc_port_mask - find the mask of a registered CRTC by port OF node
41 if (tmp->port == port) in drm_of_crtc_port_mask()
52 * drm_of_find_possible_crtcs - find the possible CRTCs for an encoder port
85 * drm_of_component_match_add - Add a component helper OF node match rule
103 * drm_of_component_probe - Generic probe function for a component based master
123 if (!dev->of_node) in drm_of_component_probe()
124 return -EINVAL; in drm_of_component_probe()
131 port = of_parse_phandle(dev->of_node, "ports", i); in drm_of_component_probe()
135 if (of_device_is_available(port->parent)) in drm_of_component_probe()
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/display/panel/
Dadvantech,idk-2121wr.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/display/panel/advantech,idk-2121wr.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Advantech IDK-2121WR 21.5" Full-HD dual-LVDS panel
10 - Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
11 - Thierry Reding <thierry.reding@gmail.com>
14 The IDK-2121WR from Advantech is a Full-HD dual-LVDS panel.
15 A dual-LVDS interface is a dual-link connection with even pixels traveling
16 on one link, and with odd pixels traveling on the other link.
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/display/bridge/
Dthine,thc63lvd1024.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jacopo Mondi <jacopo+renesas@jmondi.org>
11 - Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
14 The THC63LVD1024 is a dual link LVDS receiver designed to convert LVDS
15 streams to parallel data outputs. The chip supports single/dual input/output
19 Single or dual operation mode, output data mapping and DDR output modes are
33 The device can operate in single-link mode or dual-link mode. In
34 single-link mode, all pixels are received on port@0, and port@1 shall not
[all …]
Dtoshiba,tc358775.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Vinay Simha BN <simhavcs@gmail.com>
15 MIPI DSI-RX Data 4-lane, CLK 1-lane with data rates up to 800 Mbps/lane.
17 Up to 1600x1200 24-bit/pixel resolution for single-link LVDS display panel
19 Up to WUXGA (1920x1200 24-bit pixels) resolution for dual-link LVDS display
30 vdd-supply:
34 vddio-supply:
38 stby-gpios:
[all …]
/kernel/linux/linux-4.19/Documentation/scsi/
Dbfa.txt5 ------------------
12 1657:0013:1657:0014 425 4Gbps dual port FC HBA
13 1657:0013:1657:0014 825 8Gbps PCIe dual port FC HBA
15 1657:0013:103c:1744 HP 42B 4Gbps dual port FC HBA
20 1657:0021:103c:1779 804 8Gbps FC HBA for HP Bladesystem c-class
22 1657:0014:1657:0014 1010 10Gbps single port CNA - FCOE
23 1657:0014:1657:0014 1020 10Gbps dual port CNA - FCOE
24 1657:0014:1657:0014 1007 10Gbps dual port CNA - FCOE
25 1657:0014:1657:0014 1741 10Gbps dual port CNA - FCOE
28 1657:0022:1657:0022 1860 10Gbps CNA - FCOE
[all …]
/kernel/linux/linux-5.10/Documentation/scsi/
Dbfa.rst1 .. SPDX-License-Identifier: GPL-2.0
8 ------------------
16 1657:0013:1657:0014 425 4Gbps dual port FC HBA
17 1657:0013:1657:0014 825 8Gbps PCIe dual port FC HBA
19 1657:0013:103c:1744 HP 42B 4Gbps dual port FC HBA
24 1657:0021:103c:1779 804 8Gbps FC HBA for HP Bladesystem c-class
26 1657:0014:1657:0014 1010 10Gbps single port CNA - FCOE
27 1657:0014:1657:0014 1020 10Gbps dual port CNA - FCOE
28 1657:0014:1657:0014 1007 10Gbps dual port CNA - FCOE
29 1657:0014:1657:0014 1741 10Gbps dual port CNA - FCOE
[all …]
/kernel/linux/linux-5.10/Documentation/networking/device_drivers/ethernet/ti/
Dcpsw_switchdev.rst1 .. SPDX-License-Identifier: GPL-2.0
17 ip -d link show dev sw0p1 | grep switchid
23 Dual mac mode
26 - The new (cpsw_new.c) driver is operating in dual-emac mode by default, thus
30 - optimized promiscuous mode: The P0_UNI_FLOOD (both ports) is enabled in
36 - learning disabled on ports as it make not too much sense for
37 segregated ports - no forwarding in HW.
38 - enabled basic support for devlink.
47 name switch_mode type driver-specific
50 name ale_bypass type driver-specific
[all …]
/kernel/linux/linux-4.19/drivers/gpu/drm/amd/display/dc/bios/
Dcommand_table.c2 * Copyright 2012-15 Advanced Micro Devices, Inc.
38 …(amdgpu_atom_execute_table(((struct amdgpu_device *)bp->base.ctx->driver_context)->mode_info.atom_…
43 …amdgpu_atom_parse_cmd_header(((struct amdgpu_device *)bp->base.ctx->driver_context)->mode_info.ato…
47 bios_cmd_table_para_revision(bp->base.ctx->driver_context, \
91 if (amdgpu_atom_parse_cmd_header(adev->mode_info.atom_context, in bios_cmd_table_para_revision()
127 bp->cmd_tbl.dig_encoder_control = encoder_control_digx_v3; in init_dig_encoder_control()
130 bp->cmd_tbl.dig_encoder_control = encoder_control_digx_v4; in init_dig_encoder_control()
134 bp->cmd_tbl.dig_encoder_control = encoder_control_digx_v5; in init_dig_encoder_control()
155 struct cmd_tbl *cmd_tbl = &bp->cmd_tbl; in init_encoder_control_dig_v1()
158 cmd_tbl->encoder_control_dig1 = encoder_control_dig1_v1; in init_encoder_control_dig_v1()
[all …]
/kernel/linux/linux-5.10/drivers/gpu/drm/amd/display/dc/bios/
Dcommand_table.c2 * Copyright 2012-15 Advanced Micro Devices, Inc.
38 …(amdgpu_atom_execute_table(((struct amdgpu_device *)bp->base.ctx->driver_context)->mode_info.atom_…
43 …amdgpu_atom_parse_cmd_header(((struct amdgpu_device *)bp->base.ctx->driver_context)->mode_info.ato…
47 bios_cmd_table_para_revision(bp->base.ctx->driver_context, \
89 if (amdgpu_atom_parse_cmd_header(adev->mode_info.atom_context, in bios_cmd_table_para_revision()
125 bp->cmd_tbl.dig_encoder_control = encoder_control_digx_v3; in init_dig_encoder_control()
128 bp->cmd_tbl.dig_encoder_control = encoder_control_digx_v4; in init_dig_encoder_control()
132 bp->cmd_tbl.dig_encoder_control = encoder_control_digx_v5; in init_dig_encoder_control()
153 struct cmd_tbl *cmd_tbl = &bp->cmd_tbl; in init_encoder_control_dig_v1()
156 cmd_tbl->encoder_control_dig1 = encoder_control_dig1_v1; in init_encoder_control_dig_v1()
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/display/connector/
Ddvi-connector.yaml1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
4 $id: http://devicetree.org/schemas/display/connector/dvi-connector.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Laurent Pinchart <Laurent.pinchart@ideasonboard.com>
14 const: dvi-connector
18 hpd-gpios:
22 ddc-i2c-bus:
23 description: phandle link to the I2C controller used for DDC EDID probing
34 dual-link:
[all …]
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/display/connector/
Ddvi-connector.txt5 - compatible: "dvi-connector"
8 - label: a symbolic name for the connector
9 - ddc-i2c-bus: phandle to the i2c bus that is connected to DVI DDC
10 - analog: the connector has DVI analog pins
11 - digital: the connector has DVI digital pins
12 - dual-link: the connector has pins for DVI dual-link
13 - hpd-gpios: HPD GPIO number
16 - Video port for DVI input
21 -------
24 compatible = "dvi-connector";
[all …]
/kernel/linux/linux-4.19/Documentation/networking/
Dixgbe.txt6 Copyright(c) 1999 - 2013 Intel Corporation.
11 - Identifying Your Adapter
12 - Additional Configurations
13 - Performance Tuning
14 - Known Issues
15 - Support
20 The driver in this release is compatible with 82598, 82599 and X540-based
26 http://support.intel.com/support/network/sb/CS-012904.htm
29 ----------------------------------
31 82599-BASED ADAPTERS
[all …]
/kernel/linux/linux-5.10/Documentation/networking/device_drivers/ethernet/intel/
Dixgbe.rst1 .. SPDX-License-Identifier: GPL-2.0+
8 Copyright(c) 1999-2018 Intel Corporation.
13 - Identifying Your Adapter
14 - Command Line Parameters
15 - Additional Configurations
16 - Known Issues
17 - Support
36 ----------------------------------
38 82599-BASED ADAPTERS
41 - If your 82599-based Intel(R) Network Adapter came with Intel optics or is an
[all …]
De1000e.rst1 .. SPDX-License-Identifier: GPL-2.0+
8 Copyright(c) 2008-2018 Intel Corporation.
13 - Identifying Your Adapter
14 - Command Line Parameters
15 - Additional Configurations
16 - Support
48 ---------------------
49 :Valid Range: 0,1,3,4,100-100000
82 - 0: Off
86 - 1: Dynamic mode
[all …]
/kernel/linux/linux-4.19/drivers/staging/sm750fb/
Dreadme4 - dual display
5 - 2D acceleration
6 - 16MB integrated video memory
11 insmod ./sm750fb.ko g_option="1280x1024-8@60"
17 dual frame buffer for driver with "dual" parameter
18 insmod ./sm750fb.ko g_option="dual,800x600:1024x768"
20 and user can use con2fb to link fbX and ttyX
23 1) if you build the driver with built-in method, the parameter
37 and this driver will use fb1, fb2. In that case, you need to configure your X-server
/kernel/linux/linux-5.10/drivers/staging/sm750fb/
Dreadme4 - dual display
5 - 2D acceleration
6 - 16MB integrated video memory
11 insmod ./sm750fb.ko g_option="1280x1024-8@60"
17 dual frame buffer for driver with "dual" parameter
18 insmod ./sm750fb.ko g_option="dual,800x600:1024x768"
20 and user can use con2fb to link fbX and ttyX
23 1) if you build the driver with built-in method, the parameter
37 and this driver will use fb1, fb2. In that case, you need to configure your X-server
/kernel/linux/linux-5.10/drivers/scsi/pcmcia/
Dfdomain_cs.c1 // SPDX-License-Identifier: (GPL-2.0 OR MPL-1.1)
3 * Driver for Future Domain-compatible PCMCIA SCSI cards
20 MODULE_LICENSE("Dual MPL/GPL");
24 p_dev->io_lines = 10; in fdomain_config_check()
25 p_dev->resource[0]->end = FDOMAIN_REGION_SIZE; in fdomain_config_check()
26 p_dev->resource[0]->flags &= ~IO_DATA_PATH_WIDTH; in fdomain_config_check()
27 p_dev->resource[0]->flags |= IO_DATA_PATH_WIDTH_AUTO; in fdomain_config_check()
31 static int fdomain_probe(struct pcmcia_device *link) in fdomain_probe() argument
36 link->config_flags |= CONF_ENABLE_IRQ | CONF_AUTO_SET_IO; in fdomain_probe()
37 link->config_regs = PRESENT_OPTION; in fdomain_probe()
[all …]
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/display/bridge/
Dthine,thc63lvd1024.txt2 -------------------------------------------
4 The THC63LVD1024 is a dual link LVDS receiver designed to convert LVDS streams
5 to parallel data outputs. The chip supports single/dual input/output modes,
8 Single or dual operation mode, output data mapping and DDR output modes are
12 - compatible: Shall be "thine,thc63lvd1024"
13 - vcc-supply: Power supply for TTL output, TTL CLOCKOUT signal, LVDS input,
17 - powerdown-gpios: Power down GPIO signal, pin name "/PDWN". Active low
18 - oe-gpios: Output enable GPIO signal, pin name "OE". Active high
24 - port@0: First LVDS input port
25 - port@2: First digital CMOS/TTL parallel output
[all …]
/kernel/linux/linux-5.10/drivers/gpu/drm/rcar-du/
Drcar_lvds.c1 // SPDX-License-Identifier: GPL-2.0
3 * rcar_lvds.c -- R-Car LVDS Encoder
5 * Copyright (C) 2013-2018 Renesas Electronics Corporation
51 #define RCAR_LVDS_QUIRK_DUAL_LINK BIT(4) /* Supports dual-link operation */
88 iowrite32(data, lvds->mmio + reg); in rcar_lvds_write()
91 /* -----------------------------------------------------------------------------
99 return drm_panel_get_modes(lvds->panel, connector); in rcar_lvds_connector_get_modes()
111 if (!conn_state->crtc) in rcar_lvds_connector_atomic_check()
114 if (list_empty(&connector->modes)) { in rcar_lvds_connector_atomic_check()
115 dev_dbg(lvds->dev, "connector: empty modes list\n"); in rcar_lvds_connector_atomic_check()
[all …]
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/display/panel/
Dsharp,lq101r1sx01.txt3 This panel requires a dual-channel DSI host to operate. It supports two modes:
4 - left-right: each channel drives the left or right half of the screen
5 - even-odd: each channel drives the even or odd lines of the screen
8 driven by the first link (DSI-LINK1), left or even, is considered the primary
10 to the peripheral driven by the second link (DSI-LINK2, right or odd).
12 Note that in video mode the DSI-LINK1 interface always provides the left/even
13 pixels and DSI-LINK2 always provides the right/odd pixels. In command mode it
14 is possible to program either link to drive the left/even or right/odd pixels
19 - compatible: should be "sharp,lq101r1sx01"
20 - reg: DSI virtual channel of the peripheral
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/display/msm/
Ddsi.txt5 - compatible:
6 * "qcom,mdss-dsi-ctrl"
7 - reg: Physical base address and length of the registers of controller
8 - reg-names: The names of register regions. The following regions are required:
10 - interrupts: The interrupt signal from the DSI block.
11 - power-domains: Should be <&mmcc MDSS_GDSC>.
12 - clocks: Phandles to device clocks.
13 - clock-names: the following clocks are required:
25 - assigned-clocks: Parents of "byte" and "pixel" for the given platform.
26 - assigned-clock-parents: The Byte clock and Pixel clock PLL outputs provided
[all …]
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/display/msm/
Ddsi.txt5 - compatible:
6 * "qcom,mdss-dsi-ctrl"
7 - reg: Physical base address and length of the registers of controller
8 - reg-names: The names of register regions. The following regions are required:
10 - interrupts: The interrupt signal from the DSI block.
11 - power-domains: Should be <&mmcc MDSS_GDSC>.
12 - clocks: Phandles to device clocks.
13 - clock-names: the following clocks are required:
25 - assigned-clocks: Parents of "byte" and "pixel" for the given platform.
26 - assigned-clock-parents: The Byte clock and Pixel clock PLL outputs provided
[all …]
/kernel/linux/linux-4.19/drivers/gpu/drm/i2c/
DKconfig18 Support for sil164 and similar single-link (or dual-link
/kernel/linux/linux-5.10/drivers/gpu/drm/i2c/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
19 Support for sil164 and similar single-link (or dual-link
/kernel/linux/linux-5.10/drivers/net/wireless/ti/wl12xx/
Dconf.h1 /* SPDX-License-Identifier: GPL-2.0-only */
41 * Range: 0 - 255 (ms)
50 * Range: 0 - 255 (ms)
59 * Range: 0 - 255 (ms)
68 * Range: 0 - 255 (ms)
77 * Range: 0 - 255 (ms)
86 * Range: 0 - 255 (ms)
110 * during BT voice/ACL link.
112 * Range: 0 - 255 (%)
120 * Range: 0 - 255 (%)
[all …]

12345678910>>...34