On 21:01, Kumar, Udit wrote: Hi Udit,
On 12/10/2024 7:27 PM, Prasanth Babu Mantena wrote:
From: Vaishnav Achath vaishnav.a@ti.com
J722S R5 SPL uses sec-proxy threads 28 and 29 for communication with TIFS. Mark these as valid threads in the driver.
Please mention doc link also,
Also is this only for R5 SPL
Yes this is only for R5, as DM is not active on dmsc, in R5 stage, use dm_tifs whose sec-proxy threads are specified in documentation. https://software-dl.ti.com/tisci/esd/latest/5_soc_doc/j722s/sec_proxy.html Will add this doc link in v2.
Thanks, Prasanth
Signed-off-by: Vaishnav Achath vaishnav.a@ti.com Signed-off-by: Prasanth Babu Mantena p-mantena@ti.com
drivers/mailbox/k3-sec-proxy.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mailbox/k3-sec-proxy.c b/drivers/mailbox/k3-sec-proxy.c index 5eafe46fd4d..6f5ad37919f 100644 --- a/drivers/mailbox/k3-sec-proxy.c +++ b/drivers/mailbox/k3-sec-proxy.c @@ -408,7 +408,7 @@ static int k3_sec_proxy_remove(struct udevice *dev) return 0; } -static const u32 am6x_valid_threads[] = { 0, 1, 4, 5, 6, 7, 8, 9, 11, 12, 13, 20, 21, 22, 23 }; +static const u32 am6x_valid_threads[] = { 0, 1, 4, 5, 6, 7, 8, 9, 11, 12, 13, 20, 21, 22, 23, 28, 29 }; static const struct k3_sec_proxy_desc am654_desc = { .thread_count = 90,