/linux/net/openvswitch/ |
H A D | Kconfig | 28 which are often characterized by highly dynamic endpoints and the
|
/linux/arch/arm/mach-omap2/ |
H A D | opp2430_data.c | 11 * These configurations are characterized by voltage and speed for clocks.
|
H A D | opp2420_data.c | 11 * These configurations are characterized by voltage and speed for clocks.
|
H A D | opp2xxx.h | 11 * These configurations are characterized by voltage and speed for clocks.
|
/linux/drivers/phy/broadcom/ |
H A D | phy-brcm-sata.c | 243 /* These defaults were characterized by H/W group */ 422 /* NS2 SATA PLL1 defaults were characterized by H/W group */
|
/linux/drivers/media/i2c/ |
H A D | max9271.c | 140 * characterized in the serializer manual. Sleep up to 5msec to in max9271_configure_i2c()
|
H A D | max9286.c | 450 * The delay is not characterized in de-serializer manual, wait up in max9286_check_video_links() 506 * The delay is not characterized in the chip manual: wait up in max9286_check_config_link()
|
/linux/drivers/iio/chemical/ |
H A D | sunrise_co2.c | 34 * The calibration timeout is not characterized in the datasheet.
|
/linux/Documentation/devicetree/bindings/cpu/ |
H A D | idle-states.yaml | 45 be characterized with bindings that provide the required information to OS PM 70 Idle states are characterized for a specific system through a set of
|
/linux/Documentation/scheduler/ |
H A D | sched-deadline.rst | 76 - Each SCHED_DEADLINE task is characterized by the "runtime", 331 Each job J_j (where J_j is the j^th job of the task) is characterized by an
|
/linux/Documentation/networking/ |
H A D | tls-offload.rst | 398 TLS offload can be characterized by the following basic metrics:
|
/linux/Documentation/admin-guide/pm/ |
H A D | cpuidle.rst | 133 Each idle state present in that array is characterized by two parameters to be
|
/linux/sound/soc/codecs/ |
H A D | nau8825.c | 351 * The orignal and cross talk signal vlues need to be characterized. 352 * Once these values have been characterized, this sidetone value
|
/linux/drivers/gpu/drm/tegra/ |
H A D | dc.c | 1889 * above the characterized maximum. In this case it's okay to fall in tegra_dc_update_voltage_state() 1890 * back to the characterized maximum. in tegra_dc_update_voltage_state()
|
/linux/tools/perf/pmu-events/arch/x86/haswell/ |
H A D | hsw-metrics.json | 620 …the L1. Another example is loads who miss in the TLB. These cases are characterized by execution u…
|
/linux/drivers/clk/tegra/ |
H A D | clk-dfll.c | 990 * characterized to keep the downstream device stable at any DVCO
|
/linux/tools/perf/pmu-events/arch/x86/ivybridge/ |
H A D | ivb-metrics.json | 699 …the L1. Another example is loads who miss in the TLB. These cases are characterized by execution u…
|
/linux/tools/perf/pmu-events/arch/x86/broadwell/ |
H A D | bdw-metrics.json | 778 …the L1. Another example is loads who miss in the TLB. These cases are characterized by execution u…
|
/linux/Documentation/security/keys/ |
H A D | core.rst | 867 of the KDF is returned to the caller. The KDF is characterized with
|
/linux/tools/perf/pmu-events/arch/x86/broadwellde/ |
H A D | bdwde-metrics.json | 770 …the L1. Another example is loads who miss in the TLB. These cases are characterized by execution u…
|
/linux/tools/perf/pmu-events/arch/x86/ivytown/ |
H A D | ivt-metrics.json | 719 …the L1. Another example is loads who miss in the TLB. These cases are characterized by execution u…
|
/linux/tools/perf/pmu-events/arch/x86/haswellx/ |
H A D | hsx-metrics.json | 842 …the L1. Another example is loads who miss in the TLB. These cases are characterized by execution u…
|
/linux/drivers/gpu/drm/stm/ |
H A D | ltdc.c | 605 * either characterized by a FourCC format code
|
/linux/tools/perf/pmu-events/arch/x86/broadwellx/ |
H A D | bdx-metrics.json | 1000 …the L1. Another example is loads who miss in the TLB. These cases are characterized by execution u…
|
/linux/tools/perf/pmu-events/arch/x86/tigerlake/ |
H A D | tgl-metrics.json | 1228 …the L1. Another example is loads who miss in the TLB. These cases are characterized by execution u…
|