Lines Matching refs:to

8 these masters and channels are statically allocated to certain
9 hardware trace sources, others are available to software. Software
10 trace sources are usually free to pick for themselves any
15 order for the decoder to be able to make sense of the trace that
16 involves multiple trace sources, it needs to be able to map those
17 master/channel pairs to the trace sources that it understands.
19 For instance, it is helpful to know that syslog messages come on
21 48 to 63 and channels 0 to 127.
25 identifiers to ranges of masters and channels. If these rules (policy)
26 are consistent with what decoder expects, it will be able to properly
33 the STM device name to which this policy applies and and arbitrary
54 Trace sources have to open the stm class device's node and write their
55 trace data into its file descriptor. In order to identify themselves
56 to the policy, they need to do a STP_POLICY_ID_SET ioctl on this file
58 automatically allocated a master/channel pair upon first write to this
59 file descriptor according to the "default" rule of the policy, if such
63 to userspace for zero-copy writing. One mappable page (in terms of
65 need to allocate that many channels to themselves (via the
66 aforementioned ioctl() call) to be able to do this. That is, if your
69 width==64, you should be able to mmap() one page on this file
70 descriptor and obtain direct access to an mmio region for 64 channels.
73 class. Devices of this class can be connected and disconnected to/from