diff options
| author | Philipp Zabel <[email protected]> | 2016-05-12 15:00:44 +0200 |
|---|---|---|
| committer | Philipp Zabel <[email protected]> | 2016-05-23 12:35:11 +0200 |
| commit | 310944d148e3600dcff8b346bee7fa01d34903b1 (patch) | |
| tree | ca14e1344f6122ee02f005e5e67bf8d9a75f8f80 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | 2dcd0af568b0cf583645c8a317dd12e344b1c72a (diff) | |
drm/imx: Match imx-ipuv3-crtc components using device node in platform data
The component master driver imx-drm-core matches component devices using
their of_node. Since commit 950b410dd1ab ("gpu: ipu-v3: Fix imx-ipuv3-crtc
module autoloading"), the imx-ipuv3-crtc dev->of_node is not set during
probing. Before that, of_node was set and caused an of: modalias to be
used instead of the platform: modalias, which broke module autoloading.
On the other hand, if dev->of_node is not set yet when the imx-ipuv3-crtc
probe function calls component_add, component matching in imx-drm-core
fails. While dev->of_node will be set once the next component tries to
bring up the component master, imx-drm-core component binding will never
succeed if one of the crtc devices is probed last.
Add of_node to the component platform data and match against the
pdata->of_node instead of dev->of_node in imx-drm-core to work around
this problem.
Cc: <[email protected]> # 4.4.x
Fixes: 950b410dd1ab ("gpu: ipu-v3: Fix imx-ipuv3-crtc module autoloading")
Signed-off-by: Philipp Zabel <[email protected]>
Tested-by: Fabio Estevam <[email protected]>
Tested-by: Lothar Waßmann <[email protected]>
Tested-by: Heiko Schocher <[email protected]>
Tested-by: Chris Ruehl <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions