| /f-stack/freebsd/arm64/rockchip/clk/ |
| H A D | rk_clk_fract.c | 99 uint64_t tmp, fact; in clk_compute_fract_div() local
113 fact = n_rem / d_rem; in clk_compute_fract_div()
121 tmp = n_prev + fact * n_cur; in clk_compute_fract_div()
126 tmp = d_prev + fact * d_cur; in clk_compute_fract_div()
|
| /f-stack/freebsd/contrib/device-tree/src/arm64/mediatek/ |
| H A D | mt8183-kukui-krane.dtsi | 329 * we're relying on the fact that this pin has a default
|
| /f-stack/freebsd/contrib/device-tree/Bindings/iio/dac/ |
| H A D | adi,ad5770r.yaml | 29 that are in fact the same.
|
| /f-stack/freebsd/contrib/device-tree/Bindings/input/touchscreen/ |
| H A D | ti-tsc-adc.txt | 49 charge step, so this does in fact function as a
|
| /f-stack/freebsd/contrib/zlib/ |
| H A D | FAQ | 39 made with more input or output space. A Z_BUF_ERROR may in fact be
236 As far as we know, no. In fact, that was originally the whole point behind
332 efficient approach (and in fact exactly what the zlib format was designed
349 part of zlib. In fact none of the stuff in contrib is part of zlib. The
|
| /f-stack/freebsd/contrib/device-tree/Bindings/net/ |
| H A D | ti,dp83867.yaml | 91 This denotes the fact that the board has RX_DV/RX_CTRL pin strapped in
|
| H A D | micrel-ksz90x1.txt | 16 steps, *but* these values are in not fact what you get because this chip's
|
| /f-stack/freebsd/contrib/device-tree/Bindings/clock/ |
| H A D | baikal,bt1-ccu-pll.yaml | 50 biggest system interfaces in fact include nearly all of the rest SoC
|
| /f-stack/freebsd/contrib/device-tree/Bindings/pinctrl/ |
| H A D | nvidia,tegra114-pinmux.txt | 5 nvidia,tegra30-pinmux.txt. In fact, this document assumes that binding as
|
| H A D | nvidia,tegra30-pinmux.txt | 4 as described in nvidia,tegra20-pinmux.txt. In fact, this document assumes
|
| H A D | nvidia,tegra124-pinmux.txt | 5 nvidia,tegra30-pinmux.txt. In fact, this document assumes that binding as
|
| /f-stack/freebsd/contrib/device-tree/src/arm/ |
| H A D | exynos5420-arndale-octa.dts | 509 * fact controlled by LDO18EN. The eMMC does
754 * fact controlled by BUCK10EN. The eMMC does
|
| H A D | rk3288-veyron-mickey.dts | 102 * with the fact that there are two passive cooling devices:
|
| H A D | dra76-evm.dts | 440 * SDCD signal is not being used here - using the fact that GPIO mode
|
| H A D | rk3288-veyron.dtsi | 266 * powered from vcc33_pmuio. In fact, on later boards
|
| H A D | dra72-evm-common.dtsi | 425 * SDCD signal is not being used here - using the fact that GPIO mode
|
| H A D | dra7-evm.dts | 385 * SDCD signal is not being used here - using the fact that GPIO mode
|
| /f-stack/freebsd/contrib/device-tree/Bindings/mux/ |
| H A D | mux-controller.txt | 64 for the consumer node in fact asks for a named mux controller, that name is of
|
| /f-stack/freebsd/contrib/device-tree/Bindings/pci/ |
| H A D | host-generic-pci.yaml | 16 and clock management. In fact, the controller may not even require the
|
| /f-stack/freebsd/contrib/device-tree/src/powerpc/fsl/ |
| H A D | mpc8641_hpcn.dts | 370 * due to the fact that the 2 now share address space in the new memory
|
| /f-stack/freebsd/contrib/device-tree/Bindings/powerpc/fsl/ |
| H A D | mpic.txt | 65 in fact big-endian, so certain boards override this property.
|
| /f-stack/freebsd/contrib/device-tree/Bindings/regulator/ |
| H A D | pfuze100.txt | 13 old dtb's which rely on the fact that the switched regulators are always on
|
| /f-stack/dpdk/doc/guides/sample_app_ug/ |
| H A D | performance_thread.rst | 456 The fact that L-threads cannot preempt each other means that in many cases
711 ``lthread_set_affinity()`` is similar to a yield apart from the fact that the
1031 of some other loop that does in fact yield, if this is possible.
1047 or in fact most likely should be placed in L-thread local storage.
1103 expected to return, and in fact the thread is being destroyed. These
1164 When debugging you must take account of the fact that the L-threads are run in
|
| /f-stack/freebsd/contrib/device-tree/Bindings/gpio/ |
| H A D | nvidia,tegra186-gpio.txt | 54 Each GPIO controller in fact generates multiple interrupts signals for each set
|
| /f-stack/dpdk/doc/guides/nics/ |
| H A D | nfp.rst | 66 have any functionality for controlling VFs. In fact, it is not possible to use
|