Messages in this thread | | | Date | Fri, 6 Apr 2012 17:28:22 -0700 | From | Asai Thambi S P <> | Subject | Re: [PATCH 2/5] mtip32xx: Add new sysfs entry 'status' and fix restart port |
| |
On 4/6/2012 4:30 PM, Greg KH wrote:
>>> > > What do the existing api files show for block devices? >>> > > >> > >> > >> > I was looking into sysfs-driver-* files to create sysfs-driver-mtip32xx. >> > These files have paths like /sys/bus/pci/*, /sys/devices/*, >> > /sys/class/bluetooth/*, etc. >> > >> > There are sysfs-block-dm and sysfs-block-zram files with >> > /sys/block/dm-<num>/dm/* and /sys/block/zram<id>/*. If I have to follow >> > these, then the file would be sysfs-driver-rssd with /sys/block/<disk>/*. >> > >> > Let me know. > /sys/block/rs*/ would be the right place, right? You know the tree > better than I do as you have this hardware and can see where in sysfs > the files really are :)
Yes, I started that way and found /sys/block/rssda is a sym link to /sys/devices/pci0000\:00/0000\:00\:01.0/0000\:01\:00.0/block/rssda/. That is when I got the doubt, is it ok to use the sym link path or should use the actual path.
I will go ahead with filename sysfs-block-rssd and path /sys/block/rssd*/<entry>.
Thanks.
-- Regards, Asai Thambi
| |