| /linux-6.12.1/Documentation/devicetree/bindings/fpga/ |
| D | fpga-region.yaml | 65 * FPGA Bridges gate bus signals between a host and FPGA.
66 * FPGA Bridges should be disabled while the FPGA is being programmed to
68 * FPGA bridges may be actual hardware or soft logic on an FPGA.
69 * During Full Reconfiguration, hardware bridges between the host and FPGA
74 buses, eliminating the need to show the hardware FPGA bridges in the
118 1. Disable appropriate FPGA bridges.
120 3. Enable the FPGA bridges.
125 will disable the bridges.
136 * FPGA Bridges
152 FPGA region will be the child of one of the hardware bridges (the bridge that
[all …]
|
| D | altr,freeze-bridge-controller.yaml | 10 The Altera Freeze Bridge Controller manages one or more freeze bridges.
11 The controller can freeze/disable the bridges which prevents signal
13 unfreeze/enable the bridges which allows traffic to pass through the bridge
|
| D | xlnx,pr-decoupler.yaml | 17 decouplers/fpga bridges. The controller can decouple/disable the bridges
19 can also couple / enable the bridges which allows traffic to pass through the
|
| /linux-6.12.1/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 …]
|
| /linux-6.12.1/include/drm/ |
| D | drm_bridge.h | 222 * of the bridges chain, for instance when the first bridge in the chain
224 * bridge in the chain and is likely irrelevant for the other bridges.
372 * otherwise. For bridges that don't subclass &drm_bridge_state, the
389 * For bridges that don't subclass &drm_bridge_state, the
443 * Bridge drivers that need to support being linked to bridges that are
501 * bridges that don't subclass &drm_bridge_state, the
510 * 2. It's meant to be used exclusively on bridges that have been
526 * Bridges that implement this callback shall set the
542 * displays such as many fixed panels. Bridges that support reading
546 * This callback is optional. Bridges that implement it shall set the
[all …]
|
| /linux-6.12.1/drivers/gpu/drm/ |
| 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 …]
|
| /linux-6.12.1/drivers/gpu/drm/display/ |
| D | drm_bridge_connector.c | 28 * operations are fully implemented based on the operations of the bridges in
34 * connector with the chain of bridges passed to the function and registers it
39 * provided by the bridges in the chain. Each connector operation is delegated
43 * To make use of this helper, all bridges in the chain shall report bridge
46 * flag (none of the bridges shall create a DRM connector directly).
50 * struct drm_bridge_connector - A connector backed by a chain of bridges
60 * The encoder at the start of the bridges chain.
114 /* Notify all bridges in the pipeline of hotplug events. */ in drm_bridge_connector_hpd_notify()
304 /* No need for .mode_valid(), the bridges are checked by the core. */
368 * drm_bridge_connector_init - Initialise a connector for a chain of bridges
[all …]
|
| /linux-6.12.1/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
|
| /linux-6.12.1/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
|
| /linux-6.12.1/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
|
| D | Kconfig | 109 Say Y here if you want to support bridges connected between host
113 tristate "Altera SoCFPGA FPGA Bridges"
116 Say Y to enable drivers for FPGA bridges for Altera SOCFPGA
123 Say Y to enable drivers for Altera FPGA Freeze bridges. A
150 and the FPGA Bridges associated with either a reconfigurable
|
| /linux-6.12.1/Documentation/devicetree/bindings/pci/ |
| D | pci.txt | 1 PCI bus bridges have standardized Device Tree bindings:
18 host bridges in the system, otherwise potentially conflicting domain numbers
19 may be assigned to root buses behind different host bridges. The domain
68 When present, the port is external-facing. All bridges and endpoints
|
| /linux-6.12.1/include/linux/fpga/ |
| D | fpga-region.h | 17 * @get_bridges: optional function to get bridges to a list
35 * @bridge_list: list of FPGA bridges specified in region
41 * @get_bridges: optional function to get bridges to a list
|
| /linux-6.12.1/Documentation/networking/ |
| D | bridge.rst | 10 The IEEE 802.1Q-2022 (Bridges and Bridged Networks) standard defines the
11 operation of bridges in computer networks. A bridge, in the context of this
67 IEEE 802.1Q (Bridges and Bridged Networks) or IEEE 802.1AC (MAC Service
101 different bridges.
102 3. Bridge Election: When the network starts, all bridges initially assume
106 4. BPDU Comparison: Bridges exchange BPDUs to determine the root bridge.
111 BPDUs with information about the root bridge to all other bridges in the
112 network. This information is used by other bridges to calculate the
119 all in the forwarding state. while other bridges have some ports in the
|
| /linux-6.12.1/Documentation/devicetree/bindings/ata/ |
| D | cortina,gemini-sata-bridge.yaml | 14 takes two Faraday Technology FTIDE010 PATA controllers and bridges
26 description: phandles to the reset lines for both SATA bridges
55 bridges.
|
| /linux-6.12.1/drivers/gpu/drm/bridge/ |
| D | megachips-stdpxxxx-ge-b850v3-fw.c | 11 * display bridge of the GE B850v3. There are two physical bridges on the video
13 * physical bridges are automatically configured by the input video signal, and
16 * STDP4028. The driver communicates with both bridges over i2c. The video
308 /* Only register after both bridges are probed */ in stdp4028_ge_b850v3_fw_probe()
355 /* Only register after both bridges are probed */ in stdp2690_ge_b850v3_fw_probe()
|
| D | Kconfig | 22 build bridges chain.
32 menu "Display Interface Bridges"
187 This is a driver for the display bridges of
293 Support for non-programmable DRM bridges, such as ADI ADV7123, TI
|
| /linux-6.12.1/arch/alpha/kernel/ |
| D | sys_eiger.c | 168 /* Find the number of backplane bridges. */ in eiger_swizzle()
173 case 0x00: bridge_count = 0; break; /* No bridges */ in eiger_swizzle()
182 /* Check for built-in bridges on hose 0. */ in eiger_swizzle()
192 /* Move up the chain of bridges. */ in eiger_swizzle()
|
| /linux-6.12.1/drivers/ata/ |
| D | pata_ftide010.c | 274 int bridges = 0; in pata_ftide010_gemini_port_start() local
285 bridges++; in pata_ftide010_gemini_port_start()
291 bridges++; in pata_ftide010_gemini_port_start()
298 bridges++; in pata_ftide010_gemini_port_start()
305 bridges++; in pata_ftide010_gemini_port_start()
308 dev_info(dev, "brought %d bridges online\n", bridges); in pata_ftide010_gemini_port_start()
309 return (bridges > 0) ? 0 : -EINVAL; // -ENODEV; in pata_ftide010_gemini_port_start()
|
| /linux-6.12.1/Documentation/PCI/ |
| D | msi-howto.rst | 50 bridges). In order to ensure that all the data has arrived in memory,
239 Some PCI bridges are not able to route MSIs between buses properly.
242 Some bridges allow you to enable MSIs by changing some bits in their
259 Again, please notify linux-pci@vger.kernel.org of any bridges that need
280 Then, 'lspci -t' gives the list of bridges above a device. Reading
283 to bridges between the PCI root and the device, MSIs are disabled.
|
| /linux-6.12.1/drivers/pci/ |
| D | probe.c | 427 * Some bridges set the base > limit by default, and some in pci_read_bridge_mmio_pref()
1095 * - PCI-to-PCI bridges in pci_bridge_child_ext_cfg_accessible()
1096 * - PCIe-to-PCI/PCI-X forward bridges in pci_bridge_child_ext_cfg_accessible()
1097 * - PCI/PCI-X-to-PCIe reverse bridges in pci_bridge_child_ext_cfg_accessible()
1266 * distributed equally between hotplug-capable bridges.
1267 * @pass: Either %0 (scan already configured bridges) or %1 (scan bridges
1271 * For CardBus bridges, we don't scan behind as the devices will
1274 * We need to process bridges in two passes -- first we scan those
1380 * configuration cycles on all bridges in in pci_scan_bridge_extend()
1383 * bridges programmed with overlapping bus in pci_scan_bridge_extend()
[all …]
|
| /linux-6.12.1/drivers/fpga/tests/ |
| D | fpga-bridge-test.c | 106 /* Test the functions for getting and controlling a list of bridges */
132 /* Disable an then enable both bridges from the list */ in fpga_bridge_test_get_put_list()
145 /* Put and remove both bridges from the list */ in fpga_bridge_test_get_put_list()
|