Home
last modified time | relevance | path

Searched full:side (Results 1 – 25 of 3439) sorted by relevance

12345678910>>...138

/OK3568_Linux_fs/kernel/drivers/char/hw_random/
H A DKconfig28 This driver provides kernel-side support for a generic Random
43 This driver provides kernel-side support for the Random Number
56 This driver provides kernel-side support for the Random Number
69 This driver provides kernel-side support for the Random Number
81 This driver provides kernel-side support for the Random Number
93 This driver provides kernel-side support for the Random Number
106 This driver provides kernel-side support for the RNG200
119 This driver provides kernel-side support for the Random Number
132 This driver provides kernel-side support for the Random Number
145 This driver provides kernel-side support for the Random Number
[all …]
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/devfreq/
H A Drk3399_dmc.txt75 the ODT on the DRAM side and controller side are
79 the DRAM side driver strength in ohms. Default
83 the DRAM side ODT strength in ohms. Default value
87 the phy side CA line (incluing command line,
92 the PHY side DQ line (including DQS/DQ/DM line)
96 the PHY side ODT strength. Default value is
102 the ODT on the DRAM side and controller side are
106 the DRAM side driver strength in ohms. Default
110 the DRAM side ODT strength in ohms. Default value
114 the PHY side CA line (including command line,
[all …]
/OK3568_Linux_fs/kernel/tools/perf/pmu-events/arch/powerpc/power8/
H A Dtranslation.json29 …r chip's L2 or L3 on a different Node or Group (Distant), as this chip due to a data side request",
35 …r chip's L2 or L3 on a different Node or Group (Distant), as this chip due to a data side request",
41 …ion": "A Page Table Entry was loaded into the TLB from local core's L2 due to a data side request",
47 …was loaded into the TLB from a location other than the local core's L2 due to a data side request",
53 …TLB from local core's L2 hit without dispatch conflicts on Mepf state. due to a data side request",
59 …le Entry was loaded into the TLB from local core's L2 without conflict due to a data side request",
65 …ion": "A Page Table Entry was loaded into the TLB from local core's L3 due to a data side request",
71 …ry was loaded into the TLB from local core's L3 with dispatch conflict due to a data side request",
77 …TLB from local core's L3 without dispatch conflicts hit on Mepf state. due to a data side request",
83 …le Entry was loaded into the TLB from local core's L3 without conflict due to a data side request",
[all …]
H A Dfrontend.json293 …s L2 or L3 on a different Node or Group (Distant), as this chip due to a instruction side request",
299 …s L2 or L3 on a different Node or Group (Distant), as this chip due to a instruction side request",
305 …B from another chip's L4 on a different Node or Group (Distant) due to a instruction side request",
311 … from another chip's memory on the same Node or Group (Distant) due to a instruction side request",
317 …A Page Table Entry was loaded into the TLB from local core's L2 due to a instruction side request",
323 …ded into the TLB from a location other than the local core's L2 due to a instruction side request",
329 …m local core's L2 hit without dispatch conflicts on Mepf state. due to a instruction side request",
335 …y was loaded into the TLB from local core's L2 without conflict due to a instruction side request",
341 …A Page Table Entry was loaded into the TLB from local core's L3 due to a instruction side request",
347 …ded into the TLB from a location other than the local core's L3 due to a instruction side request",
[all …]
H A Dmarked.json365 …s L2 or L3 on a different Node or Group (Distant), as this chip due to a marked data side request",
371 …s L2 or L3 on a different Node or Group (Distant), as this chip due to a marked data side request",
377 …B from another chip's L4 on a different Node or Group (Distant) due to a marked data side request",
383 … from another chip's memory on the same Node or Group (Distant) due to a marked data side request",
389 …A Page Table Entry was loaded into the TLB from local core's L2 due to a marked data side request",
395 …ded into the TLB from a location other than the local core's L2 due to a marked data side request",
401 …m local core's L2 hit without dispatch conflicts on Mepf state. due to a marked data side request",
407 …y was loaded into the TLB from local core's L2 without conflict due to a marked data side request",
413 …A Page Table Entry was loaded into the TLB from local core's L3 due to a marked data side request",
419 …ded into the TLB from a location other than the local core's L3 due to a marked data side request",
[all …]
/OK3568_Linux_fs/kernel/Documentation/locking/
H A Dseqlock.rst15 read side critical section is even and the same sequence count value is
17 be copied out inside the read side critical section. If the sequence
24 the end of the write side critical section the sequence count becomes
27 A sequence counter write side critical section must never be preempted
28 or interrupted by read side sections. Otherwise the reader will spin for
43 multiple writers. Write side critical sections must thus be serialized
48 write side section. If the read section can be invoked from hardirq or
76 /* ... [[write-side critical section]] ... */
85 /* ... [[read-side critical section]] ... */
95 As discussed at :ref:`seqcount_t`, sequence count write side critical
[all …]
/OK3568_Linux_fs/kernel/Documentation/usb/
H A Dgadget_serial.rst57 side driver. It runs on a Linux system that has USB device side
66 | Host-Side CDC ACM USB Host |
78 | Device-Side | Gadget | Controller | |
84 On the device-side Linux system, the gadget serial driver looks
87 On the host-side system, the gadget serial device looks like a
92 The host side driver can potentially be any ACM compliant driver
98 With the gadget serial driver and the host side ACM or generic
100 the host and the gadget side systems as if they were connected by a
111 side kernel for "Support for USB Gadgets", for a "USB Peripheral
128 side Linux system. You can add this to the start up scripts, if
[all …]
/OK3568_Linux_fs/buildroot/dl/qt5location/git/src/3rdparty/mapbox-gl-native/deps/boost/1.65.1/include/boost/geometry/strategies/agnostic/
H A Dpoint_in_box_by_side.hpp33 static inline bool apply(int side, bool& result) in apply()
35 if (side != 1) in apply()
46 static inline bool apply(int side, bool& result) in apply()
48 if (side != 1) in apply()
50 result = side >= 0; in apply()
60 // longer than 180deg because e.g. the SSF formula picks the side of the closer
61 // longitude, so for long edges the side is the opposite.
65 typedef typename strategy::side::services::default_strategy
73 // Every point should be on the LEFT side (=1), or ON the border (=0), in apply()
85 int const side = strategy.apply(point, bp[i - 1], bp[i]); in apply() local
[all …]
/OK3568_Linux_fs/kernel/tools/perf/pmu-events/arch/x86/silvermont/
H A Dvirtual-memory.json19 "BriefDescription": "D-side page-walks",
23 …"PublicDescription": "This event counts every cycle when a D-side (walks due to a load) page walk …
29 "BriefDescription": "Duration of D-side page-walks in core cycles"
38 "BriefDescription": "I-side page-walks",
42 …"PublicDescription": "This event counts every cycle when a I-side (walks due to an instruction fet…
48 "BriefDescription": "Duration of I-side page-walks in core cycles"
57 "BriefDescription": "Total page walks that are completed (I-side and D-side)",
67 "BriefDescription": "Total cycles for all the page walks. (I-side and D-side)"
/OK3568_Linux_fs/buildroot/dl/qt5location/git/src/3rdparty/mapbox-gl-native/deps/boost/1.65.1/include/boost/geometry/algorithms/detail/buffer/
H A Dbuffer_inserter.hpp33 #include <boost/geometry/strategies/side.hpp>
137 geometry::strategy::buffer::buffer_side_selector side, in add_join()
142 Strategy const& strategy) // side strategy in add_join()
180 // For linestrings, only add spike at one side to avoid in add_join()
183 …end_strategy.apply(penultimate_input, prev_perp2, previous_input, perp1, side, distance, range_out… in add_join()
195 distance.apply(previous_input, input, side), in add_join()
211 Strategy const& strategy) // side strategy in get_join_type()
213 int const side = strategy.apply(p0, p1, p2); in get_join_type() local
214 return side == -1 ? geometry::strategy::buffer::join_convex in get_join_type()
215 : side == 1 ? geometry::strategy::buffer::join_concave in get_join_type()
[all …]
H A Dturn_in_piece_visitor.hpp135 int const side = strategy::side::side_of_intersection::apply(p, q, r, in check_segment() local
138 if (side == 0) in check_segment()
142 if (side == -1 && from_monotonic) in check_segment()
146 if (side == 1 && from_monotonic) in check_segment()
154 typedef typename strategy::side::services::default_strategy in check_segment()
196 // Not monotonic, on left or right side: continue analysing in check_segment()
258 int const side = strategy::side::side_of_intersection::apply(p, q, r, in apply() local
262 if (side == 1) in apply()
267 else if (side == 0) in apply()
323 int const side = strategy::side::side_of_intersection::apply(p, q, r, in check_helper_segment() local
[all …]
/OK3568_Linux_fs/kernel/Documentation/RCU/
H A Dchecklist.rst18 tool for the job. Yes, RCU does reduce read-side overhead by
19 increasing write-side overhead, which is exactly why normal uses
28 read-side primitives is critically important.
59 2. Do the RCU read-side critical sections make proper use of
63 under your read-side code, which can greatly increase the
68 rcu_read_lock_sched(), or by the appropriate update-side lock.
72 Letting RCU-protected pointers "leak" out of an RCU read-side
76 -before- letting them out of the RCU read-side critical section.
151 perfectly legal (if redundant) for update-side code to
156 of an RCU read-side critical section. See lockdep.txt
[all …]
H A DwhatisRCU.rst94 b. Wait for all previous readers to complete their RCU read-side
157 entering an RCU read-side critical section. It is illegal
158 to block while in an RCU read-side critical section, though
160 read-side critical sections. Any RCU-protected data structure
161 accessed during an RCU read-side critical section is guaranteed to
171 exiting an RCU read-side critical section. Note that RCU
172 read-side critical sections may be nested and/or overlapping.
180 read-side critical sections on all CPUs have completed.
182 any subsequent RCU read-side critical sections to complete.
195 read-side critical sections to complete, not necessarily for
[all …]
H A Dlockdep.rst8 aware of when each task enters and leaves any flavor of RCU read-side
31 Check for RCU read-side critical section.
33 Check for RCU-bh read-side critical section.
35 Check for RCU-sched read-side critical section.
37 Check for SRCU read-side critical section.
80 1. An RCU read-side critical section (implicit), or
85 RCU read-side critical sections, in case (2) the ->file_lock prevents
96 complain if this was used in an RCU read-side critical section unless one
104 traversal primitives check for being called from within an RCU read-side
108 false and they are called from outside any RCU read-side critical section.
[all …]
/OK3568_Linux_fs/buildroot/dl/qt5location/git/src/3rdparty/mapbox-gl-native/deps/boost/1.65.1/include/boost/geometry/algorithms/detail/overlay/
H A Dget_turn_info.hpp81 // Same side of a segment (not being 0)
158 SidePolicy const& side) in apply()
173 int const side_qk_p = side.qk_wrt_p1(); in apply()
186 int const side_qk_q = side.qk_wrt_q1(); in apply()
190 // Q turns left on the right side of P (test "MR3") in apply()
197 // Q turns right on the left side of P (test "ML3") in apply()
205 // Q turns left on the left side of P (test "ML2") in apply()
206 // or Q turns right on the right side of P (test "MR2") in apply()
281 SidePolicy const& side) in apply()
286 int const side_qk_p1 = side.qk_wrt_p1(); in apply()
[all …]
/OK3568_Linux_fs/kernel/drivers/gpu/arm/midgard/
H A Dmali_uk.h23 * and kernel side of the User-Kernel interface.
41 …* The User-Kernel Interface abstracts the communication mechanism between the user and kernel-side…
44 …* It exposes an OS independent API to user-side code (UKU) which routes functions calls to an OS-i…
45 * kernel-side API (UKK) via an OS-specific communication mechanism.
53 * These are identifiers for kernel-side drivers implementing a UK interface, aka UKK clients. The
122 … during uku_open to identify the versions of the UK module in use by the user-side and kernel-side.
128 …/**< This field carries the user-side major version on input and the kernel-side major version on …
130 …/**< This field carries the user-side minor version on input and the kernel-side minor version on …
/OK3568_Linux_fs/kernel/include/linux/
H A Dsrcu.h70 * srcu_read_lock_held - might we be in SRCU read-side critical section?
74 * read-side critical section. In absence of CONFIG_DEBUG_LOCK_ALLOC,
75 * this assumes we are in an SRCU read-side critical section unless it can
105 * really are in an SRCU read-side critical section.
106 * @c: condition to check for update-side use
108 * If PROVE_RCU is enabled, invoking this outside of an RCU read-side
120 * really are in an SRCU read-side critical section.
123 * is enabled, invoking this outside of an RCU read-side critical
132 * really are in an SRCU read-side critical section.
140 * Enter an SRCU read-side critical section. Note that SRCU read-side
[all …]
/OK3568_Linux_fs/buildroot/dl/qt5location/git/src/3rdparty/mapbox-gl-native/deps/wagyu/0.4.3/include/mapbox/geometry/wagyu/
H A Dbound.hpp34 edge_side side; // side only refers to current side of solution poly member
49 side(edge_left) {
65 side(std::move(b.side)) { in bound()
86 if (bnd.side == edge_left) { in operator <<()
87 out << " side: left" << std::endl; in operator <<()
89 out << " side: right" << std::endl; in operator <<()
/OK3568_Linux_fs/kernel/Documentation/RCU/Design/Requirements/
H A DRequirements.rst20 updaters do not block readers, which means that RCU's read-side
74 of all pre-existing RCU read-side critical sections. An RCU read-side
77 RCU treats a nested set as one big RCU read-side critical section.
131 | Second, even when using ``synchronize_rcu()``, the other update-side |
173 The RCU read-side critical section in ``do_something_dlm()`` works with
190 In order to avoid fatal problems such as deadlocks, an RCU read-side
192 Similarly, an RCU read-side critical section must not contain anything
198 be good to be able to use RCU to coordinate read-side access to linked
372 outermost RCU read-side critical section containing that
386 #. Wait for all pre-existing RCU read-side critical sections to complete
[all …]
/OK3568_Linux_fs/external/mpp/inc/
H A Dmpp_task.h29 * On input side user will dequeue task from input port, setup task and enqueue task
31 * On output side user will dequeue task from output port, get the information from
139 * input side:
143 * output side:
149 * input side:
154 * output side:
172 * input side:
176 * output side:
182 * input side:
187 * output side:
[all …]
/OK3568_Linux_fs/external/rknpu2/examples/3rdparty/mpp/include/rockchip/
H A Dmpp_task.h29 * On input side user will dequeue task from input port, setup task and enqueue task
31 * On output side user will dequeue task from output port, get the information from
139 * input side:
143 * output side:
149 * input side:
154 * output side:
172 * input side:
176 * output side:
182 * input side:
187 * output side:
[all …]
/OK3568_Linux_fs/kernel/tools/perf/pmu-events/arch/x86/knightslanding/
H A Dvirtual-memory.json18 …"BriefDescription": "Counts the total D-side page walks that are completed or started. The page wa…
27 …"BriefDescription": "Counts the total number of core cycles for all the D-side page walks. The cyc…
35 "BriefDescription": "Counts the total I-side page walks that are completed.",
39 …"PublicDescription": "This event counts every cycle when an I-side (walks due to an instruction fe…
45 …"BriefDescription": "Counts the total number of core cycles for all the I-side page walks. The cyc…
53 "BriefDescription": "Counts the total page walks that are completed (I-side and D-side)",
/OK3568_Linux_fs/buildroot/dl/qt5location/git/src/3rdparty/mapbox-gl-native/deps/boost/1.65.1/include/boost/geometry/strategies/geographic/
H A Dside_vincenty.hpp18 #include <boost/geometry/strategies/geographic/side.hpp>
25 namespace strategy { namespace side namespace
29 \brief Check at which side of a segment a point lies
41 : public side::geographic<strategy::vincenty, Spheroid, CalculationType>
43 typedef side::geographic<strategy::vincenty, Spheroid, CalculationType> base_t;
54 }} // namespace strategy::side
H A Dside_thomas.hpp18 #include <boost/geometry/strategies/geographic/side.hpp>
25 namespace strategy { namespace side namespace
29 \brief Check at which side of a segment a point lies
41 : public side::geographic<strategy::thomas, Spheroid, CalculationType>
43 typedef side::geographic<strategy::thomas, Spheroid, CalculationType> base_t;
54 }} // namespace strategy::side
H A Dside_andoyer.hpp18 #include <boost/geometry/strategies/geographic/side.hpp>
25 namespace strategy { namespace side namespace
29 \brief Check at which side of a segment a point lies
41 : public side::geographic<strategy::andoyer, Spheroid, CalculationType>
43 typedef side::geographic<strategy::andoyer, Spheroid, CalculationType> base_t;
54 }} // namespace strategy::side

12345678910>>...138