Home
last modified time | relevance | path

Searched full:formulas (Results 1 – 25 of 57) sorted by relevance

123

/linux-6.12.1/include/linux/platform_data/
Dapds990x.h27 * @df: device factor for conversion formulas
/linux-6.12.1/Documentation/hwmon/
Dtmp513.rst86 formulas:
Dw83781d.rst248 > What formulas do I use to program a new R-T table for a given Beta?
/linux-6.12.1/Documentation/misc-devices/
Dapds990x.rst38 Platform data can provide tuned values to the conversion formulas if
/linux-6.12.1/Documentation/devicetree/bindings/iio/dac/
Dadi,ad3552r.yaml88 The formulas for calculation the output voltages are
/linux-6.12.1/drivers/pwm/
Dpwm-bcm-iproc.c125 * period. This is done according to formulas described below: in iproc_pwmc_apply()
Dpwm-spear.c85 * according to formulas described below: in spear_pwm_config()
Dpwm-bcm-kona.c110 * period_ns. This is done according to formulas described below: in kona_pwmc_config()
/linux-6.12.1/drivers/thermal/
Damlogic_thermal.c8 * Register value to celsius temperature formulas:
/linux-6.12.1/Documentation/iio/
Dadis16475.rst27 each sensor has dynamic compensation formulas that provide accurate sensor
46 includes the application of unique correction formulas, which are derived from
50 correction formulas are not accessible, but users do have the opportunity to
/linux-6.12.1/drivers/gpu/drm/amd/display/dc/link/
Dlink_validation.c29 * provides helper functions exposing bandwidth formulas used in validation.
Dlink_factory.c97 * provides helper functions exposing bandwidth formulas used in validation.
/linux-6.12.1/tools/perf/Documentation/
Dperf-list.txt286 When metrics are computed using formulas from event counts, it is useful to
Dtopdown.txt343 values in some of the metrics’ formulas on processors that support TPEBS feature.
/linux-6.12.1/Documentation/kbuild/
Dkconfig-language.rst728 translate Kconfig logic into boolean formulas and run a SAT solver on this to
752 boolean formulas and run a SAT solver on it [5]_. Another known related project
/linux-6.12.1/tools/perf/arch/x86/util/
Diostat.c41 * in corresponding direction. The formulas to compute metrics are generic:
/linux-6.12.1/Documentation/input/
Dmulti-touch-protocol.rst380 equal to the tool thickness, and we arrive at the formulas above.
/linux-6.12.1/drivers/misc/
Dapds990x.c291 * IAC1 > IAC2 (see apds990x_get_lux for formulas) in apds990x_lux_to_threshold()
436 /* Formulas: in apds990x_get_lux()
/linux-6.12.1/drivers/rtc/
Drtc-armada38x.c357 * They give two different formulas for calculating the offset value,
/linux-6.12.1/drivers/thermal/renesas/
Drcar_gen3_thermal.c126 * threshold is also calculated from PTAT and THCODE using formulas from the
/linux-6.12.1/drivers/leds/
Dleds-aw200xx.c271 * So we have two formulas to calculate the global current:
/linux-6.12.1/Documentation/power/
Denergy-model.rst164 formulas calculating 'cost' values. To register an EM for such platform, the
/linux-6.12.1/drivers/staging/media/sunxi/cedrus/
Dcedrus_h264.c592 * Formulas for deblock and intra prediction buffer sizes in cedrus_h264_start()
/linux-6.12.1/drivers/video/backlight/
Dpwm_bl.c161 * expressed as a fixed-point number, so the above formulas in cie1931()
/linux-6.12.1/Documentation/userspace-api/media/v4l/
Dcolorspaces-details.rst196 As seen by the xvYCC formulas these encodings always use limited range quantization,

123