Commits on Source (5)
-
Leandro Ribeiro authored
As we are not using the returned value, so let's change to void. Signed-off-by: Leandro Ribeiro <leandro.ribeiro@collabora.com>
8fc9d68f -
Leandro Ribeiro authored
It makes no sense to keep the scanout tranche on the dma-buf feedback if there are no overlay planes available. So start to remove it. Signed-off-by: Leandro Ribeiro <leandro.ribeiro@collabora.com>
0251c052 -
Leandro Ribeiro authored
We log the reasons why the fb of a certain view was not placed in an overlay plane and use that for debug purposes. With these reasons we also decide if the scanout tranche should be included on the dma-buf feedback or not. For instance: 1. If the reason is the incompatibility between the format/modifier pair of the fb and those supported by the KMS device, the scanout tranche is added and feedback is re-sent (so that the client can re-allocate with parameters that makes it eligible for direct scanout). 2. If the reason is because we have no overlay planes available, the scanout tranche is useless. So the scanout tranche is removed and the feedback re-sent (so that clients can re-allocate with parameters optimal for the render device). Also, when we detect that a view is eligible for direct scanout, we don't even consider sending new feedback, as our interpretation of the dma-buf feedback spec was that we should avoid bothering clients with new feedback when they are already hitting direct scanout. After some discussions and clarifications regarding the spec, we've realized that Weston should start to also include the scanout tranche even when the compositor is able to place client's content on overlay planes. Basically, because this gives a chance for clients to re-allocate with the proper parameters (not only format/modifier pair, but also the target_device and the flags) from the scanout tranche. In this patch we start doing this. Signed-off-by: Leandro Ribeiro <leandro.ribeiro@collabora.com>
c9b7c708 -
Leandro Ribeiro authored
Cosmetic changes that makes dmabuf_feedback_maybe_update() easier to read. Signed-off-by: Leandro Ribeiro <leandro.ribeiro@collabora.com>
6517accf -
Leandro Ribeiro authored
There's a comment explaining how to hack the DRM-backend in order to fake that a certain format is not supported by the KMS device. This is useful in order to test dma-buf feedback implementations using the simple-dmabuf-feedback client. But with recent changes on the DRM-backend, this got outdated. Drop this comment, as everyone interested in this client is probably familiar enough with the DRM-backend in order to do that. Also made some adjustments to other comments explaining how this client works. Signed-off-by: Leandro Ribeiro <leandro.ribeiro@collabora.com>
190770e3