| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/fpga/ |
| D | fpga-region.txt | 58 * FPGA Bridges gate bus signals between a host and FPGA.
59 * FPGA Bridges should be disabled while the FPGA is being programmed to
61 * FPGA bridges may be actual hardware or soft logic on an FPGA.
62 * During Full Reconfiguration, hardware bridges between the host and FPGA
67 buses, eliminating the need to show the hardware FPGA bridges in the
111 1. Disable appropriate FPGA bridges.
113 3. Enable the FPGA bridges.
118 will disable the bridges.
129 * FPGA Bridges
145 FPGA region will be the child of one of the hardware bridges (the bridge that
[all …]
|
| D | altera-freeze-bridge.txt | 3 The Altera Freeze Bridge Controller manages one or more freeze bridges.
4 The controller can freeze/disable the bridges which prevents signal
6 unfreeze/enable the bridges which allows traffic to pass through the
|
| D | xilinx-pr-decoupler.txt | 4 decouplers / fpga bridges.
5 The controller can decouple/disable the bridges which prevents signal
7 couple / enable the bridges which allows traffic to pass through the
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/fpga/ |
| D | fpga-region.txt | 58 * FPGA Bridges gate bus signals between a host and FPGA.
59 * FPGA Bridges should be disabled while the FPGA is being programmed to
61 * FPGA bridges may be actual hardware or soft logic on an FPGA.
62 * During Full Reconfiguration, hardware bridges between the host and FPGA
67 buses, eliminating the need to show the hardware FPGA bridges in the
111 1. Disable appropriate FPGA bridges.
113 3. Enable the FPGA bridges.
118 will disable the bridges.
129 * FPGA Bridges
145 FPGA region will be the child of one of the hardware bridges (the bridge that
[all …]
|
| D | altera-freeze-bridge.txt | 3 The Altera Freeze Bridge Controller manages one or more freeze bridges.
4 The controller can freeze/disable the bridges which prevents signal
6 unfreeze/enable the bridges which allows traffic to pass through the
|
| /kernel/linux/linux-6.6/drivers/pcmcia/ |
| D | Kconfig | 63 bridge. Virtually all modern PCMCIA bridges do this, and most of
71 comment "PC-card bridges"
79 This option enables support for CardBus host bridges. Virtually
80 all modern PCMCIA bridges are CardBus compatible. A "bridge" is
91 bool "Special initialization for O2Micro bridges" if EXPERT
96 bool "Special initialization for Ricoh bridges" if EXPERT
101 bool "Special initialization for TI and EnE bridges" if EXPERT
106 bool "Auto-tune EnE bridges for CB cards" if EXPERT
111 bool "Special initialization for Toshiba ToPIC bridges" if EXPERT
136 Say Y here to include support for ISA-bus PCMCIA host bridges that
[all …]
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/ |
| D | drm_bridge.c | 42 * either connected to it directly, or through a chain of bridges::
48 * Chaining multiple bridges to the output of a bridge, or the same bridge to
49 * the output of different bridges, is not supported.
58 * Bridges are responsible for linking themselves with the next bridge in the
62 * Once these links are created, the bridges can participate along with encoder
70 * bridges in the chain.
82 * Bridges also participate in implementing the &drm_connector at the end of
168 * Note that bridges attached to encoders are auto-detached during encoder
258 * - The encoder-related operations support control of the bridges in the
279 * negotiate the formats transmitted between bridges in the chain when
[all …]
|
| D | drm_bridge_connector.c | 24 * operations are fully implemented based on the operations of the bridges in
30 * connector with the chain of bridges passed to the function and registers it
35 * provided by the bridges in the chain. Each connector operation is delegated
39 * To make use of this helper, all bridges in the chain shall report bridge
42 * flag (none of the bridges shall create a DRM connector directly).
46 * struct drm_bridge_connector - A connector backed by a chain of bridges
56 * The encoder at the start of the bridges chain.
103 /* Notify all bridges in the pipeline of hotplug events. */ in drm_bridge_connector_hpd_notify()
292 /* No need for .mode_valid(), the bridges are checked by the core. */
300 * drm_bridge_connector_init - Initialise a connector for a chain of bridges
[all …]
|
| /kernel/linux/linux-5.10/drivers/pcmcia/ |
| D | Kconfig | 63 bridge. Virtually all modern PCMCIA bridges do this, and most of
71 comment "PC-card bridges"
79 This option enables support for CardBus host bridges. Virtually
80 all modern PCMCIA bridges are CardBus compatible. A "bridge" is
91 bool "Special initialization for O2Micro bridges" if EXPERT
96 bool "Special initialization for Ricoh bridges" if EXPERT
101 bool "Special initialization for TI and EnE bridges" if EXPERT
106 bool "Auto-tune EnE bridges for CB cards" if EXPERT
111 bool "Special initialization for Toshiba ToPIC bridges" if EXPERT
136 Say Y here to include support for ISA-bus PCMCIA host bridges that
[all …]
|
| /kernel/linux/linux-6.6/drivers/gpu/drm/ |
| D | drm_bridge_connector.c | 24 * operations are fully implemented based on the operations of the bridges in
30 * connector with the chain of bridges passed to the function and registers it
35 * provided by the bridges in the chain. Each connector operation is delegated
39 * To make use of this helper, all bridges in the chain shall report bridge
42 * flag (none of the bridges shall create a DRM connector directly).
46 * struct drm_bridge_connector - A connector backed by a chain of bridges
56 * The encoder at the start of the bridges chain.
103 /* Notify all bridges in the pipeline of hotplug events. */ in drm_bridge_connector_hpd_notify()
290 /* No need for .mode_valid(), the bridges are checked by the core. */
300 * drm_bridge_connector_init - Initialise a connector for a chain of bridges
[all …]
|
| D | drm_bridge.c | 48 * either connected to it directly, or through a chain of bridges::
54 * Chaining multiple bridges to the output of a bridge, or the same bridge to
55 * the output of different bridges, is not supported.
71 * Bridges are responsible for linking themselves with the next bridge in the
75 * Once these links are created, the bridges can participate along with encoder
83 * bridges in the chain.
95 * Bridges also participate in implementing the &drm_connector at the end of
105 * The interaction between the bridges and other frameworks involved in
162 * DSI host interfaces are expected to be implemented as bridges rather than
295 * Note that bridges attached to encoders are auto-detached during encoder
[all …]
|
| /kernel/linux/linux-6.6/include/drm/ |
| D | drm_bridge.h | 220 * of the bridges chain, for instance when the first bridge in the chain
222 * bridge in the chain and is likely irrelevant for the other bridges.
370 * otherwise. For bridges that don't subclass &drm_bridge_state, the
387 * For bridges that don't subclass &drm_bridge_state, the
441 * Bridge drivers that need to support being linked to bridges that are
499 * bridges that don't subclass &drm_bridge_state, the
508 * 2. It's meant to be used exclusively on bridges that have been
524 * Bridges that implement this callback shall set the
540 * displays such as many fixed panels. Bridges that support reading
544 * This callback is optional. Bridges that implement it shall set the
[all …]
|
| /kernel/linux/linux-5.10/include/drm/ |
| D | drm_bridge.h | 209 * of the bridges chain, for instance when the first bridge in the chain
211 * bridge in the chain and is likely irrelevant for the other bridges.
373 * otherwise. For bridges that don't subclass &drm_bridge_state, the
390 * For bridges that don't subclass &drm_bridge_state, the
444 * Bridge drivers that need to support being linked to bridges that are
502 * bridges that don't subclass &drm_bridge_state, the
511 * 2. It's meant to be used exclusively on bridges that have been
527 * Bridges that implement this callback shall set the
543 * displays such as many fixed panels. Bridges that support reading
547 * This callback is optional. Bridges that implement it shall set the
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/display/bridge/ |
| D | megachips-stdpxxxx-ge-b850v3-fw.txt | 2 STDP4028-ge-b850v3-fw bridges (LVDS-DP)
3 STDP2690-ge-b850v3-fw bridges (DP-DP++)
11 STDP2690 behave as the stock bridges would. The compatible strings include the
12 suffix "-ge-b850v3-fw" to make it clear that the driver is for the bridges with
16 two bridges behaves as a single one. The only interfaces exposed by the
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/display/bridge/ |
| D | megachips-stdpxxxx-ge-b850v3-fw.txt | 2 STDP4028-ge-b850v3-fw bridges (LVDS-DP)
3 STDP2690-ge-b850v3-fw bridges (DP-DP++)
11 STDP2690 behave as the stock bridges would. The compatible strings include the
12 suffix "-ge-b850v3-fw" to make it clear that the driver is for the bridges with
16 two bridges behaves as a single one. The only interfaces exposed by the
|
| /kernel/linux/linux-5.10/Documentation/driver-api/fpga/ |
| D | fpga-region.rst | 12 an FPGA Manager and a bridge (or bridges) with a reprogrammable region of an
26 * which bridges to disable before programming and enable afterwards.
62 The FPGA region will need to specify which bridges to control while programming
63 the FPGA. The region driver can build a list of bridges during probe time
65 the list of bridges to program just before programming
73 * fpga_bridges_put() — Given a list of bridges, put them
|
| D | fpga-programming.rst | 12 the FPGA manager and bridges. It will:
16 * build a list of FPGA bridges if a method has been specified to do so
17 * disable the bridges
19 * re-enable the bridges
31 bridges to control during programming or it has a pointer to a function that
|
| /kernel/linux/linux-6.6/Documentation/driver-api/fpga/ |
| D | fpga-region.rst | 12 an FPGA Manager and a bridge (or bridges) with a reprogrammable region of an
26 * which bridges to disable before programming and enable afterwards.
68 The FPGA region will need to specify which bridges to control while programming
69 the FPGA. The region driver can build a list of bridges during probe time
71 the list of bridges to program just before programming
79 * fpga_bridges_put() - Given a list of bridges, put them
|
| D | fpga-programming.rst | 12 the FPGA manager and bridges. It will:
16 * build a list of FPGA bridges if a method has been specified to do so
17 * disable the bridges
19 * re-enable the bridges
31 bridges to control during programming or it has a pointer to a function that
|
| /kernel/linux/linux-5.10/drivers/fpga/ |
| D | of-fpga-region.c | 72 * of_fpga_region_get_bridges - create a list of bridges
75 * Create a list of bridges including the parent bridge and the bridges
76 * specified by "fpga-bridges" property. Note that the
81 * done with the bridges.
83 * Return 0 for success (even if there are no bridges specified)
84 * or -EBUSY if any of the bridges are in use.
106 /* If overlay has a list of bridges, use it. */ in of_fpga_region_get_bridges()
107 br = of_parse_phandle(info->overlay, "fpga-bridges", 0); in of_fpga_region_get_bridges()
116 br = of_parse_phandle(np, "fpga-bridges", i); in of_fpga_region_get_bridges()
131 /* If any of the bridges are in use, give up */ in of_fpga_region_get_bridges()
|
| D | fpga-region.c | 89 * bridges will be held if programming succeeds. This is intended to prevent
115 * In some cases, we already have a list of bridges in the in fpga_region_program_fpga()
116 * fpga region struct. Or we don't have any bridges. in fpga_region_program_fpga()
121 dev_err(dev, "failed to get fpga region bridges\n"); in fpga_region_program_fpga()
128 dev_err(dev, "failed to disable bridges\n"); in fpga_region_program_fpga()
140 dev_err(dev, "failed to enable region bridges\n"); in fpga_region_program_fpga()
186 * @get_bridges: optional function to get bridges to a list
258 * @get_bridges: optional function to get bridges to a list
|
| D | fpga-bridge.c | 19 /* Lock for adding/removing bridges to linked lists*/
155 * fpga_bridges_enable - enable bridges in a list
156 * @bridge_list: list of FPGA bridges
178 * fpga_bridges_disable - disable bridges in a list
180 * @bridge_list: list of FPGA bridges
202 * fpga_bridges_put - put bridges
204 * @bridge_list: list of FPGA bridges
229 * @bridge_list: list of FPGA bridges
259 * @bridge_list: list of FPGA bridges
|
| /kernel/linux/linux-6.6/drivers/fpga/ |
| D | of-fpga-region.c | 74 * of_fpga_region_get_bridges - create a list of bridges
77 * Create a list of bridges including the parent bridge and the bridges
78 * specified by "fpga-bridges" property. Note that the
83 * done with the bridges.
85 * Return: 0 for success (even if there are no bridges specified)
86 * or -EBUSY if any of the bridges are in use.
108 /* If overlay has a list of bridges, use it. */ in of_fpga_region_get_bridges()
109 br = of_parse_phandle(info->overlay, "fpga-bridges", 0); in of_fpga_region_get_bridges()
118 br = of_parse_phandle(np, "fpga-bridges", i); in of_fpga_region_get_bridges()
133 /* If any of the bridges are in use, give up */ in of_fpga_region_get_bridges()
|
| D | fpga-bridge.c | 19 /* Lock for adding/removing bridges to linked lists*/
159 * fpga_bridges_enable - enable bridges in a list
160 * @bridge_list: list of FPGA bridges
182 * fpga_bridges_disable - disable bridges in a list
184 * @bridge_list: list of FPGA bridges
206 * fpga_bridges_put - put bridges
208 * @bridge_list: list of FPGA bridges
233 * @bridge_list: list of FPGA bridges
263 * @bridge_list: list of FPGA bridges
|
| D | fpga-region.c | 90 * bridges will be held if programming succeeds. This is intended to prevent
116 * In some cases, we already have a list of bridges in the in fpga_region_program_fpga()
117 * fpga region struct. Or we don't have any bridges. in fpga_region_program_fpga()
122 dev_err(dev, "failed to get fpga region bridges\n"); in fpga_region_program_fpga()
129 dev_err(dev, "failed to disable bridges\n"); in fpga_region_program_fpga()
141 dev_err(dev, "failed to enable region bridges\n"); in fpga_region_program_fpga()
253 * @get_bridges: optional function to get bridges to a list
|