Searched refs:GTE (Results 1 – 5 of 5) sorted by relevance
8 The Nvidia tegra HTE provider also known as GTE (Generic Timestamping Engine)9 driver implements two GTE instances: 1) GPIO GTE and 2) LIC10 (Legacy Interrupt Controller) IRQ GTE. Both GTE instances get the timestamp14 GPIO GTE17 This GTE instance timestamps GPIO in real time. For that to happen GPIO20 the GPIO GTE. To support this, GPIOLIB adds two optional APIs as mentioned21 below. The GPIO GTE code supports both kernel and userspace consumers. The34 LIC (Legacy Interrupt Controller) IRQ GTE42 this GTE instance in the HTE framework.44 The provider source code of both IRQ and GPIO GTE instances is located at[all …]
13 Tegra SoC has two instances of generic hardware timestamping engines (GTE)14 known as GTE GPIO and GTE IRQ, which can monitor subset of GPIO and on chip18 to enable or disable for the hardware timestamping. The GTE GPIO monitors50 GTE instances for both Tegra194 and Tegra234 has 3 slices. The Tegra19458 namespace conversion between GPIO and GTE.63 consumers. For the GTE IRQ, this is IRQ number as mentioned in the64 SoC technical reference manual. For the GTE GPIO, its value is same as
22 known as generic timestamping engine (GTE) support on NVIDIA Tegra19430 The NVIDIA Tegra194 GTE test driver demonstrates how to use HTE
66 GTE, enumerator444 case knob::DepexOperators::GTE: in evaluateExprStack()573 operators.emplace(knob::DepexOperators::GTE); in evaluateExpression()
54 %token ASR LSR EQ NEQ LTE GTE MIN MAX ANDL FOR ICIRC IF MUN FSCR FCHK SXT86 %left '<' '>' LTE GTE643 | rvalue GTE rvalue