diff options
| author | Daniel Vetter <[email protected]> | 2019-11-15 10:21:15 +0100 |
|---|---|---|
| committer | Daniel Vetter <[email protected]> | 2019-11-22 18:09:18 +0100 |
| commit | d268f42e68561594d304f9255f809b3ee50b1cdc (patch) | |
| tree | 93b8de18d4a92d2b319592e17a9cc493ff1d20d4 /tools/perf/scripts/python/bin/stackcollapse-report | |
| parent | 92ec07677107974c31b32030a4f897398e452ca9 (diff) | |
drm/mediatek: don't open-code drm_gem_fb_create
Aside: There's a few other fb_create implementations which
simply check for valid buffer format (or an approximation thereof),
and then call drm_gem_fb_create. For atomic drivers at least we could
walk all planes and make sure the format/modifier combo is valid,
and remove even more code.
For non-atomic drivers that's not possible, since the format list for
the primary buffer might be garbage (and most likely it is).
Also delete mtk_drm_fb.[hc] since it would now only contain one
function.
Acked-by: CK Hu <[email protected]>
Cc: CK Hu <[email protected]>
Cc: Philipp Zabel <[email protected]>
Cc: Matthias Brugger <[email protected]>
Cc: [email protected]
Cc: [email protected]
Signed-off-by: Daniel Vetter <[email protected]>
Link: https://patchwork.freedesktop.org/patch/msgid/[email protected]
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-report')
0 files changed, 0 insertions, 0 deletions