Home
last modified time | relevance | path

Searched +full:usecase +full:- +full:specific (Results 1 – 6 of 6) sorted by relevance

/freebsd/sys/contrib/device-tree/Bindings/net/wireless/
H A Dqcom,ath12k.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
4 ---
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Jeff Johnson <quic_jjohnson@quicinc.com>
19 - pci17cb,1107 # WCN7850
24 firmware-name:
27 If present, a board or platform specific string used to lookup
28 usecase-specific firmware files for the device.
30 vddaon-supply:
33 vddwlcx-supply:
[all …]
H A Dqcom,ath11k-pci.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
4 ---
5 $id: http://devicetree.org/schemas/net/wireless/qcom,ath11k-pci.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Jeff Johnson <jjohnson@kernel.org>
19 - pci17cb,1101 # QCA6390
20 - pci17cb,1103 # WCN6855
25 qcom,calibration-variant:
31 qcom,ath11k-calibration-variant:
38 firmware-name:
[all …]
/freebsd/sys/contrib/device-tree/Bindings/iio/
H A Dmount-matrix.txt2 * is the definition of +/- values practical or counterintuitive?
13 that produce three-dimensional data in relation to the world where it is
20 The typical usecase is that where a component has an internal representation
23 relative to some specific device frame of reference.
37 reference. This means that the sensor may be flipped upside-down, left-right,
47 Device-to-world examples for some three-dimensional sensor types:
49 - Accelerometers have their world frame of reference toward the center of
57 as the gravity vector is projected 1:1 onto the sensors (z)-axis.
67 +--------+ +--------+
69 +--------+ +--------+
[all …]
/freebsd/contrib/llvm-project/llvm/lib/Transforms/Utils/
H A DAMDGPUEmitPrintf.cpp1 //===- AMDGPUEmitPrintf.cpp -----------------------------------------------===//
5 // SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
7 //===----------------------------------------------------------------------===//
15 //===----------------------------------------------------------------------===//
28 #define DEBUG_TYPE "amdgpu-emit-printf"
32 auto Ty = Arg->getType(); in fitArgInto64Bits()
35 switch (IntTy->getBitWidth()) { in fitArgInto64Bits()
43 if (Ty->getTypeID() == Type::DoubleTyID) { in fitArgInto64Bits()
56 auto M = Builder.GetInsertBlock()->getModule(); in callPrintfBegin()
57 auto Fn = M->getOrInsertFunction("__ockl_printf_begin", Int64Ty, Int64Ty); in callPrintfBegin()
[all …]
/freebsd/sys/kern/
H A Dkern_rmlock.c1 /*-
2 * SPDX-License-Identifier: BSD-3-Clause
15 * 3. Neither the name of the author nor the names of any co-contributors
17 * without specific prior written permission.
67 (LIST_FIRST(&(rm)->rm_activeReaders) == RM_DESTROYED)
161 for (queue = pc->pc_rm_queue.rmq_next; in unlock_rm()
162 queue != &pc->pc_rm_queue; queue = queue->rmq_next) { in unlock_rm()
164 if ((tracker->rmp_rmlock == rm) && in unlock_rm()
165 (tracker->rmp_thread == td)) { in unlock_rm()
171 ("rm_priotracker is non-NULL when lock held in read mode")); in unlock_rm()
[all …]
/freebsd/sys/net/route/
H A Dfib_algo.c1 /*-
2 * SPDX-License-Identifier: BSD-2-Clause
74 * This framework enables accelerated longest-prefix-match lookups for the
78 * flm - fib lookup modules - implementation of particular lookup algorithm
79 * fd - fib data - instance of an flm bound to specific routing table
85 * 1) nexhops abstraction -> provides transparent referencing, indexing
86 * and efficient idx->ptr mappings for nexthop and nexthop groups.
95 * and its argument. This function will be called with a family-specific lookup key,
96 * scope and provided argument. This array gets re-created every time when new algo
181 struct nhop_object **nh_idx; /* nhop idx->ptr array */
[all …]