Age | Commit message (Collapse) | Author |
|
IPC's Linux user space support contains a copy of a few
kernel-defined structs and definitions including the socket
address family used for rpmsg-based sockets - AF_RPMSG. This
driver is currently out-of-tree and so it's definition is
always 'one more' than the last address family defined by
the mainline kernel's socket.h.
A new address family was introduced in 5.15 (AF_MCTP), and as
a result, the AF_RPMSG macro needs to be set to 46 post 5.15
kernel. The user space header has been updated to reflect on
the kernel version and appropriately assign the value of
AF_RPMSG.
Do note that a specific value of AF_RPMSG can always be provided
through the products.mak when KERNEL_INSTALL_DIR is not set.
Signed-off-by: Sinthu Raja <sinthu.raja@ti.com>
|
|
This type is expected to work with both PG1 and PG2 versions
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
|
|
Commit 23a7eefaf8e2 ("Remoteproc: DRA7xx: Adjust entries to fix carveout
allocation failures") has split up the single DSP heap at 0x95200000 of
size 3 MB into two chunks of 2 MB and 1 MB. This erroneously used the
address 0x95300000 for the second 1 MB chunk, when it should really be
0x95400000. Fix this properly.
Fixes: 23a7eefaf8e2 ("Remoteproc: DRA7xx: Adjust entries to fix carveout allocation failures")
Signed-off-by: Suman Anna <s-anna@ti.com>
|
|
Sciclient now requires request payload to be non-NULL.
This patch updates the payload pointer to be non-NULL value
in order to be able to check the version.
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
|
|
Mark the vring device addresses as FW_RSC_ADDR_ANY, so that Linux kernel
knows it needs to update these to the actual dynamically allocated
memory locations. The virtqueue driver itself will poll for the
completion status of this update.
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
|
|
Virtqueue device address is provided by host, so poll the completion
status for this operation before proceeding. Otherwise we end up using
bad virtqueue address.
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
|
|
Mark the vring device addresses as FW_RSC_ADDR_ANY, so that Linux kernel
knows it needs to update these to the actual dynamically allocated
memory locations. The virtqueue driver itself will poll for the
completion status of this update.
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
|
|
Virtqueue device address is provided by host, so poll the completion
status for this operation before proceeding. Otherwise we end up using
bad virtqueue address.
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
|
|
AM65XX does not have an IOMMU, and currently the DEVMEM entry is used as
a work around.
But in reality the VA and PA are directly mapped and dependence on
DEVMEM to do the address translation need to be removed.
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
|
|
Mark the vring device addresses as FW_RSC_ADDR_ANY, so that Linux kernel
knows it needs to update these to the actual dynamically allocated
memory locations. The virtqueue driver itself will poll for the
completion status of this update.
Signed-off-by: Tero Kristo <t-kristo@ti.com>
|
|
Mark the vring device addresses as FW_RSC_ADDR_ANY, so that Linux kernel
knows it needs to update these to the actual dynamically allocated
memory locations. The virtqueue driver itself will poll for the
completion status of this update.
Signed-off-by: Tero Kristo <t-kristo@ti.com>
|
|
Virtqueue device address is provided by host, so poll the completion
status for this operation before proceeding. Otherwise we end up using
bad virtqueue address.
Signed-off-by: Tero Kristo <t-kristo@ti.com>
|
|
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
|
|
Previous fix to avoid the partial copy was wrong. Need to copy only the
task parameters after arg0.
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
|
|
If the linux device tree uses DMA pools for carving out memory for the
slave cores, the DMA pools uses the next power of 2 page order
fitting the requested size (eg: 6 MB gets attempted to be allocated
using 8 MB and at 8 MB alignments), and this may result in allocation
failures if the overall DMA pool size does not have enough room to
support the different RSC_CARVEOUT aligned size.
This adjustment of the entries are updated carefully to make sure the
allocation does not fail due to this alignment. The 1 MB IPC_DATA
carveout entry is placed immediately after the vdev resource so that
the image carveouts are always aligned on an even 2 MB boundary.
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
Signed-off-by: Suman Anna <s-anna@ti.com>
|
|
The MEM_IOBUFS DEVMEM entry of size 90 MB was a left-over from
OMAP4/OMAP5 code, and this was used to map a static carveout of
the same size at 0xBA300000 address into the DSP and IPU MMUs.
This region is fully owned by the Linux kernel on DRA7xx/AM57xx
SoCs, so it should not be mapped into the IPU and DSP memory space.
Drop these invalid entries from both the IPU & DSP resource tables.
Signed-off-by: Suman Anna <s-anna@ti.com>
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
|
|
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
|
|
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
|
|
Renamed local usage inside loop
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
|
|
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
|
|
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
|
|
--gcc is deprecated and will be removed in a subsequent
release. GCC compatibility is implemented through the --relaxed_ansi
option
and is the default behavior of the compiler.
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
|
|
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
|
|
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
|
|
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
|
|
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
|
|
This is to avoid uninitialized variable usage
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
|
|
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
|
|
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
|
|
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
|
|
Adding cast to UArg to indicate this is intentional
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
|
|
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
|
|
Fixes compiler warnings
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
|
|
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
|
|
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
|
|
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
|
|
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
|
|
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
|
|
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
|
|
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
|
|
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
|
|
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
|
|
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
|
|
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
|
|
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
|
|
Add appropriate handling of shared pointer which is limited to 32 bit.
But the addresses can be 64 bits for some cores.
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
|
|
arg is storing value of a pointer. Need to accomodate more than 32 bit
in 64 bit cores
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
|
|
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
|
|
Replaced UInt32 with UArg
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
|
|
With the --gcc option the current gcc compiler gives warning and hence
removed
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
|