diff options
| author | Boris Brezillon <[email protected]> | 2019-12-03 15:15:07 +0100 |
|---|---|---|
| committer | Boris Brezillon <[email protected]> | 2019-12-09 10:02:45 +0100 |
| commit | 35a61fe9218a9d32a93447bdcca1d0f167cd0433 (patch) | |
| tree | 5c6cd23da83aac637ce749cfb6e0aaa8e49b9271 /tools/perf/scripts/python/mem-phys-addr.py | |
| parent | fadf872d9d9274a3be34d8438e0f6bb465c8f98b (diff) | |
drm: Stop accessing encoder->bridge directly
We are about to replace the single-linked bridge list by a double-linked
one based on list.h, leading to the suppression of the encoder->bridge
field. But before we can do that we must provide a
drm_bridge_chain_get_first_bridge() bridge helper and patch all drivers
and core helpers to use it instead of directly accessing encoder->bridge.
Note that we still have 2 drivers (VC4 and Exynos) manipulating the
encoder->bridge field directly because they need to cut the bridge chain
in order to control the enable/disable sequence. This is definitely
not something we want to encourage, so let's keep those 2 oddities
around until we find a better solution.
Signed-off-by: Boris Brezillon <[email protected]>
Reviewed-by: Laurent Pinchart <[email protected]>
Reviewed-by: Neil Armstrong <[email protected]>
Link: https://patchwork.freedesktop.org/patch/msgid/[email protected]
Diffstat (limited to 'tools/perf/scripts/python/mem-phys-addr.py')
0 files changed, 0 insertions, 0 deletions