Back to home page

OSCL-LXR

 
 

    


0001 What:           /sys/bus/platform/devices/.../driver_override
0002 Date:           April 2014
0003 Contact:        Kim Phillips <kim.phillips@freescale.com>
0004 Description:
0005                 This file allows the driver for a device to be specified which
0006                 will override standard OF, ACPI, ID table, and name matching.
0007                 When specified, only a driver with a name matching the value
0008                 written to driver_override will have an opportunity to bind
0009                 to the device.  The override is specified by writing a string
0010                 to the driver_override file (echo vfio-platform > \
0011                 driver_override) and may be cleared with an empty string
0012                 (echo > driver_override).  This returns the device to standard
0013                 matching rules binding.  Writing to driver_override does not
0014                 automatically unbind the device from its current driver or make
0015                 any attempt to automatically load the specified driver.  If no
0016                 driver with a matching name is currently loaded in the kernel,
0017                 the device will not bind to any driver.  This also allows
0018                 devices to opt-out of driver binding using a driver_override
0019                 name such as "none".  Only a single driver may be specified in
0020                 the override, there is no support for parsing delimiters.
0021 
0022 What:           /sys/bus/platform/devices/.../numa_node
0023 Date:           June 2020
0024 Contact:        Barry Song <song.bao.hua@hisilicon.com>
0025 Description:
0026                 This file contains the NUMA node to which the platform device
0027                 is attached. It won't be visible if the node is unknown. The
0028                 value comes from an ACPI _PXM method or a similar firmware
0029                 source. Initial users for this file would be devices like
0030                 arm smmu which are populated by arm64 acpi_iort.
0031 
0032 What:           /sys/bus/platform/devices/.../msi_irqs/
0033 Date:           August 2021
0034 Contact:        Barry Song <song.bao.hua@hisilicon.com>
0035 Description:
0036                 The /sys/devices/.../msi_irqs directory contains a variable set
0037                 of files, with each file being named after a corresponding msi
0038                 irq vector allocated to that device.
0039 
0040 What:           /sys/bus/platform/devices/.../msi_irqs/<N>
0041 Date:           August 2021
0042 Contact:        Barry Song <song.bao.hua@hisilicon.com>
0043 Description:
0044                 This attribute will show "msi" if <N> is a valid msi irq
0045 
0046 What:           /sys/bus/platform/devices/.../modalias
0047 Description:
0048                 Same as MODALIAS in the uevent at device creation.
0049 
0050                 A platform device that it is exposed via devicetree uses:
0051 
0052                         - of:N`of node name`T`type`
0053 
0054                 Other platform devices use, instead:
0055 
0056                         - platform:`driver name`