AM64x uses a different thread mapping that existing K3 SoCs, so update the valid thread ID list to include those used for AM64x.
Also remove the comment identifying the purpose of each thread ID. The purpose of the thread ID is specified when describing the threads in the device tree and the same ID can mean different things on different SoCs, so the comment is not useful.
Signed-off-by: Dave Gerlach d-gerlach@ti.com --- drivers/mailbox/k3-sec-proxy.c | 10 +--------- 1 file changed, 1 insertion(+), 9 deletions(-)
diff --git a/drivers/mailbox/k3-sec-proxy.c b/drivers/mailbox/k3-sec-proxy.c index ff21a08388a9..88f320515aec 100644 --- a/drivers/mailbox/k3-sec-proxy.c +++ b/drivers/mailbox/k3-sec-proxy.c @@ -409,15 +409,7 @@ static int k3_sec_proxy_remove(struct udevice *dev) return 0; }
-/* - * Thread ID #4: ROM request - * Thread ID #5: ROM response, SYSFW notify - * Thread ID #6: SYSFW request response - * Thread ID #7: SYSFW request high priority - * Thread ID #8: SYSFW request low priority - * Thread ID #9: SYSFW notify response - */ -static const u32 am6x_valid_threads[] = { 4, 5, 6, 7, 8, 9, 11, 13 }; +static const u32 am6x_valid_threads[] = { 0, 1, 4, 5, 6, 7, 8, 9, 11, 12, 13 };
static const struct k3_sec_proxy_desc am654_desc = { .thread_count = 90,