summaryrefslogtreecommitdiffstats
path: root/sound/parisc/harmony.c
diff options
context:
space:
mode:
authorRafael J. Wysocki <rafael.j.wysocki@intel.com>2015-04-13 00:29:36 +0200
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2015-04-13 00:29:36 +0200
commit8765c5ba19490c9167fe0c4e05c2dfdcc39873a3 (patch)
treed52a854777ef8f65e272277325e38886aa2644e8 /sound/parisc/harmony.c
parent2b9c698efa58bf7d9a0d3d3b28115cf9e55ca818 (diff)
downloadtalos-obmc-linux-8765c5ba19490c9167fe0c4e05c2dfdcc39873a3.tar.gz
talos-obmc-linux-8765c5ba19490c9167fe0c4e05c2dfdcc39873a3.zip
ACPI / scan: Rework modalias creation when "compatible" is present
Currently, the ACPI modalias creation covers two mutually exclusive cases: If the PRP0001 device ID is present in the device's list of ACPI/PNP IDs and the "compatible" property is present in _DSD, the created modalias will follow the OF rules of modalias creation. Otherwise, ACPI rules are used. However, that is not really desirable, because the presence of PRP0001 in the list of device IDs generally does not preclude using other ACPI/PNP IDs with that device and those other IDs may be of higher priority. In those cases, the other IDs should take preference over PRP0001 and therefore they also should be present in the modalias. For this reason, rework the modalias creation for ACPI so that it shows both the ACPI-style and OF-style modalias strings if the device has a non-empty list of ACPI/PNP IDs (other than PRP0001) and a valid "compatible" property at the same time. Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com> Tested-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Diffstat (limited to 'sound/parisc/harmony.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud