mirror of
https://github.com/raspberrypi/linux.git
synced 2025-12-09 19:39:56 +00:00
09d1157182
[ Upstream commitd07fdf9225] DRM may support multiple in-kernel clients that run as soon as a DRM driver has been registered. To select the client(s) in a single place, introduce drm_client_setup(). Drivers that call the new helper automatically instantiate the kernel's configured default clients. Only fbdev emulation is currently supported. Later versions can add support for DRM-based logging, a boot logo or even a console. Some drivers handle the color mode for clients internally. Provide the helper drm_client_setup_with_color_mode() for them. Using the new interface requires the driver to select DRM_CLIENT_SELECTION in its Kconfig. For now this only enables the client-setup helpers if the fbdev client has been configured by the user. A future patchset will further modularize client support and rework DRM_CLIENT_SELECTION to select the correct dependencies for all its clients. v5: - add CONFIG_DRM_CLIENT_SELECTION und DRM_CLIENT_SETUP v4: - fix docs for drm_client_setup_with_fourcc() (Geert) v3: - fix build error v2: - add drm_client_setup_with_fourcc() (Laurent) - push default-format handling into actual clients Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de> Reviewed-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com> Link: https://patchwork.freedesktop.org/patch/msgid/20240924071734.98201-5-tzimmermann@suse.de Stable-dep-of:6b481ab0e6("drm/nouveau: select FW caching") Signed-off-by: Sasha Levin <sashal@kernel.org>
67 lines
2.1 KiB
C
67 lines
2.1 KiB
C
// SPDX-License-Identifier: MIT
|
|
|
|
#include <drm/drm_client_setup.h>
|
|
#include <drm/drm_device.h>
|
|
#include <drm/drm_fbdev_client.h>
|
|
#include <drm/drm_fourcc.h>
|
|
#include <drm/drm_print.h>
|
|
|
|
/**
|
|
* drm_client_setup() - Setup in-kernel DRM clients
|
|
* @dev: DRM device
|
|
* @format: Preferred pixel format for the device. Use NULL, unless
|
|
* there is clearly a driver-preferred format.
|
|
*
|
|
* This function sets up the in-kernel DRM clients. Restore, hotplug
|
|
* events and teardown are all taken care of.
|
|
*
|
|
* Drivers should call drm_client_setup() after registering the new
|
|
* DRM device with drm_dev_register(). This function is safe to call
|
|
* even when there are no connectors present. Setup will be retried
|
|
* on the next hotplug event.
|
|
*
|
|
* The clients are destroyed by drm_dev_unregister().
|
|
*/
|
|
void drm_client_setup(struct drm_device *dev, const struct drm_format_info *format)
|
|
{
|
|
int ret;
|
|
|
|
ret = drm_fbdev_client_setup(dev, format);
|
|
if (ret)
|
|
drm_warn(dev, "Failed to set up DRM client; error %d\n", ret);
|
|
}
|
|
EXPORT_SYMBOL(drm_client_setup);
|
|
|
|
/**
|
|
* drm_client_setup_with_fourcc() - Setup in-kernel DRM clients for color mode
|
|
* @dev: DRM device
|
|
* @fourcc: Preferred pixel format as 4CC code for the device
|
|
*
|
|
* This function sets up the in-kernel DRM clients. It is equivalent
|
|
* to drm_client_setup(), but expects a 4CC code as second argument.
|
|
*/
|
|
void drm_client_setup_with_fourcc(struct drm_device *dev, u32 fourcc)
|
|
{
|
|
drm_client_setup(dev, drm_format_info(fourcc));
|
|
}
|
|
EXPORT_SYMBOL(drm_client_setup_with_fourcc);
|
|
|
|
/**
|
|
* drm_client_setup_with_color_mode() - Setup in-kernel DRM clients for color mode
|
|
* @dev: DRM device
|
|
* @color_mode: Preferred color mode for the device
|
|
*
|
|
* This function sets up the in-kernel DRM clients. It is equivalent
|
|
* to drm_client_setup(), but expects a color mode as second argument.
|
|
*
|
|
* Do not use this function in new drivers. Prefer drm_client_setup() with a
|
|
* format of NULL.
|
|
*/
|
|
void drm_client_setup_with_color_mode(struct drm_device *dev, unsigned int color_mode)
|
|
{
|
|
u32 fourcc = drm_driver_color_mode_format(dev, color_mode);
|
|
|
|
drm_client_setup_with_fourcc(dev, fourcc);
|
|
}
|
|
EXPORT_SYMBOL(drm_client_setup_with_color_mode);
|