Re: [PATCH 2/6] remoteproc: qcom: Add M0 BTSS secure PIL driver

Bjorn Andersson <[email protected]> Sat, 27 Jun 2026 22:08:46 -0500

Newsgroups	org.infradead.lists.ath10k,org.kernel.vger.linux-arm-msm,org.kernel.vger.linux-block,org.kernel.vger.linux-bluetooth,org.kernel.vger.linux-devicetree,org.kernel.vger.linux-kernel,org.kernel.vger.linux-mmc,org.kernel.vger.linux-remoteproc,org.kernel.vger.linux-wireless,org.kernel.vger.netdev
Message-ID	<akCQA-bLpp31QVGV@baldur>

On Fri, Jun 26, 2026 at 01:20:25PM +0200, Konrad Dybcio wrote:
> On 6/25/26 4:10 PM, George Moussalem via B4 Relay wrote:
> > From: George Moussalem <[email protected]>
> > 
> > Add support to bring up the M0 core of the bluetooth subsystem found in
> > the IPQ5018 SoC.
> > 
> > The signed firmware loaded is authenticated by TrustZone. If successful,
> > the M0 core boots the firmware and the peripheral is taken out of reset
> > using a Secure Channel Manager call to TrustZone.
> > 
> > Signed-off-by: George Moussalem <[email protected]>
> > ---
> 
> Can this not fit inside the existing PAS driver?
> 

While the start/stop SCM calls look the same, this doesn't follow any of
the surrounding concepts. So I think this should follow the other
non-remoteproc uses of mdt_loader and scm directly instead.

Regards,
Bjorn

> Konrad