Home
last modified time | relevance | path

Searched full:lat (Results 1 – 5 of 5) sorted by relevance

/Documentation/trace/
Dhistogram.rst1825 with 3 fields: lat, pid, and prio. Each of those fields is simply a
1829 u64 lat; \
1838 wakeup_latency u64 lat; pid_t pid; int prio
1843 # echo '!wakeup_latency u64 lat pid_t pid int prio' >> \
1861 # echo 'hist:keys=pid,prio,lat.log2:sort=lat' >> \
1864 The above shows the latency "lat" in a power of 2 grouping.
1873 # trigger info: hist:keys=pid,prio,lat.log2:vals=hitcount:sort=lat.log2:size=2048 [active]
1876 { pid: 2035, prio: 9, lat: ~ 2^2 } hitcount: 43
1877 { pid: 2034, prio: 9, lat: ~ 2^2 } hitcount: 60
1878 { pid: 2029, prio: 9, lat: ~ 2^2 } hitcount: 965
[all …]
Dboottime-trace.rst224 fields = "unsigned long func", "u64 lat"
226 keys = func.sym, lat
227 values = lat
228 sort = lat
237 var.lat = common_timestamp.usecs - $ts0
240 trace = initcall_latency, func, $lat
Dhistogram-design.rst894 # echo 'wakeup_latency u64 lat; pid_t pid' >> synthetic_events
1102 # echo 'wakeup_latency u64 lat; pid_t pid; char comm[16]' >> synthetic_events
1312 # echo '!wakeup_latency u64 lat; pid_t pid; char comm[16]' >> synthetic_events
1632 # echo 'wakeup_latency u64 lat; pid_t pid; int prio' >> synthetic_events
1870 # echo '!wakeup_latency u64 lat; pid_t pid; int prio' >> synthetic_events
1880 # echo 'wakeup_latency u64 lat; pid_t pid; char comm[16]' >> synthetic_events
2115 # echo '!wakeup_latency u64 lat; pid_t pid; char comm[16]' >> synthetic_events
/Documentation/devicetree/bindings/media/
Dmediatek,vcodec-subdev-decoder.yaml22 | input -> lat soc HW -> lat HW -> lat buffer --|--> lat buffer -> core HW -> output |
25 || lat || | core workqueue <parent>
32 | (lat/lat soc/core0/core1) |
38 There are two workqueues in parent device: lat workqueue and core workqueue. They are used
39 to lat and core hardware decoder. Lat workqueue need to get input bitstream and lat buffer,
40 then enable lat to decode, writing the result to lat buffer, dislabe hardware when lat decode
41 done. Core workqueue need to get lat buffer and output buffer, then enable core to decode,
48 Lat soc is a hardware which is related with some larb(local arbiter) ports. For mt8195
49 platform, there are some ports like RDMA, UFO in lat soc larb, need to enable its power and
50 clock when lat start to work, don't have interrupt.
[all …]
/Documentation/RCU/
DRTFP.txt999 Head of thread: dipankar/2004.03.23/rcu-low-lat.1.patch