diff options
| author | Heikki Krogerus <[email protected]> | 2021-08-17 23:51:58 +0200 |
|---|---|---|
| committer | Hans de Goede <[email protected]> | 2021-09-09 12:59:07 +0200 |
| commit | a481d0e80eabbc3fed666103744aeaf47f63e708 (patch) | |
| tree | bd2bf59d9c33dff59abf7a9e1a0b8e52aca3124a /tools/perf/scripts/python/bin/export-to-postgresql-report | |
| parent | 3e31d057431a4638f891db303044f761809adb86 (diff) | |
drm/i915: Associate ACPI connector nodes with connector entries (v2)
On Intel platforms we know that the ACPI connector device
node order will follow the order the driver (i915) decides.
The decision is made using the custom Intel ACPI OpRegion
(intel_opregion.c), though the driver does not actually know
that the values it sends to ACPI there are used for
associating a device node for the connectors, and assigning
address for them.
In reality that custom Intel ACPI OpRegion actually violates
ACPI specification (we supply dynamic information to objects
that are defined static, for example _ADR), however, it
makes assigning correct connector node for a connector entry
straightforward (it's one-on-one mapping).
Changes in v2 (Hans de goede):
- Take a reference on the fwnode which we assign to the connector,
for ACPI nodes this is a no-op but in the future we may see
software-fwnodes assigned to connectors which are ref-counted.
Signed-off-by: Heikki Krogerus <[email protected]>
Tested-by: Heikki Krogerus <[email protected]>
Signed-off-by: Hans de Goede <[email protected]>
Reviewed-by: Lyude Paul <[email protected]>
Link: https://patchwork.freedesktop.org/patch/msgid/[email protected]
Diffstat (limited to 'tools/perf/scripts/python/bin/export-to-postgresql-report')
0 files changed, 0 insertions, 0 deletions