Re: qcom: add NSP firmware for nords platform

On Thu, 13 Aug 2026 at 13:26, Venkata Kota
<[email protected]> wrote:
>
>
>
> On 8/13/2026 3:20 PM, Dmitry Baryshkov wrote:
> > On Thu, Aug 13, 2026 at 10:16:57AM +0530, Venkata Kota wrote:
> >>
> >>
> >> On 8/12/2026 5:48 PM, Dmitry Baryshkov wrote:
> >>> On Wed, Aug 12, 2026 at 10:53:27AM +0530, Venkata Kota wrote:
> >>>> The following changes since commit e3c0c4b70f50ae77bea557b4a44be04413d3f3ed:
> >>>>
> >>>>     Merge branch 'robot/pr-0-1786456716' into 'main' (2026-08-11 14:02:21
> >>>> +0000)
> >>>>
> >>>> are available in the Git repository at:
> >>>>
> >>>>     https://git.codelinaro.org/clo/linux-kernel/linux-firmware.git
> >>>> dspfw-qli-nordsnsp
> >>>>
> >>>> for you to fetch changes up to a31906642ab7a73f5759e2c554fa2065ca548c5e:
> >>>>
> >>>>     qcom: add NSP firmware for nords platform (2026-08-12 10:48:05 +0530)
> >>>
> >>> Is the firmware for those instances that different? Can we please have a
> >>> single binary for all four CDSP instances?
> >>
> >> The firmware is not different. However the signature on these images is
> >> different with each image having a different SWID. This is a limitation
> >> coming from TZ at this point. There is an FR93715 on TZ, to be able to use
> >> single signature for authentication. This is TBD on future targets from TZ i
> >> believe. Till that time for our QLI meta to load this image on available
> >> NSPs different copies needs to be there.
> >
> > What is the ETA for that? Will we fix it for the lemans targets?
> >
> > Having 2 pairs of images already was questionable. Having 4 exact images
> > is a definite overkill.
>
> I do not have an ETA. This FR is on a different team and definitely is
> an overkill even for our team, I think for SECA, the next target the TZ
> team might come up with a new authentication method

Please come back with the ETA. Alternatively, please start a
discussion on linux-arm-msm@ ML.

For now, having 4 exact images for the same platform is a NAK.

-- 
With best wishes
Dmitry