~ [ source navigation ] ~ [ diff markup ] ~ [ identifier search ] ~

TOMOYO Linux Cross Reference
Linux/Documentation/trace/sys-t.rst

Version: ~ [ linux-6.12-rc7 ] ~ [ linux-6.11.7 ] ~ [ linux-6.10.14 ] ~ [ linux-6.9.12 ] ~ [ linux-6.8.12 ] ~ [ linux-6.7.12 ] ~ [ linux-6.6.60 ] ~ [ linux-6.5.13 ] ~ [ linux-6.4.16 ] ~ [ linux-6.3.13 ] ~ [ linux-6.2.16 ] ~ [ linux-6.1.116 ] ~ [ linux-6.0.19 ] ~ [ linux-5.19.17 ] ~ [ linux-5.18.19 ] ~ [ linux-5.17.15 ] ~ [ linux-5.16.20 ] ~ [ linux-5.15.171 ] ~ [ linux-5.14.21 ] ~ [ linux-5.13.19 ] ~ [ linux-5.12.19 ] ~ [ linux-5.11.22 ] ~ [ linux-5.10.229 ] ~ [ linux-5.9.16 ] ~ [ linux-5.8.18 ] ~ [ linux-5.7.19 ] ~ [ linux-5.6.19 ] ~ [ linux-5.5.19 ] ~ [ linux-5.4.285 ] ~ [ linux-5.3.18 ] ~ [ linux-5.2.21 ] ~ [ linux-5.1.21 ] ~ [ linux-5.0.21 ] ~ [ linux-4.20.17 ] ~ [ linux-4.19.323 ] ~ [ linux-4.18.20 ] ~ [ linux-4.17.19 ] ~ [ linux-4.16.18 ] ~ [ linux-4.15.18 ] ~ [ linux-4.14.336 ] ~ [ linux-4.13.16 ] ~ [ linux-4.12.14 ] ~ [ linux-4.11.12 ] ~ [ linux-4.10.17 ] ~ [ linux-4.9.337 ] ~ [ linux-4.4.302 ] ~ [ linux-3.10.108 ] ~ [ linux-2.6.32.71 ] ~ [ linux-2.6.0 ] ~ [ linux-2.4.37.11 ] ~ [ unix-v6-master ] ~ [ ccs-tools-1.8.12 ] ~ [ policy-sample ] ~
Architecture: ~ [ i386 ] ~ [ alpha ] ~ [ m68k ] ~ [ mips ] ~ [ ppc ] ~ [ sparc ] ~ [ sparc64 ] ~

  1 .. SPDX-License-Identifier: GPL-2.0
  2 
  3 ===================
  4 MIPI SyS-T over STP
  5 ===================
  6 
  7 The MIPI SyS-T protocol driver can be used with STM class devices to
  8 generate standardized trace stream. Aside from being a standard, it
  9 provides better trace source identification and timestamp correlation.
 10 
 11 In order to use the MIPI SyS-T protocol driver with your STM device,
 12 first, you'll need CONFIG_STM_PROTO_SYS_T.
 13 
 14 Now, you can select which protocol driver you want to use when you create
 15 a policy for your STM device, by specifying it in the policy name:
 16 
 17 # mkdir /config/stp-policy/dummy_stm.0:p_sys-t.my-policy/
 18 
 19 In other words, the policy name format is extended like this:
 20 
 21   <device_name>:<protocol_name>.<policy_name>
 22 
 23 With Intel TH, therefore it can look like "0-sth:p_sys-t.my-policy".
 24 
 25 If the protocol name is omitted, the STM class will chose whichever
 26 protocol driver was loaded first.
 27 
 28 You can also double check that everything is working as expected by
 29 
 30 # cat /config/stp-policy/dummy_stm.0:p_sys-t.my-policy/protocol
 31 p_sys-t
 32 
 33 Now, with the MIPI SyS-T protocol driver, each policy node in the
 34 configfs gets a few additional attributes, which determine per-source
 35 parameters specific to the protocol:
 36 
 37 # mkdir /config/stp-policy/dummy_stm.0:p_sys-t.my-policy/default
 38 # ls /config/stp-policy/dummy_stm.0:p_sys-t.my-policy/default
 39 channels
 40 clocksync_interval
 41 do_len
 42 masters
 43 ts_interval
 44 uuid
 45 
 46 The most important one here is the "uuid", which determines the UUID
 47 that will be used to tag all data coming from this source. It is
 48 automatically generated when a new node is created, but it is likely
 49 that you would want to change it.
 50 
 51 do_len switches on/off the additional "payload length" field in the
 52 MIPI SyS-T message header. It is off by default as the STP already
 53 marks message boundaries.
 54 
 55 ts_interval and clocksync_interval determine how much time in milliseconds
 56 can pass before we need to include a protocol (not transport, aka STP)
 57 timestamp in a message header or send a CLOCKSYNC packet, respectively.
 58 
 59 See Documentation/ABI/testing/configfs-stp-policy-p_sys-t for more
 60 details.
 61 
 62 * [1] https://www.mipi.org/specifications/sys-t

~ [ source navigation ] ~ [ diff markup ] ~ [ identifier search ] ~

kernel.org | git.kernel.org | LWN.net | Project Home | SVN repository | Mail admin

Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.

sflogo.php