| /Linux-v5.10/Documentation/devicetree/bindings/sound/ |
| D | cs43130.txt | 40 Define the frequencies at which to measure HP AC impedance.
42 Exactly 10 frequencies must be defined.
44 following frequencies are used:
46 The above frequencies are logarithmically equally spaced.
|
| /Linux-v5.10/drivers/devfreq/ |
| D | Kconfig | 7 A device may have a list of frequencies and voltages available.
17 However, because the clock frequencies of a single device are
91 and adjusts the operating frequencies and voltages with OPP support.
122 operating frequencies and voltages with OPP support.
132 frequencies and voltages with OPP support.
|
| /Linux-v5.10/Documentation/devicetree/bindings/media/i2c/ |
| D | imx219.yaml | 69 link-frequencies:
72 Allowed data bus frequencies.
75 - link-frequencies
107 link-frequencies = /bits/ 64 <456000000>;
|
| D | ov8856.yaml | 81 link-frequencies:
84 Allowed data bus frequencies. 360000000, 180000000 Hz or both
89 - link-frequencies
136 link-frequencies = /bits/ 64 <360000000>;
|
| D | mt9v032.txt | 21 - link-frequencies: List of allowed link frequencies in Hz. Each frequency is
37 link-frequencies = /bits/ 64
|
| D | tc358743.txt | 21 - link-frequencies: List of allowed link frequencies in Hz. Each frequency is
45 link-frequencies = /bits/ 64 <297000000>;
|
| D | nokia,smia.txt | 23 - link-frequencies: List of allowed data link frequencies. An array of
58 link-frequencies = /bits/ 64 <199200000 210000000 499200000>;
|
| D | ov2659.txt | 13 - link-frequencies: target pixel clock frequency.
42 link-frequencies = /bits/ 64 <70000000>;
|
| D | imx290.txt | 28 - link-frequencies: check ../video-interfaces.txt
53 link-frequencies = /bits/ 64 <445500000>;
|
| D | sony,imx214.txt | 31 - link-frequencies: check ../video-interfaces.txt
49 link-frequencies = /bits/ 64 <480000000>;
|
| /Linux-v5.10/drivers/iio/common/cros_ec_sensors/ |
| D | cros_ec_sensors_core.c | 260 int frequencies[ARRAY_SIZE(state->frequencies) / 2] = { 0 }; in cros_ec_sensors_core_init() local
310 &frequencies[1], in cros_ec_sensors_core_init()
311 &frequencies[2], in cros_ec_sensors_core_init()
316 &frequencies[1], in cros_ec_sensors_core_init()
317 &frequencies[2], in cros_ec_sensors_core_init()
320 frequencies[1] = state->resp->info_3.min_frequency; in cros_ec_sensors_core_init()
321 frequencies[2] = state->resp->info_3.max_frequency; in cros_ec_sensors_core_init()
325 for (i = 0; i < ARRAY_SIZE(frequencies); i++) { in cros_ec_sensors_core_init()
326 state->frequencies[2 * i] = frequencies[i] / 1000; in cros_ec_sensors_core_init()
327 state->frequencies[2 * i + 1] = in cros_ec_sensors_core_init()
[all …]
|
| /Linux-v5.10/Documentation/ABI/testing/ |
| D | sysfs-bus-iio-frequency-adf4371 | 12 frequencies from 62500000 Hz to 8000000000 Hz.
16 A frequency doubler generates frequencies from
19 A frequency quadrupler generates frequencies from
|
| D | sysfs-class-devfreq | 62 driver should provide the list of available frequencies
82 the available frequencies of the corresponding devfreq object.
83 This is a snapshot of available frequencies and not limited
|
| /Linux-v5.10/drivers/media/test-drivers/vidtv/ |
| D | vidtv_tuner.h | 24 * @vidtv_valid_dvb_t_freqs: The valid DVB-T frequencies to simulate.
25 * @vidtv_valid_dvb_c_freqs: The valid DVB-C frequencies to simulate.
26 * @vidtv_valid_dvb_s_freqs: The valid DVB-S frequencies to simulate.
|
| D | vidtv_bridge.c | 69 "Valid DVB-T frequencies to simulate, in Hz");
77 "Valid DVB-C frequencies to simulate, in Hz");
84 "Valid DVB-S/S2 frequencies to simulate at Ku-Band, in kHz");
370 /* TODO: check if the frequencies are at a valid range */ in vidtv_bridge_probe_tuner()
381 * Convert Satellite frequencies from Ku-band in kHZ into S-band in vidtv_bridge_probe_tuner()
382 * frequencies in Hz. in vidtv_bridge_probe_tuner()
|
| /Linux-v5.10/Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-fm-tx.rst | 93 If set, then transmit alternate frequencies.
96 The alternate frequencies in kHz units. The RDS standard allows for
97 up to 25 frequencies to be defined. Drivers may support fewer
98 frequencies so check the array size.
152 frequencies. Depending on the region, a time constant of either 50
|
| /Linux-v5.10/arch/x86/kernel/ |
| D | tsc_msr.c | 54 * Some CPU frequencies in the SDM do not map to known PLL freqs, in
79 * Bay Trail SDM MSR_FSB_FREQ frequencies simplified PLL model:
94 * Cherry Trail SDM MSR_FSB_FREQ frequencies simplified PLL model:
114 * Merriefield SDM MSR_FSB_FREQ frequencies simplified PLL model:
125 * Moorefield SDM MSR_FSB_FREQ frequencies simplified PLL model:
|
| /Linux-v5.10/tools/testing/selftests/cpufreq/ |
| D | cpufreq.sh | 118 # CHANGE CPU FREQUENCIES
150 printf "Available frequencies for $1: $freqs\n\n"
152 # Set all frequencies one-by-one
197 # Test all frequencies
|
| /Linux-v5.10/include/linux/iio/common/ |
| D | cros_ec_sensors_core.h | 58 * @frequencies: Table of known available frequencies:
86 int frequencies[6]; member
|
| /Linux-v5.10/Documentation/devicetree/bindings/usb/ |
| D | usb3503.txt | 21 reference clock frequencies table is used). Use clocks and
26 clock frequencies table is used)
|
| /Linux-v5.10/Documentation/admin-guide/ |
| D | rtc.rst | 72 At high frequencies, or under high loads, the user process should check
77 frequencies above 1024Hz. So you really should check the high bytes
78 of the value you read, especially at frequencies above that of the
81 Programming and/or enabling interrupt frequencies greater than 64Hz is
|
| /Linux-v5.10/Documentation/driver-api/media/drivers/ |
| D | vidtv.rst | 19 frequency is too far away from a table of valid frequencies for a
65 By default, it will accept the following frequencies:
71 LNBf, with frequencies at Ku-Band, ranging from 10.7 GHz to 12.75 GHz.
97 Valid DVB-T frequencies to simulate, in Hz.
100 Valid DVB-C frequencies to simulate, in Hz.
103 Valid DVB-S/S2 frequencies to simulate at Ku-Band, in kHz.
475 is too far away from a table of valid frequencies. For now, this means that
|
| /Linux-v5.10/drivers/cpufreq/ |
| D | pmac32-cpufreq.c | 50 * Currently, PowerMac cpufreq supports only high & low frequencies
475 * on the bus frequencies in pmac_cpufreq_init_MacRISC3()
481 freqs = of_get_property(cpunode, "bus-frequencies", &lenp); in pmac_cpufreq_init_MacRISC3()
484 pr_err("bus-frequencies incorrect or missing\n"); in pmac_cpufreq_init_MacRISC3()
494 /* Get the min/max bus frequencies */ in pmac_cpufreq_init_MacRISC3()
510 /* Now we get the frequencies, we read the GPIO to see what is out current in pmac_cpufreq_init_MacRISC3()
520 /* If we use the PMU, look for the min & max frequencies in the in pmac_cpufreq_init_MacRISC3()
|
| /Linux-v5.10/Documentation/driver-api/media/ |
| D | camera-sensor.rst | 18 firmware. No other frequencies should be used in any circumstances.
20 The reason why the clock frequencies are so important is that the clock signals
23 elsewhere. Therefore only the pre-determined frequencies are configurable by the
|
| /Linux-v5.10/Documentation/cpu-freq/ |
| D | cpu-drivers.rst | 90 .boost_enabled - If set, boost frequencies are enabled.
93 frequencies.
117 | | switch between two frequencies in |
248 frequencies, a "frequency table" with some functions might assist in
277 excluding CPUFREQ_ENTRY_INVALID frequencies.
|
