Home
last modified time | relevance | path

Searched full:downstream (Results 1 – 25 of 183) sorted by relevance

12345678

/openbmc/openbmc/poky/meta/files/common-licenses/
H A DFrameworx-1.03 …nder, effective as of Your acceptance of the Frameworx Code Base or an Downstream Distribution (ea…
14 (b) Downstream Distribution means any direct or indirect release, distribution or remote availa…
32 (a) Complete Source Code for any Downstream Distribution directly or indirectly made by You tha…
34 … that you offer or provide, directly or indirectly, in relation to any Downstream Distribution sha…
36 (c) All Downstream Distributions shall:
38 …s of the Frameworx Code Base required to build the Source Code of such Downstream Distribution int…
48 …minently display to any viewer or user of the Source Code of such Open Downstream Distribution, in…
52Downstream Distributions. Each Downstream Distribution made by You, and by any party directly or i…
54Downstream Distribution made by you, or by any direct or indirect distributee of Your Downstream D…
64 …hereunder, shall be deemed automatically terminated and void as of any Downstream Distribution dir…
H A DO-UDA-1.09 …1.2. Data Provider will not sue you or any Downstream Recipient for any claim arising out of the u…
25 …nformation that you received with the Data, and your terms require any Downstream Recipient to do …
43 …5.3. "Downstream Recipient" means any person or persons who receives the Data directly or indirect…
H A DC-UDA-1.09 1.2. Data Provider will not sue you or any Downstream Recipient for any claim arising out of the us…
23 …nformation that you received with the Data, and your terms require any Downstream Recipient to do …
43 5.4. “Downstream Recipient” means any person or persons who receives the Data directly or indirectl…
/openbmc/qemu/docs/interop/
H A Dqmp-spec.rst384 Downstream extension of QMP
387 We recommend that downstream consumers of QEMU do *not* modify QMP.
388 Management tools should be able to support both upstream and downstream
389 versions of QMP without special logic, and downstream extensions are
393 avoid modifying QMP. Both upstream and downstream need to take care to
397 ``__`` (double underscore) for downstream use ("downstream names"). This
398 means upstream will never use any downstream names for its commands,
401 Any new names downstream wishes to add must begin with ``__``. To
403 recommended that you prefix your downstream names with ``__RFQDN_`` where
411 Downstream must not change the `server greeting`_ other than
[all …]
/openbmc/qemu/hw/misc/
H A Dtz-msc.c242 const char *name = "tz-msc-downstream"; in tz_msc_realize()
247 * as we don't know the size of the MR used as the downstream until then. in tz_msc_realize()
248 * We insist on having a downstream, to avoid complicating the in tz_msc_realize()
250 * enough for the user to create an unimplemented_device as downstream in tz_msc_realize()
253 if (!s->downstream) { in tz_msc_realize()
254 error_setg(errp, "MSC 'downstream' link not set"); in tz_msc_realize()
262 size = memory_region_size(s->downstream); in tz_msc_realize()
263 address_space_init(&s->downstream_as, s->downstream, name); in tz_msc_realize()
282 DEFINE_PROP_LINK("downstream", TZMSC, downstream,
H A Dtz-mpc.c389 * blocking them; non-blocked accesses go directly to the downstream
502 * as we don't know the size of the MR used as the downstream until then. in tz_mpc_realize()
503 * We insist on having a downstream, to avoid complicating the code in tz_mpc_realize()
505 * enough for the user to create an unimplemented_device as downstream in tz_mpc_realize()
508 if (!s->downstream) { in tz_mpc_realize()
509 error_setg(errp, "MPC 'downstream' link not set"); in tz_mpc_realize()
513 size = memory_region_size(s->downstream); in tz_mpc_realize()
528 "MPC 'downstream' size %" PRId64 in tz_mpc_realize()
553 address_space_init(&s->downstream_as, s->downstream, in tz_mpc_realize()
554 "tz-mpc-downstream"); in tz_mpc_realize()
[all …]
H A Dtz-ppc.c249 * as we don't know the size of the MR used as the downstream until then. in tz_ppc_realize()
252 if (s->port[i].downstream) { in tz_ppc_realize()
262 if (!port->downstream) { in tz_ppc_realize()
279 address_space_init(&port->downstream_as, port->downstream, name); in tz_ppc_realize()
281 size = memory_region_size(port->downstream); in tz_ppc_realize()
305 DEFINE_PROP_LINK("port[" #N "]", TZPPC, port[N].downstream, \
/openbmc/qemu/include/hw/input/
H A Di8042.h45 * + Named GPIO input "ps2-kbd-input-irq": set to 1 if the downstream PS2
47 * + Named GPIO input "ps2-mouse-input-irq": set to 1 if the downstream PS2
70 * + Named GPIO input "ps2-kbd-input-irq": set to 1 if the downstream PS2
72 * + Named GPIO input "ps2-mouse-input-irq": set to 1 if the downstream PS2
/openbmc/qemu/include/hw/misc/
H A Dtz-ppc.h30 * port can be emulated simply by wiring its downstream devices directly
34 * In the hardware, selection of which downstream port to use is done by
42 * downstream MemoryRegion is connected to it) at the end of the 0..15
48 * + Property "port[0..15]": MemoryRegion defining the downstream device(s)
81 MemoryRegion *downstream; member
H A Dtz-mpc.h27 * + Property "downstream": MemoryRegion defining the downstream memory
64 MemoryRegion *downstream; member
/openbmc/qemu/include/hw/pci-bridge/
H A Dxio3130_downstream.h2 * TI X3130 pci express downstream port switch
12 #define TYPE_XIO3130_DOWNSTREAM "xio3130-downstream"
/openbmc/qemu/docs/
H A Dpcie.txt35 PCI Express Downstream ports.
88 Only use PCI Express Switches (x3130-upstream, xio3130-downstream)
107 | | Downstream Port | | Downstream Port | |
124 … -device xio3130-downstream,id=downstream_port1,bus=upstream_port1,chassis=x1,slot=y1[,addr=z1]] \
173 The PCI Express Root Ports and PCI Express Downstream ports are seen by
181 Downstream port if:
187 10 PCI Express Root Ports or PCI Express Downstream Ports per system
203 PCI Express Root Ports, PCI Express Downstream/Upstream ports)
205 can be attached to a PCI Express Root Port or PCI Express Downstream
230 Be aware that PCI Express Downstream Ports can't be hot-plugged into
[all …]
/openbmc/u-boot/drivers/pci/
H A Dpci_internal.h15 * This gets a bridge ready so that its downstream devices can be scanned.
28 * ranges to fit with the devices actually found on the other side (downstream)
39 * If the device is a bridge, downstream devices will be probed.
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Inventory/Connector/
H A DPort.interface.yaml32 - name: Downstream
34 Type is downstream - this port connects to a target device.
/openbmc/qemu/hw/pci-bridge/
H A Dxio3130_downstream.c3 * TI X3130 pci express downstream port switch
33 #define PCI_DEVICE_ID_TI_XIO3130D 0x8233 /* downstream port */
143 .name = "xio3130-express-downstream-port",
168 dc->desc = "TI X3130 Downstream Port of PCI Express Switch"; in xio3130_downstream_class_init()
/openbmc/bmcweb/redfish-core/include/registries/
H A Dfabric_message_registry.hpp175 … "Indicates that a switch's downstream connection is established but is in a degraded state.",
176 … "Switch '%1' downstream link is established on port '%2', but is running in a degraded state.",
214 "Indicates that a switch's downstream connection has gone down.",
215 "Switch '%1' downstream link has gone down on port '%2'.",
227 "Indicates that a switch's downstream connection is established.",
228 "Switch '%1' downstream link is established on port '%2'.",
240 "Indicates that a switch's downstream connection is highly unstable.",
241 …"Switch '%1' downstream link on port '%2' was established and dropped %3 times in the last %4 minu…
/openbmc/pldm/fw-update/
H A Dinventory_manager.cpp195 …"Failed to encode query downstream devices request for endpoint ID EID {EID} with response code {R… in sendQueryDownstreamDevicesRequest()
198 "Failed to encode query downstream devices request"); in sendQueryDownstreamDevicesRequest()
243 * support Downstream Devices. in queryDownstreamDevices()
276 * inventory information on downstream devices. in queryDownstreamDevices()
309 …"Failed to encode query downstream identifiers request for endpoint ID {EID} with response code {R… in sendQueryDownstreamIdentifiersRequest()
312 "Failed to encode query downstream identifiers request"); in sendQueryDownstreamIdentifiersRequest()
425 … "Failed to decode downstream device descriptor for endpoint ID {EID} with response code {RC}", in queryDownstreamIdentifiers()
434 … "Failed to decode downstream devices from iterator for endpoint ID {EID} with response code {RC}", in queryDownstreamIdentifiers()
482 …"Failed to encode query downstream firmware parameters request for endpoint ID {EID} with response… in sendGetDownstreamFirmwareParametersRequest()
485 "Failed to encode query downstream firmware parameters request"); in sendGetDownstreamFirmwareParametersRequest()
[all …]
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/
H A DCable.v1_2_4.json94 "description": "The identifier for the downstream resource.",
134 "description": "The identifier for the downstream resource.",
135 … "longDescription": "This property shall contain any identifier for a downstream resource.",
234 "description": "The identifier for the downstream resource.",
401 … "description": "An array of links to the downstream chassis connected to this cable.",
405 …ay of links to resources of type `Chassis` that represent the physical downstream containers conne…
413 … "description": "An array of links to the downstream ports connected to this cable.",
417 …array of links to resources of type `Port` that represent the physical downstream connections conn…
425 … "description": "An array of links to the downstream resources connected to this cable.",
429 …all contain an array of links to resources that represent the physical downstream connections conn…
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/
H A DCable.v1_2_4.json94 "description": "The identifier for the downstream resource.",
134 "description": "The identifier for the downstream resource.",
135 … "longDescription": "This property shall contain any identifier for a downstream resource.",
234 "description": "The identifier for the downstream resource.",
401 … "description": "An array of links to the downstream chassis connected to this cable.",
405 …ay of links to resources of type `Chassis` that represent the physical downstream containers conne…
413 … "description": "An array of links to the downstream ports connected to this cable.",
417 …array of links to resources of type `Port` that represent the physical downstream connections conn…
425 … "description": "An array of links to the downstream resources connected to this cable.",
429 …all contain an array of links to resources that represent the physical downstream connections conn…
/openbmc/qemu/include/hw/dma/
H A Dpl080.h25 * + QOM property "downstream": MemoryRegion defining where DMA
69 MemoryRegion *downstream; member
/openbmc/libcper/include/libcper/sections/
H A Dcper-section-cxl-protocol.h22 (const char *[]){ "CXL 1.1 Device", "CXL 1.1 Host Downstream Port" }
51 …UINT64 PortRcrbBaseAddress; //Active when the agent is a CXL1.1 host downstream port in CxlAgentTy…
/openbmc/qemu/hw/arm/
H A Dmusca.c119 * needs to be plugged into the downstream end of the PPC port.
226 MemoryRegion *downstream; in make_mpc() local
236 downstream = &mms->ram[i]; in make_mpc()
237 memory_region_init_rom(downstream, NULL, mpcinfo[i].name, in make_mpc()
241 downstream = &mms->ram[i]; in make_mpc()
242 memory_region_init_ram(downstream, NULL, mpcinfo[i].name, in make_mpc()
253 downstream = sysbus_mmio_get_region(SYS_BUS_DEVICE(uds), 0); in make_mpc()
260 object_property_set_link(OBJECT(mpc), "downstream", OBJECT(downstream), in make_mpc()
436 * + initialize, configure and realize downstream devices in musca_init()
437 * + connect downstream device MemoryRegions to the PPC in musca_init()
[all …]
/openbmc/u-boot/arch/arm/dts/
H A Dfsl-ls2080a.dtsi111 ranges = <0x81000000 0x0 0x00000000 0x10 0x00020000 0x0 0x00010000 /* downstream I/O */
126 ranges = <0x81000000 0x0 0x00000000 0x12 0x00020000 0x0 0x00010000 /* downstream I/O */
141 ranges = <0x81000000 0x0 0x00000000 0x14 0x00020000 0x0 0x00010000 /* downstream I/O */
156 ranges = <0x81000000 0x0 0x00000000 0x16 0x00020000 0x0 0x00010000 /* downstream I/O */
/openbmc/libcper/generator/sections/
H A Dgen-section-cxl-protocol.c42 //We only reserve bytes if it's a CXL 1.1 device, and not a host downstream port. in generate_section_cxl_protocol()
57 //If the device is a host downstream port, serial/capability structure is invalid. in generate_section_cxl_protocol()
/openbmc/libpldm/include/libpldm/
H A Dfirmware_update.h29 * 1 byte for downstream device update supported
30 * 2 bytes for number of downstream devices
31 * 2 bytes for max number of downstream devices
50 * 4 bytes for downstream devices length
51 * 2 bytes for number of downstream devices
74 * 2 bytes for downstream device count
81 * 2 bytes for Downstream Device Index
431 /** @brief Downstream device update supported in QueryDownstreamDevices response
643 * Structure representing downstream device information defined in
679 /** @brief Iterate downstream devices in QueryDownstreamIdentifiers response
[all …]

12345678