Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Jeff Johnson <quic_jjohnson@quicinc.com>
To: Gokul Sriram Palanisamy <quic_gokulsri@quicinc.com>,
	<jassisinghbrar@gmail.com>, <robh@kernel.org>,
	<krzk+dt@kernel.org>, <conor+dt@kernel.org>,
	<andersson@kernel.org>, <mathieu.poirier@linaro.org>,
	<konradybcio@kernel.org>, <quic_mmanikan@quicinc.com>,
	<linux-arm-msm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<devicetree@vger.kernel.org>, <linux-remoteproc@vger.kernel.org>,
	<dmitry.baryshkov@linaro.org>
Cc: <quic_viswanat@quicinc.com>, <quic_srichara@quicinc.com>
Subject: Re: [PATCH V3 0/8] Add new driver for WCSS secure PIL loading
Date: Fri, 24 Jan 2025 10:00:26 -0800	[thread overview]
Message-ID: <4b624830-00eb-46e8-ae5a-b822e32b2005@quicinc.com> (raw)
In-Reply-To: <20250107101647.2087358-1-quic_gokulsri@quicinc.com>

On 1/7/25 02:16, Gokul Sriram Palanisamy wrote:
> This series depends on Sricharan's tmel-qmp mailbox driver series v2 [1].
> 
> - Secure PIL is signed, split firmware images which only TrustZone (TZ)
>   can authenticate and load. Linux kernel will send a request to TZ to
>   authenticate and load the PIL images.
> 
> - When secure PIL support was added to the existing wcss PIL driver
>   earlier in [2], Bjorn suggested not to overload the existing WCSS
>   rproc driver, instead post a new driver for PAS based IPQ WCSS driver.
>   This series adds a new secure PIL driver for the same.
> 
> - Also adds changes to scm to pass metadata size as required for IPQ5332,
>   reposted from [3].
> 
> [1]
> https://patchwork.kernel.org/project/linux-arm-msm/cover/20241231054900.2144961-1-quic_srichara@quicinc.com/
> 
> [2]
> https://patchwork.kernel.org/project/linux-arm-msm/patch/1611984013-10201-3-git-send-email-gokulsri@codeaurora.org/
> 
> [3]
> https://patchwork.kernel.org/project/linux-arm-msm/patch/20240820055618.267554-6-quic_gokulsri@quicinc.com/
> 
> changes in v3:
> 	- fixed copyright years and markings based on Jeff's comments.
> 	- replaced devm_ioremap_wc() with ioremap_wc() in
> 	  wcss_sec_copy_segment().
> 	- replaced rproc_alloc() and rproc_add() with their devres
> 	  counterparts.
> 	- added mailbox call to tmelcom for secure image authentication
> 	  as required for IPQ5424. Added ipq5424 APCS comatible required. 
> 	- added changes to scm call to pass metadata size as equired for
> 	  IPQ5332.
> 
> changes in v2:
> 	- Removed dependency of this series to q6 clock removal series
> 	  as recommended by Krzysztof
> 
> Gokul Sriram Palanisamy (3):
>   dt-bindings: mailbox: qcom: Add IPQ5424 APCS compatible
>   mailbox: qcom: Add support for IPQ5424 APCS IPC
>   arm64: dts: qcom: ipq5424: add nodes to bring up q6
> 
> Manikanta Mylavarapu (4):
>   firmware: qcom_scm: ipq5332: add support to pass metadata size
>   dt-bindings: remoteproc: qcom: document hexagon based WCSS secure PIL
>   arm64: dts: qcom: ipq5332: add nodes to bringup q6
>   arm64: dts: qcom: ipq9574: add nodes to bring up q6
> 
> Vignesh Viswanathan (1):
>   remoteproc: qcom: add hexagon based WCSS secure PIL driver
> 
>  .../mailbox/qcom,apcs-kpss-global.yaml        |   1 +
>  .../remoteproc/qcom,wcss-sec-pil.yaml         | 131 ++++++
>  arch/arm64/boot/dts/qcom/ipq5332.dtsi         |  64 ++-
>  arch/arm64/boot/dts/qcom/ipq5424.dtsi         |  80 +++-
>  arch/arm64/boot/dts/qcom/ipq9574.dtsi         |  60 ++-
>  drivers/firmware/qcom/qcom_scm.c              |  13 +-
>  drivers/firmware/qcom/qcom_scm.h              |   1 +
>  drivers/mailbox/qcom-apcs-ipc-mailbox.c       |   1 +
>  drivers/remoteproc/Kconfig                    |  22 +
>  drivers/remoteproc/Makefile                   |   1 +
>  drivers/remoteproc/qcom_q6v5_wcss_sec.c       | 406 ++++++++++++++++++
>  11 files changed, 775 insertions(+), 5 deletions(-)
>  create mode 100644 Documentation/devicetree/bindings/remoteproc/qcom,wcss-sec-pil.yaml
>  create mode 100644 drivers/remoteproc/qcom_q6v5_wcss_sec.c
> 

This series is listed as a dependency of a WLAN series, and when I pull this
series using my automation I see the following kernel-doc warnings. I don't
know if these are existing issues, or issues introduced by the series, since
the automation runs kernel-doc on all of the patched files.

