nuttx/arch/arm/src/stm32/stm32_dma2d.c

1185 lines
33 KiB
C
Raw Normal View History

/****************************************************************************
* arch/arm/src/stm32/stm32_dma2d.c
*
* Copyright (C) 2014-2015, 2018 Marco Krahl. All rights reserved.
* Author: Marco Krahl <ocram.lhark@gmail.com>
*
* References:
* STM32F429 Technical Reference Manual
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
*
* 1. Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following disclaimer.
* 2. Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in
* the documentation and/or other materials provided with the
* distribution.
* 3. Neither the name NuttX nor the names of its contributors may be
* used to endorse or promote products derived from this software
* without specific prior written permission.
*
* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
* "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
* LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
* FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
* COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
* INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
* BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
* OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
* AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
* ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
* POSSIBILITY OF SUCH DAMAGE.
*
****************************************************************************/
/****************************************************************************
* Included Files
****************************************************************************/
#include <nuttx/config.h>
#include <stdint.h>
#include <string.h>
#include <errno.h>
#include <debug.h>
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
#include <semaphore.h>
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
#include <nuttx/irq.h>
#include <nuttx/kmalloc.h>
#include <nuttx/semaphore.h>
#include <nuttx/video/fb.h>
#include <arch/board/board.h>
#include "up_arch.h"
#include "up_internal.h"
#include "stm32.h"
#include "chip/stm32_ltdc.h"
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
#include "chip/stm32_dma2d.h"
#include "chip/stm32_ccm.h"
#include "stm32_dma2d.h"
/****************************************************************************
* Pre-processor Definitions
****************************************************************************/
/* DMA2D supported operation layer (output, foreground, background) */
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
#define DMA2D_NLAYERS 3
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/* DMA2D blender control */
#define STM32_DMA2D_CR_MODE_BLIT DMA2D_CR_MODE(0)
#define STM32_DMA2D_CR_MODE_BLITPFC DMA2D_CR_MODE(1)
#define STM32_DMA2D_CR_MODE_BLEND DMA2D_CR_MODE(2)
#define STM32_DMA2D_CR_MODE_COLOR DMA2D_CR_MODE(3)
#define STM32_DMA2D_CR_MODE_CLEAR STM32_DMA2D_CR_MODE_BLITPFC | \
STM32_DMA2D_CR_MODE_BLEND | \
STM32_DMA2D_CR_MODE_COLOR
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/* Only 8 bit per pixel overal supported */
#define DMA2D_PF_BYPP(n) ((n) / 8)
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/* CC clut size */
#define DMA2D_CLUT_SIZE STM32_DMA2D_NCLUT - 1
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/* Layer argb cmap conversion */
#define DMA2D_CLUT_ALPHA(n) ((uint32_t)(n) << 24)
#define DMA2D_CLUT_RED(n) ((uint32_t)(n) << 16)
#define DMA2D_CLUT_GREEN(n) ((uint32_t)(n) << 8)
#define DMA2D_CLUT_BLUE(n) ((uint32_t)(n) << 0)
#define DMA2D_CMAP_ALPHA(n) ((uint32_t)(n) >> 24)
#define DMA2D_CMAP_RED(n) ((uint32_t)(n) >> 16)
#define DMA2D_CMAP_GREEN(n) ((uint32_t)(n) >> 8)
#define DMA2D_CMAP_BLUE(n) ((uint32_t)(n) >> 0)
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/* Debug option */
#ifdef CONFIG_STM32_DMA2D_REGDEBUG
# define regerr lcderr
# define reginfo lcdinfo
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
#else
# define regerr(x...)
# define reginfo(x...)
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
#endif
/****************************************************************************
* Private Types
****************************************************************************/
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/* DMA2D General layer information */
struct stm32_dma2d_s
{
struct dma2d_layer_s dma2d; /* Public dma2d interface */
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
#ifdef CONFIG_FB_CMAP
uint32_t *clut; /* Color lookup table */
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
#endif
sem_t *lock; /* Ensure mutually exclusive access */
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
};
/* Interrupt handling */
struct stm32_interrupt_s
{
int irq; /* irq number */
int error; /* Interrupt error */
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
sem_t *sem; /* Semaphore for waiting for irq */
};
/* This enumeration foreground and background layer supported by the dma2d
* controller
*/
enum stm32_layer_e
{
DMA2D_LAYER_LFORE = 0, /* Foreground Layer */
DMA2D_LAYER_LBACK, /* Background Layer */
DMA2D_LAYER_LOUT, /* Output Layer */
};
/* DMA2D memory address register */
static const uintptr_t stm32_mar_layer_t[DMA2D_NLAYERS] =
{
STM32_DMA2D_FGMAR,
STM32_DMA2D_BGMAR,
STM32_DMA2D_OMAR
};
/* DMA2D offset register */
static const uintptr_t stm32_or_layer_t[DMA2D_NLAYERS] =
{
STM32_DMA2D_FGOR,
STM32_DMA2D_BGOR,
STM32_DMA2D_OOR
};
/* DMA2D pfc control register */
static const uintptr_t stm32_pfccr_layer_t[DMA2D_NLAYERS] =
{
STM32_DMA2D_FGPFCCR,
STM32_DMA2D_BGPFCCR,
STM32_DMA2D_OPFCCR
};
/* DMA2D color register */
static const uintptr_t stm32_color_layer_t[DMA2D_NLAYERS] =
{
STM32_DMA2D_FGCOLR,
STM32_DMA2D_BGCOLR,
STM32_DMA2D_OCOLR
};
/* DMA2D clut memory address register */
#ifdef CONFIG_FB_CMAP
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
static const uintptr_t stm32_cmar_layer_t[DMA2D_NLAYERS - 1] =
{
STM32_DMA2D_FGCMAR,
STM32_DMA2D_BGCMAR
};
#endif
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/****************************************************************************
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
* Private Function Prototypes
****************************************************************************/
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/* Private functions */
static void stm32_dma2d_control(uint32_t setbits, uint32_t clrbits);
static int stm32_dma2dirq(int irq, void *context, FAR void *arg);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
static int stm32_dma2d_waitforirq(void);
static int stm32_dma2d_start(void);
#ifdef CONFIG_FB_CMAP
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
static int stm32_dma2d_loadclut(uintptr_t reg);
#endif
static uint32_t stm32_dma2d_memaddress(FAR struct stm32_dma2d_overlay_s *oinfo,
uint32_t xpos, uint32_t ypos);
static uint32_t stm32_dma2d_lineoffset(FAR struct stm32_dma2d_overlay_s *oinfo,
FAR const struct fb_area_s *area);
static void stm32_dma2d_lfifo(FAR struct stm32_dma2d_overlay_s *oinfo, int lid,
uint32_t xpos, uint32_t ypos,
FAR const struct fb_area_s *area);
static void stm32_dma2d_lcolor(int lid, uint32_t argb);
static void stm32_dma2d_llnr(FAR const struct fb_area_s *area);
static int stm32_dma2d_loutpfc(uint8_t fmt);
static void stm32_dma2d_lpfc(int lid, uint32_t blendmode, uint8_t alpha,
uint8_t fmt);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/* Public functions */
#ifdef CONFIG_FB_CMAP
static int stm32_dma2d_setclut(FAR const struct fb_cmap_s *cmap);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
#endif
static int stm32_dma2d_fillcolor(FAR struct stm32_dma2d_overlay_s *oinfo,
FAR const struct fb_area_s *area,
uint32_t argb);
static int stm32_dma2d_blit(FAR struct stm32_dma2d_overlay_s *doverlay,
uint32_t destxpos, uint32_t destypos,
FAR struct stm32_dma2d_overlay_s *soverlay,
FAR const struct fb_area_s *sarea);
static int stm32_dma2d_blend(FAR struct stm32_dma2d_overlay_s *doverlay,
uint32_t destxpos, uint32_t destypos,
FAR struct stm32_dma2d_overlay_s *foverlay,
uint32_t forexpos, uint32_t foreypos,
FAR struct stm32_dma2d_overlay_s *boverlay,
FAR const struct fb_area_s *barea);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/****************************************************************************
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
* Private Data
****************************************************************************/
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/* The initialized state of the driver */
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
static bool g_initialized;
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/* Allocate clut */
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
#ifdef CONFIG_FB_CMAP
static uint32_t g_clut[STM32_DMA2D_NCLUT *
# ifdef CONFIG_FB_TRANSPARENCY
4
# else
3
# endif
/ 4 ];
#endif /* CONFIG_FB_CMAP */
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/* The DMA2D semaphore that enforces mutually exclusive access */
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
static sem_t g_lock;
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/* Semaphore for interrupt handling */
static sem_t g_semirq;
/* This structure provides irq handling */
static struct stm32_interrupt_s g_interrupt =
{
.irq = STM32_IRQ_DMA2D,
.error = OK,
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
.sem = &g_semirq
};
static struct stm32_dma2d_s g_dma2ddev =
{
.dma2d =
{
#ifdef CONFIG_FB_CMAP
.setclut = stm32_dma2d_setclut,
#endif
.fillcolor = stm32_dma2d_fillcolor,
.blit = stm32_dma2d_blit,
.blend = stm32_dma2d_blend
},
#ifdef CONFIG_FB_CMAP
.clut = g_clut,
#endif
.lock = &g_lock
};
/****************************************************************************
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
* Public Data
****************************************************************************/
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/****************************************************************************
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
* Private Functions
****************************************************************************/
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/****************************************************************************
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
* Name: stm32_dma2d_control
*
* Description:
* Change the DMA2D control register
*
* Input Parameters:
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
* setbits - The bits to set
* clrbits - The bits to clear
*
****************************************************************************/
static void stm32_dma2d_control(uint32_t setbits, uint32_t clrbits)
{
uint32_t cr;
lcdinfo("setbits=%08x, clrbits=%08x\n", setbits, clrbits);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
cr = getreg32(STM32_DMA2D_CR);
cr &= ~clrbits;
cr |= setbits;
lcdinfo("cr=%08x\n", cr);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
putreg32(cr, STM32_DMA2D_CR);
}
/****************************************************************************
* Name: stm32_dma2dirq
*
* Description:
* DMA2D interrupt handler
*
****************************************************************************/
static int stm32_dma2dirq(int irq, void *context, FAR void *arg)
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
{
int ret;
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
uint32_t regval = getreg32(STM32_DMA2D_ISR);
FAR struct stm32_interrupt_s *priv = &g_interrupt;
reginfo("irq = %d, regval = %08x\n", irq, regval);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
if (regval & DMA2D_ISR_TCIF)
{
/* Transfer complete interrupt */
/* Clear the interrupt status register */
reginfo("DMA transfer complete\n");
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
putreg32(DMA2D_IFCR_CTCIF, STM32_DMA2D_IFCR);
priv->error = OK;
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
}
#ifdef CONFIG_STM32_DMA2D_L8
else if (regval & DMA2D_ISR_CTCIF)
{
/* CLUT transfer complete interrupt */
/* Clear the interrupt status register */
reginfo("CLUT transfer complete\n");
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
putreg32(DMA2D_IFCR_CCTCIF, STM32_DMA2D_IFCR);
priv->error = OK;
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
}
#endif
else if (regval & DMA2D_ISR_TWIF)
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
{
/* Watermark transfer complete interrupt */
/* Clear the interrupt status register */
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
reginfo("Watermark transfer complete\n");
putreg32(DMA2D_IFCR_CTWIF, STM32_DMA2D_IFCR);
priv->error = OK;
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
}
else if (regval & DMA2D_ISR_TEIF)
{
/* Transfer error interrupt */
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/* Clear the interrupt status register */
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
reginfo("ERROR: transfer\n");
putreg32(DMA2D_IFCR_CTEIF, STM32_DMA2D_IFCR);
priv->error = -ECANCELED;
}
else if (regval & DMA2D_ISR_CAEIF)
{
/* CLUT access error interrupt */
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/* Clear the interrupt status register */
reginfo("ERROR: clut access\n");
putreg32(DMA2D_IFCR_CAECIF, STM32_DMA2D_IFCR);
priv->error = -ECANCELED;
}
else if (regval & DMA2D_ISR_CEIF)
{
/* Configuration error interrupt */
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/* Clear the interrupt status register */
reginfo("ERROR: configuration\n");
putreg32(DMA2D_IFCR_CCEIF, STM32_DMA2D_IFCR);
priv->error = -ECANCELED;
}
else
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
{
/* Unknown irq, should not occur */
ASSERT("Unknown interrupt error\n");
}
/* Unlock the semaphore if locked */
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
ret = nxsem_post(priv->sem);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
if (ret < 0)
{
lcderr("ERROR: nxsem_post() failed\n");
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
}
return OK;
}
/****************************************************************************
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
* Name: stm32_dma2d_waitforirq
*
* Description:
* Helper waits until the dma2d irq occurs. That means that an ongoing clut
* loading or dma transfer was completed.
* Note! The caller must use this function within a critical section.
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
*
* Returned Value:
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
* On success OK otherwise ERROR
*
****************************************************************************/
static int stm32_dma2d_waitforirq(void)
{
int ret;
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
FAR struct stm32_interrupt_s *priv = &g_interrupt;
ret = nxsem_wait(priv->sem);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
if (ret < 0)
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
{
lcderr("ERROR: nxsem_wait() failed\n");
return ret;
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
}
ret = priv->error;
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
return ret;
}
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/****************************************************************************
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
* Name: stm32_dma2d_loadclut
*
* Description:
* Starts clut loading but doesn't wait until loading is complete!
*
* Input Parameters:
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
* pfcreg - PFC control Register
*
* Returned Value:
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
* On success - OK
* On error - -EINVAL
*
****************************************************************************/
#ifdef CONFIG_STM32_DMA2D_L8
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
static int stm32_dma2d_loadclut(uintptr_t pfcreg)
{
int ret;
uint32_t regval;
/* Start clut loading */
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
regval = getreg32(pfcreg);
regval |= DMA2D_xGPFCCR_START;
reginfo("set regval=%08x\n", regval);
putreg32(regval, pfcreg);
reginfo("configured regval=%08x\n", getreg32(pfcreg));
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/* Wait until clut is finished */
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
ret = stm32_dma2d_waitforirq();
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
return ret;
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
}
#endif
/****************************************************************************
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
* Name: stm32_dma2d_start
*
* Description:
* Starts the dma transfer and waits until completed.
*
* Input Parameters:
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
* reg - Register to set the start
* startflag - The related flag to start the dma transfer
* irqflag - The interrupt enable flag in the DMA2D_CR register
*
****************************************************************************/
static int stm32_dma2d_start(void)
{
int ret;
/* Start dma transfer */
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
stm32_dma2d_control(DMA2D_CR_START, 0);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/* wait until transfer is complete */
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
ret = stm32_dma2d_waitforirq();
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
return ret;
}
/****************************************************************************
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
* Name: stm32_dma2d_memaddress
*
* Description:
* Helper to calculate the layer memory address
*
* Input Parameters:
* oinfo - Reference to overlay information
* xpos - x-Offset
* ypos - y-Offset
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
*
* Returned Value:
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
* memory address
*
****************************************************************************/
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
static uint32_t stm32_dma2d_memaddress(FAR struct stm32_dma2d_overlay_s *oinfo,
uint32_t xpos, uint32_t ypos)
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
{
uint32_t offset;
FAR struct fb_overlayinfo_s *poverlay = oinfo->oinfo;
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
offset = xpos * DMA2D_PF_BYPP(poverlay->bpp) + poverlay->stride * ypos;
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
lcdinfo("%p, offset=%d\n", ((uint32_t) poverlay->fbmem) + offset, offset);
return ((uint32_t) poverlay->fbmem) + offset;
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
}
/****************************************************************************
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
* Name: stm32_dma2d_lineoffset
*
* Description:
* Helper to calculate the layer line offset
*
* Input Parameters:
* oinfo - Reference to overlay information
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
*
* Returned Value:
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
* line offset
*
****************************************************************************/
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
static uint32_t stm32_dma2d_lineoffset(FAR struct stm32_dma2d_overlay_s *oinfo,
FAR const struct fb_area_s *area)
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
{
uint32_t loffset;
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/* offset at the end of each line in the context to the area layer */
loffset = oinfo->xres - area->w;
lcdinfo("%d\n", loffset);
return loffset;
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
}
/****************************************************************************
* Name: stm32_dma2d_lfifo
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
*
* Description:
* Set the fifo for the foreground, background and output layer
* Configures the memory address register
* Configures the line offset register
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
*
* Input Parameters:
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
* layer - Reference to the common layer state structure
*
****************************************************************************/
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
static void stm32_dma2d_lfifo(FAR struct stm32_dma2d_overlay_s *oinfo,
int lid, uint32_t xpos, uint32_t ypos,
FAR const struct fb_area_s *area)
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
{
lcdinfo("oinfo=%p, lid=%d, xpos=%d, ypos=%d, area=%p\n",
oinfo, lid, xpos, ypos, area);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
putreg32(stm32_dma2d_memaddress(oinfo, xpos, ypos), stm32_mar_layer_t[lid]);
putreg32(stm32_dma2d_lineoffset(oinfo, area), stm32_or_layer_t[lid]);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
}
/****************************************************************************
* Name: stm32_dma2d_lcolor
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
*
* Description:
* Set the color for the layer
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
*
* Input Parameters:
* lid - Layer type (output, foreground, background)
* argb - argb8888 color
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
*
****************************************************************************/
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
static void stm32_dma2d_lcolor(int lid, uint32_t argb)
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
{
lcdinfo("lid=%d, argb=%08x\n", lid, argb);
putreg32(argb, stm32_color_layer_t[lid]);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
}
/****************************************************************************
* Name: stm32_dma2d_llnr
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
*
* Description:
* Set the number of line register
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
*
* Input Parameters:
* area - Reference to area information
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
*
****************************************************************************/
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
static void stm32_dma2d_llnr(FAR const struct fb_area_s *area)
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
{
uint32_t nlrreg;
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
lcdinfo("pixel per line: %d, number of lines: %d\n", area->w, area->h);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
nlrreg = getreg32(STM32_DMA2D_NLR);
nlrreg = (DMA2D_NLR_PL(area->w) | DMA2D_NLR_NL(area->h));
putreg32(nlrreg, STM32_DMA2D_NLR);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
}
/****************************************************************************
* Name: stm32_dma2d_loutpfc
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
*
* Description:
* Set the output PFC control register
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
*
* Input Parameters:
* fmt - DMA2D pixel format
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
*
****************************************************************************/
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
static int stm32_dma2d_loutpfc(uint8_t fmt)
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
{
lcdinfo("pixel format: %d\n", fmt);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/* Set the mapped pixel format of the destination layer */
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
putreg32(DMA2D_OPFCCR_CM(fmt), STM32_DMA2D_OPFCCR);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
return OK;
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
}
/****************************************************************************
* Name: stm32_dma2d_lpfc
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
*
* Description:
* Configure foreground and background layer PFC control register
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
*
* Input Parameters:
* lid - Layer id (output, foreground, background)
* blendmode - Layer blendmode (dma2d register values)
* alpha - Transparency
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
*
****************************************************************************/
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
static void stm32_dma2d_lpfc(int lid, uint32_t blendmode, uint8_t alpha,
uint8_t fmt)
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
{
uint32_t pfccrreg;
lcdinfo("lid=%d, blendmode=%08x, alpha=%02x, fmt=%d\n", lid, blendmode, alpha,
fmt);
/* Set color format */
pfccrreg = DMA2D_xGPFCCR_CM(fmt);
#ifdef CONFIG_FB_CMAP
if (fmt == DMA2D_PF_L8)
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
{
FAR struct stm32_dma2d_s * layer = &g_dma2ddev;
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/* Load CLUT automatically */
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
pfccrreg |= DMA2D_xGPFCCR_START;
/* Set the CLUT color mode */
# ifndef CONFIG_FB_TRANSPARENCY
pfccrreg |= DMA2D_xGPFCCR_CCM;
# endif
/* Set CLUT size */
pfccrreg |= DMA2D_xGPFCCR_CS(DMA2D_CLUT_SIZE);
/* Set the CLUT memory address */
putreg32((uint32_t) layer->clut, stm32_cmar_layer_t[lid]);
/* Start async clut loading */
stm32_dma2d_loadclut(stm32_pfccr_layer_t[lid]);
}
#endif /* CONFIG_FB_CMAP */
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/* Set alpha blend mode */
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
pfccrreg |= DMA2D_xGPFCCR_AM(blendmode);
if (blendmode == STM32_DMA2D_PFCCR_AM_CONST ||
blendmode == STM32_DMA2D_PFCCR_AM_PIXEL)
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
{
/* Set alpha value */
pfccrreg |= DMA2D_xGPFCCR_ALPHA(alpha);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
}
putreg32(pfccrreg, stm32_pfccr_layer_t[lid]);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
}
/****************************************************************************
* Public Functions
****************************************************************************/
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/****************************************************************************
* Name: stm32_dma2d_setclut
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
*
* Description:
* Configure layer clut (color lookup table).
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
*
* Input Parameters:
* cmap - Color lookup table with up the 256 entries
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
*
* Returned Value:
* On success - OK
* On error - -EINVAL
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
*
****************************************************************************/
#ifdef CONFIG_FB_CMAP
static int stm32_dma2d_setclut(FAR const struct fb_cmap_s *cmap)
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
{
int n;
FAR struct stm32_dma2d_s * priv = &g_dma2ddev;
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
lcdinfo("cmap=%p\n", cmap);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
nxsem_wait(priv->lock);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
for (n = cmap->first; n < cmap->len - 1 && n < STM32_DMA2D_NCLUT; n++)
{
/* Update the layer clut entry, will be automatically loaded before
* blit operation becomes active
*/
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
# ifndef CONFIG_FB_TRANSPARENCY
uint8_t *clut = (uint8_t *)g_dma2ddev.clut;
uint16_t offset = 3 * n;
clut[offset] = cmap->blue[n];
clut[offset + 1] = cmap->green[n];
clut[offset + 2] = cmap->red[n];
reginfo("n=%d, red=%02x, green=%02x, blue=%02x\n", n, clut[offset],
clut[offset + 1], clut[offset + 2]);
# else
uint32_t *clut = g_dma2ddev.clut;
clut[n] = (uint32_t)DMA2D_CLUT_ALPHA(cmap->transp[n]) |
(uint32_t)DMA2D_CLUT_RED(cmap->red[n]) |
(uint32_t)DMA2D_CLUT_GREEN(cmap->green[n]) |
(uint32_t)DMA2D_CLUT_BLUE(cmap->blue[n]);
reginfo("n=%d, alpha=%02x, red=%02x, green=%02x, blue=%02x\n", n,
DMA2D_CLUT_ALPHA(cmap->transp[n]),
DMA2D_CLUT_RED(cmap->red[n]),
DMA2D_CLUT_GREEN(cmap->green[n]),
DMA2D_CLUT_BLUE(cmap->blue[n]));
# endif
}
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
nxsem_post(priv->lock);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
return OK;
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
}
#endif /* CONFIG_FB_CMAP */
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/****************************************************************************
* Name: stm32_dma2d_fillcolor
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
*
* Description:
* Fill the selected area of the whole overlay with a specific color.
* The caller must ensure that the area is within the entire overlay.
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
*
* Input Parameters:
* oinfo - Overlay to fill
* area - Reference to the valid area structure select the area
* argb - Color to fill the selected area. Color must be argb8888 formated.
*
* Returned Value:
* OK - On success
* -EINVAL - If one of the parameter invalid or if the size of the selected
* area outside the visible area of the layer.
* -ECANCELED - Operation cancelled, something goes wrong.
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
*
****************************************************************************/
static int stm32_dma2d_fillcolor(FAR struct stm32_dma2d_overlay_s *oinfo,
FAR const struct fb_area_s *area,
uint32_t argb)
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
{
int ret;
FAR struct stm32_dma2d_s * priv = &g_dma2ddev;
DEBUGASSERT(oinfo != NULL && oinfo->oinfo != NULL && area != NULL);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
lcdinfo("oinfo=%p, argb=%08x\n", oinfo, argb);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
#ifdef CONFIG_FB_CMAP
if (oinfo->fmt == DMA2D_PF_L8)
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
{
/* CLUT output not supported */
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
lcderr("ERROR: Returning ENOSYS, "
"output to layer with CLUT format not supported.\n");
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
return -ENOSYS;
}
#endif
nxsem_wait(priv->lock);
/* Set output pfc */
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
stm32_dma2d_loutpfc(oinfo->fmt);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/* Set output fifo */
stm32_dma2d_lfifo(oinfo, DMA2D_LAYER_LOUT, area->x, area->y, area);
/* Set the output color register */
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
stm32_dma2d_lcolor(DMA2D_LAYER_LOUT, argb);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/* Set number of lines and pixel per line */
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
stm32_dma2d_llnr(area);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/* Set register to memory transfer */
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
stm32_dma2d_control(STM32_DMA2D_CR_MODE_COLOR, STM32_DMA2D_CR_MODE_CLEAR);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/* Start DMA2D and wait until completed */
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
ret = stm32_dma2d_start();
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
if (ret != OK)
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
{
ret = -ECANCELED;
lcderr("ERROR: Returning ECANCELED\n");
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
}
nxsem_post(priv->lock);
return ret;
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
}
/****************************************************************************
* Name: stm32_dma2d_blit
*
* Description:
* Copy memory from a source overlay (defined by sarea) to destination
* overlay position (defined by destxpos and destypos).
*
* Input Parameters:
* doverlay - Valid reference to the destination overlay
* destxpos - Valid selected x position of the destination overlay
* destypos - Valid selected y position of the destination overlay
* soverlay - Valid reference to the source overlay
* sarea - Valid reference to the selected area of the source overlay
*
* Returned Value:
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
* OK - On success
* -EINVAL - If one of the parameter invalid or if the size of the selected
* source area outside the visible area of the destination layer.
* (The visible area usually represents the display size)
* -ECANCELED - Operation cancelled, something goes wrong.
*
****************************************************************************/
static int stm32_dma2d_blit(FAR struct stm32_dma2d_overlay_s *doverlay,
uint32_t destxpos, uint32_t destypos,
FAR struct stm32_dma2d_overlay_s *soverlay,
FAR const struct fb_area_s *sarea)
{
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
int ret;
uint32_t mode;
FAR struct stm32_dma2d_s * priv = &g_dma2ddev;
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
lcdinfo("doverlay=%p, destxpos=%d, destypos=%d, soverlay=%p, sarea=%p\n",
doverlay, destxpos, destypos, soverlay, sarea);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
nxsem_wait(priv->lock);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/* Set output pfc */
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
stm32_dma2d_loutpfc(doverlay->fmt);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/* Set foreground pfc */
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
stm32_dma2d_lpfc(DMA2D_LAYER_LFORE, STM32_DMA2D_PFCCR_AM_NONE, 0,
soverlay->fmt);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/* Set foreground fifo */
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
stm32_dma2d_lfifo(soverlay, DMA2D_LAYER_LFORE, sarea->x, sarea->y, sarea);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/* Set output fifo */
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
stm32_dma2d_lfifo(doverlay, DMA2D_LAYER_LOUT, destxpos, destypos, sarea);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/* Set number of lines and pixel per line */
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
stm32_dma2d_llnr(sarea);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/* Set dma2d mode for blit operation */
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
if (doverlay->fmt == soverlay->fmt)
{
/* Blit without pfc */
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
mode = STM32_DMA2D_CR_MODE_BLIT;
}
else
{
/* Blit with pfc */
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
mode = STM32_DMA2D_CR_MODE_BLITPFC;
}
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
stm32_dma2d_control(mode, STM32_DMA2D_CR_MODE_CLEAR);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/* Start DMA2D and wait until completed */
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
ret = stm32_dma2d_start();
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
if (ret != OK)
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
{
ret = -ECANCELED;
lcderr("ERROR: Returning ECANCELED\n");
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
}
nxsem_post(priv->lock);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
return ret;
}
/****************************************************************************
* Name: stm32_dma2d_blend
*
* Description:
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
* Blends the selected area from a background layer with selected position
* of the foreground layer. Copies the result to the selected position of
* the destination layer. Note! The content of the foreground and background
* layer keeps unchanged as long destination layer is unequal to the
* foreground and background layer.
*
* Input Parameters:
* doverlay - Destination overlay
* destxpos - x-Offset destination overlay
* destypos - y-Offset destination overlay
* foverlay - Foreground overlay
* forexpos - x-Offset foreground overlay
* foreypos - y-Offset foreground overlay
* boverlay - Background overlay
* barea - x-Offset, y-Offset, x-resolution and y-resolution of background
* overlay
*
* Returned Value:
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
* OK - On success
* -EINVAL - If one of the parameter invalid or if the size of the selected
* source area outside the visible area of the destination layer.
* (The visible area usually represents the display size)
* -ECANCELED - Operation cancelled, something goes wrong.
*
****************************************************************************/
static int stm32_dma2d_blend(FAR struct stm32_dma2d_overlay_s *doverlay,
uint32_t destxpos, uint32_t destypos,
FAR struct stm32_dma2d_overlay_s *foverlay,
uint32_t forexpos, uint32_t foreypos,
FAR struct stm32_dma2d_overlay_s *boverlay,
FAR const struct fb_area_s *barea)
{
int ret;
FAR struct stm32_dma2d_s * priv = &g_dma2ddev;
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
lcdinfo("doverlay=%p, destxpos=%d, destypos=%d, "
"foverlay=%p, forexpos=%d, foreypos=%d, "
"boverlay=%p, barea=%p, barea.x=%d, barea.y=%d, barea.w=%d, "
"barea.h=%d\n", doverlay, destxpos, destypos, foverlay, forexpos,
foreypos, boverlay, barea, barea->x, barea->y, barea->w, barea->h);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
#ifdef CONFIG_FB_CMAP
if (doverlay->fmt == DMA2D_PF_L8)
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
{
/* CLUT output not supported */
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
lcderr("ERROR: Returning ENOSYS, "
"output to layer with CLUT format not supported.\n");
return -ENOSYS;
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
}
#endif
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
nxsem_wait(priv->lock);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/* Set output pfc */
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
stm32_dma2d_loutpfc(doverlay->fmt);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/* Set background pfc */
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
stm32_dma2d_lpfc(DMA2D_LAYER_LBACK, boverlay->transp_mode,
boverlay->oinfo->transp.transp, boverlay->fmt);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/* Set foreground pfc */
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
stm32_dma2d_lpfc(DMA2D_LAYER_LFORE, foverlay->transp_mode,
foverlay->oinfo->transp.transp, foverlay->fmt);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/* Set background fifo */
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
stm32_dma2d_lfifo(boverlay, DMA2D_LAYER_LBACK, barea->x, barea->y, barea);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/* Set foreground fifo */
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
stm32_dma2d_lfifo(foverlay, DMA2D_LAYER_LFORE, forexpos, foreypos, barea);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/* Set output fifo */
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
stm32_dma2d_lfifo(doverlay, DMA2D_LAYER_LOUT, destxpos, destypos, barea);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/* Set number of lines and pixel per line */
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
stm32_dma2d_llnr(barea);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/* Set watermark */
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/* Enable DMA2D blender */
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
stm32_dma2d_control(STM32_DMA2D_CR_MODE_BLEND, STM32_DMA2D_CR_MODE_CLEAR);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/* Start DMA2D and wait until completed */
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
ret = stm32_dma2d_start();
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
if (ret != OK)
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
{
ret = -ECANCELED;
lcderr("ERROR: Returning ECANCELED\n");
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
}
nxsem_post(priv->lock);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
return ret;
}
/****************************************************************************
* Name: stm32_dma2dinitialize
*
* Description:
* Initialize the dma2d controller
*
* Returned Value:
* OK - On success
* An error if initializing failed.
*
****************************************************************************/
int stm32_dma2dinitialize(void)
{
lcdinfo("Initialize DMA2D driver\n");
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
if (g_initialized == false)
{
/* Abort current dma2d data transfer */
stm32_dma2duninitialize();
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
2015-10-07 21:45:15 +02:00
/* Enable dma2d is done in rcc_enableahb1, see
* arch/arm/src/stm32/stm32f40xxx_rcc.c
*/
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/* Initialize the DMA2D semaphore that enforces mutually exclusive access
* to the driver
*/
nxsem_init(&g_lock, 0, 1);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/* Initialize the semaphore for interrupt handling. This waitsem
* semaphore is used for signaling and, hence, should not have
* priority inheritance enabled.
*/
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
nxsem_init(g_interrupt.sem, 0, 0);
nxsem_setprotocol(g_interrupt.sem, SEM_PRIO_NONE);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
#ifdef CONFIG_FB_CMAP
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/* Enable dma2d transfer and clut loading interrupts only */
2015-10-07 21:45:15 +02:00
stm32_dma2d_control(DMA2D_CR_TCIE | DMA2D_CR_CTCIE, DMA2D_CR_TEIE |
DMA2D_CR_TWIE | DMA2D_CR_CAEIE | DMA2D_CR_CEIE);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
#else
/* Enable dma transfer interrupt only */
2015-10-07 21:45:15 +02:00
stm32_dma2d_control(DMA2D_CR_TCIE, DMA2D_CR_TEIE | DMA2D_CR_TWIE |
DMA2D_CR_CAEIE | DMA2D_CR_CTCIE | DMA2D_CR_CEIE);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
#endif
stm32_dma2d_control(DMA2D_CR_TCIE | DMA2D_CR_CTCIE | DMA2D_CR_TEIE |
DMA2D_CR_CAEIE | DMA2D_CR_CTCIE | DMA2D_CR_CEIE, 0);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/* Attach DMA2D interrupt vector */
(void)irq_attach(g_interrupt.irq, stm32_dma2dirq, NULL);
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/* Enable the IRQ at the NVIC */
up_enable_irq(g_interrupt.irq);
g_initialized = true;
}
return OK;
}
/****************************************************************************
* Name: stm32_dma2duninitialize
*
* Description:
* Uninitialize the dma2d controller
*
****************************************************************************/
void stm32_dma2duninitialize(void)
{
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
/* Disable DMA2D interrupts */
up_disable_irq(g_interrupt.irq);
irq_detach(g_interrupt.irq);
/* Abort current dma2d transfer */
stm32_dma2d_control(DMA2D_CR_ABORT, 0);
/* Set initialized state */
g_initialized = false;
}
/****************************************************************************
* Name: stm32_dma2ddev
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
*
* Description:
* Get a reference to the dma2d controller.
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
*
* Returned Value:
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
* On success - A valid dma2d layer reference
* On error - NULL
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
*
****************************************************************************/
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
FAR struct dma2d_layer_s *stm32_dma2ddev(void)
Defines a second interface for the dma2d controller. Controlling both LTDC and DMA2D was unpractical from the programmers view because both controllers are to different. LTDC only controls the display visibility but the DMA2D controller changes the content of the frame buffer (buffer of the layer). The main features are: 1. DMA2D interface Supports the nuttx pixel formats: - FB_FMT_RGB8 - FB_FMT_RGB24 - FB_FMT_RGB16_565 Dynamic layer allocation during runtime for the supported formats - The number of allocatable layer can be configured. Supported dma2d operation: - blit (Copy content from source to destination layer) also works with selectable area. - blend (Blend two layer and copy the result to a destination layer wich can be a third layer or one of the source layer) also works with selectable area. - fillarea (Fill a defined area of the whole layer with a specific color) As a result of that the dma2d controller can't transfer data from the core coupled memory, CCM is disabled but usable by the ccm allocator. Currently the ccm allocator is used for allocating the layer structurei only. For the dma memory (layers frame buffer) memory is allocated from heap 2 and 3. 2. LTDC interface I have changed the api for the currently non implemented operations: - blit (Copy content from a dma2d layer to an ltdc layer) also works with selectable area. - blend (Blend two dma2d layer and copy the result to a destination ltdc layer) also works with selectable area. Note! ltdc layer is a layer referenced by the ltdc interface. dma2d layer is a layer referenced by the dma2d interface. One of the most important questions for me was, How can i flexible use an ltdc layer with the dma2d interface, e.g. as source layer for dma2d operations? Get the layer id of the related dma2d layer by a special flag when using getlid() function of the ltdc interface and use the layer id to reference the specific dma2d layer by the dma2d interface. The ltdc coupled dma2d layers are predefined and can't be dynamically allocated of freed. They use the same frame buffer memory and the same color lookup table. Changes: - layer internal format of the clut table - interrupt handling for register reload (vertical vblank) instead using waiting loop - small fixes and refactoring From Marco Krahl.
2015-04-16 16:50:23 +02:00
{
return &g_dma2ddev.dma2d;
}