| /linux/include/linux/platform_data/ |
| H A D | apds990x.h | 27 * @df: device factor for conversion formulas
|
| /linux/Documentation/hwmon/ |
| H A D | tmp513.rst | 86 formulas:
|
| H A D | w83781d.rst | 248 > What formulas do I use to program a new R-T table for a given Beta?
|
| /linux/Documentation/misc-devices/ |
| H A D | apds990x.rst | 38 Platform data can provide tuned values to the conversion formulas if
|
| /linux/drivers/pwm/ |
| H A D | pwm-spear.c | 85 * according to formulas described below: in spear_pwm_config()
|
| H A D | pwm-bcm-iproc.c | 125 * period. This is done according to formulas described below: in iproc_pwmc_apply()
|
| H A D | pwm-bcm-kona.c | 110 * period_ns. This is done according to formulas described below: in kona_pwmc_config()
|
| /linux/Documentation/iio/ |
| H A D | adis16475.rst | 27 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/Documentation/kbuild/ |
| H A D | kconfig-language.rst | 728 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/tools/perf/Documentation/ |
| H A D | perf-list.txt | 301 When metrics are computed using formulas from event counts, it is useful to
|
| H A D | topdown.txt | 343 values in some of the metrics’ formulas on processors that support TPEBS feature.
|
| /linux/drivers/gpu/drm/amd/display/dc/link/ |
| H A D | link_validation.c | 29 * provides helper functions exposing bandwidth formulas used in validation.
|
| H A D | link_factory.c | 97 * provides helper functions exposing bandwidth formulas used in validation.
|
| /linux/tools/perf/arch/x86/util/ |
| H A D | iostat.c | 41 * in corresponding direction. The formulas to compute metrics are generic:
|
| /linux/Documentation/input/ |
| H A D | multi-touch-protocol.rst | 380 equal to the tool thickness, and we arrive at the formulas above.
|
| /linux/drivers/rtc/ |
| H A D | rtc-armada38x.c | 357 * They give two different formulas for calculating the offset value,
|
| /linux/Documentation/power/ |
| H A D | energy-model.rst | 164 formulas calculating 'cost' values. To register an EM for such platform, the
|
| /linux/drivers/leds/ |
| H A D | leds-aw200xx.c | 271 * So we have two formulas to calculate the global current:
|
| /linux/drivers/staging/media/sunxi/cedrus/ |
| H A D | cedrus_h264.c | 592 * Formulas for deblock and intra prediction buffer sizes in cedrus_h264_start()
|
| /linux/drivers/video/backlight/ |
| H A D | pwm_bl.c | 161 * expressed as a fixed-point number, so the above formulas in cie1931()
|
| /linux/drivers/iio/magnetometer/ |
| H A D | yamaha-yas530.c | 555 * Calibrate [x,y,z] with some formulas like this: in yas530_get_measure()
599 * Unfortunately, no linearization or temperature compensation formulas in yas537_get_measure()
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | colorspaces-details.rst | 196 As seen by the xvYCC formulas these encodings always use limited range quantization,
|
| /linux/tools/bpf/bpftool/ |
| H A D | btf_dumper.c | 283 * The below formulas shows what upper_num and lower_num represents: in btf_int128_print()
|
| /linux/drivers/power/supply/ |
| H A D | twl4030_charger.c | 206 * TI provided formulas:
|
| /linux/drivers/media/pci/mgb4/ |
| H A D | mgb4_cmt.c | 9 * are precomputed based on formulas given by Xilinx in their FPGA documentation
|