162306a36Sopenharmony_ciWhat: /sys/bus/platform/devices/.../driver_override 262306a36Sopenharmony_ciDate: April 2014 362306a36Sopenharmony_ciContact: Kim Phillips <kim.phillips@freescale.com> 462306a36Sopenharmony_ciDescription: 562306a36Sopenharmony_ci This file allows the driver for a device to be specified which 662306a36Sopenharmony_ci will override standard OF, ACPI, ID table, and name matching. 762306a36Sopenharmony_ci When specified, only a driver with a name matching the value 862306a36Sopenharmony_ci written to driver_override will have an opportunity to bind 962306a36Sopenharmony_ci to the device. The override is specified by writing a string 1062306a36Sopenharmony_ci to the driver_override file (echo vfio-platform > \ 1162306a36Sopenharmony_ci driver_override) and may be cleared with an empty string 1262306a36Sopenharmony_ci (echo > driver_override). This returns the device to standard 1362306a36Sopenharmony_ci matching rules binding. Writing to driver_override does not 1462306a36Sopenharmony_ci automatically unbind the device from its current driver or make 1562306a36Sopenharmony_ci any attempt to automatically load the specified driver. If no 1662306a36Sopenharmony_ci driver with a matching name is currently loaded in the kernel, 1762306a36Sopenharmony_ci the device will not bind to any driver. This also allows 1862306a36Sopenharmony_ci devices to opt-out of driver binding using a driver_override 1962306a36Sopenharmony_ci name such as "none". Only a single driver may be specified in 2062306a36Sopenharmony_ci the override, there is no support for parsing delimiters. 2162306a36Sopenharmony_ci 2262306a36Sopenharmony_ciWhat: /sys/bus/platform/devices/.../numa_node 2362306a36Sopenharmony_ciDate: June 2020 2462306a36Sopenharmony_ciContact: Barry Song <song.bao.hua@hisilicon.com> 2562306a36Sopenharmony_ciDescription: 2662306a36Sopenharmony_ci This file contains the NUMA node to which the platform device 2762306a36Sopenharmony_ci is attached. It won't be visible if the node is unknown. The 2862306a36Sopenharmony_ci value comes from an ACPI _PXM method or a similar firmware 2962306a36Sopenharmony_ci source. Initial users for this file would be devices like 3062306a36Sopenharmony_ci arm smmu which are populated by arm64 acpi_iort. 3162306a36Sopenharmony_ci 3262306a36Sopenharmony_ciWhat: /sys/bus/platform/devices/.../msi_irqs/ 3362306a36Sopenharmony_ciDate: August 2021 3462306a36Sopenharmony_ciContact: Barry Song <song.bao.hua@hisilicon.com> 3562306a36Sopenharmony_ciDescription: 3662306a36Sopenharmony_ci The /sys/devices/.../msi_irqs directory contains a variable set 3762306a36Sopenharmony_ci of files, with each file being named after a corresponding msi 3862306a36Sopenharmony_ci irq vector allocated to that device. 3962306a36Sopenharmony_ci 4062306a36Sopenharmony_ciWhat: /sys/bus/platform/devices/.../msi_irqs/<N> 4162306a36Sopenharmony_ciDate: August 2021 4262306a36Sopenharmony_ciContact: Barry Song <song.bao.hua@hisilicon.com> 4362306a36Sopenharmony_ciDescription: 4462306a36Sopenharmony_ci This attribute will show "msi" if <N> is a valid msi irq 4562306a36Sopenharmony_ci 4662306a36Sopenharmony_ciWhat: /sys/bus/platform/devices/.../modalias 4762306a36Sopenharmony_ciDescription: 4862306a36Sopenharmony_ci Same as MODALIAS in the uevent at device creation. 4962306a36Sopenharmony_ci 5062306a36Sopenharmony_ci A platform device that it is exposed via devicetree uses: 5162306a36Sopenharmony_ci 5262306a36Sopenharmony_ci - of:N`of node name`T`type` 5362306a36Sopenharmony_ci 5462306a36Sopenharmony_ci Other platform devices use, instead: 5562306a36Sopenharmony_ci 5662306a36Sopenharmony_ci - platform:`driver name` 57