| /Linux-v6.1/drivers/iio/common/cros_ec_sensors/ |
| D | cros_ec_sensors_core.c | 250 int frequencies[ARRAY_SIZE(state->frequencies) / 2] = { 0 }; in cros_ec_sensors_core_init() local
308 &frequencies[1], in cros_ec_sensors_core_init()
309 &frequencies[2], in cros_ec_sensors_core_init()
314 &frequencies[1], in cros_ec_sensors_core_init()
315 &frequencies[2], in cros_ec_sensors_core_init()
318 frequencies[1] = state->resp->info_3.min_frequency; in cros_ec_sensors_core_init()
319 frequencies[2] = state->resp->info_3.max_frequency; in cros_ec_sensors_core_init()
323 for (i = 0; i < ARRAY_SIZE(frequencies); i++) { in cros_ec_sensors_core_init()
324 state->frequencies[2 * i] = frequencies[i] / 1000; in cros_ec_sensors_core_init()
325 state->frequencies[2 * i + 1] = in cros_ec_sensors_core_init()
[all …]
|
| /Linux-v6.1/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-v6.1/Documentation/devicetree/bindings/media/i2c/ |
| 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 | 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>;
|
| /Linux-v6.1/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-v6.1/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.
121 operating frequencies and voltages with OPP support.
|
| /Linux-v6.1/Documentation/ABI/testing/ |
| D | sysfs-class-devfreq | 48 driver should provide the list of available frequencies
60 the available frequencies of the corresponding devfreq object.
61 This is a snapshot of available frequencies and not limited
|
| /Linux-v6.1/arch/arm64/boot/dts/qcom/ |
| D | sdm636.dtsi | 13 * different CPU frequencies, Adreno
|
| D | msm8996-v3.0.dtsi | 14 * parameters, GPU frequencies and some differences
|
| /Linux-v6.1/Documentation/cpu-freq/ |
| D | cpu-drivers.rst | 84 .boost_enabled - If set, boost frequencies are enabled.
87 frequencies.
111 | | switch between two frequencies in |
242 frequencies, a "frequency table" with some functions might assist in
271 excluding CPUFREQ_ENTRY_INVALID frequencies.
|
| D | core.rst | 60 frequencies (in kHz) of the new policy).
89 the OPP layer's internal information about the available frequencies
|
| /Linux-v6.1/Documentation/devicetree/bindings/cpufreq/ |
| D | cpufreq-spear.txt | 9 - cpufreq_tbl: Table of frequencies CPU could be transitioned into, in the
|
| /Linux-v6.1/arch/arm/boot/dts/ |
| D | exynos4412-prime.dtsi | 10 * Exynos4412 Prime SoC revision supports higher CPU frequencies than
|
| D | mstar-infinity3.dtsi | 16 // overclock frequencies below, shown to work fine up to 1.3 GHz
|
| /Linux-v6.1/Documentation/driver-api/media/drivers/ |
| D | radiotrack.rst | 44 available through a miniature phone plug. Its RF frequencies of operation are
46 band). Although the registers can be programmed to request frequencies beyond
49 signal probably has a small range of useful frequencies, and wraps around or
|
| 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-v6.1/Documentation/mm/damon/ |
| D | design.rst | 133 that assumed to have the same access frequencies into a region. As long as the
134 assumption (pages in a region have the same access frequencies) is kept, only
150 fulfill the assumption (pages in same region have similar access frequencies),
155 For each ``aggregation interval``, it compares the access frequencies of
|
| /Linux-v6.1/include/linux/iio/common/ |
| D | cros_ec_sensors_core.h | 84 int frequencies[6]; member
|
| /Linux-v6.1/Documentation/devicetree/bindings/clock/ |
| D | armada3700-xtal-clock.txt | 3 Marvell Armada 37xx SoCs allow to determine the xtal clock frequencies by
|
| /Linux-v6.1/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-v6.1/arch/arm64/boot/dts/renesas/ |
| D | hihope-rzg2-ex-aistarvision-mipi-adapter-2.1.dtsi | 51 link-frequencies = /bits/ 64 <456000000>;
|
| /Linux-v6.1/arch/arm64/boot/dts/freescale/ |
| D | imx8mm-venice-gw72xx-0x-imx219.dts | 55 link-frequencies = /bits/ 64 <456000000>;
|
| D | imx8mm-venice-gw73xx-0x-imx219.dts | 55 link-frequencies = /bits/ 64 <456000000>;
|
