Commits on Source (13)
-
The fb already contains a DRM fd for later use. So just use that one instead of fetching it from the backend. This is necessary if the fbs are allocated on different devices, since otherwise the wrong device might be used to get the fd of the passed fb. Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de> Signed-off-by: Michael Tretter <m.tretter@pengutronix.de>
83d1eafd -
The gbm_format is the same as the drm format used by the pixel format. Print the format name using the pixel format in the error message to make the error message easier to understand for humans. Signed-off-by: Michael Tretter <m.tretter@pengutronix.de>
00b74293 -
Get the backend at the beginning of the function instead of retrieving it from another object in the debug statement. This simplifies refactoring, as the debug statement is not affected by changes how the backend is retrieved. Signed-off-by: Michael Tretter <m.tretter@pengutronix.de>
2860933d -
Extract the kms device from the backend to allow a better separation of the backend and the kms device. This will allow to handle multiple kms devices with a single drm backend. Signed-off-by: Michael Tretter <m.tretter@pengutronix.de>
0d967bd7 -
The atomic commit is device specific. If we have multiple kms devices, we need to know which device was used for the atomic commit. Pass the device instead of the backend through the atomic commit. Signed-off-by: Michael Tretter <m.tretter@pengutronix.de>
d89fcf10 -
The fbs are specific to the device on which they will be displayed. Therefore, we have to tell which device shall be used when we are creating the fb. Signed-off-by: Michael Tretter <m.tretter@pengutronix.de>
101c0f6b -
The scanout format for the dma-buf feedback are specific to the kms device that is used for scanout. Therefore, we have to pass the device of the output when retrieving the scanout formats. Signed-off-by: Michael Tretter <m.tretter@pengutronix.de>
615a37dc -
The commits happen per device instead of per backend. The pending state is therefore per device as well. Allow to retrieve the device from the pending state. Signed-off-by: Michael Tretter <m.tretter@pengutronix.de>
c4685d94 -
The outputs, heads, crtcs, and connectors are specific to a drm device and not the backend in general. Link them to the device that they belong to to be able to retrieve the respective device. Signed-off-by: Michael Tretter <m.tretter@pengutronix.de>
345e705e -
The compositor lists the heads from all devices, but we must only disable the connectors that belong to the current device. Therefore, other heads must be ignored. Signed-off-by: Michael Tretter <m.tretter@pengutronix.de>
d990c6a9 -
If Weston receives a hotplug event, it has to check if the hotplug device actually belongs to the drm device before updating the heads of the device. The hotplug event should only remove heads that belong to the device and must not change heads of other devices. Signed-off-by: Michael Tretter <m.tretter@pengutronix.de>
6e36787d -
If we have multiple drm devices, we cannot use the drm device from the backend, because we would only get the primary device and not the device of the output. Signed-off-by: Michael Tretter <m.tretter@pengutronix.de>
deebfd99 -
The drm_device is initialized as a side effect of the (badly named) drm_device_is_kms function. Explicitly pass the drm_device to be able to initialize kms devices that are not the main drm device of the drm backend. Signed-off-by: Michael Tretter <m.tretter@pengutronix.de>
dfceb602
This diff is collapsed.
This diff is collapsed.