Home
last modified time | relevance | path

Searched hist:"64 e58ce3ee5a8fe273a4bfb2fd6c3b66bbc5a088" (Results 1 – 2 of 2) sorted by relevance

/rk3399_ARM-atf/drivers/ti/ipc/
H A Dmailbox.c64e58ce3ee5a8fe273a4bfb2fd6c3b66bbc5a088 Thu Jun 12 06:14:32 UTC 2025 Dhruva Gole <d-gole@ti.com> fix(ti): specify allowable rcv_addr in mailbox

The ti_sci_transport_recv function had an overly restrictive check
where we enforced the rcv_addr to be always at the start of the
RX_START region in shared memory. This started failing unnecessarily
when messages started being received at a location other than the
beginning.
However, the sender might send the messages at any location within
the share memory region if it does some sort of buffer management.
In such a case, TFA needs to just make sure the message being read
is well within the allocated shared memory region. Not necessarily
at the start.

Fixes: 9347ff4561e445d4 ("feat(ti): add support for TI mailbox driver")
Change-Id: I32cf0f5e4b9fedf49e40ace0bef06b7fc4c016f6
Signed-off-by: Dhruva Gole <d-gole@ti.com>
/rk3399_ARM-atf/plat/ti/k3low/board/am62lx/include/
H A Dboard_def.h64e58ce3ee5a8fe273a4bfb2fd6c3b66bbc5a088 Thu Jun 12 06:14:32 UTC 2025 Dhruva Gole <d-gole@ti.com> fix(ti): specify allowable rcv_addr in mailbox

The ti_sci_transport_recv function had an overly restrictive check
where we enforced the rcv_addr to be always at the start of the
RX_START region in shared memory. This started failing unnecessarily
when messages started being received at a location other than the
beginning.
However, the sender might send the messages at any location within
the share memory region if it does some sort of buffer management.
In such a case, TFA needs to just make sure the message being read
is well within the allocated shared memory region. Not necessarily
at the start.

Fixes: 9347ff4561e445d4 ("feat(ti): add support for TI mailbox driver")
Change-Id: I32cf0f5e4b9fedf49e40ace0bef06b7fc4c016f6
Signed-off-by: Dhruva Gole <d-gole@ti.com>