OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/drivers/display/Kconfig.intel_multibootfb

11 lines
317 B
Plaintext
Raw Normal View History

drivers: display: framebuffer: rework to make it self-contained The "framebuf" driver was an incomplete driver expecting _clients_ to implement missing functionality (i.e. init and device definition) outside of the driver. This pattern of scattering driver code throughout the tree is not common (if used at all). If certain drivers share functionality, one can create a common module within the subsystem (see e.g. ILI9XXX drivers). The _generic_ framebuffer code was only used to implement the Intel Multiboot framebuffer driver. This patch centralizes all the scattered code in the subsystem and adjusts the driver name to "intel_multibootfb" to make things clear. If there's ever another framebuffer driver that shares code, it can be split into multiple modules. Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
2022-08-24 19:32:15 +08:00
# Copyright (c) 2017 Intel Corporation
# SPDX-License-Identifier: Apache-2.0
config INTEL_MULTIBOOTFB_DISPLAY
bool "Intel Multiboot Framebuffer"
default y
drivers: display: intel_multibootfb: convert to DT Convert the device to be Devicetree based. Adjusted tests and other areas that were using old Kconfig properties. Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
2022-08-24 19:54:35 +08:00
depends on MULTIBOOT && MULTIBOOT_INFO && \
DT_HAS_INTEL_MULTIBOOT_FRAMEBUFFER_ENABLED
drivers: display: framebuffer: rework to make it self-contained The "framebuf" driver was an incomplete driver expecting _clients_ to implement missing functionality (i.e. init and device definition) outside of the driver. This pattern of scattering driver code throughout the tree is not common (if used at all). If certain drivers share functionality, one can create a common module within the subsystem (see e.g. ILI9XXX drivers). The _generic_ framebuffer code was only used to implement the Intel Multiboot framebuffer driver. This patch centralizes all the scattered code in the subsystem and adjusts the driver name to "intel_multibootfb" to make things clear. If there's ever another framebuffer driver that shares code, it can be split into multiple modules. Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
2022-08-24 19:32:15 +08:00
help
Enable Intel Multiboot framebuffer-based display driver.