Home
last modified time | relevance | path

Searched full:bandwidths (Results 1 – 25 of 36) sorted by relevance

12

/linux/Documentation/driver-api/cxl/
H A Daccess-coordinates.rst15 arrived for a region in order to recalculate the bandwidths with possible
62 is created to collect all the endpoint bandwidths via the
81 this point all the bandwidths are aggregated per each host bridge, which is
85 bandwidth from the Generic Port (GP). The bandwidths for the GP is retrieved
/linux/drivers/gpu/drm/tegra/
H A Dplane.h60 /* bandwidths are in ICC units, i.e. kbytes/sec */
H A Ddc.c2016 * bandwidths from the ICC paths. in tegra_crtc_update_memory_bandwidth()
2050 * which explains why bandwidths need to be updated when in tegra_crtc_update_memory_bandwidth()
2409 * the same time, hence bandwidths are accumulated in this case. in tegra_crtc_calculate_memory_bandwidth()
/linux/drivers/gpu/drm/armada/
H A Darmada_510.c65 * Lower the watermark so to eliminate jitter at higher bandwidths. in armada510_crtc_init()
/linux/Documentation/mm/
H A Dnuma.rst34 bandwidths than accesses to memory on other, remote cells. NUMA platforms
/linux/drivers/net/ipa/
H A Dipa_data.h196 * struct ipa_interconnect_data - description of IPA interconnect bandwidths
/linux/drivers/gpu/drm/amd/display/dc/dml2/dml21/src/dml2_mcg/
H A Ddml2_mcg_dcn4.c61 // First calculate the table for "balanced" bandwidths across UCLK/FCLK in build_min_clk_table_fine_grained()
/linux/Documentation/scheduler/
H A Dsched-deadline.rst198 For each runqueue, the algorithm GRUB keeps track of two different bandwidths:
200 - Active bandwidth (running_bw): this is the sum of the bandwidths of all
602 can be created while the sum of their bandwidths stays below:
/linux/drivers/net/ipa/data/
H A Dipa_data-v3.5.1.c381 /* Interconnect bandwidths are in 1000 byte/second units */
H A Dipa_data-v3.1.c500 /* Interconnect bandwidths are in 1000 byte/second units */
/linux/include/linux/
H A Dresctrl.h162 * different memory bandwidths
/linux/Documentation/core-api/
H A Dworkqueue.rst470 are the read bandwidths and CPU utilizations depending on different affinity
471 scope settings on ``kcryptd`` measured over five runs. Bandwidths are in
/linux/drivers/media/dvb-frontends/
H A Dl64781.c456 value of 2 with all possible bandwidths and guard in l64781_init()
/linux/net/wireless/
H A Dpmsr.c20 if (!(rdev->wiphy.pmsr_capa->ftm.bandwidths & BIT(out->chandef.width))) { in pmsr_parse_ftm()
H A Dcore.c782 !wiphy->pmsr_capa->ftm.bandwidths)) in wiphy_register()
796 if (WARN_ON(wiphy->pmsr_capa->ftm.bandwidths & in wiphy_register()
/linux/Documentation/admin-guide/sysctl/
H A Dnet.rst174 which require setting up classes and bandwidths. Note that physical multiqueue
/linux/drivers/net/wireless/intel/iwlwifi/fw/api/
H A Drs.h14 * bandwidths <= 80MHz
/linux/include/media/
H A Ddvb_frontend.h78 * struct dvb_tuner_info - Frontend name and min/max ranges/bandwidths
/linux/drivers/net/ethernet/intel/ice/
H A Dice_type.h952 /* Device max aggregate bandwidths corresponding to the GL_PWR_MODE_CTL
/linux/drivers/net/wireless/ath/ath10k/
H A Drx_desc.h832 * bandwidths. Value of 0x80 indicates invalid.
/linux/drivers/net/wireless/intel/iwlwifi/mvm/
H A Dmld-mac80211.c747 /* Exit EMLSR if links don't have equal bandwidths */ in iwl_mvm_esr_bw_criteria()
H A Dmvm.h372 * @IWL_MVM_ESR_EXIT_BANDWIDTH: Bandwidths of primary and secondry links
/linux/net/ipv4/
H A Dtcp_bbr.c70 * This handles bandwidths from 0.06pps (715bps) to 256Mpps (3Tbps) in a u32.
/linux/drivers/staging/media/av7110/
H A Dav7110.c2293 * dvbtraffic should give this stable bandwidths:
2297 * (stable bandwidths and almost no packet loss)
/linux/net/sched/
H A Dsch_cake.c37 * setting, as is necessary at low bandwidths.

12