| /kernel/linux/linux-6.6/Documentation/process/ |
| D | contribution-maturity-model.rst | 19 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 …]
|
| /kernel/linux/linux-6.6/rust/alloc/ |
| D | README.md | 9 upstream. In general, only additions should be performed (e.g. new
10 methods). Eventually, changes should make it into upstream so that,
13 The Rust upstream version on top of which these files are based matches
24 upstream as possible and avoid as much divergence as possible, which
28 in-tree that would be as small and as close as possible to upstream.
29 Then, upstream can start adding the functions that we add to `alloc`
32 upstream, so that we can drop `alloc` from the kernel tree and go back
33 to using the upstream one.
|
| /kernel/linux/linux-6.6/Documentation/translations/sp_SP/process/ |
| D | contribution-maturity-model.rst | 24 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
|
| /kernel/linux/linux-5.10/drivers/net/phy/ |
| D | sfp-bus.c | 34 void *upstream; member
483 ops->link_down(bus->upstream); in sfp_register_bus()
485 ret = ops->connect_phy(bus->upstream, bus->phydev); in sfp_register_bus()
494 bus->upstream_ops->attach(bus->upstream, bus); in sfp_register_bus()
503 bus->upstream_ops->detach(bus->upstream, bus); in sfp_unregister_bus()
508 ops->disconnect_phy(bus->upstream); in sfp_unregister_bus()
584 bus->upstream = NULL; in sfp_upstream_clear()
603 * - an error from the upstream's connect_phy() method.
635 * @upstream: the upstream private data
636 * @ops: the upstream's &struct sfp_upstream_ops
[all …]
|
| /kernel/linux/linux-6.6/Documentation/maintainer/ |
| D | rebasing-and-merging.rst | 68 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 …]
|
| /kernel/linux/linux-6.6/drivers/net/phy/ |
| D | sfp-bus.c | 28 void *upstream; member
464 ops->link_down(bus->upstream); in sfp_register_bus()
466 ret = ops->connect_phy(bus->upstream, bus->phydev); in sfp_register_bus()
475 bus->upstream_ops->attach(bus->upstream, bus); in sfp_register_bus()
484 bus->upstream_ops->detach(bus->upstream, bus); in sfp_unregister_bus()
489 ops->disconnect_phy(bus->upstream); in sfp_unregister_bus()
585 bus->upstream = NULL; in sfp_upstream_clear()
624 * - an error from the upstream's connect_phy() method.
656 * @upstream: the upstream private data
657 * @ops: the upstream's &struct sfp_upstream_ops
[all …]
|
| D | marvell-88x2222.c | 478 static int mv2222_sfp_insert(void *upstream, const struct sfp_eeprom_id *id) in mv2222_sfp_insert() argument
481 struct phy_device *phydev = upstream; in mv2222_sfp_insert()
521 static void mv2222_sfp_remove(void *upstream) in mv2222_sfp_remove() argument
523 struct phy_device *phydev = upstream; in mv2222_sfp_remove()
533 static void mv2222_sfp_link_up(void *upstream) in mv2222_sfp_link_up() argument
535 struct phy_device *phydev = upstream; in mv2222_sfp_link_up()
542 static void mv2222_sfp_link_down(void *upstream) in mv2222_sfp_link_down() argument
544 struct phy_device *phydev = upstream; in mv2222_sfp_link_down()
|
| /kernel/linux/linux-5.10/Documentation/maintainer/ |
| D | rebasing-and-merging.rst | 68 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 …]
|
| /kernel/linux/linux-5.10/drivers/fsi/ |
| D | fsi-master-hub.c | 29 * 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), ®, 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()
|
| /kernel/linux/linux-6.6/drivers/fsi/ |
| D | fsi-master-hub.c | 29 * 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), ®, 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()
|
| /kernel/linux/linux-6.6/drivers/pci/pcie/ |
| D | ptm.c | 13 * If the next upstream device supports PTM, return it; otherwise return
22 * capability; their PTM behavior is controlled by the Upstream in pci_upstream_ptm()
23 * Port (PCIe r5.0, sec 7.9.16), so if the upstream bridge is a in pci_upstream_ptm()
60 * furthest upstream Time Source as the PTM Root. For Endpoints, in pci_ptm_init()
133 * from a PTM Root that's farther upstream. Every device along the in __pci_enable_ptm()
136 * upstream link partner must have PTM enabled before we can enable in __pci_enable_ptm()
166 * is not a PTM Root and lacks an upstream path of PTM-enabled devices.
|
| D | aspm.c | 30 #define ASPM_STATE_L0S_UP (1) /* Upstream direction L0s state */
46 struct pci_dev *pdev; /* Upstream component of the Link */
217 /* Check upstream component if bit Slot Clock Configuration is 1 */ in pcie_aspm_configure_common_clock()
250 /* Configure upstream component */ in pcie_aspm_configure_common_clock()
394 /* Check upstream direction L0s latency */ in pcie_aspm_check_latency()
507 /* Program Common_Mode_Restore_Time in upstream device */ in aspm_calc_l12_info()
611 * Re-read upstream/downstream components' register state after in pcie_aspm_cap_init()
723 u32 upstream = 0, dwstream = 0; in pcie_config_aspm_link() local
743 /* Convert ASPM state to upstream/downstream ASPM register state */ in pcie_config_aspm_link()
747 upstream |= PCI_EXP_LNKCTL_ASPM_L0S; in pcie_config_aspm_link()
[all …]
|
| /kernel/linux/linux-6.6/Documentation/kbuild/ |
| D | gcc-plugins.rst | 39 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
|
| /kernel/linux/linux-5.10/drivers/pci/pcie/ |
| D | ptm.c | 53 * capability; their PTM behavior is controlled by the Upstream in pci_ptm_init()
73 * upstream device or this device can be a PTM Root itself. Per in pci_ptm_init()
75 * furthest upstream Time Source as the PTM Root. in pci_ptm_init()
118 * issue PTM requests to upstream devices that have PTM enabled. in pci_enable_ptm()
120 * For Root Complex Integrated Endpoints, there is no upstream in pci_enable_ptm()
|
| D | aspm.c | 29 #define ASPM_STATE_L0S_UP (1) /* Upstream direction L0s state */
50 struct pci_dev *pdev; /* Upstream component of the Link */
70 struct aspm_latency latency_up; /* Upstream direction exit latency */
267 /* Check upstream component if bit Slot Clock Configuration is 1 */ in pcie_aspm_configure_common_clock()
300 /* Configure upstream component */ in pcie_aspm_configure_common_clock()
409 /* Check upstream direction L0s latency */ in pcie_aspm_check_latency()
538 /* Program Common_Mode_Restore_Time in upstream device */ in aspm_calc_l1ss_info()
587 * Re-read upstream/downstream components' register state after in pcie_aspm_cap_init()
760 u32 upstream = 0, dwstream = 0; in pcie_config_aspm_link() local
780 /* Convert ASPM state to upstream/downstream ASPM register state */ in pcie_config_aspm_link()
[all …]
|
| /kernel/linux/linux-5.10/drivers/net/ethernet/neterion/vxge/ |
| D | vxge-traffic.h | 1211 * the posted header credits for upstream PCI writes were depleted
1213 * the posted header credits for upstream PCI writes were depleted
1215 * the posted header credits for upstream PCI writes were depleted
1217 * the posted header credits for upstream PCI writes were depleted
1219 * the posted header credits for upstream PCI writes were depleted
1221 * the posted header credits for upstream PCI writes were depleted
1223 * the posted header credits for upstream PCI writes were depleted
1225 * the posted header credits for upstream PCI writes were depleted
1227 * the posted header credits for upstream PCI writes were depleted
1229 * the posted header credits for upstream PCI writes were depleted
[all …]
|
| /kernel/linux/linux-5.10/drivers/staging/media/imx/ |
| D | imx-media-utils.c | 696 * Search upstream/downstream for a subdevice or video device pad in the
707 enum v4l2_buf_type buftype, bool upstream) in imx_media_pipeline_pad() argument
718 if ((upstream && !(spad->flags & MEDIA_PAD_FL_SINK)) || in imx_media_pipeline_pad()
719 (!upstream && !(spad->flags & MEDIA_PAD_FL_SOURCE))) in imx_media_pipeline_pad()
734 buftype, upstream); in imx_media_pipeline_pad()
743 buftype, upstream); in imx_media_pipeline_pad()
754 * Search upstream/downstream for a subdev or video device in the current
759 enum v4l2_buf_type buftype, bool upstream) in find_pipeline_entity() argument
775 pad = imx_media_pipeline_pad(start, grp_id, buftype, upstream); in find_pipeline_entity()
781 * Find the upstream mipi-csi2 virtual channel reached from the given
[all …]
|
| /kernel/linux/linux-6.6/Documentation/PCI/ |
| D | pcieaer-howto.rst | 145 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.
|
| /kernel/linux/linux-5.10/Documentation/scsi/ |
| D | lpfc.rst | 11 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
|
| /kernel/linux/linux-6.6/Documentation/scsi/ |
| D | lpfc.rst | 11 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
|
| /kernel/linux/linux-6.6/drivers/staging/media/imx/ |
| D | imx-media-utils.c | 645 * 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 …]
|
| /kernel/linux/linux-6.6/Documentation/driver-api/acpi/ |
| D | linuxized-acpica.rst | 18 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
|
| /kernel/linux/linux-5.10/Documentation/driver-api/acpi/ |
| D | linuxized-acpica.rst | 18 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
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/amdzen4/ |
| D | data-fabric.json | 388 …"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 …]
|
| /kernel/linux/linux-5.10/Documentation/PCI/ |
| D | pcieaer-howto.rst | 155 default reset_link function, but different upstream ports might
157 upstream ports should provide their own reset_link functions.
191 at upstream is not required. The AER driver calls error_detected(dev,
197 If Upstream port A captures an AER error, the hierarchy consists of
206 a hierarchy in question. Then, performing link reset at upstream is
253 What happens if an upstream port service driver does not provide
258 upstream ports who are attached by the service driver.
|