# SPDX-License-Identifier: GPL-2.0-only

config DRM_HOBOT
	tristate "DRM Support for Hobot SoC"
	depends on DRM
	select DRM_GEM_CMA_HELPER
	select DRM_PANEL
	select VIDEOMODE_HELPERS
	select DRM_DW_MIPI_DSI if HOBOT_DW_MIPI_DSI
	help
	  Choose this option if you have a Hobot soc chipset.
	  This driver provides kernel mode setting and buffer
	  management to userspace. This driver does not provide
	  2D or 3D acceleration; acceleration is performed by other
	  IP found on the SoC.

config HOBOT_CHIP_SUPER
	tristate "D-Robotics Super chipset"
	default y

config HOBOT_CHIP_ULTRA
	tristate "Hobot Journey5 chipset"
	default n

config HOBOT_DRM_IDU
	tristate "Hobot IDU Driver"
	default n

config HOBOT_DRM_MIPI_DSI
	tristate "Hobot specific extensions for Synopsys DW MIPI DSI"
	select DRM_MIPI_DSI

config HOBOT_MIPI_DSI_RESOLUTION_QUIRK
	bool "Enable resolution-specific quirks for 2K and 4K modes"
	depends on HOBOT_DRM_MIPI_DSI
	help
	  Enable special handling for specific resolutions (e.g., 2560x1440 @ 60Hz)
	  and 4K modes, such as adjustments to mipiclk and hline timing.

	  This option is dependent on HOBOT_DRM_MIPI_DSI being enabled.


config HOBOT_DRM_MIPI_CSI_TX
	tristate "Hobot specific extensions for Synopsys DW MIPI CSI-TX"
	select DRM_MIPI_DSI
	select HOBOT_DRM_MIPI_DPHY

config HOBOT_DRM_MIPI_DPHY
	tristate "Hobot specific extensions for Synopsys DW MIPI TX DPHY"


config HOBOT_MMU
	tristate "Hobot MMU"
	depends on HOBOT_DRM_IDU

config HOBOT_DISPLAY_WRITEBACK
	tristate "Hobot IDU Writeback"
	depends on HOBOT_CHIP_SUPER
	default n

config DISP_SPARKLER_DEBUG
	tristate "Sparkler environment"
	default n

config HOBOT_IDE_WRAPPER
	tristate "IDE wrapper driver"
	depends on HOBOT_CHIP_SUPER
	default n

config HOBOT_GEM_ION
	bool "GEM support ion interfaces"
	depends on ION
	help
	  HB GEM is able to using ION interfaces when ION is enabled. ION is a
	  generalized memory manager to address the issue of fragmented memory
	  management interfaces across different Android devices. ION also enables
	  its clients to share buffers, hence it treads the same ground as the DMA
	  buffer sharing framework (DMABUF).

source "../hobot-drivers/ide/hobot-panel/Kconfig"
