Cleaning up redefinition of mpm areas and moving to use what is defined
in the base device tree files as is.
This effectively changes to a new memory partition.
Note that this change needs a corresponding change in the dts files in
the kernel tree to adjust the mpm memory area to the new memory
partition.
The CMEM areas here are adjusted such that there is no overlap with the
mpm areas defined in the dts files in the kernel tree.
Note also the address ranges are arranged differently for K2G compared
to the other Keystone platforms.
(This is to accomodate common memory map for multiple k2g platforms)
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Cleaning up redefinition of mpm areas and moving to use what is defined
in the base device tree files as is.
This effectively changes to a new memory partition.
Note that this change needs a corresponding change in the dts files in
the kernel tree to adjust the mpm memory area to the new memory
partition.
The CMEM areas here are adjusted such that there is no overlap with the
mpm areas defined in the dts files in the kernel tree.
Also fixes issue with K2L, by removing overlapping memory area section.
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Both parameter depth and bpp are set to uiPixelWidthInBits at the current
implementation, however, the depth may not be the same as bpp for certain
pixel format such as XRGB8888. This bug was exposed by the recent DRM
driver change introducing strict error checking. To fix this problem,
add utility function uiPixelDepthInBits to derive and use depth based on
the pixel format.
Signed-off-by: Eric Ruei <e-ruei1@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Update and fixes to handle different type of memory sections in sysfs
entry or device tree.
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
cmem.dtsi splits the already defined dsp_common_mpm_area DDR memory into
a smaller MPM segment and other CMEM blocks.
The mpm_block_mem is removed and instead the original memory sections
dsp_common_mpm_area and mpm_mem in the kernel dtb are updated to reflect
On the MSMC memory, cmem.dtsi defines a sram subnode instead of the
reserved memory.
mpm MSMC areas are already captured in the kernel dtb.
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Created ti-ipc-common.inc & ti-ipc-rtos.inc to gather common definitions
Updated commmit ids for ipc-examples
Update ti-ipc-rtos to add ALT_PLATFORM examples
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Random build failures are reported on SGX driver when building for
different targets. Disable parallel compilation in SGX driver.
Signed-off-by: Anand Balagopalakrishnan <anandb@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Due to bug fixes and updates, the package version number
is being incremented to 5.1.0. The commit ID is also being
updated to reflect these changes.
Signed-off-by: Jason Reeder <jreeder@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
This helps in using this inc file from other BSP
layers which are dependent on meta-ti
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
CC is being redefined here but its not considering
the essential options to specify the sysroot as a result
this breaks on systems tied to sstate servers where the toolchain
might have had a different sysroot when built, in here
it fails to find the standard headers due to missing sysroot
options.
Deleting the extra oeconf works fine.
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
This patch adds support for importing DMABUFs as EGLImages.
This work is based on the Spec defined in
https://www.khronos.org/registry/egl/extensions/EXT/EGL_EXT_image_dma_buf_import.txt
The feature currently supports YUYV and NV12 formats
In addition, the following are supported:
* YUV full range and narrow range
* YUV color space BT709 and BT601
* YUV color space BT2020 is not supported
* Chroma siting parameters are ignored
For YUYV buffers, user needs to pass the width, height, and a 3-tuple
consisting of the dmabuf fd, pitch, and offset=0.
For YUV buffers, user needs to pass the width, height and two 3-tuples
consisting of the dmabuf fds, pitches, and offsets=0.
Please note that multiple dmabuf fds are not supported, and therefore,
for NV12,
* fd[0] must be equal to fd[1] and
* pitch[0] must be equal to pitch[1]
Signed-off-by: Anand Balagopalakrishnan <anandb@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Sam Nelson
Denys Dmytriyenko
e-ruei1@ti.com
Anand Balagopalakrishnan
Jacob Stiffler
Jason Reeder
Khem Raj