1What: /sys/class/most/mostcore/aims 2Date: June 2015 3KernelVersion: 4.3 4Contact: Christian Gromm <christian.gromm@microchip.com> 5Description: 6 List of AIMs that have been loaded. 7Users: 8 9What: /sys/class/most/mostcore/aims/<aim>/add_link 10Date: June 2015 11KernelVersion: 4.3 12Contact: Christian Gromm <christian.gromm@microchip.com> 13Description: 14 This is used to establish a connection of a channel and the 15 current AIM. 16Users: 17 18What: /sys/class/most/mostcore/aims/<aim>/remove_link 19Date: June 2015 20KernelVersion: 4.3 21Contact: Christian Gromm <christian.gromm@microchip.com> 22Description: 23 This is used to remove a connected channel from the 24 current AIM. 25Users: 26 27What: /sys/class/most/mostcore/devices 28Date: June 2015 29KernelVersion: 4.3 30Contact: Christian Gromm <christian.gromm@microchip.com> 31Description: 32 List of attached MOST interfaces. 33Users: 34 35What: /sys/class/most/mostcore/devices/<mdev>/description 36Date: June 2015 37KernelVersion: 4.3 38Contact: Christian Gromm <christian.gromm@microchip.com> 39Description: 40 Provides information about the interface type and the physical 41 location of the device. Hardware attached via USB, for instance, 42 might return <usb_device 1-1.1:1.0> 43Users: 44 45What: /sys/class/most/mostcore/devices/<mdev>/interface 46Date: June 2015 47KernelVersion: 4.3 48Contact: Christian Gromm <christian.gromm@microchip.com> 49Description: 50 Indicates the type of peripheral interface the current device 51 uses. 52Users: 53 54What: /sys/class/most/mostcore/devices/<mdev>/dci 55Date: June 2016 56KernelVersion: 4.9 57Contact: Christian Gromm <christian.gromm@microchip.com> 58Description: 59 If the network interface controller is attached via USB, a dci 60 directory is created that allows applications to use the 61 controller's direct communication interface (DCI) to exchange 62 information. 63Users: 64 65What: /sys/class/most/mostcore/devices/<mdev>/dci/arb_address 66Date: June 2016 67KernelVersion: 4.9 68Contact: Christian Gromm <christian.gromm@microchip.com> 69Description: 70 This is used to set an arbitrary DCI register address an 71 application wants to read from or write to. 72Users: 73 74What: /sys/class/most/mostcore/devices/<mdev>/dci/arb_value 75Date: June 2016 76KernelVersion: 4.9 77Contact: Christian Gromm <christian.gromm@microchip.com> 78Description: 79 This is used to read from or write to the arbitrary DCI register 80 whose address is stored in arb_address. 81Users: 82 83What: /sys/class/most/mostcore/devices/<mdev>/dci/mep_eui48_hi 84Date: June 2016 85KernelVersion: 4.9 86Contact: Christian Gromm <christian.gromm@microchip.com> 87Description: 88 This is used to check and configure the MAC address. 89Users: 90 91What: /sys/class/most/mostcore/devices/<mdev>/dci/mep_eui48_lo 92Date: June 2016 93KernelVersion: 4.9 94Contact: Christian Gromm <christian.gromm@microchip.com> 95Description: 96 This is used to check and configure the MAC address. 97Users: 98 99What: /sys/class/most/mostcore/devices/<mdev>/dci/mep_eui48_mi 100Date: June 2016 101KernelVersion: 4.9 102Contact: Christian Gromm <christian.gromm@microchip.com> 103Description: 104 This is used to check and configure the MAC address. 105Users: 106 107What: /sys/class/most/mostcore/devices/<mdev>/dci/mep_filter 108Date: June 2016 109KernelVersion: 4.9 110Contact: Christian Gromm <christian.gromm@microchip.com> 111Description: 112 This is used to check and configure the MEP filter address. 113Users: 114 115What: /sys/class/most/mostcore/devices/<mdev>/dci/mep_hash0 116Date: June 2016 117KernelVersion: 4.9 118Contact: Christian Gromm <christian.gromm@microchip.com> 119Description: 120 This is used to check and configure the MEP hash table. 121Users: 122 123What: /sys/class/most/mostcore/devices/<mdev>/dci/mep_hash1 124Date: June 2016 125KernelVersion: 4.9 126Contact: Christian Gromm <christian.gromm@microchip.com> 127Description: 128 This is used to check and configure the MEP hash table. 129Users: 130 131What: /sys/class/most/mostcore/devices/<mdev>/dci/mep_hash2 132Date: June 2016 133KernelVersion: 4.9 134Contact: Christian Gromm <christian.gromm@microchip.com> 135Description: 136 This is used to check and configure the MEP hash table. 137Users: 138 139What: /sys/class/most/mostcore/devices/<mdev>/dci/mep_hash3 140Date: June 2016 141KernelVersion: 4.9 142Contact: Christian Gromm <christian.gromm@microchip.com> 143Description: 144 This is used to check and configure the MEP hash table. 145Users: 146 147What: /sys/class/most/mostcore/devices/<mdev>/dci/ni_state 148Date: June 2016 149KernelVersion: 4.9 150Contact: Christian Gromm <christian.gromm@microchip.com> 151Description: 152 Indicates the current network interface state. 153Users: 154 155What: /sys/class/most/mostcore/devices/<mdev>/dci/node_address 156Date: June 2016 157KernelVersion: 4.9 158Contact: Christian Gromm <christian.gromm@microchip.com> 159Description: 160 Indicates the current node address. 161Users: 162 163What: /sys/class/most/mostcore/devices/<mdev>/dci/node_position 164Date: June 2016 165KernelVersion: 4.9 166Contact: Christian Gromm <christian.gromm@microchip.com> 167Description: 168 Indicates the current node position. 169Users: 170 171What: /sys/class/most/mostcore/devices/<mdev>/dci/packet_bandwidth 172Date: June 2016 173KernelVersion: 4.9 174Contact: Christian Gromm <christian.gromm@microchip.com> 175Description: 176 Indicates the configured packet bandwidth. 177Users: 178 179What: /sys/class/most/mostcore/devices/<mdev>/dci/sync_ep 180Date: June 2016 181KernelVersion: 4.9 182Contact: Christian Gromm <christian.gromm@microchip.com> 183Description: 184 Triggers the controller's synchronization process for a certain 185 endpoint. 186Users: 187 188What: /sys/class/most/mostcore/devices/<mdev>/<channel>/ 189Date: June 2015 190KernelVersion: 4.3 191Contact: Christian Gromm <christian.gromm@microchip.com> 192Description: 193 For every channel of the device a directory is created, whose 194 name is dictated by the HDM. This enables an application to 195 collect information about the channel's capabilities and 196 configure it. 197Users: 198 199What: /sys/class/most/mostcore/devices/<mdev>/<channel>/available_datatypes 200Date: June 2015 201KernelVersion: 4.3 202Contact: Christian Gromm <christian.gromm@microchip.com> 203Description: 204 Indicates the data types the current channel can transport. 205Users: 206 207What: /sys/class/most/mostcore/devices/<mdev>/<channel>/available_directions 208Date: June 2015 209KernelVersion: 4.3 210Contact: Christian Gromm <christian.gromm@microchip.com> 211Description: 212 Indicates the directions the current channel is capable of. 213Users: 214 215What: /sys/class/most/mostcore/devices/<mdev>/<channel>/number_of_packet_buffers 216Date: June 2015 217KernelVersion: 4.3 218Contact: Christian Gromm <christian.gromm@microchip.com> 219Description: 220 Indicates the number of packet buffers the current channel can 221 handle. 222Users: 223 224What: /sys/class/most/mostcore/devices/<mdev>/<channel>/number_of_stream_buffers 225Date: June 2015 226KernelVersion: 4.3 227Contact: Christian Gromm <christian.gromm@microchip.com> 228Description: 229 Indicates the number of streaming buffers the current channel can 230 handle. 231Users: 232 233What: /sys/class/most/mostcore/devices/<mdev>/<channel>/size_of_packet_buffer 234Date: June 2015 235KernelVersion: 4.3 236Contact: Christian Gromm <christian.gromm@microchip.com> 237Description: 238 Indicates the size of a packet buffer the current channel can 239 handle. 240Users: 241 242What: /sys/class/most/mostcore/devices/<mdev>/<channel>/size_of_stream_buffer 243Date: June 2015 244KernelVersion: 4.3 245Contact: Christian Gromm <christian.gromm@microchip.com> 246Description: 247 Indicates the size of a streaming buffer the current channel can 248 handle. 249Users: 250 251What: /sys/class/most/mostcore/devices/<mdev>/<channel>/set_number_of_buffers 252Date: June 2015 253KernelVersion: 4.3 254Contact: Christian Gromm <christian.gromm@microchip.com> 255Description: 256 This is to configure the number of buffers of the current channel. 257Users: 258 259What: /sys/class/most/mostcore/devices/<mdev>/<channel>/set_buffer_size 260Date: June 2015 261KernelVersion: 4.3 262Contact: Christian Gromm <christian.gromm@microchip.com> 263Description: 264 This is to configure the size of a buffer of the current channel. 265Users: 266 267What: /sys/class/most/mostcore/devices/<mdev>/<channel>/set_direction 268Date: June 2015 269KernelVersion: 4.3 270Contact: Christian Gromm <christian.gromm@microchip.com> 271Description: 272 This is to configure the direction of the current channel. 273 The following strings will be accepted: 274 'dir_tx', 275 'dir_rx' 276Users: 277 278What: /sys/class/most/mostcore/devices/<mdev>/<channel>/set_datatype 279Date: June 2015 280KernelVersion: 4.3 281Contact: Christian Gromm <christian.gromm@microchip.com> 282Description: 283 This is to configure the data type of the current channel. 284 The following strings will be accepted: 285 'control', 286 'async', 287 'sync', 288 'isoc_avp' 289Users: 290 291What: /sys/class/most/mostcore/devices/<mdev>/<channel>/set_subbuffer_size 292Date: June 2015 293KernelVersion: 4.3 294Contact: Christian Gromm <christian.gromm@microchip.com> 295Description: 296 This is to configure the subbuffer size of the current channel. 297Users: 298 299What: /sys/class/most/mostcore/devices/<mdev>/<channel>/set_packets_per_xact 300Date: June 2015 301KernelVersion: 4.3 302Contact: Christian Gromm <christian.gromm@microchip.com> 303Description: 304 This is to configure the number of packets per transaction of 305 the current channel. This is only needed network interface 306 controller is attached via USB. 307Users: 308 309What: /sys/class/most/mostcore/devices/<mdev>/<channel>/channel_starving 310Date: June 2015 311KernelVersion: 4.3 312Contact: Christian Gromm <christian.gromm@microchip.com> 313Description: 314 Indicates whether current channel ran out of buffers. 315Users: 316