Vineeth Vijayan fd53ec768c s390/cio: add dev_busid sysfs entry for each subchannel ... [ Upstream commit d3683c055212bf910d4e318f7944910ce10dbee6 ] 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> Signed-off-by: Sasha Levin <sashal@kernel.org>		2024-07-05 19:09:35 +02:00
..
airq.c
blacklist.c
blacklist.h
ccwgroup.c
ccwreq.c
chp.c	s390/cio: dont call css_wait_for_slow_path() inside a lock	2021-07-14 16:55:43 +02:00
chp.h
chsc_sch.c
chsc_sch.h
chsc.c	s390/cio: dont call css_wait_for_slow_path() inside a lock	2021-07-14 16:55:43 +02:00
chsc.h
cio_debug.h
cio.c
cio.h
cmf.c
crw.c
css.c	s390/cio: add dev_busid sysfs entry for each subchannel	2024-07-05 19:09:35 +02:00
css.h
device_fsm.c
device_id.c
device_ops.c
device_pgid.c
device_status.c
device.c
device.h
eadm_sch.c
eadm_sch.h
fcx.c
idset.c
idset.h
io_sch.h
ioasm.c
ioasm.h
isc.c
itcw.c
Makefile
orb.h
qdio_debug.c
qdio_debug.h
qdio_main.c
qdio_setup.c
qdio_thinint.c
qdio.h
scm.c
trace.c
trace.h
vfio_ccw_async.c
vfio_ccw_chp.c
vfio_ccw_cp.c
vfio_ccw_cp.h
vfio_ccw_drv.c	vfio-ccw: Serialize FSM IDLE state with I/O completion	2021-06-16 12:01:35 +02:00
vfio_ccw_fsm.c
vfio_ccw_ops.c
vfio_ccw_private.h
vfio_ccw_trace.c
vfio_ccw_trace.h