drivers/gpu/drm/solomon/Kconfig

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/solomon/Kconfig

Extension

[no extension]

Size

1033 bytes

Lines

33

Domain

Driver Families

Bucket

drivers/gpu

Inferred role

Driver Families: build/configuration rule

Status

atlas-only

Why This File Exists

Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.

• Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.

Dependency Surface

• No C-style include directives detected by the generator.

Detected Declarations

• No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

config DRM_SSD130X
	tristate "DRM support for Solomon SSD13xx OLED displays"
	depends on DRM && MMU
	select BACKLIGHT_CLASS_DEVICE
	select DRM_CLIENT_SELECTION
	select DRM_GEM_SHMEM_HELPER
	select DRM_KMS_HELPER
	help
	  DRM driver for the SSD13xx Solomon and SINO WEALTH SH110x OLED
	  controllers. This is only for the core driver, a driver for the
	  appropriate bus transport in your chip also must be selected.

	  If M is selected the module will be called ssd130x.

config DRM_SSD130X_I2C
	tristate "DRM support for Solomon SSD13xx OLED displays (I2C bus)"
	depends on DRM_SSD130X && I2C
	select REGMAP_I2C
	help
	  Say Y here if the SSD13xx or SH110x OLED display is connected via
	  I2C bus.

	  If M is selected the module will be called ssd130x-i2c.

config DRM_SSD130X_SPI
	tristate "DRM support for Solomon SSD13xx OLED displays (SPI bus)"
	depends on DRM_SSD130X && SPI
	select REGMAP
	help
	  Say Y here if the SSD13xx OLED display is connected via SPI bus.

	  If M is selected the module will be called ssd130x-spi.

Annotation

• Atlas domain: Driver Families / drivers/gpu.
• Implementation status: atlas-only.

Implementation Notes

• This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
• Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
• Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.