1*4882a593SmuzhiyunWhat: /sys/class/rapidio_port 2*4882a593SmuzhiyunDescription: 3*4882a593Smuzhiyun On-chip RapidIO controllers and PCIe-to-RapidIO bridges 4*4882a593Smuzhiyun (referenced as "Master Port" or "mport") are presented in sysfs 5*4882a593Smuzhiyun as the special class of devices: "rapidio_port". 6*4882a593Smuzhiyun The /sys/class/rapidio_port subdirectory contains individual 7*4882a593Smuzhiyun subdirectories named as "rapidioN" where N = mport ID registered 8*4882a593Smuzhiyun with RapidIO subsystem. 9*4882a593Smuzhiyun 10*4882a593Smuzhiyun NOTE: An mport ID is not a RapidIO destination ID assigned to a 11*4882a593Smuzhiyun given local mport device. 12*4882a593Smuzhiyun 13*4882a593SmuzhiyunWhat: /sys/class/rapidio_port/rapidioN/sys_size 14*4882a593SmuzhiyunDate: Apr, 2014 15*4882a593SmuzhiyunKernelVersion: v3.15 16*4882a593SmuzhiyunContact: Matt Porter <mporter@kernel.crashing.org>, 17*4882a593Smuzhiyun Alexandre Bounine <alexandre.bounine@idt.com> 18*4882a593SmuzhiyunDescription: 19*4882a593Smuzhiyun (RO) reports RapidIO common transport system size: 20*4882a593Smuzhiyun 21*4882a593Smuzhiyun 0 = small (8-bit destination ID, max. 256 devices), 22*4882a593Smuzhiyun 23*4882a593Smuzhiyun 1 = large (16-bit destination ID, max. 65536 devices). 24*4882a593Smuzhiyun 25*4882a593SmuzhiyunWhat: /sys/class/rapidio_port/rapidioN/port_destid 26*4882a593SmuzhiyunDate: Apr, 2014 27*4882a593SmuzhiyunKernelVersion: v3.15 28*4882a593SmuzhiyunContact: Matt Porter <mporter@kernel.crashing.org>, 29*4882a593Smuzhiyun Alexandre Bounine <alexandre.bounine@idt.com> 30*4882a593SmuzhiyunDescription: 31*4882a593Smuzhiyun 32*4882a593Smuzhiyun(RO) reports RapidIO destination ID assigned to the given 33*4882a593SmuzhiyunRapidIO mport device. If value 0xFFFFFFFF is returned this means 34*4882a593Smuzhiyunthat no valid destination ID have been assigned to the mport 35*4882a593Smuzhiyun(yet). Normally, before enumeration/discovery have been executed 36*4882a593Smuzhiyunonly fabric enumerating mports have a valid destination ID 37*4882a593Smuzhiyunassigned to them using "hdid=..." rapidio module parameter. 38*4882a593Smuzhiyun 39*4882a593SmuzhiyunAfter enumeration or discovery was performed for a given mport device, 40*4882a593Smuzhiyunthe corresponding subdirectory will also contain subdirectories for each 41*4882a593Smuzhiyunchild RapidIO device connected to the mport. 42*4882a593Smuzhiyun 43*4882a593SmuzhiyunThe example below shows mport device subdirectory with several child RapidIO 44*4882a593Smuzhiyundevices attached to it:: 45*4882a593Smuzhiyun 46*4882a593Smuzhiyun [rio@rapidio ~]$ ls /sys/class/rapidio_port/rapidio0/ -l 47*4882a593Smuzhiyun total 0 48*4882a593Smuzhiyun drwxr-xr-x 3 root root 0 Feb 11 15:10 00:e:0001 49*4882a593Smuzhiyun drwxr-xr-x 3 root root 0 Feb 11 15:10 00:e:0004 50*4882a593Smuzhiyun drwxr-xr-x 3 root root 0 Feb 11 15:10 00:e:0007 51*4882a593Smuzhiyun drwxr-xr-x 3 root root 0 Feb 11 15:10 00:s:0002 52*4882a593Smuzhiyun drwxr-xr-x 3 root root 0 Feb 11 15:10 00:s:0003 53*4882a593Smuzhiyun drwxr-xr-x 3 root root 0 Feb 11 15:10 00:s:0005 54*4882a593Smuzhiyun lrwxrwxrwx 1 root root 0 Feb 11 15:11 device -> ../../../0000:01:00.0 55*4882a593Smuzhiyun -r--r--r-- 1 root root 4096 Feb 11 15:11 port_destid 56*4882a593Smuzhiyun drwxr-xr-x 2 root root 0 Feb 11 15:11 power 57*4882a593Smuzhiyun lrwxrwxrwx 1 root root 0 Feb 11 15:04 subsystem -> ../../../../../../class/rapidio_port 58*4882a593Smuzhiyun -r--r--r-- 1 root root 4096 Feb 11 15:11 sys_size 59*4882a593Smuzhiyun -rw-r--r-- 1 root root 4096 Feb 11 15:04 uevent 60