s390/cio: add dev_busid sysfs entry for each subchannel
authorVineeth Vijayan <vneethv@linux.ibm.com>
Sun, 25 Apr 2021 08:52:38 +0000 (10:52 +0200)
committerVasily Gorbik <gor@linux.ibm.com>
Wed, 18 Aug 2021 08:01:27 +0000 (10:01 +0200)
commitd3683c055212bf910d4e318f7944910ce10dbee6
treee0372b5a25b0492cefbd976a4ae5906785e4cf24
parentcec0c58d34f26a8ed7bf7ca8726608edbac7e958
s390/cio: add dev_busid sysfs entry for each subchannel

Introduce dev_busid, which exports the device-id associated with the
io-subchannel (and message-subchannel). The dev_busid indicates that of
the device which may be physically installed on the corrosponding
subchannel. The dev_busid value "none" indicates that the subchannel
is not valid, there is no I/O device currently associated with the
subchannel.

The dev_busid information would be helpful to write device-specific
udev-rules associated with the subchannel. The dev_busid interface would
be available even when the sch is not bound to any driver or if there is
no operational device connected on it. Hence this attribute can be used to
write udev-rules which are specific to the device associated with the
subchannel.

Signed-off-by: Vineeth Vijayan <vneethv@linux.ibm.com>
Reviewed-by: Peter Oberparleiter <oberpar@linux.ibm.com>
Signed-off-by: Vasily Gorbik <gor@linux.ibm.com>
drivers/s390/cio/css.c