Home
last modified time | relevance | path

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

1234567891011

/linux/Documentation/driver-api/cxl/linux/
H A Daccess-coordinates.rst36 for traversing the switch between the switch upstream port and the switch
85 Shared Upstream Link Calculation
89 the endpoints behind a switch being more than the switch upstream link.
90 A similar situation can occur within the host, upstream of the root ports.
93 upstream link being a limiting factor in mind.
124 Min(SW 0 Upstream Link to RP0 BW,
125 Min(SW0SSLBIS for SW0DSP0 (EP0), EP0 DSLBIS, EP0 Upstream Link) +
126 Min(SW0SSLBIS for SW0DSP1 (EP1), EP1 DSLBIS, EP1 Upstream link)) +
127 Min(SW 1 Upstream Link to RP1 BW,
128 Min(SW1SSLBIS for SW1DSP0 (EP2), EP2 DSLBIS, EP2 Upstream Link) +
[all …]
/linux/Documentation/process/
H A 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 …]
H A Dstable-kernel-rules.rst9 - It or an equivalent fix must already exist in Linux mainline (upstream).
155 to. When doing so, you must note the upstream commit ID in the changelog of your
158 commit <sha1> upstream.
162 [ Upstream commit <sha1> ]
164 If the submitted patch deviates from the original upstream patch (for example
/linux/Documentation/translations/pt_BR/process/
H A Dcontribution-maturity-model.rst19 incentivados a assumir contribuições no upstream, como revisar os patches de
24 Linux. Essas expectativas comuns para o engajamento da comunidade upstream visam
34 comunidade upstream.
57 * As contribuições de código no upstream de um Engenheiro de Software serão
77 * O número de contribuições ao kernel no upstream por equipe ou organização
81 upstream em relação ao total de desenvolvedores de kernel na organização.
83 da organização e a data de publicação do kernel upstream no qual o kernel
92 de trabalho focados no Trabalho no Upstream, o qual é definido como a revisão
95 no upstream, escrita de documentação, etc.
104 * O desenvolvimento de kernel no upstream é considerado um cargo formal, com
[all …]
/linux/Documentation/translations/sp_SP/process/
H A 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/Documentation/maintainer/
H A 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 …]
H A Dmessy-diffstat.rst8 process of sending work upstream. Normally, the result includes a nice
73 upstream is a well-known way to get a grumpy response.
96 shows what is really going on. That request can then be sent upstream.
/linux/drivers/net/phy/
H A Dsfp-bus.c27 void *upstream; member
448 ops->link_down(bus->upstream); in sfp_register_bus()
450 ret = ops->connect_phy(bus->upstream, bus->phydev); in sfp_register_bus()
459 bus->upstream_ops->attach(bus->upstream, bus); in sfp_register_bus()
468 bus->upstream_ops->detach(bus->upstream, bus); in sfp_unregister_bus()
473 ops->disconnect_phy(bus->upstream, bus->phydev); in sfp_unregister_bus()
569 bus->upstream = NULL; in sfp_upstream_clear()
608 * - an error from the upstream's connect_phy() method.
640 * @upstream: the upstream private data
641 * @ops: the upstream's &struct sfp_upstream_ops
[all …]
/linux/drivers/fsi/
H A 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/Documentation/kbuild/
H A 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/drivers/cxl/core/
H A Dcdat.c603 * doing walking the port hierarchy to deal with shared upstream link.
615 * indexed by the upstream device with data of 'struct cxl_perf_ctx'.
621 * an xarray indexed by the upstream device of the switch or the RP
623 * from the endpoint CDAT, the endpoint upstream link bandwidth, and the
624 * bandwidth from the SSLBIS of the switch CDAT for the switch upstream port to
662 * otherwise it's the parent switch upstream device. in cxl_endpoint_gather_bandwidth()
683 /* Direct upstream link from EP bandwidth */ in cxl_endpoint_gather_bandwidth()
689 * Min of upstream link bandwidth and Endpoint CDAT bandwidth from in cxl_endpoint_gather_bandwidth()
716 * of the endpoints with the same switch upstream device or RP. in cxl_endpoint_gather_bandwidth()
741 * @input_xa: xarray indexed by upstream device of a switch with data of 'struct in DEFINE_FREE()
[all …]
/linux/Documentation/scsi/
H A 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/Documentation/driver-api/acpi/
H A 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/tools/perf/pmu-events/arch/x86/amdzen4/
H A 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/drivers/media/pci/cx25821/
H A 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/drivers/net/fddi/skfp/
H A 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/scripts/dtc/
H A 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/Documentation/devicetree/bindings/sound/
H A Dmrvl,pxa-ssp.txt6 port A phandle reference to a PXA ssp upstream device
18 /* upstream device */
/linux/Documentation/filesystems/nfs/
H A Dnfsd-maintainer-entry-profile.rst41 Bug reports against upstream Linux code bases are welcome on the
66 fests). Non-Linux NFS clients are not part of upstream NFSD CI/CD.
359 When the upstream merge window closes, the nfsd-next branch is
361 the upstream -rc1 tag.
363 Fixes that are destined for an upstream -rc release also run the
368 that occurred during the most recent upstream merge.
446 Upstream NFSD continuous integration testing runs against LTS trees
519 - **Upstream Release Manager** : This role is responsible for
531 upstream, that's usually whether contributions violate licensing
/linux/Documentation/devicetree/bindings/i2c/
H A 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.
H A Di2c-atr.yaml14 ("upstream") port and N I2C master child ("downstream") ports, and
15 forwards transactions from upstream to the appropriate downstream port
H A Di2c-mux-ltc4306.txt26 - ltc,upstream-accelerators-enable: Enables the rise time accelerators
27 on the upstream port.
/linux/drivers/pci/pcie/
H A Dptm.c15 * If the next upstream device supports PTM, return it; otherwise return
24 * capability; their PTM behavior is controlled by the Upstream in pci_upstream_ptm()
25 * Port (PCIe r5.0, sec 7.9.16), so if the upstream bridge is a in pci_upstream_ptm()
63 * furthest upstream Time Source as the PTM Root. For Endpoints, in pci_ptm_init()
170 * is not a PTM Root and lacks an upstream path of PTM-enabled devices.
179 * from a PTM Root that's farther upstream. Every device along in pci_enable_ptm()
182 * Root, the upstream link partner must have PTM enabled before in pci_enable_ptm()
/linux/Documentation/gpu/rfc/
H A Di915_gem_lmem.rst5 Upstream plan
7 For upstream the overall plan for landing all the DG1 stuff and turning it for
/linux/Documentation/networking/
H A Dphy-link-topology.rst48 its SFP upstream ops.
90 upstream is phylink (so, no media-converter).
92 PHY drivers that can be used as SFP upstream need to call :c:func:`phy_sfp_attach_phy`

1234567891011