1. For the situation when the RAM space is limited and the driver's frame buffer cannot be place in RAM, add a new property 'ext-ram' in the binding, so if in device tree this property is assigned to a secondary RAM space, place the frame buffer there. The old way is to define the frame bufeer address in Kconfig, which may cause inconvenience if other data also needs to be placed in the same RAM space. 2. Update the driver to support new requirement on RT700. The IP requires a 64-byte alignment for the frame buffer stride. 3. Update the calculation of frame buffer size. If the pixel format is updated, the frame buffer size shall be updated too. Signed-off-by: Kate Wang <yumeng.wang@nxp.com>
38 lines
1.1 KiB
Plaintext
38 lines
1.1 KiB
Plaintext
# Copyright 2023,2025 NXP
|
|
# SPDX-License-Identifier: Apache-2.0
|
|
|
|
|
|
menuconfig DISPLAY_MCUX_DCNANO_LCDIF
|
|
bool "MCUX DCNano LCDIF driver"
|
|
default y
|
|
depends on DT_HAS_NXP_DCNANO_LCDIF_ENABLED
|
|
help
|
|
Enable support for mcux DCNano LCDIF driver.
|
|
|
|
|
|
if DISPLAY_MCUX_DCNANO_LCDIF
|
|
|
|
config MCUX_DCNANO_LCDIF_FB_NUM
|
|
int "Framebuffers to allocate in driver"
|
|
default 1
|
|
range 0 2
|
|
help
|
|
Number of framebuffers to allocate in DCNANO driver. Driver allocated
|
|
framebuffers are required to support partial display updates.
|
|
The driver has been validated to support 0 through 2 framebuffers.
|
|
Note that hardware will likely perform best if zero driver
|
|
framebuffers are allocated by the driver, and the application
|
|
implements double framebuffering by always calling display_write with
|
|
a buffer equal in size to the connected panel.
|
|
|
|
|
|
config MCUX_DCNANO_LCDIF_MAINTAIN_CACHE
|
|
bool "Maintain cache coherency"
|
|
default y
|
|
help
|
|
Maintain cache coherency for LCDIF framebuffer. This is generally
|
|
required, unless an external framebuffer is utilized with custom
|
|
caching settings, or caching is disabled.
|
|
|
|
endif # DISPLAY_MCUX_DCNANO_LCDIF
|