Home
last modified time | relevance | path

Searched full:upstream (Results 1 – 25 of 413) sorted by relevance

12345678910>>...17

/linux-6.12.1/Documentation/driver-api/cxl/
Daccess-coordinates.rst8 Shared Upstream Link Calculation
12 the endpoints behind a switch being more than the switch upstream link.
13 A similar situation can occur within the host, upstream of the root ports.
16 upstream link being a limiting factor in mind.
47 Min(SW 0 Upstream Link to RP0 BW,
48 Min(SW0SSLBIS for SW0DSP0 (EP0), EP0 DSLBIS, EP0 Upstream Link) +
49 Min(SW0SSLBIS for SW0DSP1 (EP1), EP1 DSLBIS, EP1 Upstream link)) +
50 Min(SW 1 Upstream Link to RP1 BW,
51 Min(SW1SSLBIS for SW1DSP0 (EP2), EP2 DSLBIS, EP2 Upstream Link) +
52 Min(SW1SSLBIS for SW1DSP1 (EP3), EP3 DSLBIS, EP3 Upstream link))) +
[all …]
/linux-6.12.1/Documentation/process/
Dcontribution-maturity-model.rst19 take on upstream contributions such as reviewing other people’s patches,
24 expectations for upstream community engagement aim to increase the
35 upstream community.
58 * A Software Engineer’s upstream code contributions will be considered
78 * The number of upstream kernel contributions by team or organization
80 * The percentage of kernel developers who have made upstream
84 and/or products, and the publication date of the upstream kernel
92 time focused on Upstream Work, which is defined as reviewing patches,
94 such as writing or maintaining tests, upstream tech debt reduction,
104 * Upstream kernel development is considered a formal job position, with
[all …]
/linux-6.12.1/Documentation/translations/sp_SP/process/
Dcontribution-maturity-model.rst24 upstream, como revisar los parches de otras personas, reestructurar la
29 expectativas comunes para la participación con la comunidad upstream
41 upstream.
63 * Las contribuciones de código upstream de un ingeniero de software se
84 * El número de contribuciones al kernel upstream por equipo u
88 contribuciones upstream relativo al total de desarrolladores
92 upstream en el que se basa el kernel interno.
103 de tecnología upstream, escribir documentación, etc.
112 * El desarrollo del kernel upstream se considera un puesto de trabajo
119 de trabajo upstream a trabajo enfocado en perseguir directamente los
/linux-6.12.1/drivers/net/phy/
Dphy_link_topology.c32 enum phy_upstream upt, void *upstream) in phy_link_topo_add_phy() argument
53 pdn->upstream.netdev = (struct net_device *)upstream; in phy_link_topo_add_phy()
55 pdn->parent_sfp_bus = pdn->upstream.netdev->sfp_bus; in phy_link_topo_add_phy()
58 pdn->upstream.phydev = (struct phy_device *)upstream; in phy_link_topo_add_phy()
60 pdn->parent_sfp_bus = pdn->upstream.phydev->sfp_bus; in phy_link_topo_add_phy()
Dsfp-bus.c28 void *upstream; member
465 ops->link_down(bus->upstream); in sfp_register_bus()
467 ret = ops->connect_phy(bus->upstream, bus->phydev); in sfp_register_bus()
476 bus->upstream_ops->attach(bus->upstream, bus); in sfp_register_bus()
485 bus->upstream_ops->detach(bus->upstream, bus); in sfp_unregister_bus()
490 ops->disconnect_phy(bus->upstream, bus->phydev); in sfp_unregister_bus()
586 bus->upstream = NULL; in sfp_upstream_clear()
625 * - an error from the upstream's connect_phy() method.
657 * @upstream: the upstream private data
658 * @ops: the upstream's &struct sfp_upstream_ops
[all …]
Dmarvell-88x2222.c476 static int mv2222_sfp_insert(void *upstream, const struct sfp_eeprom_id *id) in mv2222_sfp_insert() argument
479 struct phy_device *phydev = upstream; in mv2222_sfp_insert()
519 static void mv2222_sfp_remove(void *upstream) in mv2222_sfp_remove() argument
521 struct phy_device *phydev = upstream; in mv2222_sfp_remove()
531 static void mv2222_sfp_link_up(void *upstream) in mv2222_sfp_link_up() argument
533 struct phy_device *phydev = upstream; in mv2222_sfp_link_up()
540 static void mv2222_sfp_link_down(void *upstream) in mv2222_sfp_link_down() argument
542 struct phy_device *phydev = upstream; in mv2222_sfp_link_down()
/linux-6.12.1/Documentation/maintainer/
Drebasing-and-merging.rst68 newer base or avoiding a merge with an upstream repository is not
102 required before any given branch finds its way into an upstream repository.
127 requests, and upstream maintainers should verify the tags when pulling
135 Merging from sibling or upstream trees
139 trees tend to be a red flag when it comes time to push a branch upstream.
152 you are managing is stable and ready for upstream. Frequent merges can
160 Even then, you should not back merge a tree above your immediate upstream
161 tree; if a higher-level back merge is really required, the upstream tree
165 maintainer merges with the upstream in order to resolve merge conflicts
185 asking upstream to do.
[all …]
/linux-6.12.1/drivers/fsi/
Dfsi-master-hub.c29 * device (the hub->upstream device), and provides access to the downstream FSI
38 struct fsi_device *upstream; member
54 return fsi_slave_read(hub->upstream->slave, addr, val, size); in hub_master_read()
66 return fsi_slave_write(hub->upstream->slave, addr, val, size); in hub_master_write()
94 return fsi_device_write(hub->upstream, FSI_MCENP0 + (4 * idx), in hub_master_link_enable()
97 rc = fsi_device_write(hub->upstream, FSI_MSENP0 + (4 * idx), &reg, 4); in hub_master_link_enable()
126 struct fsi_device *dev = hub->upstream; in hub_master_init()
226 hub->upstream = fsi_dev; in hub_master_probe()
267 fsi_slave_release_range(hub->upstream->slave, hub->addr, hub->size); in hub_master_remove()
/linux-6.12.1/drivers/pci/pcie/
Dptm.c14 * If the next upstream device supports PTM, return it; otherwise return
23 * capability; their PTM behavior is controlled by the Upstream in pci_upstream_ptm()
24 * Port (PCIe r5.0, sec 7.9.16), so if the upstream bridge is a in pci_upstream_ptm()
61 * furthest upstream Time Source as the PTM Root. For Endpoints, in pci_ptm_init()
134 * from a PTM Root that's farther upstream. Every device along the in __pci_enable_ptm()
137 * upstream link partner must have PTM enabled before we can enable in __pci_enable_ptm()
167 * is not a PTM Root and lacks an upstream path of PTM-enabled devices.
Daspm.c114 * on the downstream component before the upstream. So, don't attempt to in pci_restore_aspm_l1ss_state()
148 * by the upstream in pci_restore_aspm_l1ss_state()
195 #define PCIE_LINK_STATE_L0S_UP BIT(0) /* Upstream direction L0s state */
208 struct pci_dev *pdev; /* Upstream component of the Link */
405 /* Check upstream component if bit Slot Clock Configuration is 1 */ in pcie_aspm_configure_common_clock()
438 /* Configure upstream component */ in pcie_aspm_configure_common_clock()
582 /* Check upstream direction L0s latency */ in pcie_aspm_check_latency()
690 /* Program Common_Mode_Restore_Time in upstream device */ in aspm_calc_l12_info()
798 * Re-read upstream/downstream components' register state after in pcie_aspm_cap_init()
910 u32 upstream = 0, dwstream = 0; in pcie_config_aspm_link() local
[all …]
/linux-6.12.1/Documentation/kbuild/
Dgcc-plugins.rst39 compiler features that are neither in GCC nor Clang upstream. Once
40 their utility is proven, the goal is to upstream the feature into GCC
45 upstream compiler support (in either GCC or Clang).
48 bring the feature to upstream GCC (rather than just as a kernel-specific
53 to upstream the feature to GCC (and Clang).
55 After a feature is available in upstream GCC, the plugin will be made
/linux-6.12.1/drivers/cxl/core/
Dcdat.c599 * doing walking the port hierarchy to deal with shared upstream link.
611 * indexed by the upstream device with data of 'struct cxl_perf_ctx'.
617 * an xarray indexed by the upstream device of the switch or the RP
619 * from the endpoint CDAT, the endpoint upstream link bandwidth, and the
620 * bandwidth from the SSLBIS of the switch CDAT for the switch upstream port to
659 * otherwise it's the parent switch upstream device. in cxl_endpoint_gather_bandwidth()
680 /* Direct upstream link from EP bandwidth */ in cxl_endpoint_gather_bandwidth()
686 * Min of upstream link bandwidth and Endpoint CDAT bandwidth from in cxl_endpoint_gather_bandwidth()
713 * of the endpoints with the same switch upstream device or RP. in cxl_endpoint_gather_bandwidth()
738 * @input_xa: xarray indexed by upstream device of a switch with data of 'struct in DEFINE_FREE()
[all …]
/linux-6.12.1/Documentation/PCI/
Dpcieaer-howto.rst145 default reset_link function, but different Upstream Ports might
147 Upstream Port drivers may provide their own reset_link functions.
181 at upstream is not required. The AER driver calls error_detected(dev,
185 Endpoint <==> Downstream Port B <==> Upstream Port A <==> Root Port
187 If Upstream Port A captures an AER error, the hierarchy consists of
196 a hierarchy in question. Then, performing link reset at upstream is
218 What happens if an upstream port service driver does not provide
223 upstream ports who are attached by the service driver.
/linux-6.12.1/Documentation/scsi/
Dlpfc.rst11 toward the upstream kernel. As such, we removed #ifdefs for older kernels
16 and extended attribute support is now part of the upstream kernel
27 history of the driver as we push for upstream acceptance.
67 This source package is targeted for the upstream kernel only. (See notes
/linux-6.12.1/drivers/staging/media/imx/
Dimx-media-utils.c645 * Search upstream/downstream for a subdevice or video device pad in the
656 enum v4l2_buf_type buftype, bool upstream) in imx_media_pipeline_pad() argument
667 if ((upstream && !(spad->flags & MEDIA_PAD_FL_SINK)) || in imx_media_pipeline_pad()
668 (!upstream && !(spad->flags & MEDIA_PAD_FL_SOURCE))) in imx_media_pipeline_pad()
683 buftype, upstream); in imx_media_pipeline_pad()
692 buftype, upstream); in imx_media_pipeline_pad()
703 * Search upstream/downstream for a subdev or video device in the current
708 enum v4l2_buf_type buftype, bool upstream) in find_pipeline_entity() argument
724 pad = imx_media_pipeline_pad(start, grp_id, buftype, upstream); in find_pipeline_entity()
730 * Find a subdev reached upstream from the given start entity in
[all …]
/linux-6.12.1/Documentation/driver-api/acpi/
Dlinuxized-acpica.rst18 upstream.
169 Figure 2. ACPICA -> Linux Upstream Process
198 the ACPICA code in Linux and the upstream ACPICA code, referred to as
210 upstream source code and generate the linuxized fix using the ACPICA
215 Those changes may not be acceptable by ACPICA upstream and in such cases
223 fixups are backported to the upstream ACPICA sources, they must follow
224 the upstream ACPICA rules and so further modifications may appear.
235 This paragraph guides Linux developers to use the ACPICA upstream release
236 utilities to obtain Linux patches corresponding to upstream ACPICA commits
273 If you have local copies of both Linux and upstream ACPICA, you can generate
/linux-6.12.1/include/linux/
Dphy_link_topology.h32 } upstream; member
42 enum phy_upstream upt, void *upstream);
65 enum phy_upstream upt, void *upstream) in phy_link_topo_add_phy() argument
/linux-6.12.1/tools/perf/pmu-events/arch/x86/amdzen4/
Ddata-fabric.json388 …"PublicDescription": "Read data beats (64 bytes) for local socket upstream DMA at IO Moderator (IO…
396 …"PublicDescription": "Read data beats (64 bytes) for local socket upstream DMA at IO Moderator (IO…
404 …"PublicDescription": "Read data beats (64 bytes) for local socket upstream DMA at IO Moderator (IO…
412 …"PublicDescription": "Read data beats (64 bytes) for local socket upstream DMA at IO Moderator (IO…
420 …"PublicDescription": "Write data beats (64 bytes) for local socket upstream DMA at IO Moderator (I…
428 …"PublicDescription": "Write data beats (64 bytes) for local socket upstream DMA at IO Moderator (I…
436 …"PublicDescription": "Write data beats (64 bytes) for local socket upstream DMA at IO Moderator (I…
444 …"PublicDescription": "Write data beats (64 bytes) for local socket upstream DMA at IO Moderator (I…
452 …"PublicDescription": "Read data beats (64 bytes) for remote socket upstream DMA at IO Moderator (I…
460 …"PublicDescription": "Read data beats (64 bytes) for remote socket upstream DMA at IO Moderator (I…
[all …]
/linux-6.12.1/drivers/media/pci/cx25821/
Dcx25821.h254 /* Analog Audio Upstream */
284 /* Video Upstream */
305 #define SRAM_CH09 9 /* Video Upstream I */
306 #define SRAM_CH10 10 /* Video Upstream J */
307 #define SRAM_CH11 11 /* Audio Upstream AUD_CHANNEL_B */
336 /* For Upstream Video */
/linux-6.12.1/drivers/net/fddi/skfp/
Decm.c444 /* trace propagate upstream */ in prop_actions()
450 /* trace propagate upstream */ in prop_actions()
468 int upstream ; in prop_actions() local
490 upstream = cem_get_upstream(smc,initiator) ; in prop_actions()
492 if (upstream == ENTITY_MAC) { in prop_actions()
498 /* trace propagate upstream */ in prop_actions()
499 DB_ECM("ECM : propagate TRACE on PHY %d", upstream); in prop_actions()
500 queue_event(smc,EVENT_PCM+upstream,PC_TRACE) ; in prop_actions()
/linux-6.12.1/scripts/dtc/
Dupdate-dtc-source.sh43 git log --oneline scripts/dtc/ | grep 'upstream' | head -1 | sed -e 's/^.* \(.*\)/\1/'
72 scripts/dtc: Update to upstream version ${dtc_version}
74 This adds the following commits from upstream:
/linux-6.12.1/Documentation/devicetree/bindings/sound/
Dmrvl,pxa-ssp.txt6 port A phandle reference to a PXA ssp upstream device
18 /* upstream device */
/linux-6.12.1/Documentation/devicetree/bindings/i2c/
Di2c-mux-pca954x.yaml77 isolated from the upstream bus. If not set all channels are isolated from
78 the upstream bus until the fault is cleared.
89 channel is isolated from the upstream bus.
/linux-6.12.1/Documentation/gpu/rfc/
Di915_gem_lmem.rst5 Upstream plan
7 For upstream the overall plan for landing all the DG1 stuff and turning it for
/linux-6.12.1/drivers/infiniband/hw/hfi1/
Daspm.c29 * If the driver does not have access to the upstream component, in aspm_hw_l1_supported()
62 * If the driver does not have access to the upstream component, in aspm_hw_enable_l1()
68 /* Enable ASPM L1 first in upstream component and then downstream */ in aspm_hw_enable_l1()
81 /* Disable ASPM L1 first in downstream component and then upstream */ in aspm_hw_disable_l1()

12345678910>>...17