drivers/firmware/qcom/qcom_scm.c:302: warning: No description found for return value of 'qcom_scm_call'
drivers/firmware/qcom/qcom_scm.c:328: warning: No description found for return value of 'qcom_scm_call_atomic'
drivers/firmware/qcom/qcom_scm.c:425: warning: No description found for return value of 'qcom_scm_set_warm_boot_addr'
drivers/firmware/qcom/qcom_scm.c:438: warning: No description found for return value of 'qcom_scm_set_cold_boot_addr'
drivers/firmware/qcom/qcom_scm.c:675: warning: No description found for return value of 'qcom_scm_pas_mem_setup'
drivers/firmware/qcom/qcom_scm.c:714: warning: No description found for return value of 'qcom_scm_pas_auth_and_reset'
drivers/firmware/qcom/qcom_scm.c:750: warning: No description found for return value of 'qcom_scm_pas_shutdown'
drivers/firmware/qcom/qcom_scm.c:787: warning: No description found for return value of 'qcom_scm_pas_supported'
drivers/firmware/qcom/qcom_scm.c:892: warning: No description found for return value of 'qcom_scm_restore_sec_cfg_available'
drivers/firmware/qcom/qcom_scm.c:1070: warning: No description found for return value of 'qcom_scm_assign_mem'
drivers/firmware/qcom/qcom_scm.c:1141: warning: No description found for return value of 'qcom_scm_ocmem_lock_available'
drivers/firmware/qcom/qcom_scm.c:1158: warning: No description found for return value of 'qcom_scm_ocmem_lock'
drivers/firmware/qcom/qcom_scm.c:1182: warning: No description found for return value of 'qcom_scm_ocmem_unlock'
drivers/firmware/qcom/qcom_scm.c:1298: warning: No description found for return value of 'qcom_scm_hdcp_available'
drivers/firmware/qcom/qcom_scm.c:1323: warning: No description found for return value of 'qcom_scm_hdcp_req'
drivers/firmware/qcom/qcom_scm.c:1879: warning: No description found for return value of 'qcom_scm_is_available'
drivers/firmware/qcom/qcom_scm.h:47: warning: missing initial short description on line:
 * struct qcom_scm_desc
drivers/firmware/qcom/qcom_scm.h:57: warning: Function parameter or struct member 'svc' not described in 'qcom_scm_desc'
drivers/firmware/qcom/qcom_scm.h:57: warning: Function parameter or struct member 'cmd' not described in 'qcom_scm_desc'
drivers/firmware/qcom/qcom_scm.h:57: warning: Function parameter or struct member 'owner' not described in 'qcom_scm_desc'
drivers/firmware/qcom/qcom_scm.h:60: warning: missing initial short description on line:
 * struct qcom_scm_res
21 warnings as Errors


  parent reply	other threads:[~2025-01-24 18:00 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-07 10:16 [PATCH V3 0/8] Add new driver for WCSS secure PIL loading Gokul Sriram Palanisamy
2025-01-07 10:16 ` [PATCH V3 1/8] firmware: qcom_scm: ipq5332: add support to pass metadata size Gokul Sriram Palanisamy
2025-01-08  4:15   ` Bjorn Andersson
2025-01-07 10:16 ` [PATCH V3 2/8] dt-bindings: remoteproc: qcom: document hexagon based WCSS secure PIL Gokul Sriram Palanisamy
2025-01-07 12:21   ` Dmitry Baryshkov
     [not found]     ` <f0eef19b-8497-4e7d-bed1-882cdb8c1ab1@quicinc.com>
2025-01-08  7:34       ` Krzysztof Kozlowski
2025-01-08 11:19         ` Gokul Sriram P (QUIC)
2025-01-08 11:51           ` Krzysztof Kozlowski
     [not found]     ` <3e64b792-bfca-4b07-a13e-6deb966f3d4f@quicinc.com>
2025-01-08 10:54       ` Dmitry Baryshkov
2025-01-08 12:44         ` Gokul Sriram P (QUIC)
2025-01-07 10:16 ` [PATCH V3 3/8] dt-bindings: mailbox: qcom: Add IPQ5424 APCS compatible Gokul Sriram Palanisamy
2025-01-08  8:32   ` Krzysztof Kozlowski
2025-01-07 10:16 ` [PATCH V3 4/8] remoteproc: qcom: add hexagon based WCSS secure PIL driver Gokul Sriram Palanisamy
2025-01-08  4:09   ` Bjorn Andersson
2025-01-08  6:29     ` Sricharan Ramabadhran
2025-01-08  6:42       ` Sricharan Ramabadhran
2025-01-09 12:18     ` Gokul Sriram Palanisamy
2025-01-11 13:46       ` Kathiravan Thirumoorthy
2025-01-07 10:16 ` [PATCH V3 5/8] mailbox: qcom: Add support for IPQ5424 APCS IPC Gokul Sriram Palanisamy
2025-01-07 10:16 ` [PATCH V3 6/8] arm64: dts: qcom: ipq5332: add nodes to bringup q6 Gokul Sriram Palanisamy
2025-01-07 12:24   ` Dmitry Baryshkov
2025-01-09 13:11   ` Konrad Dybcio
2025-01-07 10:16 ` [PATCH V3 7/8] arm64: dts: qcom: ipq9574: add nodes to bring up q6 Gokul Sriram Palanisamy
2025-01-09 13:12   ` Konrad Dybcio
2025-01-15 10:05     ` Gokul Sriram P
2025-01-07 10:16 ` [PATCH V3 8/8] arm64: dts: qcom: ipq5424: " Gokul Sriram Palanisamy
2025-01-24 18:00 ` Jeff Johnson [this message]
2025-03-28  5:17   ` [PATCH V3 0/8] Add new driver for WCSS secure PIL loading Vignesh Viswanathan
  -- strict thread matches above, loose matches on Subject: below --
2025-01-07 10:13 Gokul Sriram Palanisamy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4b624830-00eb-46e8-ae5a-b822e32b2005@quicinc.com \
    --to=quic_jjohnson@quicinc.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=jassisinghbrar@gmail.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=quic_gokulsri@quicinc.com \
    --cc=quic_mmanikan@quicinc.com \
    --cc=quic_srichara@quicinc.com \
    --cc=quic_viswanat@quicinc.com \
    --cc=robh@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox