Thread (27 messages) 27 messages, 6 authors, 14h ago

Re: [PATCH v2 0/9] remoteproc: qcom_q6v5_wcss: add native ipq9574 support

From: Alex G. <hidden>
Date: 2026-01-14 03:54:05
Also in: linux-arm-msm, linux-clk, linux-remoteproc, lkml

On Tuesday, January 13, 2026 8:28:11 AM CST Konrad Dybcio wrote:
On 1/9/26 5:33 AM, Alexandru Gagniuc wrote:
quoted
Support loading remoteproc firmware on IPQ9574 with the qcom_q6v5_wcss
driver. This firmware is usually used to run ath11k firmware and enable
wifi with chips such as QCN5024.

When submitting v1, I learned that the firmware can also be loaded by
the trustzone firmware. Since TZ is not shipped with the kernel, it
makes sense to have the option of a native init sequence, as not all
devices come with the latest TZ firmware.

Qualcomm tries to assure us that the TZ firmware will always do the
right thing (TM), but I am not fully convinced
Why else do you think it's there in the firmware? :(
A more relevant question is, why do some contributors sincerely believe that 
the TZ initialization of Q6 firmware is not a good idea for their use case?

To answer your question, I think the TZ initialization is an afterthought of 
the SoC design. I think it was only after ther the design stage that it was 
brought up that a remoteproc on AHB has out-of-band access to system memory, 
which poses security concerns to some customers. I think authentication was 
implemented in TZ to address that. I also think that in order to prevent clock 
glitching from bypassing such verification, they had to move the initialization 
sequence in TZ as well.

Alex




Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help