57 lines · plain
1What: /sys/bus/css/devices/.../type2Date: March 20083Contact: linux-s390@vger.kernel.org4Description: Contains the subchannel type, as reported by the hardware.5 This attribute is present for all subchannel types.6 7What: /sys/bus/css/devices/.../modalias8Date: March 20089Contact: linux-s390@vger.kernel.org10Description: Contains the module alias as reported with uevents.11 It is of the format css:t<type> and present for all12 subchannel types.13 14What: /sys/bus/css/drivers/io_subchannel/.../chpids15Date: December 200216Contact: linux-s390@vger.kernel.org17Description: Contains the ids of the channel paths used by this18 subchannel, as reported by the channel subsystem19 during subchannel recognition.20 21 Note: This is an I/O-subchannel specific attribute.22Users: s390-tools, HAL23 24What: /sys/bus/css/drivers/io_subchannel/.../pimpampom25Date: December 200226Contact: linux-s390@vger.kernel.org27Description: Contains the PIM/PAM/POM values, as reported by the28 channel subsystem when last queried by the common I/O29 layer (this implies that this attribute is not necessarily30 in sync with the values current in the channel subsystem).31 32 Note: This is an I/O-subchannel specific attribute.33Users: s390-tools, HAL34 35What: /sys/bus/css/devices/.../driver_override36Date: June 201937Contact: linux-s390@vger.kernel.org38Description: This file allows the driver for a device to be specified. When39 specified, only a driver with a name matching the value written40 to driver_override will have an opportunity to bind to the41 device. The override is specified by writing a string to the42 driver_override file (echo vfio-ccw > driver_override) and43 may be cleared with an empty string (echo > driver_override).44 This returns the device to standard matching rules binding.45 Writing to driver_override does not automatically unbind the46 device from its current driver or make any attempt to47 automatically load the specified driver. If no driver with a48 matching name is currently loaded in the kernel, the device49 will not bind to any driver. This also allows devices to50 opt-out of driver binding using a driver_override name such as51 "none". Only a single driver may be specified in the override,52 there is no support for parsing delimiters.53 54 Note that unlike the mechanism of the same name for pci, this55 file does not allow to override basic matching rules. I.e.,56 the driver must still match the subchannel type of the device.57