linux/drivers/s390
Vineeth Vijayan d3683c0552 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>
2021-08-18 10:01:27 +02:00
..
block s390/dasd: remove debug printk 2021-07-27 09:39:14 +02:00
char s390/sclp: replace deprecated CPU-hotplug functions 2021-08-05 14:10:53 +02:00
cio s390/cio: add dev_busid sysfs entry for each subchannel 2021-08-18 10:01:27 +02:00
crypto s390/ap: Rework ap_dqap to deal with messages greater than recv buffer 2021-07-08 15:37:27 +02:00
net s390/qdio: clarify reporting of errors to the drivers 2021-07-27 09:39:18 +02:00
scsi s390/qdio: clarify reporting of errors to the drivers 2021-07-27 09:39:18 +02:00
virtio virtio/s390: get rid of open-coded kvm hypercall 2021-06-28 11:18:28 +02:00
Makefile s390: remove pointless drivers-y in drivers/s390/Makefile 2019-09-16 13:21:51 +02:00