On Wed, 21 Aug 2024 15:10:53 -0300 Jason Gunthorpe <jgg@xxxxxxxxxx> wrote: > Create the class, character device and functions for a fwctl driver to > un/register to the subsystem. > > A typical fwctl driver has a sysfs presence like: > > $ ls -l /dev/fwctl/fwctl0 > crw------- 1 root root 250, 0 Apr 25 19:16 /dev/fwctl/fwctl0 > > $ ls /sys/class/fwctl/fwctl0 > dev device power subsystem uevent > > $ ls /sys/class/fwctl/fwctl0/device/infiniband/ > ibp0s10f0 > > $ ls /sys/class/infiniband/ibp0s10f0/device/fwctl/ > fwctl0/ > > $ ls /sys/devices/pci0000:00/0000:00:0a.0/fwctl/fwctl0 > dev device power subsystem uevent > > Which allows userspace to link all the multi-subsystem driver components > together and learn the subsystem specific names for the device's > components. > > Signed-off-by: Jason Gunthorpe <jgg@xxxxxxxxxx> Hi Jason, Tags I'm giving for this are still on a purely technical basis. I'm not taking a position (yet anyway) on whether this is is a good idea in general. I would like that discussion to not risk being distracted by the code state etc though, so FWIW this is nice and clean and looks good to me, so that shouldn't be an issue! Reviewed-by: Jonathan Cameron <Jonathan.Cameron@xxxxxxxxxx>
